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

Laws, frameworks and the policy document hierarchy

1 min read

The outline's governance concepts start with where an obligation comes from. Laws and regulations are imposed by governments and enforced by the state.

An industry standard such as the Payment Card Industry Data Security Standard is imposed by the card brands through contracts, so failing it is a breach of agreement with fines or loss of card processing, not a breach of statute.

Frameworks and guidelines are reference material an organization chooses to adopt. Much NIST guidance is required for US federal agencies but voluntary for a private company unless a contract, regulator or customer requires it.

Inside the organization, documents form a hierarchy. A policy states what must be achieved and why, in technology-neutral terms, and gets its authority from approval by senior management.

A standard names the specific, measurable requirement that carries out the policy. A procedure gives step-by-step instructions. A guideline recommends good practice and leaves room for judgment. Policies, standards and procedures are mandatory; guidelines are advisory.

Example: "Customer data must be protected at rest" is a policy sentence. "All servers must use AES-256 disk encryption" is a standard, because it is mandatory and names an exact technology without giving steps.

"Open the console, select the volume, choose Encrypt" is a procedure. "Consider a password manager for personal accounts" is a guideline. The outline adds that AI tools follow the same policies and legal requirements as any other software.

Check yourself

1. A governance document contains this sentence: “All company laptops must use full-disk encryption with AES-256.” Which document type does that sentence belong to?

2. A privately owned United States manufacturer adopts the NIST Cybersecurity Framework to organize its security programme. What is that framework's status for this company?

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 →