164.308(a)(8) Evaluation (Standard)
Perform periodic technical and nontechnical evaluation. NIST recommends combining policy review, control testing, vulnerability assessments, and audits to evaluate ongoing compliance.
Source: HIPAA Security Rule, 164.308(a)(8). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open HIPAA Security Rule in the compliance library.
Applies to covered entities and business associates. An addressable specification can be met by a documented, reasonable alternative.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Annual evaluation report · Document repository
- Internal audit reports · Policy repository / GRC workspace
- Vulnerability assessment results · Vulnerability scanner / patch tooling
- Policy compliance reviews · Policy repository / GRC workspace
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Evaluation skipped after major changes
- Evaluation limited to technical scans
- Findings unremediated
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)(7)(ii)(E) Applications and Data Criticality Analysis (Addressable) · 164.308(b)(1) Business Associate Contracts and Other Arrangements (Standard)