Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, individual lessons, and BMC Cyber Challenge activities.

NIST CSF Category profileIntermediate

Incident Mitigation (RS.MI) — NIST CSF 2.0 Category

Use RS.MI to manage containment, eradication, risk tradeoffs, and preventing recurrence or spread within the Respond Function.

Framework mapping

NIST Cybersecurity Framework 2.0

CSF 2.0
CategoryRS.MI — Incident Mitigation
FunctionRS — RespondCategoryRS.MI — Incident Mitigation
Official CSF Core outcome

Activities are performed to prevent expansion of an event and mitigate its effects.

CSF outcomes describe what an organization may seek to achieve. They do not prescribe one implementation or turn the Core into a universal checklist.

Category outcome

NIST CSF 2.0 places Incident Mitigation (RS.MI) within the Respond Function. The official Category outcome is: “Activities are performed to prevent expansion of an event and mitigate its effects.”

This Category provides a structured way to address containment, eradication, risk tradeoffs, and preventing recurrence or spread. It groups related Subcategory outcomes without prescribing a specific technology, organizational model, or implementation sequence.

What this means in practice

A credible Incident Mitigation capability connects policy and risk decisions to repeatable operating practices. The organization should define scope, ownership, expected outcomes, evidence, exceptions, and reassessment triggers.

Implementation should be proportionate to mission needs, legal and contractual obligations, threat exposure, business impact, and the organization’s risk appetite. The same Category may be implemented differently across systems and business contexts.

Implementation priorities

The following priorities translate the Category into an operating capability. They are starting points for design and governance, not a replacement for architecture, procedures, or risk analysis.

  • Select containment actions based on incident scope, business impact, evidence needs, and safety.
  • Remove malicious access, artifacts, persistence, and exploited conditions.
  • Validate that containment and eradication are effective across affected environments.
  • Monitor for recurrence, alternate paths, and unintended operational consequences.
  • Document risk decisions when complete mitigation is delayed or infeasible.

Evidence and measurement

Evidence should show that the Category’s outcomes are achieved in the intended scope, remain effective, and are reviewed when conditions change. A policy, tool purchase, or completed checklist is not sufficient by itself.

  • Containment and eradication action records
  • Change approvals and emergency action authority
  • Validation scans, telemetry, and recurrence monitoring
  • Removed accounts, artifacts, vulnerabilities, and access paths
  • Residual-risk and delayed-mitigation decisions

Subcategories within RS.MI

This Category contains 2 CSF 2.0 Subcategory outcomes. Each outcome has a dedicated Bare Metal Cyber profile with the official NIST statement and original implementation guidance.

  • RS.MI-01 — Contain Incidents: Incidents are contained
  • RS.MI-02 — Eradicate Incidents: Incidents are eradicated

Using this Category in Current and Target Profiles

For a Current Profile, record which Subcategory outcomes are achieved, the scope of the assessment, and the evidence supporting the judgment. For a Target Profile, select the outcomes needed to meet risk management objectives and describe the target conditions.

Prioritize the resulting gaps by mission consequence, risk exposure, dependencies, obligations, implementation effort, and the value of the improvement. Record the owner and the evidence that will demonstrate closure.

Common failure modes

The following conditions can create the appearance of coverage without reliable outcome achievement. Treat them as hypotheses to test during assessments, exercises, and operational reviews.

  • Containment is delayed while teams seek perfect certainty.
  • Eradication removes visible artifacts but not access paths or root causes.
  • Actions are taken without preserving evidence or understanding dependencies.
  • The organization declares success without sustained monitoring for recurrence.

Source, scope, and attribution

The Category identifier, name, description, and Subcategory outcomes are from NIST CSWP 29. Bare Metal Cyber’s implementation, evidence, failure-mode, and Profile guidance is original educational material.

The CSF describes outcomes, not mandatory implementation steps. Use NIST’s current online Implementation Examples and Informative References when selecting practices and controls for a specific environment.

Certification relevance

This subject appears in or supports the following certification bodies of knowledge:

NIST CSF 2.0CompTIA CySA+ISC2 CISSPGIAC GCIH

Authoritative sources