Framework crosswalk · HIPAA and SOC 2
HIPAA vs SOC 2: the requirement-level crosswalk
56 HIPAA standards and implementation specifications mapped to 29 SOC 2 Trust Services Criteria: 48 equivalent, 2 partial and 6 related. This is the pre-built, static crosswalk Shieldra's audit evidence pack uses. Neither framework substitutes for the other: a SOC 2 report does not make you HIPAA compliant, and HIPAA work does not produce a SOC 2 report.
Key takeaways
- Equivalent: The HIPAA requirement and the SOC 2 criteria address the same control objective, so one control and one body of evidence can usually support both. A SOC 2 auditor still tests the criteria on their own terms.
- Partial: They overlap, but each side asks for something the other does not. Plan for extra work on both.
- Related: Same topic, different obligation. HIPAA breach notification, for example, sets recipients and deadlines that SOC 2 incident response does not.
Administrative safeguards (164.308)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Security Management Process (45 CFR 164.308(a)(1)) | CC3.1 Specifies suitable objectives; CC3.2 Identifies and analyzes risk; CC3.4 Identifies and assesses changes that could impact internal control | Equivalent |
| Risk Analysis (45 CFR 164.308(a)(1)(ii)(A)) | CC3.2 Identifies and analyzes risk; CC3.4 Identifies and assesses changes that could impact internal control | Equivalent |
| Risk Management (45 CFR 164.308(a)(1)(ii)(B)) | CC3.4 Identifies and assesses changes that could impact internal control; CC4.2 Communicates internal control deficiencies | Equivalent |
| Sanction Policy (45 CFR 164.308(a)(1)(ii)(C)) | CC1.5 Holds individuals accountable for internal control responsibilities | Equivalent |
| Information System Activity Review (45 CFR 164.308(a)(1)(ii)(D)) | CC4.1 Selects and develops ongoing and separate evaluations; CC7.2 Monitors system components for anomalies; CC7.3 Evaluates security events | Equivalent |
| Assigned Security Responsibility (45 CFR 164.308(a)(2)) | CC1.3 Management establishes structure, reporting lines, and authority; CC1.4 Demonstrates commitment to competence | Equivalent |
| Workforce Security (45 CFR 164.308(a)(3)) | CC1.4 Demonstrates commitment to competence; CC1.5 Holds individuals accountable for internal control responsibilities | Equivalent |
| Authorization and/or Supervision (45 CFR 164.308(a)(3)(ii)(A)) | CC1.4 Demonstrates commitment to competence; CC1.5 Holds individuals accountable for internal control responsibilities; CC6.2 Registers and authorizes new users | Equivalent |
| Workforce Clearance Procedure (45 CFR 164.308(a)(3)(ii)(B)) | CC1.4 Demonstrates commitment to competence | Equivalent |
| Termination Procedures (45 CFR 164.308(a)(3)(ii)(C)) | CC1.4 Demonstrates commitment to competence; CC6.2 Registers and authorizes new users | Equivalent |
| Information Access Management (45 CFR 164.308(a)(4)) | CC6.1 Implements logical access security measures; CC6.2 Registers and authorizes new users; CC6.3 Authorizes, modifies, and removes access | Equivalent |
| Access Authorization (45 CFR 164.308(a)(4)(ii)(B)) | CC6.1 Implements logical access security measures; CC6.2 Registers and authorizes new users | Equivalent |
| Access Establishment and Modification (45 CFR 164.308(a)(4)(ii)(C)) | CC6.2 Registers and authorizes new users; CC6.3 Authorizes, modifies, and removes access | Equivalent |
| Security Awareness and Training (45 CFR 164.308(a)(5)) | CC1.4 Demonstrates commitment to competence; CC2.2 Communicates internally about system responsibilities | Equivalent |
| Security Reminders (45 CFR 164.308(a)(5)(ii)(A)) | CC2.2 Communicates internally about system responsibilities | Equivalent |
| Protection from Malicious Software (45 CFR 164.308(a)(5)(ii)(B)) | CC6.8 Prevents and detects unauthorized or malicious software; CC7.1 Detects changes to configurations and vulnerabilities | Equivalent |
| Log-in Monitoring (45 CFR 164.308(a)(5)(ii)(C)) | CC6.1 Implements logical access security measures; CC7.2 Monitors system components for anomalies | Equivalent |
| Password Management (45 CFR 164.308(a)(5)(ii)(D)) | CC6.1 Implements logical access security measures | Equivalent |
| Security Incident Procedures (45 CFR 164.308(a)(6)) | CC7.3 Evaluates security events; CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Equivalent |
| Response and Reporting (45 CFR 164.308(a)(6)(ii)) | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Equivalent |
| Contingency Plan (45 CFR 164.308(a)(7)) | A1.2 Implements backup, recovery, and continuity procedures; A1.3 Tests recovery plan procedures | Equivalent |
| Data Backup Plan (45 CFR 164.308(a)(7)(ii)(A)) | A1.2 Implements backup, recovery, and continuity procedures | Equivalent |
| Disaster Recovery Plan (45 CFR 164.308(a)(7)(ii)(B)) | A1.2 Implements backup, recovery, and continuity procedures; A1.3 Tests recovery plan procedures | Equivalent |
| Emergency Mode Operation Plan (45 CFR 164.308(a)(7)(ii)(C)) | A1.3 Tests recovery plan procedures | Equivalent |
| Testing and Revision Procedures (45 CFR 164.308(a)(7)(ii)(D)) | A1.3 Tests recovery plan procedures | Equivalent |
| Evaluation (45 CFR 164.308(a)(8)) | CC4.1 Selects and develops ongoing and separate evaluations; CC4.2 Communicates internal control deficiencies | Equivalent |
| Business Associate Contracts and Other Arrangements (45 CFR 164.308(b)(1)) | CC9.2 Assesses and manages risks associated with vendors and business partners | Equivalent |
Physical safeguards (164.310)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Facility Access Controls (45 CFR 164.310(a)(1)) | CC6.4 Restricts physical access | Equivalent |
| Workstation Use (45 CFR 164.310(b)) | CC6.4 Restricts physical access; CC6.5 Discontinues and securely disposes of physical assets | Equivalent |
| Workstation Security (45 CFR 164.310(c)) | CC6.4 Restricts physical access | Equivalent |
| Device and Media Controls (45 CFR 164.310(d)(1)) | CC6.4 Restricts physical access; CC6.5 Discontinues and securely disposes of physical assets | Equivalent |
| Disposal (45 CFR 164.310(d)(2)(i)) | CC6.5 Discontinues and securely disposes of physical assets | Equivalent |
| Media Re-use (45 CFR 164.310(d)(2)(ii)) | CC6.5 Discontinues and securely disposes of physical assets | Equivalent |
Technical safeguards (164.312)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Access Control (45 CFR 164.312(a)(1)) | CC6.1 Implements logical access security measures; CC6.2 Registers and authorizes new users; CC6.3 Authorizes, modifies, and removes access | Equivalent |
| Unique User Identification (45 CFR 164.312(a)(2)(i)) | CC6.1 Implements logical access security measures | Equivalent |
| Emergency Access Procedure (45 CFR 164.312(a)(2)(ii)) | A1.3 Tests recovery plan procedures; CC6.1 Implements logical access security measures | Equivalent |
| Automatic Logoff (45 CFR 164.312(a)(2)(iii)) | CC6.1 Implements logical access security measures | Equivalent |
| Encryption and Decryption (at rest) (45 CFR 164.312(a)(2)(iv)) | CC6.7 Restricts and protects data transmission | Equivalent |
| Audit Controls (45 CFR 164.312(b)) | CC7.2 Monitors system components for anomalies; CC7.3 Evaluates security events | Equivalent |
| Integrity (45 CFR 164.312(c)(1)) | CC6.7 Restricts and protects data transmission; CC7.1 Detects changes to configurations and vulnerabilities | Equivalent |
| Mechanism to Authenticate ePHI (45 CFR 164.312(c)(2)) | CC7.1 Detects changes to configurations and vulnerabilities | Equivalent |
| Person or Entity Authentication (45 CFR 164.312(d)) | CC6.1 Implements logical access security measures | Equivalent |
| Transmission Security (45 CFR 164.312(e)(1)) | CC6.7 Restricts and protects data transmission | Equivalent |
| Integrity Controls (45 CFR 164.312(e)(2)(i)) | CC6.7 Restricts and protects data transmission; CC7.1 Detects changes to configurations and vulnerabilities | Equivalent |
| Encryption (in transit) (45 CFR 164.312(e)(2)(ii)) | CC6.7 Restricts and protects data transmission | Equivalent |
Organizational requirements (164.314)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Business Associate Contracts (45 CFR 164.314(a)(1)) | CC9.2 Assesses and manages risks associated with vendors and business partners | Equivalent |
Policies, procedures and documentation (164.316)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Policies and Procedures (45 CFR 164.316(a)) | CC2.2 Communicates internally about system responsibilities; CC2.3 Communicates externally about system responsibilities | Equivalent |
| Documentation (45 CFR 164.316(b)(1)) | CC2.2 Communicates internally about system responsibilities; CC2.3 Communicates externally about system responsibilities | Equivalent |
Breach Notification Rule (164.400-414)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Notification to Individuals (45 CFR 164.404). Covered-entity duty. A business associate notifies the covered entity under 164.410 instead. | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Related |
| Notification to the Media (45 CFR 164.406). Covered-entity duty. A business associate notifies the covered entity under 164.410 instead. | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Related |
| Notification to the Secretary (45 CFR 164.408). Covered-entity duty. A business associate notifies the covered entity under 164.410 instead. | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Related |
| Notification by a Business Associate (45 CFR 164.410) | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents; CC2.3 Communicates externally about system responsibilities; CC9.2 Assesses and manages risks associated with vendors and business partners | Related |
| Breach Documentation and Burden of Proof (45 CFR 164.414) | CC7.4 Responds to identified security incidents; CC7.5 Recovers from identified security incidents | Related |
Business associate obligations (164.502, 164.504, 164.514)
| HIPAA requirement | SOC 2 criteria | Mapping |
|---|---|---|
| Business Associate Permitted Uses and Disclosures (45 CFR 164.502(a)(3)). Business associate duty, owed under your BAAs. | C1.1 Identifies and maintains confidential information; P4.1 Uses personal information for intended purposes | Partial |
| Return or Destruction of PHI at Contract End (45 CFR 164.504(e)(2)(ii)(J)). Business associate duty, owed under your BAAs. | C1.2 Disposes of confidential information; P4.3 Disposes of personal information securely | Partial |
| De-identification of PHI (45 CFR 164.514(b)). Business associate duty, owed under your BAAs. | C1.1 Identifies and maintains confidential information; P4.1 Uses personal information for intended purposes | Related |
Which SOC 2 criteria have no HIPAA counterpart?
26 of the 55 criteria in Shieldra’s SOC 2 catalog are not mapped from any HIPAA requirement in this crosswalk. A HIPAA program gives you no head start on these. Availability, Processing Integrity, Confidentiality and Privacy criteria only matter if they are in your SOC 2 scope.
- CC1.1 Demonstrates commitment to integrity and ethical values (Control Environment)
- CC1.2 Board exercises oversight of internal control (Control Environment)
- CC2.1 Obtains or generates quality information (Communication & Information)
- CC3.3 Considers the potential for fraud (Risk Assessment)
- CC5.1 Selects and develops control activities (Control Activities)
- CC5.2 Selects and develops general control activities over technology (Control Activities)
- CC5.3 Deploys control activities through policies and procedures (Control Activities)
- CC6.6 Protects against external threats (Logical & Physical Access)
- CC8.1 Authorizes, designs, tests, and implements changes (Change Management)
- CC9.1 Identifies, selects, and develops risk mitigation activities (Risk Mitigation)
- A1.1 Maintains, monitors, and evaluates current processing capacity (Availability)
- PI1.1 Obtains or generates accurate and complete system input (Processing Integrity)
- PI1.2 Processes inputs completely, accurately, and timely (Processing Integrity)
- PI1.3 Produces complete and accurate output (Processing Integrity)
- PI1.4 Stores inputs and processed outputs completely and accurately (Processing Integrity)
- PI1.5 Restricts modification of stored data (Processing Integrity)
- P1.1 Provides notice of privacy practices (Privacy)
- P2.1 Obtains consent for collection and use of personal information (Privacy)
- P3.1 Collects personal information consistent with objectives (Privacy)
- P4.2 Retains personal information per retention policy (Privacy)
- P5.1 Provides access to personal information (Privacy)
- P5.2 Allows correction of personal information (Privacy)
- P6.1 Discloses personal information to third parties only as authorized (Privacy)
- P6.2 Creates and retains disclosure records (Privacy)
- P7.1 Maintains data quality (Privacy)
- P8.1 Monitors and enforces compliance with privacy policies (Privacy)
What this crosswalk does not tell you
- A mapping is not coverage. SOC 2 CC9.2 asks you to manage vendor and business-partner risk; it does not require a business associate agreement with the content 45 CFR 164.504(e) prescribes.
- The table lists the HIPAA standards that have a SOC 2 counterpart. Privacy Rule duties only covered entities owe, such as the notice of privacy practices and individual access and amendment, have no counterpart and are not listed.
- Rows marked as covered-entity duties are out of scope for a business associate. The readiness score leaves them out for business associates, using the same rules.
- The crosswalk is general information, not legal advice or an audit opinion. Your SOC 2 auditor decides what evidence satisfies each criterion.
Frequently asked questions
Does HIPAA compliance cover SOC 2?
No. 48 of the 56 rows in this crosswalk are equivalent mappings, so much of the Security Rule work produces evidence a SOC 2 auditor can test. But SOC 2 is an attestation report issued by an independent CPA firm, and 26 of the 55 criteria in Shieldra's SOC 2 catalog have no HIPAA counterpart here, including change management (CC8.1).
Does a SOC 2 report make us HIPAA compliant?
No. SOC 2 does not require a HIPAA risk analysis, BAAs with the content HIPAA prescribes, or breach notification to covered entities on HIPAA terms. Hospital and payer security reviews of a business associate often ask for that HIPAA evidence alongside, or instead of, a SOC 2 report.
What do equivalent, partial and related mean?
Equivalent: The HIPAA requirement and the SOC 2 criteria address the same control objective, so one control and one body of evidence can usually support both. A SOC 2 auditor still tests the criteria on their own terms. Partial: They overlap, but each side asks for something the other does not. Plan for extra work on both. Related: Same topic, different obligation. HIPAA breach notification, for example, sets recipients and deadlines that SOC 2 incident response does not.
How does Shieldra use this crosswalk?
It is a pre-built, static table. The audit evidence pack shows, for each HIPAA control, the SOC 2 criteria it relates to. The readiness score does not read this table. It reuses evidence through the curated requirement-to-requirement mappings in your workspace, and only for a criterion that has no direct evidence of its own. Only a high-confidence equivalent mapping can carry a compliant status across; a partial or related mapping never counts as more than partial. The methodology page explains the scoring.