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 →
← Data Security & Security Operations

Chapter 9 · Lesson 1 of 5

Data classification, labeling, data states and masking

1 min read

Classification comes first in handling data because it decides how sensitive the data is, and every later rule comes from that decision: what encryption is needed, who may see it, how long it is kept and how its media are wiped.

The data owner makes that decision and stays accountable; custodians such as IT staff carry out the controls. Labeling is a separate act. It is the visible or machine-readable marking, such as a header stamp or a metadata tag, that tells people and systems the level. The label conveys the classification; it does not create it.

  • Data at rest is protected by storage encryption, and data in transit by an encrypted channel.
  • Data in use is the hardest state to protect, because it must be decrypted in memory for an application to work with it.
  • Archive is a lifecycle stage, not a fourth data state.

Masking, also called obfuscation, swaps sensitive values for realistic fake ones so the data keeps its format and stays useful.

Example: a test copy of a gym's member list shows card number 4000 0000 0000 0002 for every member instead of the real numbers, so testers can run billing code without ever seeing a real card. Encrypting the copy would not solve this, because anyone with the key could still read the real values.

Check yourself

1. A document is assessed as "Confidential" under the company's scheme, and the word "Confidential" is then placed in its header and in its metadata. Which statement BEST describes these two acts?

2. A finance database is encrypted on disk, and its records travel to a reporting server over an encrypted channel. Which data state remains the LEAST protected by these two measures?

Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization

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