The vCenter Lookup service must initiate session logging upon startup.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-259039 | SRG-APP-000092-AS-000053 | VCLU-80-000013 | SV-259039r960888_rule | 2024-07-11 | 2 |
| Description |
|---|
| Logging must be started as soon as possible when a service starts and as late as possible when a service is stopped. Many forms of suspicious actions can be detected by analyzing logs for unexpected service starts and stops. Also, by starting to log immediately after a service starts, it becomes more difficult for suspicious activity to go unlogged. |
| ℹ️ Check |
|---|
| At the command prompt, run the following command: # grep StreamRedirectFile /etc/vmware/vmware-vmon/svcCfgfiles/lookupsvc.json Expected output: "StreamRedirectFile": "%VMWARE_LOG_DIR%/vmware/lookupsvc/lookupsvc_stream.log", If no log file is specified for the "StreamRedirectFile" setting, this is a finding. |
| ✔️ Fix |
|---|
| Navigate to and open: /etc/vmware/vmware-vmon/svcCfgfiles/lookupsvc.json Below the last line of the "PreStartCommandArg" block, add the following line: "StreamRedirectFile": "%VMWARE_LOG_DIR%/vmware/lookupsvc/lookupsvc_stream.log", Restart the service with the following command: # vmon-cli --restart lookupsvc |