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

Asset lifecycle, configuration and change management

1 min read

Asset protection starts with knowing what you have. If nobody can list the company's servers, laptops and cloud subscriptions, building a complete inventory comes before anything else, because scanning, patching and access reviews only cover assets already on the list.

The lifecycle also has an end. When end-of-life laptops are disposed of, sanitizing the drives is not the last step: the inventory entry is retired with a dated disposal record, and the licenses, certificates and machine accounts tied to the devices are revoked.

End of support is a growing risk even when software still works: newly found flaws will never be patched, so exposure rises until the system is replaced or fenced off with compensating controls such as segmentation and restricted access.

Configuration management is about state. A baseline is the approved secure configuration for a type of system, often based on a hardening benchmark; new systems are built to it and later audited against it to spot drift. Change management is about process: a change is requested, assessed for risk, approved, tested, scheduled and recorded before the state may change.

Example: a technician opens a remote desktop port on a shop's point-of-sale server to help a vendor and never logs it. That unrecorded change is an unauthorized deviation from the baseline and counts as a security incident even before anyone exploits it. Emergency changes can be fast-tracked, but they are still documented and reviewed afterward.

Check yourself

1. An auditor asks a team to distinguish configuration management from change management. Which statement is correct?

2. A new security manager finds that nobody can say how many servers, laptops and cloud subscriptions the company has. Vulnerability scanning, patching and access reviews are all running. Which action should be taken FIRST, and why?

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 →