Chunghwa Telecom: Delayed to Submit Annual CCADB Self-Assessment 2024 by GTLSCA
This case concerns GTLSCA (Chunghwa Telecom) submitting its 2024 annual CCADB self-assessment report late. The self-assessment was submitted to the Root CA Team and uploaded to CCADB for review, but it was delayed by 21 days, which the report states resulted in non-compliance with Section 6 of the Chrome Root Certificate Program policy and the Mozilla Root Store policy. The delay was attributed to personnel changes and unfamiliarity with the self-assessment form’s approximately 300 confirmation items, along with temporary reassignment of the responsible person to other work. The CA submitted the 2024 CCADB self-assessment report and provided an incident report explaining the reason for the delay. The closure summary states that GTLSCA strengthened internal work allocation and process monitoring, including redefining roles, establishing a review mechanism, and implementing agile tracking to ensure future on-time submissions. The bug is marked RESOLVED with resolution FIXED, and the report closure summary requests closure after action items were completed as described.
- GTLSCA began filling out the 2024 CCADB self-assessment.
- GTLSCA submitted the 2024 CCADB self-assessment to the Root CA Team.
- The Root CA Team requested an incident report explaining the reason for the delay.
- GTLSCA posted the incident report on Bugzilla describing the 21-day delay.
- The incident report closure summary was posted and closure was requested.
- Cht representative — Created the incident report attachment and explained that the 2024 CCADB self-assessment was submitted 21 days late, with the delay attributed to personnel changes and time spent verifying ~300 items.
- Cht representative — Stated that they were continuing to monitor the issue.
- Cht representative — Stated that they were continuing to monitor the issue.
- Cht representative — Stated that they were continuing to monitor the issue.
- Cht representative — Stated that they were continuing to monitor the issue.
- Cht representative — Posted the report closure summary describing the incident, root cause, remediation steps, and requested closure after action items were completed.
- Mozilla representative — Said they would leave the bug open briefly for more comments and then review closing it.