Securing integrations that exchange protected health information
Key Takeaway
For an unattended server-to-server integration that carries PHI, use the JWT Bearer Flow through a dedicated External Client App, running as a dedicated integration user. Don't use the Username-Password Flow.
Agentforce Health often exchanges protected health information (PHI) with outside systems, such as electronic medical record (EMR) systems. Every integration must protect that data in transit, at rest, and at the point where each system connects. Salesforce secures the platform itself, but the customer's design owns integration security: how each integration authenticates, what it can reach, how PHI is encrypted, and how its activity is monitored.
Who secures what
Security follows a Shared Responsibility Model, which splits the work between Salesforce and the customer.
| Responsible for | Includes | |
|---|---|---|
| Salesforce | Security of the platform | Infrastructure, patching, compliance certifications, TLS 1.2+ encryption in transit, baseline encryption at rest |
| Customer | Security on the platform | Configuration, access controls, integration security, compliance |
Salesforce's HIPAA regulatory support applies to HIPAA-eligible services covered by a Business Associate Agreement (BAA). Platform certifications reduce the compliance burden, but they don't remove it. The customer's integrations, custom objects, code, and configuration must keep the compliance posture the platform provides.