164.308(a)(1)(ii)(A) Risk Analysis (Required)
Conduct accurate and thorough assessment of potential risks and vulnerabilities to ePHI. NIST recommends the nine-step risk analysis methodology and integration with NIST SP 800-30 and the NIST RMF.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Periodic refresh schedule · Policy repository / GRC workspace
- Evidence of ePHI scoping · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Documented risk analysis report · Policy repository / GRC workspace
- Risk analysis methodology aligned to NIST SP 800-30 · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Risk analysis is checklist-style, not threat-based
- Not refreshed after material changes
- No integration with enterprise risk register
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(1)(i) Security Management Process (Standard) · 164.308(a)(1)(ii)(B) Risk Management (Required)