Details
Logging must be started as soon as possible when a service starts and 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.
On the VCSA, the vmware-vmon service starts up the JVMs for various vCenter processes, including vSphere Client, and the individual json config files control the early jvm logging. Ensuring these json files are configured correctly enables early Java stdout and stderr logging.
Solution
Navigate to and open /etc/vmware/vmware-vmon/svcCfgfiles/vsphere-client.json.
Below the last line of the ‘PreStartCommandArg’ block, add the following line:
‘StreamRedirectFile’: ‘%VMWARE_LOG_DIR%/vmware/vsphere-client/logs/vsphere-client-runtime.log’,
Restart the appliance for changes to take effect.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.
References
- 800-53|AU-12a.
- CAT|II
- CCI|CCI-000169
- Rule-ID|SV-239752r679483_rule
- STIG-ID|VCFL-67-000010
- Vuln-ID|V-239752