Details

Log data is essential in the investigation of events. If log data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve.

In addition, access to log records provides information an attacker could potentially use to their advantage since each event record might contain communication ports, protocols, services, trust relationships, user names, etc. The vSphere UI restricts all access to log file by default, but this configuration must be verified.

Satisfies: SRG-APP-000118-WSR-000068, SRG-APP-000119-WSR-000069, SRG-APP-000120-WSR-000070

Solution

At the command prompt, execute the following commands:

# chmod 600 /storage/log/vmware/vsphere-ui/logs/

# chown vsphere-ui:users /storage/log/vmware/vsphere-ui/logs/

Note: Substitute with the listed file.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-7_STIG.zip

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-9
• CAT|II
• CCI|CCI-000162
• CCI|CCI-000163
• CCI|CCI-000164
• Rule-ID|SV-239688r679170_rule
• STIG-ID|VCUI-67-000007
• Vuln-ID|V-239688

Source

• Tenable.com/audits