SC-35 External Malicious Code Identification

Guidance: nonePolicy clause: noneWhat these mean

Baselines	Implementation level	Enhancements
Not in a baseline	System	None

Related controls: SC-7, SC-26, SC-44, SI-3, SI-4

Control statement

Include system components that proactively seek to identify network-based malicious code or malicious websites.

NIST discussion

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.

Assessment objectives (SP 800-53A)

Objectives and methods for SC-35

Determine if system components that proactively seek to identify network-based malicious code or malicious websites are included.

Examine: 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: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; system developers/integrators.

Test: Automated mechanisms supporting and/or implementing external malicious code identification.