Published on
November 20, 2026
Most certificate attacks don't break anything. They simply ask. A user sends a request with someone else's name in it, and the certificate authority signs it.
That is not a bug in the certificate authority (CA). It is doing its job, which is signing. What is missing is someone who decides what should be signed in the first place. In PKI, that role has a name: the registration authority (RA). It is often treated as optional. It shouldn't be.
Registration authority vs certificate authority: two jobs, often done by one
Think of a passport office. One desk checks your documents and decides what goes in your passport. Another desk prints and stamps it. You would never let the printer decide your name.
In PKI, the CA is the printer. The RA is the desk that checks. In theory, they are separate roles. In practice, many companies run a CA alone and let it do both.
When that happens, the quality of every certificate depends on how carefully each template was written. Microsoft AD CS shows what that costs. Most of the 17 known AD CS attacks catalogued since 2021 are cases where the CA accepted what a user asked for.
A request is a claim, not a fact
A certificate request says two things: here is my key, and here is who I am. The user writes both.
In a Windows network, that second part carries real weight. A certificate can log someone in, just like a password. If a user writes an administrator's name into their request, and the CA signs it, they become that administrator.
So checking a request properly means two things. Confirm who is asking from something they cannot fake, like their login session. Then decide what goes in the certificate from your policy, not from the request.
How Evertrust CLM handles a request
Evertrust CLM, our certificate lifecycle management platform, can act as the RA in front of your CA, whether that is Microsoft AD CS or Evertrust PKI. It works in three steps:
Check. Every name in the request is tested against your policy. Is it allowed? Does it match the right format? Anything unexpected is refused.
Rebuild. What the user sent is thrown away. Evertrust CLM writes a clean request from approved values only.
Send on one path. Evertrust CLM asks the CA on the user's behalf, using one template you chose. Users never pick a template themselves.
The key word is rebuild. Evertrust CLM doesn't filter a request and pass the rest along. It writes a new one.
Take control of your PKI infrastructure
See how Evertrust simplifies certificate lifecycle management.
Get StartedWhat that stops
Shopping for a weak template. Users never see the template list, so they cannot hunt for the loosest one.
Sneaking in extra permissions. There is simply no field for them. Whatever a user adds to the request is dropped.
Side doors into the server. Evertrust CLM talks to the CA through one authenticated channel. It does not use the web pages attackers like to target.
Tricks like Certighost. That AD CS flaw, patched by Microsoft in July 2026, relied on extra details hidden in the request. Through Evertrust CLM, those details never reach the CA. Read our Certighost article for the full story.
Your part of the job
An RA is only as strict as its policy. Two choices close the remaining doors:
Lock identity fields to the person asking. If users can type any name they like, they can type someone else's.
Give every policy clear name rules. A policy without rules trusts whatever the request says.
Even then, users can only influence the fields your policy allows. They can never add permissions of their own.
One door, not many
There is one condition behind all of this. Evertrust CLM protects the requests that go through it. If users can still reach the CA directly, they skip it. So make Evertrust CLM the only way in, and block direct access to the CA.
That condition is also the payoff. With one door, you get one policy that defines who gets what, one log of everything issued, and one place to act when threats change.
An RA does not fix the CA behind it, and AD CS still needs patching. For organizations that want to go further, Evertrust PKI replaces AD CS with a CA that does not depend on Active Directory.
The CA signs. The RA decides. Treating them as one job is how a valid certificate ends up with the wrong name on it.
Registration authority FAQ
What is a registration authority in PKI?
A registration authority (RA) checks certificate requests and decides what each certificate should contain. The certificate authority then signs it.
What is the difference between an RA and a CA?
The CA signs certificates. The RA confirms who is asking and what they are allowed to get. When the CA does both, every decision depends on template settings.
Does a registration authority replace AD CS?
No. An RA like Evertrust CLM sits in front of AD CS. To remove AD CS, you also need a different CA, such as Evertrust PKI.
Does an RA protect against AD CS attacks?
It blocks attacks that rely on what users put in their requests, as long as it is the only way to reach the CA. It does not fix flaws inside the CA itself.