Close network connections when a session ends or after a period of inactivity.
What it actually means
Network connections tied to a communications session should terminate at the end of the session or after a defined idle timeout — so abandoned sessions can't be hijacked. Practically, that means idle timeouts on your VPN, remote desktop, and any web application that handles CUI.
Pass or fail — an assessor needs a "yes" to each
- Do VPN / remote sessions terminate after a defined period of inactivity?
- Do CUI-handling applications enforce session idle timeouts?
What to have ready
- VPN / RDP / application configuration showing idle-timeout values
- Policy defining the inactivity period
Where teams trip up
- VPN sessions that stay up indefinitely
- No timeout on web apps handling CUI
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in System & Communications Protection (3.13)
3.13.1 — Protect your boundaries3.13.2 — Build security in by design3.13.3 — Separate user and admin functions3.13.4 — Stop data leaking through shared resources3.13.5 — Wall off your public-facing systems3.13.6 — Deny all, permit by exception3.13.7 — Block split tunneling on VPNs3.13.8 — Encrypt CUI in transit3.13.10 — Manage your encryption keys3.13.11 — FIPS-validated cryptography3.13.12 — Control cameras and microphones3.13.13 — Control mobile code3.13.14 — Control and monitor VoIP3.13.15 — Protect session authenticity3.13.16 — Encrypt CUI at rest