Vulnerability Monitoring and Scanning (03.11.02)_vulnerability-monitoring-and-scanning

Vulnerability Monitoring and Scanning (03.11.02) Vulnerability Monitoring and Scanning

High-Level Description

Family: Risk Assessment Framework: NIST SP 800-171 Rev 3 Applicability: Systems processing, storing, or transmitting CUI

Monitor and scan the system for vulnerabilities [organization-defined] and when new vulnerabilities affecting the system are identified. Remediate system vulnerabilities within [organization-defined]. Update system vulnerabilities to be scanned [organization-defined] and when new vulnerabilities are identified and reported.

What to Check

• Verify Vulnerability Monitoring and Scanning (03.11.02) Vulnerability Monitoring and Scanning is implemented for CUI systems
• Review SSP documentation for Vulnerability Monitoring and Scanning (03.11.02)
• Validate CMMC Level 2 assessment objective for Vulnerability Monitoring and Scanning (03.11.02)
• Confirm POA&M addresses any gaps for Vulnerability Monitoring and Scanning (03.11.02)

How to Test

Step 1: Review System Security Plan

Examine the SSP for Vulnerability Monitoring and Scanning (03.11.02) implementation description and responsible parties.

Step 2: Assess Implementation

# Verify security controls protecting CUI
# Check access controls, encryption, monitoring as applicable

# For Linux systems:
ls -la /etc/security/ 2>/dev/null
grep -r "CUI\|controlled" /etc/security/ 2>/dev/null

# For cloud:
# Use cloud-audit-mcp tools to assess posture

Step 3: CMMC Assessment Validation

Verify this requirement passes CMMC Level 2 assessment methodology per SP 800-171A Rev 3.

Tools

Remediation Guide

Requirement Statement

Monitor and scan the system for vulnerabilities [organization-defined] and when new vulnerabilities affecting the system are identified. Remediate system vulnerabilities within [organization-defined]. Update system vulnerabilities to be scanned [organization-defined] and when new vulnerabilities are identified and reported.

Supplemental Guidance

Organizations determine the required vulnerability scanning for system components and ensure that potential sources of vulnerabilities (e.g., networked printers, scanners, and copiers) are not overlooked. Vulnerability analyses for custom software may require additional approaches, such as static analysis, dynamic analysis, or binary analysis. Organizations can use these approaches in source code reviews and tools (e.g., static analysis tools, web-based application scanners, binary analyzers). Vulnerability scanning includes scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating flow control mechanisms. To facilitate interoperability, organizations consider using scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention. Sources for vulnerability information also include the Common Weakness Enumeration (CWE) listing, the National Vulnerability Database (NVD), and the Common Vulnerability Scoring System (CVSS).

Risk Assessment

CWE Categories

References

• NIST SP 800-171 Rev 3
• NIST SP 800-171A Rev 3 (Assessment)
• CMMC Model Overview
• NIST OSCAL Content

Checklist

• SSP documents Vulnerability Monitoring and Scanning (03.11.02) implementation
• Evidence of operating effectiveness collected
• POA&M addresses any gaps
• CMMC assessment objective met
• Continuous monitoring active