CVE-2023-0397

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

Establishing and monitoring system metrics with correlation and response actions helps identify and address improper handling of exceptional conditions.

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.

Testing verifies the system's ability to detect, handle, and recover from exceptional conditions as part of the plan, reducing exploitability of improper exception handling.

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.

A.8.25 mandates security requirements, checkpoints, secure coding, testing and developer capability in the SDLC which reaches improper initialization as a design/coding defect, but leaves a bounded remainder (e.g. initialization of third-party components or libraries chosen in procurement, and post-deployment configuration defaults).

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 (least privilege, default-deny, fail-securely, distrust-external-input, hardening) plus explicit design reviews that can catch and block many uninitialized-resource cases before they ship, but leaves a bounded remainder (e.g. vendor libraries, runtime-initialization bugs, or post-review code changes) that can still be present and exploitable.

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.

Security testing can detect uninitialized variables but does not itself enforce initialization practices.