SOC 2HIPAA Security Rule

SOC 2 covers 59.7% of HIPAA Security Rule

40 of the 67 controls in HIPAA Security Rule are already satisfied by evidence you collected for SOC 2. 27 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

59.7%

of the target already covered

controls evidenced

genuine gaps

150

claims rejected in review

What this leaves you to do

HIPAA Security Rule has 67 controls. Holding SOC 2 already evidences 40 of them, so the work in front of you is 27 controls, not 67, which is 40% of the standard rather than all of it.

That is the whole claim. We do not know your hourly rate, how long a control takes you, or how many people you have, so there is no figure here in dollars or weeks. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.

This number is directional. It says how much of HIPAA Security Rule your SOC 2 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

218 candidate mappings were examined and 152 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

Administrative23 of 32 evidenced, 9 to do

Policies and Procedures3 of 5 evidenced, 2 to do

Physical7 of 12 evidenced, 5 to do

Technical6 of 12 evidenced, 6 to do

Organizational1 of 6 evidenced, 5 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

SOC2-CC5.1164.308(a)(1)(i)argued against and upheld

Security Management Process (Standard)

Control activities selected and developed to mitigate risk are the security management process.

SOC2-CC3.2164.308(a)(1)(ii)(A)argued against and upheld

Risk Analysis (Required)

Identifying risks to objectives and analyzing them is the risk analysis an assessor tests.

SOC2-CC5.1164.308(a)(1)(ii)(B)argued against and upheld

Risk Management (Required)

Control activities that reduce risk to acceptable levels are the required security measures.

SOC2-CC1.5164.308(a)(1)(ii)(C)argued against and upheld

Sanction Policy (Required)

Holding individuals accountable for control responsibilities includes disciplinary action for non compliance.

SOC2-CC7.2164.308(a)(1)(ii)(D)argued against and upheld

Information System Activity Review (Required)

Monitoring system components and analyzing anomalies is the activity review of logs and reports.

SOC2-CC1.3164.308(a)(2)argued against and upheld

Assigned Security Responsibility (Standard)

Establishing structures, reporting lines and authorities assigns the security responsibility.

SOC2-CC6.3164.308(a)(3)(i)argued against and upheld

Workforce Security (Standard)

Access is authorized, modified or removed by role so unauthorized persons are prevented.

SOC2-CC6.2164.308(a)(3)(ii)(A)argued against and upheld

Authorization and Supervision (Addressable)

Users are registered and authorized before system access is granted.

Claims that did not hold

150 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.

SOC2-CC5.1164.306