TheArtOfService
HIPAA Security RulePCI DSS 4.0

HIPAA Security Rule covers 16.9% of PCI DSS 4.0

42 of the 249 controls in PCI DSS 4.0 are already satisfied by evidence you collected for HIPAA Security Rule. 207 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.

16.9%
of the target already covered
42
controls evidenced
207
genuine gaps
208
claims rejected in review

What this leaves you to do

PCI DSS 4.0 has 249 controls. Holding HIPAA Security Rule already evidences 42 of them, so the work in front of you is 207 controls, not 249, which is 83% 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 PCI DSS 4.0 your HIPAA Security Rule 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.

269 candidate mappings were examined and 208 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.

Req 7: Restrict Access by Need to Know6 of 12 evidenced, 6 to do
Req 8: Identify and Authenticate Users10 of 29 evidenced, 19 to do
Req 9: Restrict Physical Access8 of 26 evidenced, 18 to do
Req 10: Logging and Monitoring6 of 27 evidenced, 21 to do
Req 12: Information Security Policies8 of 37 evidenced, 29 to do
Req 4: Protect Cardholder Data in Transit1 of 6 evidenced, 5 to do
Req 5: Anti-Malware2 of 13 evidenced, 11 to do
Req 3: Protect Stored Account Data1 of 29 evidenced, 28 to do
Req 1: Network Security Controls0 of 19 evidenced, 19 to do
Req 11: Test Security Regularly0 of 21 evidenced, 21 to do
Req 2: Secure Configurations0 of 11 evidenced, 11 to do
Req 6: Secure Systems and Software0 of 19 evidenced, 19 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.

164.312(b)10.2.1argued against and upheld
Audit logs enabled on system components

Mechanisms that record activity in systems containing protected data enable audit logs.

164.312(b)10.2.1.1argued against and upheld
Log all user access to CHD

Recording and examining activity in systems holding protected data logs user access to it.

164.312(b)10.2.2argued against and upheld
Audit log content

Hardware, software and procedural recording mechanisms determine the content captured.

164.308(a)(1)(ii)(D)10.4.1argued against and upheld
Daily log review for critical systems

Regularly reviewing audit logs and access reports is the log review this requirement sets.

164.308(a)(1)(ii)(D)10.4.2argued against and upheld
Periodic review of other system component logs

The activity review covers access reports and incident tracking across systems.

164.308(a)(1)(ii)(D)10.4.3argued against and upheld
Exceptions and anomalies addressed

Reviewing security incident tracking reports is how exceptions and anomalies are addressed.

164.316(a)12.1.1argued against and upheld
An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners

Implementing reasonable and appropriate policies and procedures is the overall security policy.

164.316(b)(2)(iii)12.1.2argued against and upheld
The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment

Reviewing documentation periodically and updating in response to changes is the annual policy review.

Claims that did not hold

208 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.

164.308(a)(1)(ii)(D)10.2.1.1
Log all user access to CHD

retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.

Claimed at medium confidence before it was rejected.

164.312(a)(1)10.2.1.1
Log all user access to CHD

retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.

Claimed at medium confidence before it was rejected.

164.312(b)10.2.1.7
Log creation and deletion of system level objects

Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.

Claimed at high confidence before it was rejected.

164.308(a)(6)(ii)10.4.3
Exceptions and anomalies addressed

Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.

Claimed at high confidence before it was rejected.

164.308(a)(1)(ii)(D)10.6.3
Time settings protected

retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.

Claimed at medium confidence before it was rejected.

164.312(b)10.6.3
Time settings protected

Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.

Claimed at high confidence before it was rejected.

164.312(a)(1)10.6.3
Time settings protected

retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.

Claimed at medium confidence before it was rejected.

164.308(a)(6)(ii)10.7.3
Failure response timeline

Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.

Claimed at high confidence before it was rejected.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk