ETSI EN 319 411-1 How should certificate authorities handle suspension under ETSI EN 319 411-1

Treat suspension as part of the same controlled certificate-status process as revocation, while keeping the two outcomes distinct. A definitive revocation cannot be reinstated under EN 319 411-1; suspension is therefore useful only where the applicable certificate policy, CPS, customer terms, and status systems can represent a temporary invalid state without confusing relying parties.

The CPS and subscriber-facing terms should describe whether certificates can be suspended or revoked, the reasons and request channels, the mechanism used to distribute status information, and the maximum delays for making the changed status visible to relying parties. EN 319 411-1 sets a hard outer timing rule for revocation or suspension requests: the actual certificate status information must be available to all relying parties within at most 24 hours after receipt of the request.

The evidence should show both the business decision and the status-system result. A reviewer should be able to see who requested suspension, how the CA confirmed the request, when the request arrived, what certificate and policy were affected, when the status changed, which CRL or OCSP channel carried the new status, and whether the subject or subscriber was notified.

EN 319 411-1 also expects status information to be available continuously, protected for integrity and authenticity, and available at least until certificate expiry. Where a CA supports both CRL and online certificate status service methods, updates should be available for all methods and the information should stay consistent over time.

A CA should offer suspension only when the surrounding policy, repository, and status-service design can make the temporary state unambiguous. The risk is not just operational delay; it is that relying parties, subscribers, auditors, or customer contracts may treat a suspended certificate differently from the CA's status infrastructure.

Before enabling or continuing suspension, compare the certificate policy, CPS, subscriber agreement, relying-party notice, CRL profile, OCSP behavior, repository wording, and incident or compromise procedures. The documents and systems should tell the same story about when suspension is available, how long it can last, who can request it, and what happens next.