CRL distribution points define where revocation checks can fail
CRL distribution points define where revocation checks can fail A certificate can be structurally valid and still belong to a key that the issuer has revoked. Certificate Revocation Lists provide one way to carry that
CRL distribution points define where revocation checks can fail
A certificate can be structurally valid and still belong to a key that the issuer has revoked. Certificate Revocation Lists provide one way to carry that decision. The cRLDistributionPoints extension tells a relying party where to find the relevant list. It is a routing instruction with security consequences, not a decorative certificate field.
RFC 5280 defines distribution point names, reasons, issuer information, and related extensions. A verifier has to find a CRL that covers the certificate's issuer and scope, validate the CRL signature and time, and then determine whether the serial number is present. Delta CRLs and indirect CRLs add useful flexibility and more conditions that the verifier must understand.
A URL is not a revocation result
If the distribution point is unreachable, returns an error, or serves a list that is outside the certificate's scope, the verifier does not have a valid revocation answer. That is different from finding the certificate absent from a valid CRL. Operational systems often collapse both outcomes into a generic certificate failure, which hides whether the problem is policy, network access, or a compromised key.
A distribution point may point to an HTTP or LDAP location. The relying party needs a deliberate policy for each transport: when it may use the network, whether it caches results, how long it accepts an old CRL, and whether it fails open or closed when the location is unavailable. A client that silently skips revocation checking after a timeout has changed the security policy without saying so.
Scope and issuer checks come first
The verifier must not accept the first CRL returned by a URL. It should check the issuer, the issuing distribution point extension, reason codes, and the certificate scope. Indirect CRLs require checking the certificate's cRLIssuer and the authority that signed the list. Delta CRLs require a valid base CRL and a correct sequence relationship.
These checks are easy to implement incompletely because most test certificates are simple. A test suite should include an expired CRL, a CRL signed by the wrong issuer, a list with an unexpected scope, a revoked entry with a reason filter, and a certificate that names more than one distribution point.
Make availability visible
Certificate authorities and operators should monitor distribution point reachability independently from the services that use them. A revocation endpoint can be down while the main application remains healthy. Monitoring should record the certificate issuer, the distribution point, the last successful CRL retrieval, the CRL number, and the validation result.
When a distribution point changes, treat the change as a certificate-management event. Update firewall rules, proxies, trust stores, and offline validation caches. If a private CA is being retired, remove its distribution points only after issued certificates have expired or been reissued under the replacement hierarchy.
Fail with a reason
Revocation checking exists to preserve a negative security decision. The system needs a readable failure reason so an operator can distinguish "revoked" from "could not determine status." Fail-closed is appropriate for high-assurance authentication, but it must be paired with a recovery path and clear monitoring. Fail-open may be defensible for a narrow, documented availability requirement, but it should not emerge from an undocumented library default.
The final control is a simple inventory question: for each certificate profile, where is revocation published, who owns that endpoint, and how is a stale or missing list detected? If the answer is only a URL inside a certificate, the revocation process is not yet operated.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.