🛡️ Essential 8 Guide

Implementation guidance for Australian Essential Eight controls in Microsoft environments - ISM controls with PSPF mappings

About
HOME ← ISM-1685
ISM-1690 →

Credential Guard functionality is enabled.

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

Summary

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

Justification

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 check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard\Enabled.

Design Decision

[!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.

Prerequisites

Implementation Steps

Configure Credential Guard with Intune

  1. In Microsoft Intune, create a Settings catalog policy.
  2. In the policy, under the category Device Guard, set the Credential Guard setting to one of the options:
    • Enabled with UEFI lock
    • Enabled without lock

    Note: If you want to be able to turn off Credential Guard remotely, choose Enabled without lock.

  3. Assign the policy to a group that contains the devices or users you want to configure.
  4. After the policy is applied, restart the device.
  5. Optional: You can also configure Credential Guard by using an account protection policy in endpoint security. For more information, see Account protection policy settings for endpoint security in Microsoft Intune.
HOME ← ISM-1685
ISM-1690 →