HIPAA Security Evaluation Standard (45 CFR 164.308(a)(8))
Required standard for periodic technical and non-technical evaluation in response to environmental or operational changes affecting the security of ePHI.
Primary source
45 CFR 164.308(a)(8) — eCFR →https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.308#p-164.308(a)(8)
Verified May 23, 2026 · This is the authoritative regulator URL. The summary below is a research aid; the linked source controls.
45 CFR 164.308(a)(8)(8)) requires a covered entity to perform a periodic technical and non-technical evaluation, initially based on standards in 164.308 and subsequently in response to environmental or operational changes affecting the security of ePHI, that establishes the extent to which an entity's security policies and procedures meet the requirements of subpart C.
This standard is separate from — and complementary to — the risk analysis at 164.308(a)(1)(ii)(A). The risk analysis identifies what could go wrong; the evaluation verifies that the safeguards actually implemented still match the rule and current operations.
Triggers for re-evaluation: adoption of a new ePHI-bearing technology, organizational restructuring, new service offerings, vendor changes, results of a security incident investigation, and the cyclical annual review. The evaluation can be internal or external. OCR has cited the absence of a periodic evaluation in audit findings — many practices conflate it with the risk analysis and end up with neither documented separately.
Output of the evaluation feeds back into the risk analysis and the remediation/risk-management activity at 164.308(a)(1)(ii)(B).
Use this in your workspace
D3rx assembles the documentation linked to this regulation, walks the practical decisions in plain English, and stores the artifacts against the .gov sources cited above. It is an administrative research aid, not a substitute for counsel.
Related regulations
D3rx is a healthcare-billing and compliance research aid maintained by D3rx Inc. Articles are drafted by an LLM (Anthropic Claude) against primary HHS, OCR, CMS, eCFR, NIST, and state-regulator publications, and reviewed for restraint and source fidelity by the D3rx team.
Reviewer status: a named credentialed reviewer (CHC, CHPC, or healthcare attorney) is being engaged. Until that engagement is finalized, this page does not claim credentialed review.
Related across the archive
- RegulationHIPAA Administrative Safeguards (45 CFR 164.308)Nine standards covering security management, workforce security, training, contingency planning, incident procedures, evaluation, and business associate contracts.
- RegulationHIPAA Security Risk Analysis Standard (45 CFR 164.308(a)(1)(ii)(A))Required implementation specification: conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI.
- RegulationHIPAA Security Rule: General Rules (45 CFR 164.306)Required objectives — confidentiality, integrity, and availability of ePHI — plus the flexibility provisions that govern how covered entities select and implement specific safeguards.
- RegulationHIPAA Security Access Control (45 CFR 164.312(a))Technical policies and procedures for systems containing ePHI to allow access only to those granted access rights, with required specifications for unique user identification and emergency access.
- ComplianceHIPAA Contingency Plan Template — 45 CFR § 164.308(a)(7)2026 HIPAA contingency plan template — 45 CFR § 164.308(a)(7) data backup, DRP, emergency mode, testing, and applications/data criticality analysis.
- SRAChange Healthcare Ransomware: What Small Practices Took AwayThe February 2024 Change Healthcare cyberattack, what HHS and UnitedHealth Group disclosed, and the small-practice lessons about clearinghouse concentration risk, contingency planning, and the Security Rule's information system activity review.
- GlossaryAccess ControlsTechnical policies and procedures that allow only authorized persons or software programs to access ePHI.
- BillingBusiness Associate Agreement Checklist for Small PracticesA working checklist for small practices to identify which vendors need a Business Associate Agreement, what clauses the BAA must contain, and how to track them.
Last reviewed May 23, 2026 · Citation verified May 23, 2026
Research aid, not legal advice. This summary is an administrative research aid prepared by D3rx. It does not certify compliance, provide legal advice, replace counsel, or guarantee an audit outcome. For authoritative regulatory text follow the primary source link at the top of this page. The practice remains responsible for reviewing, adopting, and maintaining its compliance program.