← Saudi Data and Artificial Intelligence Authority (SDAIA) cases
Bugzilla #2015567 Ccadb Metadata Update Incident Ccadb Disclosure Issue Information Request

SDAIA missing required CCADB contact email aliases

RESOLVED FIXED Saudi Data and Artificial Intelligence Authority (SDAIA)
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

This case concerns SDAIA’s failure to keep required CCADB contact information current. The bug was opened by Apple after SDAIA had not updated the CCADB record following a notification on 2026-01-23, and the required fields “CA Email Alias 1” and “CA Email Alias 2” were empty. SDAIA acknowledged the issue, investigated why the notification had not been acted on, and later reported that it populated a non-personal contact email alias on 2026-02-10. SDAIA also said it updated internal review activities and later consolidated two CCADB accounts into one on 2026-04-13. The report closure summary states that all action items were completed and closure was requested, and CCADB issued a final call for comments before closing the report.

Model: gpt-5.4-mini Generated: 2026-06-13 17:28 UTC Revised: 2026-07-06 09:41 UTC Confidence: 0.97 17 comments
Chronology
  1. The SDAIA/NCDC CA Owner record was created in CCADB without the required non-personal contact email aliases.
  2. SDAIA was notified that its CCADB contact information needed updating.
  3. SDAIA populated CA Email Alias 1 in CCADB.
  4. The two CCADB accounts for the former NCDC PKI hierarchy and Saudi National SSL PKI hierarchy were consolidated into one account.
  5. SDAIA submitted a report closure summary requesting closure of the incident report.
Thread Activity
  1. Apple representative — Apple reported that SDAIA had not updated required CCADB contact information and asked it to populate at least one required email alias.
  2. Sdaia representative — SDAIA acknowledged the discrepancy, said it had started an investigation, and committed to taking the requested action.
  3. Mozilla representative — Mozilla stated that SDAIA was required to complete the incident reporting process under the CCADB Incident Reporting Guidelines.
  4. Sdaia representative — SDAIA filed a full incident report describing the missing contact aliases, the timeline, and the fact that the issue did not directly affect certificates.
  5. Sdaia representative — SDAIA said the non-personal contact alias had been populated and that immediate remediation and preventive actions were complete, while account consolidation remained in progress.
  6. Apple representative — Apple confirmed the CCADB update fixed the initial problem and asked for overdue action-item and closure updates.
  7. Sdaia representative — SDAIA posted an updated action-items table showing the alias update and internal review updates as complete and account consolidation as ongoing.
  8. Sdaia representative — SDAIA said the account consolidation had been completed on 2026-04-13 and that minor follow-up adjustments were being discussed with CCADB.
  9. Sdaia representative — SDAIA submitted a report closure summary stating that all action items were completed and requesting closure.
  10. CCADB representative — CCADB issued a final call for comments or questions and said the report would be closed if none were raised.
Participants
Apple representative Sdaia representative Mozilla representative CCADB representative Cabbage representative
Similar Local Cases
#2050850 RESOLVED Ca Certificate Compliance Common Ca Database Incident Externally Reported Incident Opened 2026-06-26 · Closed 2026-08-04 · 81% similar
Asseco DS / Certum: HTTP 404 returned by CRL Distribution Point URLs for six pre-inclusion Root CAs
#2058363 RESOLVED Common Ca Database Ccadb Disclosure Issue Incident Externally Reported Incident Opened 2026-07-28 · Closed 2026-08-29 · 80% similar
DigiCert: Blank SubCA Owner field in CCADB for cross-certificate
#2055120 RESOLVED Ca Certificate Compliance Incident Ccadb Disclosure Issue Policy Document Issue Opened 2026-07-15 · Closed 2026-08-21 · 80% similar
Chunghwa Telecom: Incomplete disclosure of CRL URLs in CCADB
#2054450 RESOLVED Ca Certificate Compliance Ccadb Disclosure Issue Incident Externally Reported Incident Opened 2026-07-13 · Closed 2026-09-01 · 80% similar
Firmaprofesional: Chrome Root Program Policy - Incorrect CCADB hierarchy associations
#2055047 RESOLVED Common Ca Database Ccadb Disclosure Issue Incident Self Reported Incident Opened 2026-07-14 · Closed 2026-08-17 · 80% similar
DigiCert: Incomplete disclosure of CRL URLs in CCADB
#2049012 RESOLVED Ccadb Metadata Update Opened By Ca Ccadb Disclosure Issue Policy Document Issue Opened 2026-06-19 · Closed 2026-08-04 · 80% similar
FNMT: Inaccuracy in CRL URL in CCADB
#2054849 RESOLVED Ca Certificate Compliance Common Ca Database Incident Self Reported Incident Opened 2026-07-14 · Closed 2026-07-30 · 79% similar
Atos: Incorrect CRL URL in CCADB
#2047866 RESOLVED Ccadb Metadata Update Ccadb Disclosure Issue Remediation Tracking Opened By Ca Opened 2026-06-16 · Closed 2026-07-21 · 79% similar
certSIGN: incorrect URL in CCADB

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

Confirm action