← All posts

Internal and External Notification: HIPAA notification duties beside the CSF outcome

July 9, 2026 · Ken Armstrong

NIST CSF 2.0 RS.CO-02 covers internal and external notification. In most assessments the control itself is present and the record proving it is not, which is why this outcome produces findings at organizations that are, in practice, doing the work.

What the framework says

NIST CSF 2.0 RS.CO-02 sets the expectation for internal and external notification. The framework describes the outcome rather than prescribing a technology, so the question is whether your implementation achieves it and whether you can show that it does.

What this looks like in practice

On the ground, NIST CSF 2.0 RS.CO-02 is not one check. It resolves into several questions, and each one is really asking for different evidence:

  • Does the organization have a documented breach notification policy that defines what constitutes a notifiable breach and the risk-assessment process used to determine whether notification is required?
  • Does the organization have a documented plan defining how security incidents are communicated to internal stakeholders and external parties such as affected individuals, regulators, media, and partners?
  • Does the organization have a process to notify affected individuals of a breach of their data without unreasonable delay and within the required time limit, using a notice that contains all required content?

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

NIST CSF 2.0 is voluntary rather than binding, and that changes how it should be used. Adopting it does not create a legal obligation, and declining it is not a violation. It earns its place when a customer contract names it, when it gives structure to a program HIPAA describes only in outcomes, or when a recognized practice is worth having on record. Treat it as a way of organizing work you already owe, if HIPAA applies to you, not as a second regime.

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. Develop an incident communications plan as a companion to the technical response plan.

Where this meets HIPAA

For a healthcare organization the practical reason to care is the overlap with HIPAA. In our reading this outcome covers some of the same ground as 45 CFR 164.402, 45 CFR 164.402(2), and 45 CFR 164.404. That is an editorial mapping, not an official NIST or HHS crosswalk, so read the HIPAA provision itself before relying on it; where the overlap holds, the evidence you produce can be cited against both so long as it is written once and kept in one place.

Evidence an assessor asks for

For this outcome the evidence types that satisfy it are plan, 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 document and keep the superseded versions. No federal rule sets a retention period for a voluntary framework document, so this is our recommendation rather than a requirement: keep six years, because that is what HIPAA requires of the documentation this work usually overlaps with (45 CFR 164.316(b)(2)(i) for security documentation, 164.530(j)(2) for privacy), and holding two sets of dates is how the earlier one goes missing.

Where this usually goes wrong

The usual cause of a gap here 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 evidence, not the intention. For NIST CSF 2.0 RS.CO-02 that means a written plan naming who does what, and evidence it was tested, 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. 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.
  • Review it on a fixed date, not when you remember. Put the review on the calendar with an owner, and keep the dated output of each one.
  • Keep the two sources apart. The framework outcome is voluntary. The steps above that cite 45 CFR are not: for a covered entity or business associate they are obligations in their own right.

The recurring lesson with internal and external notification 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 outcomes

References

  • RS.CO-02, in NIST Cybersecurity Framework 2.0. This is a voluntary framework, not a legal requirement.
  • The HIPAA provisions this post names are an editorial reading of where the work overlaps, not an official NIST or HHS crosswalk.
  • This post describes what a framework outcome asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations of its own.