Evaluation: The periodic evaluation most practices skip

45 CFR 164.308(a)(8) is the requirement on evaluation. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

Standard: Evaluation. Perform a periodic technical and nontechnical evaluation, based initially upon the standards implemented under this rule and, subsequently, in response to environmental or operational changes affecting the security of electronic protected health information, that establishes the extent to which a covered entity's or business associate's security policies and procedures meet the requirements of this subpart.

That is the text of 45 CFR 164.308(a)(8). Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

This is a standard, and a standard is met in full: 45 CFR 164.306(c) requires a covered entity or business associate to comply with the applicable standards.

What this looks like in practice

In an assessment, 45 CFR 164.308(a)(8) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Does the organization perform a periodic technical and nontechnical evaluation, and a further evaluation in response to environmental or operational changes affecting the security of ePHI, that establishes the extent to which its security policies and procedures meet the requirements of the Security Rule?
• Does the organization follow a secure software development lifecycle for applications it builds that handle sensitive data?
• Does the organization test its incident and breach response procedures periodically and update them based on exercise findings and actual incidents?

Ownership usually sits with the security official, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Every covered entity and every business associate, at any size. 45 CFR 164.306(b) allows flexibility of approach, so a two-provider practice and a hospital system may implement this differently and both comply. What flexibility does not allow is skipping the decision: the smaller the organization, the more the written reasoning carries the weight, because there is no scale of operation to make the control self-evident.

Building it, in order

These steps are one way to meet it, drawn from our question bank. Unless a step names a provision, the Security Rule does not require that particular measure: 45 CFR 164.306(b)(1) lets you use any security measures that allow you to reasonably and appropriately implement the standards and implementation specifications, chosen with the factors in 45 CFR 164.306(b)(2).

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Set the interval for the periodic evaluation and the environmental or operational changes that trigger a further one.
2. Evaluate the technical and nontechnical safeguards against each Security Rule standard and implementation specification.
3. Record the extent to which each is met, and the gaps.
4. Feed the gaps into risk management.
5. An internal audit or a third-party assessment is one way to perform it.
6. Establish a secure software development lifecycle framework covering requirements, design, coding, testing, and release.

Where else this maps

The questions behind 45 CFR 164.308(a)(8) also map to HHS 405(d) HICP (2023 Edition) CSP 7, CSP 8 and NIST SP 800-66 Rev. 2 5.1.1, 5.1.6, 5.1.8, which are voluntary guidance rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are configuration, policy, and report. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. 45 CFR 164.316(b)(2)(i) requires the documentation 164.316(b)(1) calls for (the Security Rule policies and procedures, and the written record of any action, activity or assessment the Security Rule requires to be documented) to be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

Where this usually goes wrong

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.308(a)(8) that means a configuration export or screenshot showing the setting live, dated, a signed, dated policy with a named owner and a review date, and a dated report with the period it covers and who reviewed it. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your security official should be recorded as the owner. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.
• There is no documented-alternative route for the requirement itself. It is required (45 CFR 164.306(d)(2) for a specification, 164.306(c) for a standard), so a risk-based decision not to meet it is not available. How you meet it is yours to choose under 45 CFR 164.306(b); the measures in this post are examples, not the rule's text.

The recurring lesson with evaluation is that documentation is not the paperwork after the control. It is the part an assessor can read, and therefore the part that has to exist.

Related requirements

• Applications and Data Criticality Analysis: Ranking applications and data by criticality
• Business Associate Contracts and Other Arrangements: What the contract must require of a vendor
• Testing and Revision Procedures: Testing the contingency plan and recording the result

References

• 45 CFR 164.308(a)(8), in 45 CFR 164.308 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations; HIPAA preempts a State law only where it is contrary to HIPAA (45 CFR 160.202, 160.203).