The NSX Tier-1 Gateway firewall must be configured to send traffic log entries to a central audit server.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-265496 | NT1F-4X-000020 | SV-265496r994857_rule | Medium |
| Description |
| Without the ability to centrally manage the content captured in the traffic log entries, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The DOD requires centralized management of all network component audit record content. Network components requiring centralized traffic log management must have the ability to support centralized management. The content captured in traffic log entries must be managed from a central location (necessitating automation). Centralized management of traffic log records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. Ensure at least one syslog server is configured on the firewall. If the product inherently has the ability to store log records locally, the local log must also be secured. However, this requirement is not met since it calls for a use of a central audit server. Satisfies: SRG-NET-000333-FW-000014, SRG-NET-000098-FW-000021 |
| STIG | Date |
| VMware NSX 4.x Tier-1 Gateway Firewall Security Technical Implementation Guide | 2024-12-20 |
Details
| Check Text (C-69413r994855_chk) |
| From an NSX Edge Node shell hosting the Tier-1 Gateway, run the following command: > get logging-servers Note: This check must be run from each NSX Edge Node hosting a Tier-1 Gateway, as they are configured individually. or If Node Profiles are used, from the NSX Manager web interface, go to System >> Configuration >> Fabric >> Profiles >> Node Profiles. Click "All NSX Nodes" and verify the syslog servers listed. If any configured logging servers are configured with a protocol of "udp", this is a finding. If any configured logging servers are not configured with a level of "info", this is a finding. If no logging-servers are configured, this is a finding. |
| Fix Text (F-69321r994856_fix) |
| To configure a profile to apply syslog servers to all NSX Edge Nodes, do the following: From the NSX Manager web interface, go to System >> Configuration >> Fabric >> Profiles >> Node Profiles. Click "All NSX Nodes" and then under "Syslog Servers" click "Add". Enter the syslog server details and choose "Information" for the log level and click "Add". or (Optional) From an NSX Edge Node shell, run the following command to clear any existing incorrect logging-servers: > clear logging-servers From an NSX Edge Node shell, run the following command to configure a tcp syslog server: > set logging-server <server-ip or server-name> proto tcp level info From an NSX Edge Node shell, run the following command to configure a primary and backup TLS syslog server: > set logging-server <server-ip or server-name> proto tls level info serverca ca.pem clientca ca.pem certificate cert.pem key key.pem From an NSX Edge Node shell, run the following command to configure a LI-TLS syslog server: > set logging-server <server-ip or server-name> proto li-tls level info serverca root-ca.crt Note: If using the protocols TLS or LI-TLS to configure a secure connection to a log server, the server and client certificates must be stored in /var/vmware/nsx/file-store/ on each NSX Edge Node appliance. Note: Configure the syslog or Simple Network Management Protocol (SNMP) server to send an alert if the events server is unable to receive events from the NSX-T and also if denial-of-service (DoS) incidents are detected. This is true if the events server is STIG compliant. |