Requirement
Perform a periodic technical and non-technical evaluation of the extent to which the entity's security policies and procedures meet the requirements of the Security Rule.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
evaluationassessmentauditreviewauditorassess
Required element 2 — any one of
periodicannualsecurity rulepolicies and proceduresperiodically
Supporting terms — specificity signals
documentedgapremediationthird partyafter significant change
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no periodic evaluation
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.8.34 | Protection of information systems during audit testing | audit |
| NIST CSF 2.0 | ID.IM-01 | Improvements are identified from evaluations | audit |
| CCPA/CPRA | Regs (cybersecurity audits) | Annual independent cybersecurity audit | audit |
| SOC 2 | CC4.1 | Ongoing and separate evaluations | audit |
| SOC 2 | CC4.2 | Communication of deficiencies | audit |
| NDPA 2023 | GAID Art.10 | Compliance audit returns and records of processing (GAID 2025) | audit |