Apply the incident handling process such as NIST.SP800-61 to an event

πŸ“˜Cisco Certified CyberOps Associate (200-201 CBROPS)


πŸ”· What is Incident Handling?

Incident handling is the process used to:

  • Detect
  • Analyze
  • Contain
  • Remove
  • Recover from
  • Learn from

a security incident (such as malware infection, unauthorized access, or data breach).

The standard used is:
πŸ‘‰ NIST SP 800-61 (Computer Security Incident Handling Guide)


πŸ”· The 4 Phases of Incident Handling

According to NIST, there are 4 main phases:

  1. Preparation
  2. Detection and Analysis
  3. Containment, Eradication, and Recovery
  4. Post-Incident Activity

🟩 1. Preparation Phase

πŸ”Ή Purpose:

To get ready before an incident happens

πŸ”Ή Key Activities:

  • Create an Incident Response Plan (IRP)
  • Define roles and responsibilities
  • Train the incident response team
  • Set up tools and systems
  • Maintain asset inventory
  • Establish communication channels

πŸ”Ή Important Components:

  • Security tools:
    • SIEM (Security Information and Event Management)
    • IDS/IPS (Intrusion Detection/Prevention Systems)
    • Antivirus / EDR
  • Documentation:
    • Policies
    • Procedures
    • Contact lists

πŸ”Ή Example (IT-based):

  • Configure SIEM to collect logs from servers and firewalls
  • Maintain a list of critical servers and their owners

πŸ”Ή Exam Tips:

  • Preparation is proactive
  • Focuses on readiness and prevention

🟨 2. Detection and Analysis Phase

πŸ”Ή Purpose:

To identify whether an event is actually a security incident

πŸ”Ή Key Activities:

  • Monitor alerts
  • Analyze logs and data
  • Confirm incident
  • Determine scope and impact

πŸ”Ή Steps:

1. Event Detection

  • Alerts from:
    • SIEM
    • IDS/IPS
    • Antivirus
    • Users

2. Event Analysis

  • Check:
    • Log files
    • Network traffic
    • System behavior

3. Incident Validation

  • Determine:
    • Is it a false positive or real attack?

4. Incident Classification

  • Categorize:
    • Malware
    • Phishing
    • Unauthorized access
    • DoS attack

5. Prioritization

  • Based on:
    • Impact (high/medium/low)
    • Sensitivity of affected system

πŸ”Ή Example (IT-based):

  • SIEM alert shows multiple failed logins β†’ analyze logs β†’ confirm brute-force attack

πŸ”Ή Exam Tips:

  • Focus on:
    • Distinguishing events vs incidents
    • False positives vs true positives
    • Severity classification

πŸŸ₯ 3. Containment, Eradication, and Recovery

This is the main response phase


πŸ”Έ A. Containment

πŸ”Ή Purpose:

Stop the incident from spreading

πŸ”Ή Types:

  • Short-term containment
    • Immediate action
  • Long-term containment
    • Temporary fixes until full solution

πŸ”Ή Actions:

  • Isolate infected system
  • Block malicious IP addresses
  • Disable compromised accounts

πŸ”Ή Example:

  • Disconnect infected host from network

πŸ”Έ B. Eradication

πŸ”Ή Purpose:

Remove the root cause of the incident

πŸ”Ή Actions:

  • Delete malware
  • Remove unauthorized access
  • Patch vulnerabilities

πŸ”Ή Example:

  • Remove malicious files and close exploited ports

πŸ”Έ C. Recovery

πŸ”Ή Purpose:

Restore systems to normal operation

πŸ”Ή Actions:

  • Restore from backups
  • Reconnect systems to network
  • Monitor for re-infection

πŸ”Ή Example:

  • Restore clean server image and monitor logs

πŸ”Ή Exam Tips:

  • Containment = stop spread
  • Eradication = remove cause
  • Recovery = restore operations

🟦 4. Post-Incident Activity

πŸ”Ή Purpose:

Learn from the incident and improve security

πŸ”Ή Key Activities:

  • Conduct lessons learned meeting
  • Document the incident
  • Update policies and procedures
  • Improve detection and response

πŸ”Ή Reporting:

  • Incident reports include:
    • Timeline
    • Impact
    • Actions taken
    • Recommendations

πŸ”Ή Example:

  • Update firewall rules after analyzing attack behavior

πŸ”Ή Exam Tips:

  • Focus on:
    • Documentation
    • Process improvement
    • Future prevention

πŸ”· Applying the Process to an Event (Important for Exam)

When given a scenario, you must:

Step 1: Identify the Phase

Ask:

  • Is this preparation?
  • Is this detection?
  • Is this response?
  • Is this post-incident?

Step 2: Identify the Correct Action

SituationPhaseAction
Writing IR planPreparationPlanning
SIEM alert triggeredDetectionAnalyze logs
System isolatedContainmentStop spread
Malware removedEradicationClean system
System restoredRecoveryResume operations
Report writtenPost-IncidentDocumentation

πŸ”· Key Concepts You Must Know

πŸ”Ή 1. Incident vs Event

  • Event = Any observable activity
  • Incident = Event that violates security policy

πŸ”Ή 2. Indicators of Compromise (IoCs)

  • Evidence of attack:
    • Suspicious IP
    • File hashes
    • Domain names

πŸ”Ή 3. Chain of Custody

  • Track evidence handling for legal use

πŸ”Ή 4. Communication

  • Internal:
    • Security team
  • External:
    • Management
    • Legal teams

πŸ”Ή 5. Documentation

  • Every step must be recorded

πŸ”· Common Tools Used

  • SIEM β†’ Log analysis
  • EDR β†’ Endpoint detection
  • IDS/IPS β†’ Network monitoring
  • Packet analyzers β†’ Traffic inspection

πŸ”· Common Exam Questions Patterns

You may be asked to:

βœ” Identify which phase an action belongs to
βœ” Choose the correct next step in a scenario
βœ” Differentiate between containment and eradication
βœ” Recognize proper incident response workflow
βœ” Identify incorrect actions in a phase


πŸ”· Quick Summary (Memory Trick)

πŸ‘‰ PDCR Model:

  • P β†’ Preparation
  • D β†’ Detection & Analysis
  • C β†’ Containment, Eradication, Recovery
  • R β†’ Reporting (Post-Incident)

πŸ”· Final Exam Tips

  • Always think in order of phases
  • Understand why each step is done
  • Focus on decision-making in scenarios
  • Know difference between:
    • Detection vs Response
    • Containment vs Eradication
    • Event vs Incident
Buy Me a Coffee