External Malicious Code Identification
LOW MODERATE HIGHRequirements NIST SOURCE
Include system components that proactively seek to identify network-based malicious code or malicious websites.
Discussion (NIST Supplemental Guidance)
External malicious code identification differs from decoys in SC-26 in that the components actively probe networks, including the Internet, in search of malicious code contained on external websites. Like decoys, the use of external malicious code identification techniques requires some supporting isolation measures to ensure that any malicious code discovered during the search and subsequently executed does not infect organizational systems. Virtualization is a common technique for achieving such isolation.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SC-35 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- system components that proactively seek to identify network-based malicious code or malicious websites are included.
Examine
[SELECT FROM: System and communications protection policy; procedures addressing external malicious code identification; system design documentation; system configuration settings and associated documentation; system components deployed to identify malicious websites and/or web-based malicious code; system audit records; system security plan; other relevant documents or records].
Interview
[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; system developers/integrators].
Test
[SELECT FROM: Automated mechanisms supporting and/or implementing external malicious code identification].
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SC-35. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- System and communications protection policy
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Automated mechanisms supporting and/or implementing external malicious code identification
Other Records
- procedures addressing external malicious code identification
- system components deployed to identify malicious websites and/or web-based malicious code
- system audit records
- other relevant documents or records