CVE-2023-28970

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.

Regular updates keep contingency procedures aligned with system changes, providing structured handling for exceptional conditions that would otherwise allow unmitigated exploitation.

Policy defines checks and handling for exceptional conditions arising from security incidents.

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

Supplies advice and assistance on handling incidents, improving checks and responses to exceptional conditions.

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

Documented operating procedures may specify exception handling but do not guarantee implementation.

Logging captures unhandled exceptions, aiding detection but not preventing the weakness.

Monitoring can surface unhandled exceptions but does not enforce proper handling.

Secure SDLC mandates exception-handling requirements and testing that directly prevent improper handling of exceptional 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, defense-in-depth, distrust external input, assume-breach) plus design reviews that can catch and stop many but not all mishandlings of exceptional conditions before they reach production code; a bounded remainder (e.g. subtle runtime error paths, library-level faults, or post-review regressions) can still be present and exploitable.