SOC2C

eClinicalWorks security & compliance

An overview of eClinicalWorks's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).

SOC 2 statusSOC 2 · Listed
FrameworksNot listed
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerNot listed

Security questions about eClinicalWorks

Is eClinicalWorks secure?
Security isn't a single yes/no, but eClinicalWorks is SOC 2 compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
Does eClinicalWorks have a bug bounty or vulnerability disclosure program?
eClinicalWorks hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@eclinicalworks.com or via a /security page.
Who are eClinicalWorks's subprocessors?
eClinicalWorks's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
Where does eClinicalWorks host or store data?
eClinicalWorks's hosting and data-residency details aren't listed on SOC2C yet. The company can add where it hosts (AWS, GCP, Azure) and which data it handles.
Where is eClinicalWorks's trust center or security page?
eClinicalWorks hasn't linked a public trust center on SOC2C yet. Its SOC 2 status and frameworks are summarized on its SOC2C profile.

See eClinicalWorks's full SOC 2 profile →