Skip to content

DOMAIN 2 · Asset Security

Information classification and ownership

Assess confidentiality, integrity, and availability impacts and translate classification decisions into lifecycle handling rules.

An asset inventory should reveal what information exists, why it matters, who is responsible, and where copies travel. Classification makes protection decisions repeatable. NIST SP 800-60 provides a U.S. federal method for mapping information types to security impact categories; its principles are useful for study, but its categories are not universal corporate labels.1

Start with business processes rather than file extensions. A spreadsheet may contain public marketing figures or restricted payroll records. Its format alone does not determine the required protection.

Confidentiality concerns unauthorized disclosure. Integrity concerns unauthorized modification or destruction. Availability concerns timely and reliable access. Evaluate consequences for each objective separately. A public emergency notice may have little confidentiality need but serious integrity and availability requirements.

SP 800-60 begins with provisional impact levels, reviews them in context, and assigns a system category.1 A recommended starting level is a prompt for analysis; it is not a substitute for understanding the actual service.

Concept Example What it helps decide
Information type Payroll information Which information and process are involved
Organizational label Restricted Which internal handling rules apply
Security impact High integrity impact How harmful a particular failure could be
Retention requirement Approved payroll retention period When records may be disposed of

This table is illustrative. Names such as public, internal, confidential, and restricted must be defined locally. A label without a handling rule gives people little guidance about sharing, storage, or disposal.

A practical role model separates business decisions from technical execution. The information owner determines business value and approves protection expectations. Custodians implement storage, access, backup, and disposal procedures. Users follow handling rules and report inappropriate access. These are teaching roles; organizational titles vary.

SP 800-60 involves mission and information owners in identifying information types and selecting impact levels.1 Security staff can facilitate the process, but cannot reliably infer every business consequence without those owners.

A system can process multiple information types. In the NIST method, the highest applicable impact for each security objective contributes to the system’s categorization; context may require further adjustment.1 Averaging low-impact public data with high-impact records would hide important protection needs.

Consider a portal containing public brochures and confidential customer applications. Public brochures do not make the applications less sensitive. Conversely, a public notice can demand strong integrity controls even when anyone is allowed to read it.

For each label, define who may access information, acceptable sharing channels, storage requirements, logging expectations, retention, and disposal. Apply the decisions to exports, email attachments, test datasets, backups, and third-party transfers. A protected database can still leak through an unrestricted analytics export.

Reassess when the purpose, aggregation, audience, or business impact changes. Combining apparently low-sensitivity records can reveal sensitive patterns. Declassification and disposal should follow an authorized process, not an individual user’s assumption that old information no longer matters.

Classification is not encryption: it provides input to control selection. Nor is confidentiality the only consideration. Availability can be the dominant concern for operational services. Finally, deleting a label does not remove the obligations associated with the underlying information. Decisions should remain traceable to owners, impact analysis, and handling requirements.

Use risk assessment to examine threat scenarios and media sanitization to plan the end of the lifecycle.

  1. NIST, SP 800-60 Volume I Rev. 1, sections 3–4, especially the categorization process and system high-water marks. ↩ ↩2 ↩3 ↩4

Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.

Editorial policy & attribution