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 →
← Continuity, Disaster Recovery & Awareness

Chapter 4 · Lesson 2 of 4

Business impact analysis, RPO, RTO and alternate sites

1 min read

Continuity planning starts with a business impact analysis (BIA). It identifies mission-critical functions, ranks how critical each one is, and weighs the impact of losing it. The recovery targets come out of the BIA; they are never a number handed in by the IT team beforehand.

  • Recovery point objective (RPO): the most data loss the business can tolerate, measured in time back from the failure. Backup or replication frequency sets it.
  • Recovery time objective (RTO): how long restoring the system may take, measured forward from the failure.
  • Maximum tolerable downtime (MTD): the outer business limit on the outage. Restoration plus the work recovery time needed to clear the backlog must fit inside it.

Example: an MTD of 8 hours, a 5-hour restore and 2 hours to clear the backlog gives 5 + 2 = 7 hours, so the plan fits. If the restore took 7 hours, 7 + 2 = 9 hours would exceed the limit.

Alternate sites trade cost against speed: a cold site has only space and power and takes weeks, a warm site has hardware but needs data loaded, and a hot site is live within minutes or hours. A reciprocal agreement with another company is cheapest, but its spare capacity is unverified and each side may see the other's data.

Check yourself

1. A continuity team records a maximum tolerable downtime of eight hours for a claims system. Technology can restore the platform in six hours, after which claims staff need three more hours to clear the backlog before the function is genuinely running again. What should the team conclude?

2. A firm's business impact analysis sets a four-hour recovery target for its trading platform, while finance prefers the cheapest alternate site on offer. Which choice should the continuity manager defend?

Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline, NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems, CISA #StopRansomware Guide

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