What
Independent audit of nist/hipaa-filter.json — verify that each HIPAA Security Rule implementation specification correctly maps to the right NIST 800-53 controls.
Why
This filter was created by an AI interpreting SP 800-66 Rev. 2 and the NIST CPRT tool. It needs review by someone who actually knows HIPAA — a compliance officer, a healthcare attorney, or an engineer who's been through a HIPAA audit.
What to audit
The file is nist/hipaa-filter.json (~60 lines). For each mapping:
- Is the HIPAA spec ID correct? (164.312(a)(1), 164.308(a)(4), etc.)
- Are the right 800-53 controls mapped?
- Are required vs addressable specs handled correctly?
- Are any mappings missing from SP 800-66r2?
How to contribute
- Read
nist/hipaa-filter.json
- Cross-reference against SP 800-66 Rev. 2 and NIST CPRT
- Open a PR with corrections, or comment with findings
- Test:
bin/comply-db init --framework hipaa
Current state
52 HIPAA specs → 50 unique 800-53 controls. Source: SP 800-66r2 + NIST CPRT.
Who should review
- HIPAA compliance officers or auditors
- Healthcare attorneys familiar with the Security Rule
- Engineers who've completed a HIPAA audit
What
Independent audit of
nist/hipaa-filter.json— verify that each HIPAA Security Rule implementation specification correctly maps to the right NIST 800-53 controls.Why
This filter was created by an AI interpreting SP 800-66 Rev. 2 and the NIST CPRT tool. It needs review by someone who actually knows HIPAA — a compliance officer, a healthcare attorney, or an engineer who's been through a HIPAA audit.
What to audit
The file is
nist/hipaa-filter.json(~60 lines). For each mapping:How to contribute
nist/hipaa-filter.jsonbin/comply-db init --framework hipaaCurrent state
52 HIPAA specs → 50 unique 800-53 controls. Source: SP 800-66r2 + NIST CPRT.
Who should review