Media Notification: The more-than-500-residents threshold

45 CFR 164.406 covers media notification. In most assessments the control itself is present and the record proving it is not, which is why this requirement produces findings at organizations that are, in practice, doing the work.

What the rule says

45 CFR 164.406 governs media notification. 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.406 is not one question. It resolves into several, and each one is really asking for a different artifact:

• For breaches affecting a large number of residents of a single jurisdiction, does the organization have a process to notify prominent media serving

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. Include a media-notification trigger in the breach response plan for events that exceed the affected-resident threshold for a single jurisdiction.
2. Designate a communications lead to identify the relevant media outlets by jurisdiction.
3. Prepare a notice mirroring the content provided to individuals and issue it without unreasonable delay and within the required deadline.
4. Document the media notification issued.
5. Upload the media-notification procedure and template.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.406 also map to NIST CSF RS.CO-02; NIST 800-53 IR-6; HITRUST 11.c. 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 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.406 that means 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.

None of this makes media notification harder than it is. The requirement asks for a decision, an implementation, and a record. Organizations that struggle at assessment time are rarely the ones without controls; they are the ones that cannot show when a control started or who owns it now.

References

• 45 CFR 164.406, in 45 CFR 164.406 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).