Published on
November 10, 2026
One loose setting in Microsoft Active Directory Certificate Services (AD CS) can hand an attacker the keys to your whole Windows network. Most teams know to check certificate templates. Fewer know that templates are only one of five places where things go wrong.
This article walks through those five places, with one real example each. If you are reviewing an AD CS environment, it shows you where to look beyond the template list.
Why AD CS security matters so much
In a Windows network, a certificate can log someone in, just like a password. AD CS is the server that issues them. Think of it as the machine that prints login badges.
So every AD CS attack comes down to one question. Can an ordinary user get a badge with someone else's name on it?
The stakes are high. AD CS is trusted across every domain in the company, not just one. A badge with the wrong administrator's name on it can open everything.
1. Templates: the rules for each badge
A template is a recipe. It says what AD CS will issue, and who can ask for it.
The classic mistake is a template that lets users write their own name on the badge. The user simply writes an administrator's name instead. SpecterOps catalogued this attack, and the first AD CS attacks with it, in its Certified Pre-Owned research in 2021.
Other template mistakes are quieter. A badge allowed to do anything. A badge that quietly adds its holder to a group. Every new template created for a project is one more chance to get it wrong.
2. Server settings and permissions
A clean template list can still sit on a risky server.
One single setting on AD CS lets users add extra names to any request, even on safe templates. Too many people with admin rights on the server can switch that setting on. And anyone who reaches the server's signing key can print any badge they like.
Permissions in Active Directory matter too. If a user can edit a template, they can loosen it, use it and put it back. None of this shows up if you only review the templates themselves.
Take control of your PKI infrastructure
See how Evertrust simplifies certificate lifecycle management.
Get Started3. The doors into the server
Every way to reach AD CS is also a way to attack it.
The best-known example is the web enrollment page. If it is not protected, an attacker can trick a server into logging in to them, then pass that login on to AD CS. They walk away with a badge for that server. Compass Security showed the same trick works on another AD CS interface.
Mobile device enrollment, web services and automatic enrollment all reach AD CS too. The useful question is simple: do you know every door?
4. How domain controllers read the badge
AD CS prints the badge. The domain controller decides who it belongs to.
There are two ways to match a badge to a person. A weak match uses a name, which can be faked. A strong match uses a unique account number, which cannot be reused. According to Microsoft's KB5014754 guidance, domain controllers have required the strong match by default since February 2025, with no way back after September 2025.
That closed many attacks. But a badge printed without the account number, or an account whose matching rules anyone can edit, still brings the problem back.
5. The software itself
Every layer so far is about settings. A fully hardened AD CS closes them all. The last layer is different, because no setting can close it.
In July 2026, a flaw called Certighost showed that a standard user could get AD CS to print a Domain Controller badge. According to Help Net Security, nothing had to be misconfigured. Only Microsoft's July 14, 2026 update fixed it. We cover it in our Certighost article.
AD CS also lives inside Active Directory, so it depends on its patch cycles, its permissions and its defaults. A weakness there can quickly become a certificate weakness.
How to start an AD CS security review
A template review is a good start, not a finish line. Five questions cover the rest:
Do we know every way people and machines can request a certificate?
Can any template let a user choose the name on their own certificate?
Who can change AD CS settings and templates, and is that list short?
Do our domain controllers only accept strong matches?
Is every AD CS server patched, including the July 2026 update?
There is also a simpler way to shrink all five places at once: fewer doors, and less freedom for whoever walks through them. That is the role of a gatekeeper like Evertrust CLM in front of AD CS, which we explain in our article on the registration authority. Some organizations go one step further and replace AD CS with Evertrust PKI, which does not depend on Active Directory.
AD CS security FAQ
What is the AD CS attack surface?
It is every place where Microsoft AD CS can be abused to issue a certificate with the wrong identity: templates, server settings and permissions, enrollment interfaces, how domain controllers read certificates, and the software itself.
What is ESC1 in AD CS?
ESC1 is the best-known AD CS attack. A template lets users write their own name on a certificate that can log in, so an attacker writes an administrator's name instead.
How many AD CS attacks are known?
Researchers have catalogued 17, named ESC1 to ESC17, since 2021. Code flaws such as Certighost, disclosed in July 2026, come on top of those.
Is auditing certificate templates enough?
No. Templates are one of five areas. Server settings, permissions, enrollment interfaces and patch levels each need their own review.
Which tools find AD CS weaknesses?
Open-source tools such as Certipy and Certify list risky templates and settings. They cannot detect flaws in the AD CS code itself.