SI.L1-B.1.XV
System & File Scanning
FCI Data
Security Requirement
Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.
USU Policy, Procedures, and Standards
University Policy 5200: Information Security and Appropriate Use
- Section 2.3 - Device and Endpoint Management and Security
- Section 3.3 - Information Technology and IT Staff
Requires all devices to meet security standards, including endpoint protection against unauthorized access, malware, and other threats. IT staff are responsible for implementing endpoint protections and keeping them updated, which encompasses scheduled and real-time scanning functionality.
NIST Cybersecurity Framework v2
- Protect (PR): PR.PT-03 - Malicious code is detected and addressed.
- Detect (DE): DE.CM-04 - Monitoring is performed to detect malicious code.
- Detect (DE): DE.CM-02 - Detection processes are tested and validated regularly.
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 how and where periodic scanning for malicious code is performed.
- List how real-time scanning is configured for files downloaded from external sources (e.g., email, websites, USB devices).
- List how scanning results are monitored, logged, and responded to.
- List any additional processes to ensure malicious code scanning remains current and effective.
Document How
- the frequency for malicious code scans is defined
- malicious code scans are performed with the defined frequency
- real-time malicious code scans of files from external sources as files are downloaded, opened, or executed are performed
Example
USU's EDR performs real-time scanning of all file downloads, email attachments, and executable files. Full system scans are scheduled via the EDR console as needed. Alerts are integrated into the SIEM platform for continuous monitoring. Remediation steps and user notifications are automated based on severity, and all incidents are tracked via the ticketing system.
How might an auditor assess this control?
Method
- Examine:
- Review update policies, EDR platform settings, and update compliance logs.
- Interview:
- Ask administrators how updates are applied, monitored, and responded to.
- Test:
- Verify current update version on a sample endpoint and compare against latest available definition.
Objects (examples of items you could present to the auditor)
- Update Policy: Documentation describing how updates are managed and enforced.
- Update Logs: Showing successful application of malicious code protection updates.
- Alerting Records: Notifications for failed or missing updates.
- Support Tickets: Showing follow-up actions for systems that failed to update.
- Training Records: Staff knowledge of update requirements and procedures.