Study guide
3.3 Data States and Protection Methods: DLP, DRM, and CASB
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
3.3 Data States and Protection Methods: DLP, DRM, and CASB
Key Takeaways Explain This Topic AI
Data protection controls must match the state of data: at rest, in transit, and in use each exposes different risks.
Encryption protects confidentiality when keys are controlled, but it does not replace classification, authorization, monitoring, or retention decisions.
DLP detects and can block risky movement of sensitive data, but it requires tuning, user education, and exception handling to avoid business disruption.
DRM or IRM can apply persistent usage restrictions to documents, while CASB helps govern SaaS and cloud data flows through visibility, policy, and control.
Control selection should follow risk, data value, workflow impact, and ownership rather than tool popularity.
Last updated: May 2026
Match Controls To Data State
Data exists in several states, and each state creates different security questions. Data at rest is stored in a database, file system, object store, endpoint, backup, archive, or paper record. Data in transit moves across a network, API, message queue, email path, file transfer, replication channel, or removable media process. Data in use is being processed by an application, displayed to a user, loaded in memory, printed, analyzed, or acted on by a business workflow.
A control that works well in one state may not solve another. Full-disk encryption protects a lost laptop when it is powered off, but it does not stop an authorized user from emailing a decrypted file after login. TLS protects a network session, but it does not decide whether the recipient is allowed to have the data. Database encryption protects stored records, but an application vulnerability may still expose data through authorized queries.
Data state Common exposure Useful control families
At rest Lost device, stolen backup, exposed bucket, database compromise. Encryption, access control, key management, storage policy, monitoring, backup protection.
In transit Interception, misrouting, unauthorized transfer, insecure protocol. TLS, VPN where appropriate, secure file transfer, certificate validation, DLP, egress filtering.
In use Screen capture, copy and paste, memory exposure, excessive application access. Least privilege, session controls, masking, tokenization, DRM, endpoint controls, monitoring.
Encryption is often a foundation control. For data at rest, organizations use database encryption, volume encryption, object storage encryption, file encryption, backup encryption, and hardware security modules where risk requires stronger key protection. For data in transit, TLS and secure protocols are common expectations. For data in use, encryption is harder because the application or user must often see plaintext. Specialized methods such as confidential computing, trusted execution environments, or application-level tokenization may reduce exposure in specific designs, but they are not universal answers.
Key management is part of encryption governance. If everyone who can read the data can also export the keys, encryption may not add much protection against insider misuse. Keys need ownership, access rules, rotation expectations, backup, separation of duties, and revocation procedures. A business owner does not need to operate the key vault, but the owner should understand whether key control matches classification and legal duties.
Masking and tokenization reduce sensitive exposure by changing what users or systems see. Masking may hide part of a value, such as showing only the last digits of an identifier. Dynamic masking changes the display based on user or context. Tokenization replaces a sensitive value with a substitute token while the original is stored in a controlled vault. These methods can be better than broad encryption when a workflow needs a reference value but not the raw data.
Data loss prevention, or DLP, focuses on detecting and controlling sensitive data movement. DLP may inspect email, web uploads, endpoint copy activity, cloud storage, collaboration tools, source repositories, or network egress. It can alert, block, quarantine, encrypt, warn the user, or require justification. DLP is most effective when it knows what data matters through classification labels, content patterns, fingerprints, dictionaries, and context such as user, destination, device, and application.
DLP can create operational friction. A poorly tuned rule may block legitimate legal filings, customer support attachments, or incident response evidence. A weak rule may miss sensitive data in screenshots, encrypted archives, unusual formats, or renamed files. Strong governance includes testing, phased rollout, user coaching, owner-approved exceptions, and metrics that show both risk reduction and business impact.
Digital rights management, often called DRM or information rights management in enterprise settings, attempts to keep protection with the document. It may restrict opening, printing, forwarding, copying, offline access, or expiration even after the file leaves the original repository. DRM can help with board documents, merger plans, legal files, and partner collaboration. It is not perfect because screenshots, cameras, and authorized misuse remain possible, but it raises the barrier and improves control.
A cloud access security broker, or CASB, helps govern cloud and SaaS use. CASB capabilities vary, but common functions include discovery of unsanctioned cloud use, policy enforcement for sanctioned SaaS, activity monitoring, DLP integration, anomaly detection, malware scanning, encryption or tokenization support, and access control based on user, device, location, and risk. CASB may operate through API integration, forward proxy, reverse proxy, log analysis, or combinations.
Control selection matrix:
Situation Better first questions Likely control direction
Confidential files leaving by email Is the recipient approved and is the transfer needed? Email DLP, encryption, warning, approval, or secure portal.
Board documents shared externally Should usage remain restricted after download? DRM or IRM plus named recipient access and expiration.
Employees using unapproved file-sharing apps Which apps, users, and data are involved? CASB discovery, sanctioned alternatives, egress controls, and policy.
Developers need production-like data Do they need real personal data? Masking, tokenization, synthetic data, restricted access, and retention limits.
Database backup stored offsite What is the loss impact and who holds keys? Backup encryption, key separation, inventory, and restore testing.
Scenario: a finance team emails quarterly results to external counsel before public release. Encryption in transit is necessary but not enough. The organization may require confidential labeling, approved recipient verification, DLP warning or block for unapproved domains, DRM to limit forwarding, logging, and retention controls. The owner should approve the process because the business impact of early disclosure is high.
Scenario: a SaaS application is widely used by employees without security review. A CASB discovery function may identify the application, users, data volume, and risky activity. Leadership can then decide whether to sanction the application with controls, block it, migrate users to an approved service, or accept a limited exception. The point is not to blindly block productivity, but to make cloud data flow visible and governed.
Scenario: customer service representatives need to verify callers without seeing full government identifiers. Masking or tokenization can support the workflow better than giving every representative full raw values. Owners should decide which fields are necessary, custodians should implement display rules and audit logs, and supervisors should review misuse indicators.
The CISSP habit is to layer controls around the workflow. Ask which data state is exposed, who owns the decision, who needs access, how data moves, what a control can and cannot prevent, and how exceptions will be managed. Tool names matter less than control fit.