Details
When accessing the VM console the guest OS must be locked when the last console user disconnects, limiting the possibility of session hijacking. This setting only applies to Windows-based VMs with VMware tools installed.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
From the vSphere Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters >> Edit Configuration. Find or create the ‘tools.guest.desktop.autolock’ value and set it to ‘true’.
Note: The VM must be powered off to modify the advanced settings through the vSphere Web Client. It is recommended to configure these settings with PowerCLI as this can be done while the VM is powered on. In this case the modified settings will not take effect until a cold boot of the VM.
or
From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command:
If the setting does not exist, run:
Get-VM ‘VM Name’ | New-AdvancedSetting -Name tools.guest.desktop.autolock -Value true
If the setting exists, run:
Get-VM ‘VM Name’ | Get-AdvancedSetting -Name tools.guest.desktop.autolock | Set-AdvancedSetting -Value true
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system VMware.
References
- 800-53|CM-6b.
- CAT|II
- CCI|CCI-000366
- Rule-ID|SV-237101r640140_rule
- STIG-ID|VMCH-65-000047
- STIG-Legacy|SV-104477
- STIG-Legacy|V-94647
- Vuln-ID|V-237101