CVE-2024-21501

Associates sensitivity labels with data objects so that subsequent storage or flow decisions can enforce that only appropriately protected files or directories receive the data.

Least-privilege file and directory permissions directly prevent unauthorized actors from reading sensitive data placed in accessible locations.

Protecting data-at-rest encompasses file-level access controls and encryption that stop exposure of sensitive information in externally reachable paths.

Hardened configuration baselines and ongoing config management reduce the chance that sensitive data is written to world-readable files or directories.

A.5.10 only requires awareness, a topic-specific acceptable-use policy stating expected behaviours/monitoring, and procedures referencing classification and other controls; per the owner's explicit rule on labelling and similar dependency-style clauses, this does not itself prevent exposure (CWE-200) unless access/DLP/etc. act on it.

Requiring the return of all physical and electronic assets plus secure deletion of organizational data from personal devices reduces the chance that sensitive information remains accessible to departing personnel.

A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule, labeling/classification does not itself prevent exposure and requires other controls (e.g. access enforcement) to act on it.

By requiring classification labels and metadata on all information assets, the control makes it harder for sensitive data to be inadvertently exposed because downstream systems and users can recognize and enforce handling rules based on those labels.

Requiring encryption, access controls, and recipient authentication for transfers directly reduces the chance that sensitive data reaches an unauthorized observer.

Secure delivery, protected storage, and confidentiality of allocation records limit exposure of authentication material to unauthorized observers.