NIST CSF 2.0 Framework

Respond (RS): Managing a Cybersecurity Incident

Incident management, analysis, communication and mitigation

8 min read
CTO, CISO, IT Director
Updated 11/18/2026
Intermediate
NIST CSF 2.0RespondIncident ResponseCommunication

TL;DR (for busy owners)

  • What it is: Respond (RS) covers the actions taken once an incident is detected: managing it, analyzing it, communicating about it and containing it.
  • Why it matters: A slow or incomplete response turns a contained problem into a breach. In cloud, a common failure is revoking the leaked key but missing the extra credentials and roles the attacker already created.
  • Quick action: Decide today who leads a cloud incident, who can revoke access, and who talks to customers.

The four Respond categories

CodeCategoryIn plain English
RS.MAIncident ManagementResponses are coordinated: declared, prioritized, escalated
RS.ANIncident AnalysisInvestigation establishes what happened and the root cause
RS.COIncident Response Reporting and CommunicationStakeholders, customers and authorities are informed as required
RS.MIIncident MitigationThe incident is contained and eradicated

Where cloud responses go wrong

Responders deactivate the compromised access key and declare the incident closed. Meanwhile the attacker used that key to create a second key on another user and a role trusting their own account — and existing role sessions remain valid until they expire. The cloud credential persistence scenario shows why eradication must cover every identity change made during the intrusion window.

Fast checks (30 minutes)

Respond readiness

  • An incident lead and deputy are named, with contact details (RS.MA)
  • There is a written runbook for a compromised cloud credential (RS.MI)
  • Responders know how to revoke active IAM role sessions, not just keys (RS.MI)
  • Responders can query CloudTrail for all identity changes in a time window (RS.AN)
  • Customer, regulator and insurer notification duties are documented (RS.CO)
  • The plan was exercised in the last 12 months (RS.MA)

During an incident

First-hour priorities for a cloud credential incident

Preserve evidence: confirm logging is intact and export relevant CloudTrail events

Medium
First 30 minutes
Incident lead

Deactivate compromised credentials and revoke active role sessions

Medium
First 30 minutes
Cloud admin

List every IAM change made by the compromised identity

Medium
First hour
Analyst

Brief leadership and decide on external communication

Easy
First hours
Incident lead

Map to frameworks

NIST CSF 2.0 Respond categories

NIST CSF 2.0
RS.MA
Incident Management
NIST CSF 2.0
RS.AN
Incident Analysis
NIST CSF 2.0
RS.CO
Incident Response Reporting and Communication
NIST CSF 2.0
RS.MI
Incident Mitigation

Where Securitain fits

Scoping access during and after an incident

IAM identity and trust view

Understanding what a compromised identity could reach helps scope the investigation.

  1. 1Review the compromised identity's effective permissions
  2. 2Check for roles trusting unfamiliar external accounts
  3. 3Identify privilege-escalation paths the identity could have used

Securitain is not an incident-response service or a log-analysis tool; use it alongside your CloudTrail investigation and response team.

Next steps

Rehearse one scenario

Pick the compromised access key scenario and walk through it with the people who would actually respond. Note every step that depends on someone who is not in the room.

Discuss your cloud incident readiness with Securitain.

Talk to a security architect

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain