Tenable / Nessus for NIST SP 800-171 Revision 3
What Tenable / Nessus’s data evidences toward NIST SP 800-171 Revision 3 today, and how to connect it.
What Tenable / Nessus evidences here
- Vulnerabilities feeds Risk Assessment
This is where Tenable / Nessus’s data is documented as relevant on our NIST SP 800-171 Revision 3 page — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.
How you connect Tenable / Nessus
Scan findings and scanned assets from Tenable.io or Nessus, including how long findings have been open against your remediation SLA.
About NIST SP 800-171 Revision 3
All 97 Revision 3 requirements for protecting CUI in nonfederal systems, in NIST's own 03.xx.xx numbering with the verbatim requirement text and the SP 800-171A evidence lists.
Revision 3 numbering, not the CMMC practice IDs: CMMC Level 2 is still defined by the Revision 2 requirements. The 33 requirements Revision 3 withdrew are not listed.