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 1 of 4

Redundancy, business continuity and disaster recovery

1 min read

Redundancy exists to remove single points of failure, meaning any component whose loss halts a whole business function. If every order passes through one router, one power feed and one internet circuit, the fix is to duplicate those parts and their paths. Monitoring, faster restores or an inventory entry may help, but only duplication removes the dependency.

Business continuity (BC) keeps mission-critical business functions running while a disruption is still under way. It is focused on people and processes: alternate sites, manual workarounds and staff who know what to do. Disaster recovery (DR) is the technical part that restores systems, data and facilities.

Example: after a fire closes a pharmacy's main office, staff fill prescriptions from a branch using a printed drug list (continuity), while IT rebuilds the dispensing server from backups at a second data center (recovery). Detection and containment of an attack belong to incident response, a separate plan.

Two governance points recur. Life safety comes first in every plan: when a fire alarm sounds, staff evacuate even if a critical restore is running, because data can be restored again.

And senior management owns and approves continuity plans, while the security team drafts and maintains them; plans are reviewed on a set schedule and after major changes, such as closing a data center the plan still names.

Check yourself

1. During a regional flood a firm's staff relocate to a temporary office and keep taking customer orders on paper, while the technology group rebuilds servers from backups at another data center. How should these two activities be classified?

2. A continuity planner maps how a warehouse's order system operates and finds that every transaction crosses one router, fed by one power supply and one internet circuit. What has the planner identified, and what principle addresses it?

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 →