NIST 800-53 r5 · Controls catalogue · Family SI
SI-21Information Refresh
Refresh {{ insert: param, si-21_odp.01 }} at {{ insert: param, si-21_odp.02 }} or generate the information on demand and delete the information when no longer needed.
Last updated: 20 August 2026 20:22 UTC
Implementations targeting this control (0)
- No implementations targeting this control yet.
ATT&CK techniques this control mitigates (0)
- No ATT&CK techniques mapped to this control yet.
Weaknesses this control addresses (6)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-200 | Exposure of Sensitive Information to an Unauthorized Actor | 11,000+ | Deleting information when no longer needed directly reduces the window during which sensitive data can be exposed to unauthorized actors. |
CWE-613 | Insufficient Session Expiration | 600+ | Timed refresh of session-related information or on-demand generation plus deletion implements proper session expiration. |
CWE-459 | Incomplete Cleanup | 200+ | The explicit delete step when information is no longer needed implements the cleanup that this weakness omits. |
CWE-212 | Improper Removal of Sensitive Information Before Storage or Transfer | 100+ | The generate-on-demand-and-delete requirement enforces removal of sensitive information before storage or transfer, preventing improper retention. |
CWE-524 | Use of Cache Containing Sensitive Information | 66 | Refreshing cached data or generating it ephemerally and deleting afterward directly mitigates storage of sensitive information in caches. |
CWE-226 | Sensitive Information in Resource Not Removed Before Reuse | 36 | Periodic refresh or explicit deletion before reuse prevents sensitive information from remaining in a reusable resource. |
Top CVEs where this control is the strongest mitigation
| CVE | Risk | CVSS | EPSS | Match |
|---|---|---|---|---|
| No CVEs annotated to this control yet — the per-CVE backfill is in progress. | ||||