Incident Containment: Containing an incident without destroying evidence

Auditors ask about incident containment early, because the answer tells them how the rest of the program is likely to look. The outcome is NIST CSF 2.0 RS.MI-01.

What the framework says

NIST CSF 2.0 RS.MI-01 sets the expectation for incident containment. 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.MI-01 is not one check. It resolves into several questions, and each one is really asking for different evidence:

• Does the organization maintain a documented incident response plan defining what constitutes a security incident and covering detection, analysis, containment, eradication, and recovery?

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 written incident response plan that defines a security incident and documents each phase: preparation, detection and analysis, containment, eradication, recovery, and post-incident review.
2. Assign roles and responsibilities and include decision criteria for escalation.
3. Address scenarios with widespread impact, including mass-encryption events, with isolation and clean-restoration procedures.
4. Review and update the plan at least annually.

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.308(a)(6)(i). 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. 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 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 NIST CSF 2.0 RS.MI-01 that means a written plan naming who does what, and evidence it was tested. 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.
• 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.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract names it or where it gives structure to something HIPAA describes only as an outcome, and say in your own documentation which of those reasons applies.

Work backward from the evidence. Decide what evidence would prove incident containment to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the evidence goes stale visibly.

Related outcomes

• Internal and External Notification: HIPAA notification duties beside the CSF outcome
• Recovery Plan Execution: Executing recovery and proving it worked
• Incident Analysis: Determining what actually happened

References

• RS.MI-01, 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.