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 Analysis (RS.AN) — NIST CSF 2.0 Category

Use RS.AN to manage facts, root cause, evidence preservation, action records, and magnitude estimation within the Respond Function.

Framework mapping

NIST Cybersecurity Framework 2.0

CSF 2.0
CategoryRS.AN — Incident Analysis
FunctionRS — RespondCategoryRS.AN — Incident Analysis
Official CSF Core outcome

Investigations are conducted to ensure effective response and support forensics and recovery activities.

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 Analysis (RS.AN) within the Respond Function. The official Category outcome is: “Investigations are conducted to ensure effective response and support forensics and recovery activities.”

This Category provides a structured way to address facts, root cause, evidence preservation, action records, and magnitude estimation. It groups related Subcategory outcomes without prescribing a specific technology, organizational model, or implementation sequence.

What this means in practice

A credible Incident Analysis 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.

  • Establish facts, timelines, affected assets, identities, actions, and uncertainty.
  • Preserve evidence and investigation records with integrity and access controls.
  • Analyze root cause, attack path, control failures, and continuing exposure.
  • Estimate and update incident magnitude as evidence develops.
  • Coordinate analysis with legal, privacy, law enforcement, insurance, and recovery needs as appropriate.

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.

  • Forensic images, logs, artifacts, and chain-of-custody records
  • Investigation timelines and analytical notes
  • Root-cause and attack-path analysis
  • Magnitude, scope, and impact estimates
  • Records of investigative actions and evidence handling

Subcategories within RS.AN

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

  • RS.AN-03 — Establish Incident Facts and Root Cause: Analysis is performed to establish what has taken place during an incident and the root cause of the incident
  • RS.AN-06 — Preserve Investigation Action Records: Actions performed during an investigation are recorded, and the records’ integrity and provenance are preserved
  • RS.AN-07 — Preserve Incident Data and Metadata: Incident data and metadata are collected, and their integrity and provenance are preserved
  • RS.AN-08 — Estimate and Validate Incident Magnitude: An incident’s magnitude is estimated and validated

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.

  • Response actions destroy evidence needed to understand the incident.
  • Root cause is reduced to a single technical defect without examining process and governance.
  • Magnitude estimates remain static despite new evidence.
  • Analytical conclusions are not separated from assumptions and confidence levels.

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