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 →
← Risk, Policy Hierarchy & Ethics

Chapter 2 · Lesson 2 of 4

The risk management lifecycle and the four treatments

1 min read

The lifecycle runs identify, assess, treat, then monitor. It starts by inventorying the assets the organization depends on, because you cannot rate or protect what you have not catalogued.

Assessment then ranks each scenario by likelihood and impact. A ranked register is not the end point: the next step is deciding how each risk will be treated, and monitoring continues after that.

TreatmentWhat happens
AvoidDo not start, or stop, the activity that creates the exposure
Mitigate (reduce)Keep the activity and add controls that lower likelihood, impact or both
Transfer (share)Shift the financial impact to a third party, such as an insurer
AcceptA documented, approved decision to absorb a risk within tolerance

Inherent risk is the exposure before controls; residual risk is what remains after them. No control set reaches zero, so residual risk must sit within the organization's tolerance and then be formally accepted by senior management, which owns the business objectives the risk is taken for.

Analysts advise; they do not accept risk for the organization. Example: an app's data-loss risk falls from high to low after encryption and access reviews, and an executive signs off on the low remainder with a review date.

Check yourself

1. Before any safeguards existed, a data-loss scenario was rated high. After encryption, access reviews and monitoring were deployed, the exposure that remains is rated low. What is that remaining exposure called, and what must be done with it?

2. A team has identified its assets, threats and vulnerabilities and has ranked every scenario by likelihood and impact. According to the risk management lifecycle, what comes NEXT?

Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline, ISC2 Code of Ethics

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