CVE-2023-25156

This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.

This control directly enforces limits on consecutive invalid logon attempts and automatic response (e.g., lockout) to prevent brute-force exploitation of authentication mechanisms.

Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.

Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.

Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.

Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.

Specific conditions can include excessive failed attempts, triggering stronger authentication that restricts brute-force exploitation.

Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.

Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.

Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.

Monitoring capacity and taking action to maintain availability directly reduces unchecked resource allocation.

Generating auth logs enables later detection or forensics but does not itself restrict attempts.