Mirror trusted and disallowed CTLs for disconnected Windows systems

Frame this document as a source-led configuration and assurance check: Mirror trusted and disallowed CTLs for disconnected Windows systems. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Configure trusted roots and disallowed certificates in Windows from Microsoft supports the following bounded statements:

• Windows can redirect automatic certificate-list retrieval to an internal file or web server. The research record locates this support at Opening overview.
• The documented mirror can host trusted CTLs, untrusted CTLs, or a selected subset for disconnected environments. The research record locates this support at Opening overview.

Keep the evidence boundary at these traced claims. They support a review of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

Protect mirror integrity and monitor freshness; a stale trust list can preserve revoked or remove needed trust. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles are in and out of scope?
• Which condition in Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and sanitize protected material before retention.

Verification and evidence

A reviewer should be able to retrace the decision from Opening overview; Opening overview through CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks. Record what was collected, where, when, by whom, and which system or role it represents.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• Configure trusted roots and disallowed certificates in Windows — Microsoft