← HIPAA · Administrative safeguards
164.308(a)(1)(ii)(A) — Risk analysis (R)
Requirement
Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of electronic protected health information held by the entity.
What the engine looks for
For the control to count as covered, every group below must be satisfied by an affirmative statement, not a plan, a hedge or a denial. A term ending in … matches any word it begins. Supporting terms don't change the verdict. They raise confidence, and they separate a policy that names a mechanism from one that only gestures at a category.
Finding any of these outranks coverage: a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC3.1 | Objectives and risk identification | risk-assessment |
| SOC 2 | CC3.2 | Risk analysis and response | risk-assessment |
| SOC 2 | CC3.3 | Fraud risk | risk-assessment |
| PCI DSS 4.0.1 | 12.3.1 | Targeted risk analyses | risk-assessment |
| GLBA | 314.4(b) | Written risk assessment | risk-assessment |
| NIST CSF 2.0 | ID.RA-05 | Risks are prioritised to inform response | risk-assessment |
| GDPR | Art.35 | Data protection impact assessment | risk-assessment |
| GDPR | Art.36 | Prior consultation with the supervisory authority | risk-assessment |