CVE-2023-21246

Requires detection and response to audit logging failures as an unusual or exceptional condition.

Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.

Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.

IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.

Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.

Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.

Requires detection of unusual conditions followed by a controlled transition to the defined failure state.

MTTF determination forces explicit checks for conditions that precede predictable component failure.

Least-privilege policy and enforcement directly motivate privilege-dropping code, yet the control does not address implementation-level verification of the drop.

Secure SDLC activities (code review, static analysis, testing) catch missing or incorrect privilege-drop checks, but eliminating only this one flaw covers only a fraction of the control's broader intent.

A.5.15 only requires defining policies, determining requirements, and referencing other controls for implementing access rules; it never mandates or performs the specific check for successful privilege drop that would remove CWE-273 from first-party code.

A.5.18 governs the provisioning, review, and revocation of access rights granted to identities; it does not remove or mandate the removal of a first-party code defect in which a privilege drop is attempted but never verified.

Logging can record unhandled exceptions but does not prevent the weakness itself.

Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.

Control of privileged utility programs includes ensuring privilege-dropping operations are verified before use.