IdenTrust: Temporarily Expired CRLs

IdenTrust reported that on September 8, 2023 it found that four CRLs had expired. In its investigation, IdenTrust stated that a job-control utility failure caused the CRLs to expire, and that the utility was restarted to restore normal operations. IdenTrust said it began investigating the scope of affected certificates after being flagged by CRL Watch, and that new CRLs were generated and loaded successfully shortly after the restart. The incident report stated that no certificates were affected, and that the impacted items were the listed CRLs. IdenTrust attributed the CRL generation slowdown to a major IdenTrust customer revoking a large number of certificates during the time the utility was creating the new CRLs. IdenTrust later stated that it had nothing else pending to correct and considered the issue closed, and Mozilla indicated it would close the bug unless additional questions remained. The bug is marked RESOLVED with resolution FIXED.

1. 2023-09-08 IdenTrust discovered that four CRLs had expired and began investigating after being flagged by CRL Watch.
2. 2023-09-08 IdenTrust restarted the job-control utility and successfully generated and loaded replacement CRLs.
3. 2023-09-29 IdenTrust submitted the full incident report describing the cause and remediation steps.
4. 2023-10-09 IdenTrust stated there were no further pending corrections and Mozilla planned to close the bug.

1. 2023-09-15 IdenTrust Services, LLC — IdenTrust reported that it found four CRLs had expired on September 8, 2023, restarted the job-control utility, restored normal operations, and would provide a full incident report by September 29, 2023.
2. 2023-09-29 IdenTrust Services, LLC — IdenTrust provided the incident report, stating it was flagged by CRL Watch, that CRL generation slowed due to a customer revoking many certificates during CRL creation, and that no certificates were affected while specific CRLs were impacted.
3. 2023-10-09 IdenTrust Services, LLC — IdenTrust said it had nothing else pending to correct and considered the issue close.
4. 2023-10-09 Mozilla representative — Mozilla thanked IdenTrust and said it would close the bug on Wed 11-Oct-2023 unless additional questions remained.