The CA is hardened, but its web access remains exposed

The certification authority runs on a dedicated server, template permissions have been reviewed, and administrators use separate accounts. Alongside it, classic Web Enrollment or a Certificate Enrollment Web Service (CES) is still running. Its HTTPS certificate is valid and Windows authentication is enabled in IIS. That does not complete the protection of this access path.

With NTLM, valid authentication can be accepted by another service if it lacks the appropriate binding to the intended communication channel. At an enrollment endpoint, the consequence can include issuance of identity certificates. The permissions of the identity and template remain decisive, but this access path must not rely on transport encryption alone.

This article adds a bounded work package to AD CS hardening: classic CA Web Enrollment and CES using integrated Windows authentication. It does not describe an attack simulation. Certificate templates, CA keys, and other enrollment protocols still require their own controls.

Keep only the endpoints that are actually needed

The target is specific: remove unused enrollment web services after verifying dependencies. Remaining services use validated HTTPS bindings and require Extended Protection for Authentication (EPA). On the direct TLS path considered here, EPA uses channel binding to tie Windows authentication to the protected channel. Merely offering the protection is insufficient for acceptance.

Then remove NTLM wherever actual consumers can reliably use Kerberos. Treat this as a separate, tested change. Restrict network access to the required client and management networks; that restriction complements EPA but does not replace it.

Acceptance requires more than a reassuring IIS dialog: demonstrate valid initial enrollment, renewal, rejection of unauthorized access, and a documented recovery procedure. Assign an owner and a backup owner to every endpoint.

Inventory roles, applications, and consumers separately

On each relevant host, identify installed AD CS role services and their actual IIS applications. Record the FQDN, site, application path, authentication method, certificate binding, application pool, and connection to the CA. Explicitly include load balancers and reverse proxies.

Do not identify the role solely by the name certsrv: NDES can also expose applications such as mscep and mscep_admin beneath it. Those paths do not prove that classic Web Enrollment is installed and must not receive blanket configuration changes.

Also distinguish the Certificate Enrollment Policy Web Service (CEP) from CES. CEP supplies policy information; CES processes certificate requests and communicates with the CA. Successful policy retrieval therefore does not demonstrate working issuance. An IIS change does not automatically protect RPC/DCOM enrollment either.

For each consumer, record initial enrollment, renewal, authentication type, and the last confirmed use. Retire old services only after checking an appropriate renewal period. An absence of requests during a short logging window is insufficient evidence for decommissioning.

Require HTTPS and EPA on the correct application

Before the pilot, save the IIS configuration and affected configuration files to an access-controlled change archive. Record the effective starting state, including inherited settings. Review all applications on a shared site before changing anything at site level.

For Web Enrollment and the CES endpoint in scope, select the application actually used in IIS Manager:

  1. Provide a valid HTTPS binding with the correct DNS name, a trusted certificate chain, and working certificate renewal.
  2. Enable Require SSL under SSL Settings. An HTTP redirect alone does not provide equivalent evidence that the enrollment endpoint rejects unencrypted requests.
  3. Under Authentication > Windows Authentication > Advanced Settings, set Extended Protection to Required.
  4. Verify the effective configuration at the application path, including inheritance. The UI value Required corresponds to tokenChecking="Require" in the IIS configuration. Accept, or validation performed only when supported, does not meet this target.

This baseline assumes a direct TLS connection to the authenticating IIS server. TLS termination followed by re-encryption through a proxy can change the channel-binding assumptions. A successful HTTPS connection at the client does not prove a matching binding at the backend. Such topologies need a separately supported configuration and their own acceptance tests; do not disable protection checks to resolve compatibility failures.

If the same site also publishes public CA certificates or revocation lists, enrollment hardening must not accidentally break their intended anonymous HTTP retrieval. Writing and reading PKI publication data remain separate operations.

Apply the matching WCF configuration to CES

For CES, changing the IIS dialog is insufficient. For the Windows-integrated CES instance, the file to inspect is typically %windir%\systemdata\CES\<CA Name>_CES_Kerberos\web.config. Identify the instance and active binding actually used; do not overwrite an existing configuration with a complete sample file.

In the applicable WCF transport with clientCredentialType="Windows", the extendedProtectionPolicy element must use policyEnforcement="Always". This matches the IIS target of Required. By comparison, WhenSupported permits clients without this support and remains a weaker transitional setting.

Verify both layers together and retain a traceable configuration comparison. Assess other CES authentication variants, particularly certificate authentication, separately. A directory name also does not prove that every connection actually uses Kerberos.

Schedule the required IIS restart in a maintenance window. A full IIS restart interrupts all running IIS services on that host, not only enrollment. This can include other applications with different operational owners.

