CVE-2023-28975

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.

Secure SDLC practices directly require proper validation of all function return values and status codes.

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 lifecycle requires handling of all return values and status codes.

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 enforce, implement, or prevent the specific missing or incorrect status-code check that CWE-394 names.