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

Roles definition and provisioning new accounts

1 min read

Roles come before accounts. A role is a set of permissions that matches a job function, such as accounts payable clerk, and people receive access by being assigned to that role.

Because the permissions belong to the job and not to the person, everyone doing the same job gets the same access, and access is granted or removed simply by adding or removing the role assignment.

Provisioning should start from an authoritative source, normally the approved new-hire record in the HR system, and run through an automated workflow.

That keeps access identical for everyone in a role and leaves an audit trail, which a manager's email to the help desk never guarantees. The order matters: verify the person's identity, create the account, assign the role, and only then issue credentials.

  • Give every person a unique account. A shared login breaks accountability because logged actions cannot be tied to one human.
  • Never build a new account by copying a veteran's memberships. The copy imports years of extra access.
  • Grant ordinary role access at hire. Administrative rights are a separate approved request, held in a separate admin account so email and browsing run without elevated rights.

Example: a new nurse scheduler is hired. HR approves the record, ID is checked, the account is created, the Scheduler role is assigned, and the password and token are issued last.

Check yourself

1. Which sequence correctly orders the provisioning steps for a newly hired employee?

2. New hires at a company receive accounts when a manager emails the help desk, and the access granted varies from hire to hire. Which change best corrects this?

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 →