Breach Definition and Risk Assessment: The four-factor analysis and the presumption

45 CFR 164.402 is the breach definition and risk assessment requirement. It is short to read and easy to underestimate, because satisfying it means producing an artifact rather than holding an intention.

What the rule says

45 CFR 164.402 governs breach definition and risk assessment. The operative text is not reproduced here: read it at the source linked below, because the conditions in it are the requirement and a summary of a conditional rule is not a safe substitute for the rule.

What this looks like in practice

In an assessment, 45 CFR 164.402 is not one question. It resolves into several, and each one is really asking for a different artifact:

• A documented breach notification policy that defines what constitutes a notifiable breach and the risk-assessment process used to determine
• Apply the §164.402 breach standard correctly, treating any impermissible acquisition, access, use, or disclosure of PHI as PRESUMED to be a breach

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. Business associates are directly liable for only a defined subset of these obligations, so read your business associate agreement alongside the rule rather than assuming the duty transfers. There is no scalability defense here of the kind the Security Rule offers at 45 CFR 164.306(b): a deadline is a deadline at any size. What does scale is how you meet it, and 45 CFR 164.530(i) expects your policies to be designed for the size and activities of your organization.

Building it, in order

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

1. Maintain a breach notification policy that defines a notifiable breach and any recognized exceptions.
2. Document the risk-assessment process used to determine whether a security event requires notification, including the factors evaluated.
3. Define workforce roles and responsibilities in the determination process.
4. Require the determination and its basis to be documented for each event.
5. Upload the breach notification policy.
6. Adopt a written breach risk-assessment form that starts from the presumption rather than from a judgment call, and that requires a recorded finding on each of the four §164.402(2) factors before any no-breach conclusion can be reached. Include a checklist for the three §164.402(1) exceptions, good-faith unintentional acquisition by a workforce member acting within scope, inadvertent disclosure between persons authorized at the same organization or organized health care arrangement, and a good-faith belief the recipient could not reasonably have retained the information, noting that the first two also require no further impermissible use or disclosure. Record the encryption status of the affected data, because encrypted PHI meeting the HHS guidance is not unsecured PHI and does not trigger notification. Retain every completed assessment for six years, including those concluding no breach occurred, since a no-breach determination you cannot evidence is indistinguishable from a breach you failed to report.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.402 also map to NIST CSF RS.AN-03, RS.CO-02; ISO 27001 A.5.24; SOC 2 CC7.3; NIST 800-53 IR-4, IR-6, IR-8; HITRUST 11.a; HICP 405(d) 8. That matters for scoping: if you are working toward SOC 2 or an ISO certification alongside HIPAA, this control is one piece of work and several answers, provided the artifact is written once and referenced rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the artifact types that satisfy it are policy and procedure. 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 artifact and keep the superseded versions. The Privacy Rule carries its own retention rule at 45 CFR 164.530(j)(2): six years from the date of creation or the date when it last was in effect, whichever is later. It is the same period the Security Rule sets at 164.316(b)(2)(i), under a different provision, so cite the one that governs the document you are holding.

Where this usually goes wrong

This requirement carries critical weight in an assessment, which means a gap here tends to surface as a high finding rather than an observation. The usual cause is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the artifact, not the intention. For 45 CFR 164.402 that means a signed, dated policy with a named owner and a review date and a step-by-step procedure someone unfamiliar with the task could follow. 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. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. This requirement carries critical weight in an assessment, so a gap here surfaces as a high finding rather than an observation. Put the review on the calendar with an owner, and keep the dated output of each one.

The practical test for 45 CFR 164.402 is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the requirement is met. If they need you in the room to explain it, it is not.

References

• 45 CFR 164.402, in 45 CFR 164.402 on eCFR.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are our own mapping 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 stricter obligations (45 CFR 160.203).