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: 15 October 2026 20:36 UTC
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-assisted
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 | 4,300+ | 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,800+ | Implements the missing limits and throttling on resource allocation that this weakness describes. |
CWE-799 | Improper Control of Interaction Frequency | 87 | Allocation policies inherently restrict interaction frequency, reducing the impact of excessive requests. |
CWE-405 | Asymmetric Resource Consumption (Amplification) | 72 | Limits amplification effects by controlling how resources are allocated under high-volume or recursive load. |
CWE-410 | Insufficient Resource Pool | 21 | 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-2026-82435 | 7.4 | 9.8 | 0.0065 | partial |
CVE-2024-2511 UPD | 7.0 | 5.9 | 0.5242 | good |
CVE-2025-0453 UPD | 6.8 | 7.5 | 0.1103 | good |
CVE-2026-20295 | 6.3 | 8.6 | 0.0055 | partial |
CVE-2025-27479 UPD | 6.2 | 7.5 | 0.0223 | good |
CVE-2026-34183 UPD | 6.1 | 7.5 | 0.0105 | good |
CVE-2025-2240 UPD | 6.0 | 7.5 | 0.0102 | good |
CVE-2026-67211 | 6.0 | 7.5 | 0.0074 | partial |
CVE-2026-91752 UPD | 6.0 | 7.5 | 0.0074 | partial |
CVE-2026-55149 UPD | 6.0 | 7.5 | 0.0072 | partial |
CVE-2026-85324 | 6.0 | 7.5 | 0.0077 | partial |
CVE-2025-41653 UPD | 5.9 | 7.5 | 0.0059 | good |
CVE-2026-88045 | 5.9 | 7.5 | 0.0063 | partial |
CVE-2026-77301 | 5.9 | 7.5 | 0.0061 | partial |
CVE-2026-94626 UPD | 5.9 | 7.5 | 0.0063 | partial |
CVE-2026-58268 | 5.9 | 7.5 | 0.0061 | partial |
CVE-2026-59991 | 5.9 | 7.5 | 0.0052 | partial |
CVE-2026-77322 | 5.9 | 7.5 | 0.0052 | partial |
CVE-2026-92550 UPD | 5.9 | 7.5 | 0.0048 | partial |
CVE-2026-109226 | 5.9 | 7.5 | 0.0046 | partial |
CVE-2020-37280 | 5.9 | 7.5 | 0.0054 | partial |
CVE-2026-102731 | 5.8 | 7.5 | 0.0043 | partial |
CVE-2026-107223 | 5.8 | 7.5 | 0.0034 | partial |
CVE-2026-107227 | 5.8 | 7.5 | 0.0043 | partial |
CVE-2026-108106 | 5.8 | 7.5 | 0.0037 | partial |