The NSX Manager must terminate all network connections associated with a session after five minutes of inactivity.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| high | V-265327 | SRG-APP-000190-NDM-000267 | NMGR-4X-000052 | SV-265327r994204_rule | 2024-12-13 | 1 |
Description
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take immediate control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.
Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or deallocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Satisfies: SRG-APP-000190-NDM-000267, SRG-APP-000186-NDM-000266, SRG-APP-000400-NDM-000313
ℹ️ Check
From an NSX Manager shell, run the following command:
> get service http | find Session
Expected result:
Session timeout: 300
If the session timeout is not configured to 300 or less, this is a finding.
From an NSX Manager shell, run the following command:
> get cli-timeout
Expected result:
300 seconds
If the CLI timeout is not configured to 300 or less, this is a finding.
✔️ Fix
From an NSX Manager shell, run the following commands:
> set service http session-timeout 300
> set cli-timeout 300