Asset Security & Data Lifecycle
CISSP CISSP · Asset Security
Why classification comes first
You cannot protect what you have not identified, and you cannot protect everything equally — so Domain 2 begins with classification. Asset security is about knowing what the organisation owns (data, systems, hardware, software, people, facilities), understanding how sensitive each asset is, and applying handling rules that match that sensitivity. The exam's core insight is that classification drives everything downstream: access control, encryption, retention, and destruction all follow from the classification label. An organisation that treats all data the same either overspends protecting trivia or under-protects its crown jewels.
Classification schemes vary, but the exam expects you to know the common patterns. Government schemes typically use levels such as Top Secret, Secret, Confidential and Unclassified. Commercial schemes commonly use levels such as Public, Internal Use Only, Confidential and Restricted (or Highly Confidential). The labels themselves matter less than the principles: classification must be based on the impact of unauthorised disclosure, it must be applied by the data owner (the business person accountable for the data, not the IT department), and it must be reviewed periodically because data sensitivity changes over time. The data owner decides the classification; the data custodian (usually IT) implements the controls that enforce it; the data steward ensures data quality and policy compliance; and users handle data according to the rules. The exam tests these roles relentlessly — when a question asks who should classify data, the answer is the data owner, never the security team or the system administrator.
Asset inventory and ownership
An asset inventory is the register of everything the organisation owns that has value or carries risk: hardware, software licences, data stores, cloud resources, and even intangible assets such as intellectual property and reputation. Each asset needs a recorded owner who is accountable for it. Ownership matters because security decisions — who may access an asset, how long to keep it, when to retire it — are business decisions that only the owner can properly make. The exam treats "no asset owner" as a governance failure: without an owner, nobody approves access, nobody accepts risk, and nobody is accountable when something goes wrong. Asset management also includes software licensing compliance (unlicensed software is both a legal and a security risk) and hardware lifecycle tracking from procurement to disposal.
The data lifecycle
Data moves through stages, and each stage needs its own controls. The lifecycle is generally described as: creation/collection (data is generated or gathered — minimise what you collect, because data you do not hold cannot leak), storage (protect data at rest with encryption and access controls appropriate to its classification), use (data in use is the hardest state to protect; controls include access control, data loss prevention and careful handling), sharing (data in transit needs encryption and the sharing must be authorised and logged), archival (data kept for legal or business reasons but no longer in active use — still protected, but with different access patterns), and destruction (secure removal when retention expires). The exam's key point is that controls must follow the data through every stage: encrypting data at rest but sending it in cleartext, or protecting live data but leaving it in backups forever, are both failures.
The three states of data are a related exam favourite: data at rest (stored on disk, tape or in a database — protected by encryption, access controls and physical security), data in transit (moving across a network — protected by TLS, VPNs and secure protocols), and data in use (loaded in memory or being processed — protected by access controls, endpoint security, and increasingly by techniques such as confidential computing). Each state has different threats and different controls, and a question that asks for the best control for a specific state expects you to match them.
Handling requirements
Classification is only useful if it drives handling rules. Handling requirements specify how data at each classification level may be stored, transmitted, printed, shared, and destroyed. Common handling controls include marking and labelling (documents and files carry their classification visibly), access restrictions (only authorised personnel, enforced by the access control system), encryption requirements (higher classifications require stronger or mandatory encryption), transmission rules (restricted data may only travel over approved encrypted channels), and printing and copying controls (sensitive documents may not leave the building, or may require watermarking). The exam often presents a scenario where data is handled below its classification — for example, confidential data emailed without encryption — and the correct answer identifies the handling violation and the control that should have applied.
Retention and legal holds
Data must be kept for as long as the business or the law requires — and no longer. Retention schedules define how long each category of data is kept, driven by legal requirements (tax records, financial records, health records), regulatory obligations, and business needs. Keeping data beyond its retention period is a liability: it increases the breach exposure, raises storage costs, and can complicate legal discovery. Legal holds override retention schedules: when litigation is reasonably anticipated, relevant data must be preserved regardless of the normal destruction schedule, and destroying data under a legal hold can result in severe sanctions for spoliation. The exam tests the tension: normal operations destroy on schedule; a legal hold freezes destruction for the affected data until the hold is released.
Secure destruction
When data reaches the end of its life, it must be destroyed in a way that matches its sensitivity. The methods form a hierarchy. Clearing removes data so it cannot be recovered by normal means — overwriting with patterns of data, or factory reset. Purging goes further, using techniques such as degaussing (for magnetic media) or cryptographic erase (destroying the encryption keys so the data is unreadable) to prevent recovery even with laboratory techniques. Destroying is physical: shredding, crushing, incinerating, or chemical dissolution. The exam's key facts: degaussing works only on magnetic media and does not work on SSDs or flash memory (which require cryptographic erase or physical destruction); simple deletion only removes the file system's pointer, not the data; and a certificate of destruction should be obtained from any third party that destroys media on the organisation's behalf, because accountability for the data remains with the organisation even when destruction is outsourced.
| Method | What it does | Notes |
|---|---|---|
| Deletion | Removes the file pointer | Data remains recoverable — not secure destruction |
| Clearing (overwrite) | Replaces data with patterns | Good for reuse within the organisation; multiple passes for higher sensitivity |
| Purging (degaussing) | Disrupts magnetic fields | Magnetic media only; destroys the drive; useless on SSDs/flash |
| Purging (crypto erase) | Destroys encryption keys | Fast and effective for encrypted SSDs and cloud storage |
| Destroying | Physical destruction | Shredding, crushing, incineration — the final option for the most sensitive media |
Data security controls
Beyond classification and handling, Domain 2 covers the controls that protect data directly. Data Loss Prevention (DLP) systems monitor and block the unauthorised movement of sensitive data — at the network edge, on endpoints, and in cloud services — using content inspection and policy rules. Digital Rights Management (DRM) and Information Rights Management (IRM) embed usage controls in the data itself, so a document can be set to expire, to prevent forwarding, or to prevent printing even after it leaves the organisation. Data masking replaces sensitive values with fictional ones for use in testing and development (a masked database looks realistic but contains no real customer data), while tokenisation replaces sensitive values with non-sensitive tokens that map back to the original only in a secure vault — widely used for payment card data. The exam distinguishes masking (irreversible, for non-production use) from tokenisation (reversible through the vault, for production systems that need the real value occasionally).
Exam mindset for asset security
Asset security questions reward the answer that follows the classification. If a scenario involves data, ask first: what is its classification, and who owns it? The data owner makes classification and retention decisions; IT implements them. And when a question involves disposal, match the method to the media and the sensitivity — degaussing an SSD is the classic trap.
Exam traps to watch for
- Saying IT or the security team classifies data — the data owner (a business role) classifies; IT is the custodian that implements controls.
- Degaussing SSDs or flash media: degaussing only works on magnetic storage. For SSDs, use cryptographic erase or physical destruction.
- Treating deletion as destruction: deleting a file only removes the pointer. Secure destruction requires clearing, purging or destroying.
- Destroying data under a legal hold: a hold overrides the retention schedule, and destroying held data can mean sanctions for spoliation.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company is implementing a data classification program. Who should be responsible for determining the classification level of a set of customer records?
Explanation: Classification is a business decision about the value and sensitivity of the data, and the data owner — the business person accountable for it — is the only role positioned to make it. The system administrator and the data custodian implement the controls that enforce the classification; they do not decide it. The CISO advises on the program and the control framework but does not own the business data.
Exam objective: CISSP Domain 2: Identify and classify information and assets
Q2.A hospital is decommissioning servers that contain patient records on solid-state drives (SSDs). The drives held highly sensitive data and will not be reused. Which destruction method is MOST appropriate?
Explanation: SSDs store data in flash memory, not magnetically, so degaussing has no effect on them. Physical destruction guarantees the data cannot be recovered, and cryptographic erase (destroying the encryption keys) is equally effective if the drives were encrypted. Deleting files only removes pointers, and a single overwrite pass is unreliable on SSDs because wear-levelling means some cells may not be overwritten.
Exam objective: CISSP Domain 2: Manage data lifecycle (secure destruction)
Q3.An organisation receives notice that it may face litigation over a contract dispute. Its retention schedule says that emails older than two years should be deleted. What should the organisation do about the emails relevant to the dispute?
Explanation: A legal hold overrides the retention schedule: when litigation is reasonably anticipated, relevant data must be preserved, and destroying it can result in sanctions for spoliation of evidence. Continuing scheduled deletion after the hold is triggered is exactly the failure the law punishes. Deleting emails to limit evidence is spoliation. Moving them to archive preserves them, but the correct framing is the legal hold itself — and the archive option does not mention preserving them under hold, so it does not address the legal obligation.
Exam objective: CISSP Domain 2: Manage data lifecycle (retention and legal holds)
Q4.A development team needs a realistic database for testing a new application, but the production database contains real customer names, addresses and payment details. What is the BEST approach?
Explanation: Data masking gives the test team realistic-looking data with no real customer information in it, which is exactly what testing needs and what privacy rules require. Copying production data into a test environment exposes real customer data to a less-protected system. Encryption does not help here because the developers need the decrypted data to test with. Tokenisation is reversible by design — it preserves a path back to the real data, which is unnecessary and risky for testing.
Exam objective: CISSP Domain 2: Establish information and asset handling requirements (data masking)
Q5.An employee emails a spreadsheet containing customer Social Security numbers to a personal email account. Which control is BEST designed to detect and block this action?
Explanation: DLP inspects content in motion and can detect the pattern of a Social Security number leaving the organisation, blocking or alerting on the exfiltration. Full-disk encryption protects data at rest on the laptop, not data being emailed out. Role-based access control governs who can access the database in the first place — the employee was authorised, so RBAC cannot help. A digital signature proves authenticity and integrity; it does nothing to prevent disclosure.
Exam objective: CISSP Domain 2: Establish information and asset handling requirements (DLP)
Q6.A company classifies its product roadmap as "Confidential" and its press releases as "Public". A new employee asks why the roadmap cannot be shared with a partner company under NDA. What is the BEST explanation?
Explanation: Classification does not forbid sharing; it defines the conditions under which sharing is permitted — owner authorisation and appropriate handling controls, which can include an NDA and encrypted transmission. The claim that Confidential data can never be shared is false; businesses share confidential data under controlled conditions every day. Reclassifying the roadmap as Public to dodge the controls defeats the purpose of classification. Authorisation rests with the data owner, not the CISO.
Exam objective: CISSP Domain 2: Establish information and asset handling requirements
Q7.Which data state is MOST difficult to protect, and why?
Explanation: Data in use must be decrypted to be processed, so it sits in memory in plaintext where it is exposed to memory scraping, side-channel attacks and compromised processes — encryption at rest and in transit cannot help at this stage. Data at rest is well protected by encryption with keys stored separately (never alongside the data). Data in transit is protected by TLS and VPNs, which are mature and effective. Archived data is simply data at rest with a different access pattern.
Exam objective: CISSP Domain 2: Manage data lifecycle (states of data)
Q8.An organisation outsources the destruction of decommissioned hard drives to a third-party vendor. What is the MOST important step to ensure the organisation remains accountable for the data?
Explanation: A certificate of destruction provides documented evidence that the media was destroyed, and auditing the vendor verifies the process actually happened — accountability for the data stays with the organisation even when destruction is outsourced. The choice between degaussing and shredding is a method detail, not an accountability control. Encrypting before handover is a useful extra layer but does not prove destruction occurred. Removing labels does nothing for accountability and would hinder tracking.
Exam objective: CISSP Domain 2: Manage data lifecycle (secure destruction, third-party accountability)