Verify both base and delta CRLs through the enrollment endpoint

Treat this document as a focused evidence review: Verify both base and delta CRLs through the enrollment endpoint. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Retrieve base & delta CRLs using Web Enrollment in AD CS from Microsoft supports the following bounded statements:

• CA Web Enrollment can retrieve the current base and delta certificate revocation lists. The research record locates this support at Opening overview.
• Microsoft documents prerequisites and a browser-based retrieval procedure. The research record locates this support at Sections: Prerequisites; Retrieve a certificate revocation list.

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

Retrieval proves endpoint availability, not relying-party freshness or successful revocation checking. 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 Sections: Prerequisites; Retrieve a certificate revocation list, 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.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Opening overview; Sections: Prerequisites; Retrieve a certificate revocation list 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.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Retrieve base & delta CRLs using Web Enrollment in AD CS — Microsoft