APRA CPS 234 covers 19.4% of HIPAA Security Rule
13 of the 67 controls in HIPAA Security Rule are already satisfied by evidence you collected for APRA CPS 234. 54 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.
This number is directional. It says how much of HIPAA Security Rule your APRA CPS 234 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.
31 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.
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.
Entity must maintain a security capability sized to the threats facing its information assets.
Controls must be implemented in proportion to threats, asset sensitivity and incident consequences.
Controls sized to threats and consequences are the preventive and corrective measures required.
Robust mechanisms must detect information security incidents and respond in a timely way.
Security measures must be implemented in a timely way and sized to the risk identified.
Security roles and responsibilities must be clearly defined including senior accountability.
Response plans must be maintained for every information security incident that could plausibly occur.
Plans must set out mechanisms for every incident stage plus escalation and reporting.
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