Azure Security BenchmarkHIPAA Security Rule

Azure Security Benchmark covers 38.8% of HIPAA Security Rule

26 of the 67 controls in HIPAA Security Rule are already satisfied by evidence you collected for Azure Security Benchmark. 41 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.

38.8%
of the target already covered
26
controls evidenced
41
genuine gaps
0
claims rejected in review

This number is directional. It says how much of HIPAA Security Rule your Azure Security Benchmark 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.

70 candidate mappings were examined and 0 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.

Technical8 of 12 evidenced, 4 to do
Administrative18 of 32 evidenced, 14 to do
Physical0 of 12 evidenced, 12 to do
Organizational0 of 6 evidenced, 6 to do
Policies and Procedures0 of 5 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.

ASB v3 PV-6164.308(a)(1)(ii)(B)argued against and upheld
Risk Management (Required)

Risk prioritised remediation reduces identified risks to an acceptable level.

ASB v3 LT-1164.308(a)(1)(ii)(D)argued against and upheld
Information System Activity Review (Required)

Analytics rules extracting alerts from log data is the regular activity review required.

ASB v3 LT-5164.308(a)(1)(ii)(D)argued against and upheld
Information System Activity Review (Required)

SIEM aggregation with analyst workflow is where logs and access reports are reviewed.

ASB v3 GS-1164.308(a)(2)argued against and upheld
Assigned Security Responsibility (Standard)

Naming and documenting security accountability with leadership endorsement is this standard.

ASB v3 PA-7164.308(a)(3)(i)argued against and upheld
Workforce Security (Standard)

Role based access ensures workforce members hold only the access their role needs.

ASB v3 PA-3164.308(a)(3)(i)argued against and upheld
Workforce Security (Standard)

Joiner mover leaver handling prevents access by those who should not have it.

ASB v3 PA-2164.308(a)(3)(ii)(A)argued against and upheld
Authorization and Supervision (Addressable)

Approval workflows for time bound elevation are the authorisation and supervision mechanism.

ASB v3 PA-3164.308(a)(3)(ii)(C)argued against and upheld
Termination Procedures (Addressable)

The leaver process terminates access when employment ends.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

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