CVE-2023-22393

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

Assessments identify and document improperly implemented security checks, allowing fixes that reduce exploitation of flawed checks.

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.

Secure SDLC practices directly require correct implementation of standardized security checks and algorithms.

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.

Use of cryptography control depends on correct implementation of standardized cryptographic checks.

A.8.25 mandates security requirements, checkpoints, secure coding, testing (incl. code scans/pen tests) and developer capability in the SDLC, which reaches a minority slice of CWE-358 (incorrect implementation of a standardized security check) but leaves most instances (e.g. flawed protocol logic, spec misinterpretation, or non-coded design errors) unaddressed.