The system must not be used as a syslog server (log host) for systems external to the enclave.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-39279 | GEN005440-ESXI5-000078 | SV-51095r1_rule | Medium |
| Description |
|---|
| Syslog messages are typically unencrypted and may contain sensitive information and are, therefore, restricted to the enclave. |
| STIG | Date |
|---|---|
| VMware ESXi Server 5.0 Security Technical Implementation Guide | 2017-01-06 |
Details
| Check Text ( C-46543r1_chk ) |
|---|
| Verify that the vSphere Syslog Collector syslog host has been justified and documented with the IAO. From the vSphere Client: Select the host and click "Configuration >> Advanced Settings >> Syslog >> Global". Verify that the 'Syslog.global.logHost' is set to the (site-specific) syslog server hostname. If the 'Syslog.global.logHost' is not restricted to the enclave, this is a finding. |
| Fix Text (F-44258r1_fix) |
|---|
| Step 1: Verify that the vSphere Syslog Collector syslog host has been configured. If not, install/enable the vSphere Syslog Collector. Step 2: From the vSphere Client: Select the host and click "Configuration >> Advanced Settings >> Syslog >> Global". Step 3: Set 'Syslog.global.logHost' to the syslog server hostname restricted to the enclave. |