NIST SP 800-171 & CMMC 2.0 Control 3.1.11 Requirement:

Terminate (automatically) user sessions after a defined condition.

NIST SP 800-171 & CMMC 2.0 3.1.11 Requirement Explanation:

By automatically terminating sessions you reduce the risk of an attacker gaining access to a user's session.

Example NIST SP 800-171 & CMMC 2.0 3.1.11 Implementation:

Define a condition when user sessions are automatically terminated. An example is terminating a session after one hour of inactivity. Apply this policy to your system where feasible. Examples include terminating RDP sessions and SSH sessions after 1 hour of inactivity. You should also terminate VPN sessions and other remote sessions after a period of inactivity.

NIST SP 800-171 & CMMC 2.0 3.1.11 Scenario(s):

- Scenario 1:

Your company has a policy requiring user sessions to be automatically terminated after 1 hour of inactivity. You have several Linux servers and network devices to which you connect to using SSH. To meet you policy requirement you configure the SSH sessions to terminate after 1 hour of inactivity.
 

Discover Our NIST SP 800-171 & CMMC 2.0 Solutions:

 /assets/images/app/complaince_accelerator.gif

Compliance Accelerator

Power through compliance. Meet and maintain your NIST SP 800-171 & CMMC 2.0 compliance requirements.
 /assets/images/app/quantum_accelerator.gif

Quantum Assessor

Transform your business. Create new revenue streams and provide scalability for your NIST SP 800-171 and CMMC 2.0 services.
 /assets/images/app/supply_chain_verifier.gif

Supply Chain Verifier

Trust is everything. Verify, monitor, and support subcontactor compliance.