Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/43 ▾
  1. 1.Security Principles & Control Types0/5
    1. The CIA triad: confidentiality, integrity and availability
    2. Identification, authentication, authorization and accounting
    3. Authentication factors and true multifactor
    4. Classifying controls by category and by function
    5. Risk transfer, guidelines and due care in this domain
  2. 2.Risk, Policy Hierarchy & Ethics0/4
    1. Threats, vulnerabilities, likelihood and impact
    2. The risk management lifecycle and the four treatments
    3. Laws, frameworks and the policy document hierarchy
    4. Due care, due diligence and the ISC2 Code of Ethics
  3. 3.Governance, Risk & Compliance0/4
    1. What GRC is for, and who is accountable
    2. Frameworks, standards and where obligations come from
    3. Key metrics, KPIs and key risk indicators
    4. Dashboards, scorecards, reports and AI risk indicators
  4. 4.Continuity, Disaster Recovery & Awareness0/4
    1. Redundancy, business continuity and disaster recovery
    2. Business impact analysis, RPO, RTO and alternate sites
    3. Backup types, offline copies and test restores
    4. Security awareness, culture and AI-powered phishing
  5. 5.Identity Lifecycle Management0/4
    1. Roles definition and provisioning new accounts
    2. Access reviews, movers and privilege creep
    3. Deprovisioning leavers and non-human identities
    4. Identity frameworks and tools: SSO, federation, SCIM, PAM and IGA
  6. 6.Logical Access Controls & Models0/4
    1. Least privilege and need-to-know
    2. Separation of duties, dual control and job rotation
    3. Subjects, objects and discretionary access control
    4. MAC, RBAC, rule-based and attribute-based access control
  7. 7.Network Security Concepts0/5
    1. The OSI and TCP/IP models
    2. IPv4 private addresses, NAT and IPv6
    3. VPNs: what they protect and what they do not
    4. Firewalls, ports and applications
    5. Wireless, Bluetooth, ICS and IoT devices
  8. 8.Network Architecture & Cloud Security0/4
    1. Network segmentation, firewall zones and VLANs
    2. Defense in depth and zero trust
    3. Cloud characteristics and deployment models
    4. Service models and the shared security model
  9. 9.Data Security & Security Operations0/5
    1. Data classification, labeling, data states and masking
    2. Retention and media sanitization
    3. Symmetric and asymmetric encryption, hashing and signatures
    4. Logging, monitoring and event triage
    5. Threat actors, threat intelligence and threat frameworks
  10. 10.Incident Response, Assets & Testing0/4
    1. The incident response plan, team and exercises
    2. The incident response life cycle
    3. Asset lifecycle, configuration and change management
    4. Security testing: teams, scans, application tests and physical tests
Saved in this browser. Move it to another device →
← Incident Response, Assets & Testing

Chapter 10 · Lesson 1 of 4

The incident response plan, team and exercises

1 min read

An incident response plan is a product of preparation. It is approved and shared while things are calm, so that during an attack responders carry out agreed steps instead of improvising under pressure. A plan written after detection loses most of its value. The plan is procedural, and its typical contents are listed below.

  • Roles and who has authority to make which decisions.
  • Criteria for classifying an incident by severity, and the escalation and notification paths.
  • Current contact lists, and the one role allowed to speak to customers, regulators and the press.

Recovery order, maximum tolerable downtime and alternate-site contracts belong to continuity and disaster recovery plans, not the incident response plan. The response team, often called a CSIRT, is cross-functional: security and IT responders work with management, legal, human resources and communications, because incidents raise questions engineers cannot decide alone, such as notifying a regulator or handling an employee.

Example: a ransomware note appears on Friday night; the plan already says the on-call manager declares severity and only the communications lead posts updates, so no one tweets rumors.

The plan is validated with exercises. A tabletop is a discussion walkthrough that touches no production system, while a full interruption test actually stops live operations, giving the most realism at the most risk.

Check yourself

1. A mid-size company is chartering a computer security incident response team (CSIRT). Which statement BEST describes how the team should be composed?

2. A security committee asks why the incident response plan must be approved and distributed while nothing is going wrong, rather than assembled at the moment an attack is detected. Which explanation is BEST?

Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management

ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →