Credential Guard Not Enabled
Credential Guard is not running, so NT hashes and Kerberos tickets held in LSASS memory can be extracted by an attacker with administrative rights on the host.
| Severity | Low |
| CVSS 3.1 | 1.9 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 1.8 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-522: Insufficiently Protected Credentials |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1003.001 LSASS Memory, T1550.002 Pass the Hash, T1550.003 Pass the Ticket |
| Category | Security Misconfiguration |
Description
Credential Guard uses virtualisation-based security (VBS) to isolate secrets that would otherwise be held in the memory of the Local Security Authority Subsystem Service (LSASS). NTLM password hashes, Kerberos ticket-granting tickets and credentials stored by applications as domain credentials are kept in an isolated process, LsaIso.exe, which the operating system cannot read even with kernel-level privileges; LSASS calls it when it needs to use them. Without Credential Guard, an attacker who gains administrative rights on a host can extract the NT hashes and Kerberos tickets of users signed in there from LSASS memory and reuse them elsewhere with pass-the-hash and pass-the-ticket, a standard way of moving through a network towards privileged accounts. Credential Guard prevents that extraction, though not other ways of capturing credentials, such as keylogging.
Credential Guard needs a 64-bit processor with virtualisation extensions and second level address translation, Secure Boot, and an edition of Windows that supports it, such as Enterprise or Education, or Windows Server. Windows 11 version 22H2 and later turn it on by default on devices that meet the requirements, but it is often absent on servers, older builds and devices where it has been turned off. Microsoft does not recommend it on domain controllers, where it adds no protection, so the finding concerns workstations and member servers. The added risk depends on which accounts sign in to the host and on other controls such as tiering, and is small where privileged accounts never sign in to ordinary systems.
Its status is shown by msinfo32 (Virtualization-based security Services Running), by the presence of the LsaIso.exe process, or by the Win32_DeviceGuard WMI class, whose SecurityServicesRunning property includes the value 1 when Credential Guard is running.
Remediation
- Enable Credential Guard on supported workstations and member servers, starting with those where administrators sign in, through Computer Configuration\Administrative Templates\System\Device Guard\Turn On Virtualization Based Security, with Credential Guard Configuration set to Enabled with UEFI lock, or Enabled without lock where it may need to be turned off remotely later. Microsoft Intune and other management tools offer the same setting.
- Check hardware and firmware support (virtualisation extensions enabled in firmware, Secure Boot) and the Windows edition, and plan the replacement of devices that cannot run it.
- Test before wide deployment: with Credential Guard running, NTLMv1, MS-CHAPv2, Digest and CredSSP cannot use the signed-in credentials for single sign-on, and Kerberos unconstrained delegation and DES encryption are not supported, so some Wi-Fi and VPN configurations and legacy applications may need changes.
- Do not enable it on domain controllers.
- Combine it with LSA protection and with tiering, which keeps privileged credentials off hosts where they could be captured in other ways.
Confirm the fix after a restart with msinfo32, or with the following query on a sample of devices, which should return a list that includes 1:
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.