NIST SP 800-171 Rev 3 03.13.09: Network Disconnect

What else in your programme already covers this

This control maps to 10 controls across 10 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

C5 (Germany) · 1 control

C5-PSS-06 Session Management

CMMC 2.0 · 1 control

SC.L2-3.13.9 Connections Termination

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-UEM-06 Automatic Lock Screen

FedRAMP High · 1 control

SC-10 Network Disconnect

HIPAA Security Rule · 1 control

164.312(a)(2)(iii) Automatic Logoff (Addressable)

NIST SP 800-53 Rev 5 · 1 control

NIST800-SC-10 SC-10 Network Disconnect

NIST SP 800-66 Rev 2 · 1 control

164.312(a)(2)(iii) Automatic Logoff (Addressable)

PCI DSS 4.0 · 1 control

8.2.8 8.2.8 Re-authentication after 15 minutes idle

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.13.09 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

If you hold PCI DSS 4.071.1% covered · 28 gaps If you hold C5 (Germany)68% covered · 31 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gaps If you hold ISO 27001:202262.9% covered · 36 gaps If you hold CIS Controls v853.6% covered · 45 gaps If you hold NIST SP 800-161 Rev 152.6% covered · 46 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

See the released pairs, $299 each Browse the graph free