NIST SP 800-53 Rev 5
SC - System and Communications Protection

NIST SP 800-53 Rev 5 NIST800-SC-10: SC-10 Network Disconnect

Terminate the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 2 controls

  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 8.2.8 8.2.8 Re-authentication after 15 minutes idle

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27002:2022 · 1 control

  • 8.5 Secure authentication
  • SC-10 SC-10 Network Disconnect
  • SC-10 SC-10 Network Disconnect

SOC 2 · 1 control

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

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.

Other controls in SC - System and Communications Protection

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

NIST SP 800-53 Rev 5 NIST800-SC-10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

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. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 12 it maps to, and the evidence behind each claim, over MCP and REST.