Policy
Require strict KDC validation
Windows 11 25H2
Policy overview
Key metadata and intent for this policy.
Supported OS tags: Windows10, Windows10RT, Windows11, Windows7, Windows8, Windows81, WindowsRT, WindowsRT81, WindowsServer2008, WindowsServer2012, WindowsServer2012R2, WindowsServer2016, WindowsVista
This policy setting controls the Kerberos client's behavior in validating the KDC certificate for smart card and system certificate logon. If you enable this policy setting, the Kerberos client requires that the KDC's X.509 certificate contains the KDC key purpose object identifier in the Extended Key Usage (EKU) extensions, and that the KDC's X.509 certificate contains a dNSName subjectAltName (SAN) extension that matches the DNS name of the domain. If the computer is joined to a domain, the Kerberos client requires that the KDC's X.509 certificate must be signed by a Certificate Authority (CA) in the NTAuth store. If the computer is not joined to a domain, the Kerberos client allows the root CA certificate on the smart card to be used in the path validation of the KDC's X.509 certificate. If you disable or do not configure this policy setting, the Kerberos client requires only that the KDC certificate contain the Server Authentication purpose object identifier in the EKU extensions which can be issued to any server.
Registry values
How enabled and disabled states update the registry.
| Registry location | Type | Enabled value | Disabled value |
|---|---|---|---|
| HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\KdcValidation | REG_DWORD | 2 | 0 |
Policy elements
Inputs and configuration options exposed by this policy.
This policy has no additional user input fields.
Other policies in this category
Explore related policies at the same level.
- ComputerAllow retrieving the Azure AD Kerberos Ticket Granting Ticket during logonAt least Windows Server 2019, Windows 10 Version 2004
- ComputerAlways send compound authentication firstAt least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
- ComputerConfigure hash algorithms for certificate logonAt least Windows 11 Version 22H2
- ComputerDefine host name-to-Kerberos realm mappingsAt least Windows Vista
- ComputerDefine interoperable Kerberos V5 realm settingsAt least Windows Vista
- ComputerDisable revocation checking for the SSL certificate of KDC proxy serversAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerEnable Delegated Managed Service Account logonsAt least Windows 11 Version 24H2
- ComputerFail authentication requests when Kerberos armoring is not availableAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerKerberos client support for claims, compound authentication and Kerberos armoringAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerRequire strict target SPN match on remote procedure callsAt least Windows Server 2008 R2 or Windows 7
- ComputerSet maximum Kerberos SSPI context token buffer sizeAt least Windows Server 2003 operating systems or Windows XP Professional
- ComputerSpecify KDC proxy servers for Kerberos clientsAt least Windows Server 2012, Windows 8 or Windows RT