CVE-2023-2253

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

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.

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

Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.

Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.

Vulnerability identification processes can discover and record this class of API-related weakness.

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

Secure SDLC practices (coding standards, reviews, testing) directly prevent undefined behavior from invalid API inputs.