CVE-2023-34094

Session auditing enables detection of unauthorized exposure or access to sensitive information during user activities.

Privacy and security architectures require controls to protect sensitive information from unauthorized exposure across the system lifecycle.

Inventory identifies all systems holding or processing data, enabling detection of unauthorized exposure paths before exploitation.

Protection planning for critical infrastructure directly calls for authentication of access to essential functions before any operation is permitted.

Risk assessments evaluate exposure of critical functions lacking authentication and prioritize corrective controls.

Requires authentication gates on critical functions that must remain unavailable to anonymous public users.

Treats remote activation of surveillance-capable devices as a critical function that must be disabled or authenticated.

Decoys supply misleading data and log access attempts, directly detecting and deflecting unauthorized information exposure.

Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.

Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.

Defining and enforcing authorizations assumes prior authentication and therefore only partially mitigates the absence of authentication.

Protecting networks from unauthorized access can be undermined by missing authentication but does not address the root authentication gap.

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.