NIST 800-53 r5 · Controls catalogue · Family SC
SC-35External Malicious Code Identification
Include system components that proactively seek to identify network-based malicious code or malicious websites.
Last updated: 20 August 2026 13:14 UTC
Implementations targeting this control (0)
- No implementations targeting this control yet.
ATT&CK techniques this control mitigates (3)
Weaknesses this control addresses (3)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-829 | Inclusion of Functionality from Untrusted Control Sphere | 300+ | External identification of malicious code makes inclusion of functionality from untrusted network sources substantially harder to perform undetected. |
CWE-494 | Download of Code Without Integrity Check | 200+ | Proactive network scanning for malicious code directly detects and blocks downloads that lack integrity verification. |
CWE-830 | Inclusion of Web Functionality from an Untrusted Source | 12 | Components that flag malicious websites reduce the ability to pull and render web functionality from untrusted external sources. |
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. | ||||