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 →
← Identity Lifecycle Management

Chapter 5 · Lesson 3 of 4

Deprovisioning leavers and non-human identities

1 min read

Deprovisioning removes access when someone leaves. The first step is to disable the account, not delete it. Disabling stops sign-ins at once but keeps the account object, and with it the audit trail, the mailbox, file ownership and any encryption keys tied to the identity.

Deletion comes later, under the data retention schedule. Deleting right away can destroy evidence a legal team needs and leave encrypted data with no way to open it.

DepartureWhen access is cut
Amicable resignation with noticeLimited access can taper during handover, ending in full deprovisioning
Dismissal or hostile terminationAt or just before notification, planned in advance by HR and security

The difference is about risk. A person who learns they are being dismissed has both motive and opportunity to damage or take data, so the gap between the news and losing access must be close to zero.

Disabling the directory account is not the end. API keys, personal access tokens, federated cloud sessions, certificates, VPN profiles and physical badges can keep working, and shared passwords the person knew should be changed.

The same life cycle covers service accounts, bots and AI agents: each needs a unique identity and a named human owner, a place in access reviews, and deprovisioning when its project ends. Example: when a pilot chatbot is retired, its database account is disabled that day, not left for the next project.

Check yourself

1. An employee resigns. Security wants her access stopped at once, while the legal team needs the contents of her mailbox available for a pending matter. What is the correct handling?

2. A departing developer's directory account has been disabled on her last day. Which remaining step is most often missed and matters most?

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

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