03.11.02 Vulnerability Monitoring and Scanning
What the standard requires
a. Monitor and scan the system for vulnerabilities [frequency] and when new vulnerabilities affecting the system are identified. b. Remediate system vulnerabilities within [response times]. c. Update system vulnerabilities to be scanned [frequency] and when new vulnerabilities are identified and reported.
Quoted verbatim from NIST SP 800-171 Rev 3, which is in the public domain.
Cross-framework mappings
No cross-framework mapping is seeded for this control. That is stated rather than filled in: a mapping nobody authored is worse than a gap you can see.
Integrations that carry evidence for this family
These connectors produce data relevant to NIST SP 800-171 Revision 3’s Risk Assessment family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.