CCI-002361

Automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

6 rules found Severity: Medium

30 rules found Severity: Medium

31 rules found Severity: Medium

33 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

1 rule found Severity: Low

1 rule found Severity: Medium

2 rules found Severity: Low

1 rule found Severity: Medium

1 rule found Severity: High

1 rule found Severity: Medium

4 rules found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

3 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

1 rule found Severity: Low

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

2 rules found Severity: Medium

1 rule found Severity: Medium

CCI-002361

Set Interactive Session Timeout

Set SSH Client Alive Count Max to zero

Set SSH Client Alive Count Max

Set SSH Client Alive Interval

Compliance Guardian must provide automated mechanisms for supporting account management functions.

The BlackBerry Enterprise Mobility Server (BEMS) must be configured with an inactivity timeout of 15 minutes or less.

The CA API Gateway providing user access control intermediary services must automatically terminate a user session when organization-defined conditions or trigger events that require a session disconnect occur.

The DBN-6300 must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.

The Lifetime Minutes and Renewal Threshold Minutes Login Session Controls must be set to 10 and 0 respectively in Docker Enterprise.

The Docker Enterprise per user limit login session control must be set per the requirements in the System Security Plan (SSP).

The storage system must terminate all network connections associated with a communications session at the end of the session, at shutdown, or after 10 minutes of inactivity.

The DataPower Gateway must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.

IBM Aspera Console interactive session must be terminated after 10 minutes of inactivity for non-privileged and privileged sessions.

IBM Aspera Faspex interactive session must be terminated after 10 minutes of inactivity for non-privileged and privileged sessions.

The IBM Aspera Shares interactive session must be terminated after 10 minutes of inactivity for non-privileged and privileged sessions.

The MQ Appliance messaging server must automatically terminate a SSH user session after organization-defined conditions or trigger events requiring a session disconnect.

The MQ Appliance must automatically terminate a WebGUI user session after 600 seconds of idle time.

DB2 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The WebSphere Application Server admin console session timeout must be configured.

The MQ Appliance network device must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.

The Ivanti MobileIron Core server must automatically terminate a user session after an organization-defined period of user inactivity.

The Exchange Receive connector timeout must be limited.

SQL Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

Nutanix AOS must automatically terminate a user session after inactivity time-outs have expired or at shutdown.

Riverbed Optimization System (RiOS) must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.

Innoslate must use multifactor authentication for network access to privileged and non-privileged accounts.

Tanium must set an absolute timeout for sessions.

Tanium must set an inactive timeout for sessions.

The Tanium application must set an absolute timeout for sessions.

The Tanium application must set an inactive timeout for sessions.

Tanium Operating System (TanOS) must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The Ubuntu operating system must automatically terminate all network connections associated with SSH traffic at the end of the session or after 10 minutes of inactivity.

MongoDB must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The DBMS must terminate the network connection associated with a communications session at the end of the session or after 15 minutes of inactivity.

PostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The Red Hat Enterprise Linux operating system must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive.

The Red Hat Enterprise Linux operating system must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive.

The EDB Postgres Advanced Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The BIG-IP APM module access policy profile must be configured to automatically terminate user sessions for users connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.

The BIG-IP Core implementation must automatically terminate a user session for a user connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.

Idle timeout for the management application must be set to 10 minutes.

CA IDMS must automatically terminate a terminal session after organization-defined conditions or trigger events of terminal inactivity time.

CA IDMS must automatically terminate a batch external request unit after organization-defined conditions or trigger events after the batch program abnormally terminates.

CA IDMS must automatically terminate an external run-unit after organization-defined conditions or trigger events of time waiting to issue a database request.

CA IDMS must automatically terminate a task or session after organization-defined conditions or trigger events of time waiting to get a resource and/or time of inactivity.

The Ubuntu operating system must automatically terminate a user session after inactivity timeouts have expired.

SSMC must terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity.

SSMC web server must set an absolute timeout for sessions.

SSMC web server must set an inactive timeout for sessions.

SSMC web server must set an inactive timeout for shell sessions.

The HPE 3PAR OS must be configured to terminate all network connections associated with a communications session at the end of the session, or after 10 minutes of inactivity.

AIX must config the SSH idle timeout interval.

AIX must set inactivity time-out on login sessions and terminate all login sessions after 10 minutes of inactivity.

HTTP session timeout must be configured.

The Ivanti EPMM server must automatically terminate a user session after an organization-defined period of user inactivity.

The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

Azure SQL Database must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

The Idle Time-out monitor for each IIS 10.0 website must be enabled.

The IIS 10.0 websites connectionTimeout setting must be explicitly configured to disconnect an idle session.

Microsoft Intune service must initiate a session lock after a 15-minute period of inactivity.

The machine inactivity limit must be set to 15 minutes, locking the system with the screensaver.

The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive.

The MySQL Database Server 8.0 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

Automation Controller must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types.

The Automation Controller web server must manage sessions.

SLEM 5 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive.

Splunk Enterprise idle session timeout must be set to not exceed 15 minutes.

Splunk Enterprise idle session timeout must be set to not exceed 15 minutes.

TOSS must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.

The web server must set an absolute session timeout value of eight hours or less.

The web server must set an inactive timeout for sessions.

NixOS must terminate all SSH connections after 10 minutes of becoming unresponsive.

The Apache web server must invalidate session identifiers upon hosted application user logout or other session termination.

The Apache web server must set an inactive timeout for sessions.

The Apache web server must set an absolute timeout for sessions.

The Apache web server must set an inactive timeout for completing the TLS handshake

The Apache web server must set an inactive timeout for completing the TLS handshake.

The macOS system must configure SSHD Channel Timeout to 900.

The macOS system must configure SSHD unused connection timeout to 900.