CVE-2023-28965

Implements explicit check and handling for the exceptional condition of audit logging process failure.

Provides a defined response to detected conditions by restricting operation, ensuring exceptional conditions are handled rather than ignored or mishandled.

Contingency training equips users with defined procedures to check and respond to exceptional conditions during disruptions, reducing exploitation of mishandled errors.

Performing IR tests ensures exceptional conditions are properly checked and handled to enable effective response.

Testing and evaluation exercises error paths and exceptional conditions, surfacing improper handling that is then remediated through the defined process.

Mandates explicit, predictable handling of exceptional conditions rather than undefined continuation.

Requires systematic prediction and handling of failure conditions, reducing the impact of unhandled exceptional states.

The required verification process supplies the missing checks for exceptional conditions affecting security functions.

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.

Secure development life cycle mandates exception handling and input validation that directly prevent missing checks for unusual conditions.

A.8.26 only requires that security requirements (including resilience against attacks like SQL injection) be identified and specified during development or acquisition; it does not itself remove, fix, or eliminate any exceptional-condition handling defects already present in code.

A.8.27 mandates security-by-design principles (fail securely, least privilege, distrust external input, security-oriented design reviews) that reach some but not most CWE-754 cases; many exceptional-condition checks live in low-level code paths outside architecture-level engineering.

A.8.28 mandates secure coding practices, principles, defect removal during coding/review, and prohibiting insecure techniques that directly produce improper exception handling; this removes most instances of the first-party code defect, with a bounded remainder in incomplete adoption or edge-case defects not captured by the baseline.