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 →
← Logical Access Controls & Models

Chapter 6 · Lesson 3 of 4

Subjects, objects and discretionary access control

1 min read

Every access control model uses the same vocabulary. A subject is the active entity that requests an action, such as a user account, a process or a service acting for a user.

An object is the passive resource acted on, such as a file, table, record or device. The permission is the access right linking the two; it is not the object.

An access control list (ACL) is attached to an object and lists who may use it, so it answers who can reach this file. A capability is held by a subject and lists what it may reach, so it answers what can this user reach. Both describe the same permissions read from opposite directions.

In discretionary access control (DAC), the owner of an object decides who may use it and can pass that access on to others, usually by editing the object's ACL. The tell in a question is that the creator grants access personally with no central authority involved.

DAC is flexible and needs little administration, which suits a small team. The trade-off is that decisions are scattered among many owners, so permissions sprawl and are hard to audit or revoke. Example: a podcast producer shares an episode script folder with two freelance editors herself, without asking IT.

Check yourself

1. An employee creates a spreadsheet on a shared file server and, on his own initiative, grants two colleagues permission to open it without involving the IT department. Which access control model does this illustrate?

2. In access control terminology, a user account opens a database table. Which statement correctly identifies the subject and the object?

Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline, NIST SP 800-162 Guide to Attribute Based Access Control (ABAC) Definition and Considerations

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