CVE-2026-106501

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

Protecting data-in-use includes removing confidential values before they are processed or sent.

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

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.