NIST 800-53 r5 · Controls catalogue · Family SC
SC-6Resource Availability
Protect the availability of resources by allocating {{ insert: param, sc-06_odp.01 }} by {{ insert: param, sc-06_odp.02 }}.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 3 mapping(s) from 2 framework(s): CSF 2.0 2 (partial) · ASVS 5.0 1 (partial)
Implementations targeting this control (0)
- No implementations targeting this control yet.
ATT&CK techniques this control mitigates (1)
- T1564.009 Resource Forking Stealth
Weaknesses this control addresses (5)AI
CWEs ranked by how often they appear in real CVEs. The rationale describes how this control reduces exploitability of each weakness class.
| CWE | Name | CVEs | Why this control addresses it |
|---|---|---|---|
CWE-400 | Uncontrolled Resource Consumption | 3,572 | Directly mitigates uncontrolled consumption by enforcing allocation limits/quotas that preserve availability for legitimate use. |
CWE-770 | Allocation of Resources Without Limits or Throttling | 2,210 | Implements the missing limits and throttling on resource allocation that this weakness describes. |
CWE-799 | Improper Control of Interaction Frequency | 69 | Allocation policies inherently restrict interaction frequency, reducing the impact of excessive requests. |
CWE-405 | Asymmetric Resource Consumption (Amplification) | 48 | Limits amplification effects by controlling how resources are allocated under high-volume or recursive load. |
CWE-410 | Insufficient Resource Pool | 20 | Ensures a managed resource pool is maintained rather than allowing exhaustion by any single consumer. |
Top CVEs where this control is the strongest mitigation
| CVE | Risk | CVSS | EPSS | Match |
|---|---|---|---|---|
CVE-2025-61303 | 7.0 | 9.8 | 0.0042 | good |
CVE-2026-40104 | 5.5 | 8.2 | 0.0040 | good |
CVE-2024-46667 | 5.5 | 7.5 | 0.0057 | good |
CVE-2024-41743 | 5.5 | 7.5 | 0.0060 | good |
CVE-2025-70059 | 5.5 | 7.5 | 0.0034 | good |
CVE-2026-29168 UPD | 5.5 | 7.3 | 0.0063 | good |
CVE-2025-27479 | 5.5 | 7.5 | 0.0186 | good |
CVE-2025-27795 | 3.5 | 4.3 | 0.0041 | good |
CVE-2026-1850 | 3.5 | 6.5 | 0.0024 | good |
CVE-2026-3201 | 3.5 | 4.7 | 0.0018 | good |
CVE-2026-45498 KEV UPD | 10.0 | 4.0 | 0.6308 | good |
CVE-2023-44487 KEV | 10.0 | 7.5 | 1.0000 | good |
CVE-2024-31309 UPD | 8.0 | 7.5 | 0.9462 | good |
CVE-2022-30522 | 8.0 | 7.5 | 0.9041 | good |
CVE-2024-28182 UPD | 8.0 | 5.3 | 0.8496 | good |
CVE-2025-48976 UPD | 8.0 | 7.5 | 0.6326 | good |
CVE-2026-31283 | 7.0 | 9.8 | 0.0040 | good |
CVE-2024-12705 | 6.0 | 7.5 | 0.1618 | good |
CVE-2026-49160 UPD | 6.0 | 7.5 | 0.4844 | good |
CVE-2023-24998 | 6.0 | 7.5 | 0.4684 | good |
CVE-2023-26601 | 6.0 | 7.5 | 0.3407 | good |
CVE-2024-31152 | 6.0 | 5.3 | 0.1716 | good |
CVE-2025-21351 | 5.5 | 7.5 | 0.0220 | good |
CVE-2024-37358 | 5.5 | 8.6 | 0.0080 | good |
CVE-2025-26819 | 5.5 | 8.6 | 0.0051 | good |