← Sectigo cases
Bugzilla #1812336 Ca Documents

Sectigo: Late CCADB update after CPS update

RESOLVED FIXED Sectigo
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

Sectigo opened this bug to disclose an incident where a newly published Apple CPS was not disclosed to CCADB within the 30-day deadline required by the Mozilla Root Store Policy. The CPS was published by Apple and took effect on November 15, 2022, and it covered multiple Apple subordinate CAs issued by Sectigo (with Apple as the CA operator). Sectigo stated that it received an email on January 11, 2023 indicating that four subordinate CAs had outdated CPS documents in CCADB, and Sectigo then confirmed the new CPS in Apple’s repository and updated the CCADB records with the appropriate URLs and metadata. Sectigo also found that CCADB records for four additional Apple client subordinate CAs contained outdated CPS information and updated those records as well. Sectigo reported that there was no official notification step in the two CAs’ processes for CPS changes, and that Sectigo does not actively monitor Apple’s public repository for updates. Sectigo said discussions with Apple concluded with agreed policy changes: Apple will notify Sectigo no later than 7 days in advance of planned CPS updates and will notify Sectigo once the CPS revision is published to Apple’s public repository. The bug was requested to be marked resolved and was closed as RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 20:57 UTC Revised: 2026-06-16 18:57 UTC Confidence: 0.86 4 comments
Chronology
  1. Apple published a new CPS that took effect and covered multiple subordinate CAs issued by Sectigo.
  2. Sectigo received an email indicating CCADB records for certain subordinate CAs listed outdated CPS information.
  3. Sectigo investigated, confirmed the new CPS in Apple’s repository, and updated CCADB records (including additional subordinate CAs with outdated CPS info).
  4. Sectigo reached out to Apple to agree on steps to prevent recurrence.
  5. Mozilla indicated it would close the bug unless additional questions were raised.
Thread Activity
  1. Sectigo — Opened the bug to inform the community of a CCADB disclosure deadline incident involving a newly published CPS not being updated within 30 days.
  2. Sectigo — Provided a detailed incident timeline and remediation steps, including agreed Apple notification changes to Sectigo.
  3. Sectigo — Requested marking the bug as resolved unless questions or comments were raised.
  4. Mozilla representative — Planned to close the bug on or about 10-Feb-2023 unless additional issues were identified.
Participants
Sectigo Mozilla representative
Similar Local Cases
#1472993 RESOLVED Ca Documents Audit Document Opened By Ca Single Ca Owner Opened 2018-07-03 · Closed 2026-07-01 · 76% similar
Sectigo audit reports
#1814197 RESOLVED Ca Documents Opened 2023-01-31 · Closed 2023-02-14 · 71% similar
DigiCert: Late CP/CPS CCADB uploads
#1667846 RESOLVED Ca Documents Incident Opened 2020-09-28 · Closed 2022-11-14 · 67% similar
Izenpe: Certificates not disclosed in CCADB
#1706976 RESOLVED Ca Documents Opened 2021-04-22 · Closed 2022-11-14 · 67% similar
Google Trust Services: Out-of-date CPS disclosure
#1648593 RESOLVED Ca Documents Opened 2020-06-25 · Closed 2024-06-30 · 66% similar
Sectigo: Potential audit report delay
#1667844 RESOLVED Ca Documents Opened 2020-09-28 · Closed 2023-02-22 · 66% similar
Google Trust Services: Certificates not disclosed in CCADB
#1941675 RESOLVED Ca Documents Incident Opened 2025-01-14 · 65% similar
Certum root lists a Microsec CPS in AllCertificateRecordsCSVFormatv2
#1716351 RESOLVED Ca Documents Audit Document Remediation Tracking Opened By Root Store Opened 2021-06-14 · Closed 2026-06-25 · 65% similar
HARICA: Audit Documents

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action