KIR: Failed to respond to a Certificate Problem Report within 24 hours
This case concerns KIR’s failure to provide a preliminary response within 24 hours after receiving Certificate Problem Reports, as required by TLS BR section 4.9.5. The reports were sent by the Chrome Root Program Team on 2025-05-02 and 2025-05-05 to KIR contact points disclosed in CCADB. KIR said the first report went to a general webform that routed to a standard queue, and the second went to a CA email alias that included staff who were on vacation. KIR later filed a preliminary incident report, then a full incident report, and described remediation steps including a dedicated CPR email address, updated CCADB contact details, and an internal procedure for quarterly checking email group addresses. The bug was resolved as FIXED, and the thread later notes that all action items were completed and a closure report was submitted.
- A CPR was sent to KIR’s CCADB-listed problem reporting mechanism.
- A CPR was sent to KIR’s CCADB-listed CA email alias.
- KIR submitted a preliminary incident report.
- KIR submitted a full incident report.
- KIR submitted a closure report stating all action items were completed.
- Kir representative — KIR filed a preliminary incident report saying it failed to respond within the TLS BR 4.9.5 timeframe.
- Kir representative — KIR filed the full incident report with timeline, impact, root cause analysis, and related incidents.
- Kir representative — KIR said all action items were completed and listed the completed remediation steps.
- CCADB representative — CCADB requested a closure report if the case was ready for closure.
- Kir representative — KIR submitted a report closure summary and requested closure.
- CCADB representative — CCADB issued a final call for comments or questions before closure.