Update Vulnerabilities to Be Scanned
✓ LOW ✓ MODERATE ✓ HIGHRequirements NIST SOURCE
Update the system vulnerabilities to be scanned [one of: ; prior to a new scan; when new vulnerabilities are identified and reported].
Discussion (NIST Supplemental Guidance)
Due to the complexity of modern software, systems, and other factors, new vulnerabilities are discovered on a regular basis. It is important that newly discovered vulnerabilities are added to the list of vulnerabilities to be scanned to ensure that the organization can take steps to mitigate those vulnerabilities in a timely manner.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for RA-5(2) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- one or more of the following PARAMETER VALUES is/are selected: { <RA-05(02)_ODP[02] frequency>; prior to a new scan; when new vulnerabilities are identified and reported};
- the frequency for updating the system vulnerabilities to be scanned is defined (if selected);
- the system vulnerabilities to be scanned are updated <RA-05(02)_ODP[01] SELECTED PARAMETER VALUES>.
Examine
[SELECT FROM: Procedures addressing vulnerability scanning; assessment report; vulnerability scanning tools and associated configuration documentation; vulnerability scanning results; patch and vulnerability management records; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with vulnerability scanning responsibilities; organizational personnel with vulnerability scan analysis responsibilities; organizational personnel with security responsibilities; system/network administrators].
Test
[SELECT FROM: Organizational processes for vulnerability scanning; mechanisms/tools supporting and/or implementing vulnerability scanning].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for RA-5(2). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- system security plan
Configuration
- vulnerability scanning tools and associated configuration documentation
Testing
- Organizational processes for vulnerability scanning
- mechanisms/tools supporting and/or implementing vulnerability scanning
Other Records
- Procedures addressing vulnerability scanning
- assessment report
- vulnerability scanning results
- patch and vulnerability management records
- other relevant documents or records