Security requirement
- a.Monitor and scan the system for vulnerabilities [Organization-defined: frequency] and when new vulnerabilities affecting the system are identified.
- b.Remediate system vulnerabilities within [Organization-defined: response times].
- c.Update system vulnerabilities to be scanned [Organization-defined: frequency] and when new vulnerabilities are identified and reported.
Discussion
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).
Tailoring decisions required
Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.
Implementation perspective
Treat Vulnerability Monitoring and Scanning as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to threat, vulnerability, likelihood, impact, criticality, and risk-response decisions for the CUI environment.
- Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
- Resolve every organization-defined parameter through an approved governance and tailoring process.
- Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
- Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
- Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.
Questions to ask
- Which CUI assets, data flows, users, and services are protected by this requirement?
- Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
- Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
- What change, incident, or threshold should trigger reassessment?
Evidence and validation
- risk assessments and threat models
- vulnerability findings and prioritization records
- supply-chain risk assessments
- risk response and acceptance decisions
Common failure patterns
- risk registers detached from technical evidence
- vulnerability severity treated as business impact
- assessments not updated after material change
- accepted risks without owners or expiration
Assessment objectives and methods
Assessment objectives (7)
- a.
the system is monitored for vulnerabilities [Organization-defined: frequency].
- a.
the system is scanned for vulnerabilities [Organization-defined: frequency].
- b.
system vulnerabilities are remediated within [Organization-defined: response times].
- a.
the system is monitored for vulnerabilities when new vulnerabilities that affect the system are identified.
- a.
the system is scanned for vulnerabilities when new vulnerabilities that affect the system are identified.
- c.
system vulnerabilities to be scanned are updated [Organization-defined: frequency].
- c.
system vulnerabilities to be scanned are updated when new vulnerabilities are identified and reported.
Examine
- risk assessment policy and procedures
- procedures for vulnerability scanning
- patch and vulnerability management records
- vulnerability scanning tools and configuration documentation
- vulnerability scanning results
- risk assessment
- risk assessment report
- system security plan
- other relevant documents or records
Interview
- personnel with risk assessment and vulnerability scanning responsibilities
- personnel with vulnerability scan analysis responsibilities
- personnel with vulnerability remediation responsibilities
- personnel with information security responsibilities
- system administrators
Test
- processes for vulnerability monitoring, scanning, analysis, and remediation
- mechanisms for supporting or implementing vulnerability monitoring, scanning, analysis, and remediation
Source NIST SP 800-53 controls
These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.
Authoritative sources
- NIST SP 800-171 Revision 3 official publication ↗
- NIST SP 800-171A Revision 3 official publication ↗
- NIST OSCAL Content release used for this import ↗
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.