Remove NTLM only after validating the Kerberos path

For an IIS endpoint deliberately restricted to Kerberos, configure Windows authentication with only the Negotiate:Kerberos provider; do not leave other providers active in this list. Simply removing the explicit NTLM provider while leaving plain Negotiate is not reliable evidence that NTLM fallback has been excluded.

First check the service identity, DNS aliases, and their unique SPN assignments. Test the names intended for production and representative consumer types. Successful authentication using the server name does not prove that a published alias works. CES access to the CA, including any necessary delegation, is a separate dependency; do not broadly expand delegation rights to repair an error.

A host-wide incoming NTLM restriction has a larger scope than this IIS application. Prepare it through audit analysis, including the Microsoft-Windows-NTLM/Operational channel, and a service inventory. It must not affect all management and application paths on the host as an incidental extra change. Domain-wide NTLM restrictions belong in a separate project.

Demonstrate issuance and renewal in the pilot

Start with a representative test instance or a controlled maintenance window. Use nonprivileged test identities and a tightly permissioned test template. Private keys and complete authentication data must not be included in tickets or test records.

Acceptance includes at least the following:

  • An authorized test identity receives a certificate from the expected template through the intended HTTPS endpoint.
  • A controlled renewal test succeeds using the actual consumer, rather than only a browser.
  • Unencrypted access to that same enrollment endpoint produces neither successful authentication nor issuance.
  • An identity without enrollment permission receives no certificate, even if authentication succeeds.
  • The endpoint effectively requires Required, and CES also uses Always. Where NTLM has been removed, Kerberos is demonstrated for the successful test.
  • A compatibility rejection test using a known client without channel-binding support is performed only in an isolated test environment. Expect rejection despite an otherwise valid test identity. The test must not alter production protection settings.

A successful browser request does not prove resistance to relay. Combine configuration evidence with functional tests and correlate IIS status, Windows authentication events, and CA request records by time and test identifier. Repeat the checks after changes to proxies, bindings, and relevant configuration.

Benefits for AD CS protection

  • Specific protection at the enrollment boundary: Mandatory channel-binding validation makes it harder to accept relayed authentication on the direct TLS path in scope.
  • A bounded change: A required web service can be hardened without rebuilding the entire PKI.
  • Stronger acceptance evidence: Issuance and renewal are demonstrably tested rather than only checking configuration values.
  • Fewer legacy dependencies: Inventory and ownership provide a reliable basis for retiring unused web services and reducing NTLM selectively.

Disadvantages and operational limitations

  • Compatibility requires testing: Legacy clients and some intermediary paths can fail when EPA is mandatory. The failure may appear only at the next renewal.
  • Changes can interrupt services: IIS restarts, certificate bindings, and authentication providers require coordinated maintenance windows.
  • Other PKI paths remain in scope elsewhere: Unsafe template permissions, compromised CA keys, RPC endpoints, and inappropriate delegation remain separate risks.
  • Existing certificates are not invalidated: Suspected abusive issuance requires a separate incident-response and revocation process.
  • Ongoing maintenance remains necessary: New instances, restores, and installer changes can diverge from the validated configuration.

Resolve common mistakes and rollback criteria in advance

Common mistakes include applying Required only at the wrong IIS level, forgetting the CES file, and treating Negotiate as Kerberos-only. Untested TLS proxies and a brief browser check in place of a complete renewal test cause similar problems.

Define stop criteria in advance, such as failed renewal for an intended consumer class. Restore the saved application configuration under an assigned owner's control. If this temporarily removes a protection requirement, record a time-limited risk exception, tightly restrict reachability, and set a repair deadline. Leaving the endpoint at Accept permanently does not constitute completed hardening. If the exposure is unclear, disabling the affected web service may be preferable, provided a tested alternative enrollment path exists.

Project checklist for enrollment web services

  • [ ] Distinguish Web Enrollment, CES, CEP, NDES, and RPC paths correctly.
  • [ ] Document consumers, FQDNs, proxies, service identities, and renewal cycles.
  • [ ] Remove unnecessary web services after verifying dependencies.
  • [ ] Validate HTTPS bindings and reject unencrypted enrollment access.
  • [ ] Enforce EPA as Required at the correct application path.
  • [ ] For Windows-integrated CES, align the active WCF binding with Always.
  • [ ] Validate Kerberos and SPNs before selectively removing NTLM.
  • [ ] Coordinate the IIS restart, backup, and time-limited rollback path.
  • [ ] Record initial enrollment, renewal, and negative authorization tests.
  • [ ] Preserve CRL/AIA retrieval and review configuration drift regularly.