RA-5(5) Vulnerability monitoring | privileged access
What the standard requires
Implement privileged access authorization to [system components] for [vulnerability scanning activities].
Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), 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
Microsoft Defender for Endpoint
Vulnerabilities
Orca Security
Vulnerabilities
Qualys VMDR
Vulnerabilities
Tenable / Nessus
Vulnerabilities
These connectors produce data relevant to FedRAMP Moderate’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.
Track RA-5(5) with evidence behind it
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.