SI.L1-B.1.XIII
Malicious Code Protection
FCI Data
Security Requirement
Provide protection from malicious code at appropriate locations within organizational information systems.
USU Policy, Procedures, and Standards
University Policy 5200: Information Security and Appropriate Use
- Section 2.3 - Device and Endpoint Management and Security
- Section 2.5 - Incident Management
- Section 3.3 - Information Technology and IT Staff
Requires secure configuration and timely updates to protect university devices. Aligns with patch management expectations, though timeframes are not explicitly stated. IT staff are tasked with “timely incident response” and “consistent application of security patches, configurations, reporting, and updates.” This strongly aligns with flaw identification, reporting, and remediation. Incidents (including vulnerabilities) must be reported according to established procedures at https://infosec.usu.edu.
NIST Cybersecurity Framework v2
- Protect (PR): PR.IP-12 - Vulnerabilities are identified and managed in a timely manner.
- Detect (DE): DE.CM-08 - Vulnerability scans are performed to identify flaws.
- Respond (RS): RS.MI-01 - Incidents (including vulnerabilities) are analyzed and prioritized.
- Respond (RS): RS.MI-02 - Incidents are resolved based on severity and impact.
Implementation Details
Documentation should include details to meet the Security Requirement for this control. Complete this list for each system or systems that process or access FCI data:
- List where and how malicious code protection (e.g., antivirus, anti-malware) is implemented.
- List how real-time scanning and regular updates are enforced.
- List how alerts and incidents related to malicious code are monitored and responded to.
- List any additional measures in place to detect, prevent, or recover from malicious code activity.
Document How
- designated locations for malicious code protection are identified
- protection from malicious code at designated locations is provided
Example
All endpoints and servers at USU are protected by EDR, which provides real-time detection and response for malicious code. The system automatically updates definitions and scans downloaded files, email attachments, and removable media. Alerts are integrated with the SIEM platform and monitored by security analysts. Web traffic is filtered, and staff receive security awareness training annually.
How might an auditor assess this control?
Method
- Examine:
- Review endpoint protection configurations, update schedules, and malicious code incident logs.
- Interview:
- Ask IT and security teams how malware is detected, blocked, and how users are trained.
- Test:
- Check that systems have functioning protection, verify alerting, and test detection of a benign file.
Objects (examples of items you could present to the auditor)
- EDR Configuration Settings: Showing real-time scanning, alerting, and update status.
- Alert Logs: Showing recent detections and responses to malicious activity.
- Training Records: Demonstrating user awareness efforts.
- Email Filtering Logs: Showing blocked malicious attachments or links.
- Incident Reports: Documented responses to malware detections.
- Policy Documentation: Describing required protection methods and responsibilities.