
Wondering how to strengthen your security? Explore the five essential certificate management best practices every organization should implement.
What AD CS is, best practices for a Microsoft certificate authority, and how to close the known AD CS attack paths such as ESC1.


Content writer, trio.so
Active Directory Certificate Services (AD CS) is the Windows Server role that runs a Microsoft certificate authority (CA). It issues the certificates that machines, users and services use to prove who they are and to encrypt traffic. The best practices that matter most: use a two-tier hierarchy with an offline root, treat every CA as a Tier 0 asset like a domain controller, lock down certificate templates and who can enroll, and audit the CA configuration for the known misconfigurations (ESC1 to ESC8) listed below.
Microsoft describes AD CS as a Windows Server role for issuing and managing public key infrastructure (PKI) certificates used in secure communication and authentication. The certificates give you confidentiality (encryption), integrity (digital signatures) and authentication (binding a key to a user, computer or device account).
Microsoft lists these role services:
Typical uses, per Microsoft: user and computer authentication, smart card sign-in, secure Wi-Fi and VPN (802.1X and IPsec), S/MIME email, Encrypting File System, web server (TLS) certificates, code and document signing, and device certificates through NDES. Active Directory group policy can control who gets which certificate type, using certificate templates.
Run AD CS if you need certificates for internal systems and want them tied to your Active Directory identities: domain-joined PCs signing in to Wi-Fi, internal web apps, smart card or Windows Hello for Business certificate trust, and so on. Use a public CA for anything customers or browsers outside your network must trust.
You may not need it if you have only a few internal servers and no certificate-based authentication, or if you are moving away from on-premises Windows infrastructure. In that case cloud PKI services or a managed CA can replace it (see "AD CS alternatives" below). Remember that a CA is a high-value target. A small, unmaintained AD CS install can be worse than none.
Microsoft's KB5014754 changed how domain controllers map certificates to accounts. Certificates must carry a strong mapping, such as the SID extension, or authentication is denied once domain controllers run in Full Enforcement mode. Microsoft has ended the compatibility option for KB5014754, so check the KB for the current enforcement state, and make sure your templates add the SID extension.
In 2021 SpecterOps published "Certified Pre-Owned", the research that named the common AD CS misconfigurations ESC1 to ESC8. They are misconfigurations of templates, permissions and CA settings, not bugs in Windows, so you fix them by configuration. The table gives each class and the check that closes it. There are no exploit steps here, on purpose.
| Class | What is misconfigured | Defensive check |
|---|---|---|
| ESC1 | A template lets low-privileged users supply their own subject alternative name, has an authentication purpose, and needs no approval. | Remove "supply in request" from templates that allow authentication, or require manager approval or authorized signatures. |
| ESC2 | A template with the Any Purpose or no EKU is enrollable by low-privileged users. | Restrict enrollment to named groups and set specific purposes. |
| ESC3 | A template with the Certificate Request Agent purpose is open to low-privileged users and the CA has no enrollment agent restrictions. | Limit who can enroll and configure enrollment agent restrictions on the CA. |
| ESC4 | Unintended accounts can write to a certificate template object. | Audit permissions on template objects and remove write access except for PKI admins. |
| ESC5 | Unintended accounts control other PKI objects, such as the CA's computer object or containers under Public Key Services. | Review ACLs on all PKI objects and on the CA server. |
| ESC6 | The CA has the EDITF_ATTRIBUTESUBJECTALTNAME2 flag set, so any request can include a user-defined subject alternative name. | Make sure the flag is off, and check it after every patch cycle. |
| ESC7 | Unintended accounts hold the ManageCA or ManageCertificates permission on the CA. | Limit those permissions to tightly controlled administrators. |
| ESC8 | The CA's HTTP enrollment endpoints accept NTLM authentication without relay protection. | Disable unused web enrollment. If needed, require Kerberos, enforce HTTPS with Extended Protection for Authentication, or turn NTLM off for the endpoint. |
Researchers have published more classes since (the list is not closed), so audit your CA with a maintained tool and re-run it on a schedule. The same research advises revoking a compromised account's certificates as well as resetting its password, because a certificate can keep working after the password changes. Our guide to Active Directory security covers the surrounding controls, and how to prevent pass-the-hash attacks covers the credential side.
Searching for an "AD CS replacement" usually means one of three things:
Whichever route you pick, plan the certificate lifecycle: who issues, who renews, who revokes, and how you find certificates that are about to expire. See certificate management best practices.
trio.so manages Windows, macOS, Linux, iOS and Android devices from one console.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

Wondering how to strengthen your security? Explore the five essential certificate management best practices every organization should implement.

How to create and renew the Apple push (APNs) certificate your MDM needs, what happens when it expires, and how to avoid re-enrolling devices.

Android certificate management enables secure device authentication and encrypted communications through systematic deployment and lifecycle control of digital certificates.

How MDM manages certificates on iPhone and iPad: the APNs push certificate, SCEP and PKCS identity certificates, trusted roots, renewal and revocation.

Five real-world public key infrastructure examples, how PKI works, and the key steps and pitfalls when you implement it.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients