Contact Us

Windows Credential Guard and 802.1X

What you should do about it

David Gearing
July 9, 2025 4 min read

Organisations upgrading to Windows 11 are encountering unexpected authentication issues on wired and wireless networks. If you've recently seen disruptions to 802.1X authentication on your estate, Windows Credential Guard could be the reason.

At Roc, we’ve been working closely with customers to identify the root cause and future-proof their authentication infrastructure. Here’s what you need to know.

What is Windows Credential Guard?

Windows Credential Guard is a security feature introduced by Microsoft to combat credential theft techniques such as pass-the-hash and pass-the-ticket. It leverages Virtualisation-Based Security (VBS) to isolate and protect sensitive authentication information like NTLM hashes and Kerberos Ticket-Granting Tickets (TGTs) from the operating system.

Starting with Windows 11 version 22H2, Credential Guard is enabled by default on supported editions, including Enterprise, Education, and some Pro devices. It’s also the default in Windows Server 2025 and later.

While Credential Guard significantly boosts endpoint security, it brings with it some unintended consequences, particularly around network authentication.

The 802.1X Problem

Many enterprise networks use 802.1X authentication with PEAP-MSCHAPv2 as the inner method, which relies on saved user credentials or single sign-on (SSO).

Credential Guard blocks access to stored credential hashes, even by legitimate processes like network authentication. As a result, users may find themselves:

  • Prompted to manually re-enter credentials for every network session.
  • Completely unable to connect to the network if credential prompts are blocked by policy.

This not only frustrates end users but also creates a support burden for IT teams.

What's the Solution?

While disabling Credential Guard is technically an option, it’s not a good one. Doing so removes a critical security layer designed to prevent lateral movement and credential-based attacks.

Instead, organisations should migrate to certificate-based 802.1X authentication, using methods like EAP-TLS or PEAP-TLS. These approaches offer seamless SSO without relying on stored passwords or hashes, making them fully compatible with Credential Guard.

Roc's Recommended Approach

To transition securely and effectively, we recommend the following steps:

  • Deploy an internal Public Key Infrastructure (PKI) and issue machine and/or user certificates.
  • Configure your RADIUS servers to use EAP-TLS for authentication.
  • Automate certificate enrolment using tools such as Intune or Simple Certificate Enrolment Protocol (SCEP).
  • Update access policies and profiles using Group Policy or MDM platforms.

This shift not only resolves the compatibility issues with Credential Guard but also aligns your network with modern, zero-trust security principles.

Need Help?

Whether you’re just starting your 802.1X journey or need help modernising your authentication strategy, Roc’s team of network and security specialists are ready to assist. We offer:

  • Migration planning
  • PKI design and deployment
  • RADIUS configuration
  • End-to-end implementation and support

Let Roc help you build a secure, seamless authentication experience that works with and not against your Windows security posture.

Contact us

Written by David Gearing

Network Services Practice Lead

David leads the development of Roc’s network strategy and portfolio, shaping and refining customer propositions to strengthen performance and experience whilst delivering value.