Implementation guidance for Australian Essential Eight controls in Microsoft environments - ISM controls with PSPF mappings
| Property | Value |
|---|---|
| ISM Control | ISM-1686 |
| Revision | 1 |
| Updated | Dec-23 |
| Guideline | Not provided |
| Section | Authentication hardening |
| Topic | Protecting credentials |
| Essential Eight | ML3 |
| PSPF Levels | NC, OS, P, S, TS |
Credential Guard protects credentials by isolating secrets with virtualization-based security, reducing the risk of credential theft. Enable Credential Guard via an Intune device configuration profile to ensure consistent deployment across devices.12
What Credential Guard protects against:
Credential Guard uses Virtualization-Based Security (VBS) to isolate the Local Security Authority (LSA) process. It splits lsass.exe into a host process and a protected companion (LSAIso.exe) running inside a hypervisor-enforced Virtual Secure Mode (VSM) kernel. Credentials such as NTLM hashes and Kerberos TGTs are stored only within the VSM memory, which the host OS cannot access even with SYSTEM privileges.
| Attack technique | Protected? | Notes |
|---|---|---|
| Pass-the-Hash (PtH) | Yes | LSASS memory is isolated; Mimikatz-style tools cannot read hashes3 |
| Pass-the-Ticket (PtT) | Yes | Kerberos TGTs stored in protected VSM enclave |
| Golden Ticket | Partial | Protects TGTs on endpoints, but KRBTGT compromise at the DC is still possible |
| Credential dumping (Mimikatz, procdump) | Yes | Direct LSASS memory reads are blocked |
| Unconstrained Kerberos delegation | Blocked | Credential Guard disables unconstrained delegation; switch to constrained |
| Application-level credential storage | Protected | Credential Manager entries encrypted within VSM |
Hardware requirements beyond TPM + Secure Boot:
Known incompatibilities:
| Component | Issue |
|---|---|
| Third-party Security Support Providers (SSPs/APs) that request password hashes | Blocked; must be replaced with Microsoft-signed SSPs |
| Kerberos unconstrained delegation and DES encryption | Disabled by Credential Guard; migrate to constrained delegation |
| MS-CHAPv2, Digest, CredSSP | Legacy auth protocols may be blocked; migrate to EAP-TLS/PEAP |
| VMware Workstation (when VBS is enabled on host) | Incompatible; use a compatible hypervisor or disable Credential Guard on the workstation |
| Java GSS API / JDK Kerberos | TGT session keys not exposed; breaks Java Kerberos auth |
| TPM reset / clear | Credential Manager backups protected by Credential Guard cannot be restored after TPM clear |
[!NOTE] Default enablement: Credential Guard is enabled by default on Windows 11 22H2 and later on eligible hardware. On earlier versions it must be explicitly enabled. Verify with:
Get-WinEvent -FilterHashtable @{LogName='System';Id=6}or checkHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard\Enabled.
[!NOTE] The Credential Guard configuration will be applied via an Intune Settings Catalog policy to configure the Device Guard category’s Credential Guard setting to Enabled with UEFI lock or Enabled without lock.
Note: If you want to be able to turn off Credential Guard remotely, choose Enabled without lock.
Credential Guard requirements — hardware and firmware prerequisites for VBS/VSM ↩ ↩2
Mitigating Pass-the-Hash (PtH) Attacks and Other Credential Theft, Version 1 and 2 — Microsoft baseline whitepaper covering attack anatomy, credential isolation architecture, and enterprise mitigation strategies ↩ ↩2
Windows settings you can manage through an Intune Endpoint Protection profile ↩ ↩2