← Netlock cases
Bugzilla #1957474 Incident

Netlock: Failure to Provide Weekly Updates

RESOLVED FIXED Netlock
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 addresses Netlock's failure to provide required weekly updates for multiple incident reports, as mandated by the CCADB Incident Reporting Guidelines. The issue was triggered by procedural oversights that led to missed deadlines for updates. In response, Netlock has acknowledged the delays and initiated a preliminary incident report, followed by a full incident report detailing the root causes and corrective actions taken. The CA has implemented new internal measures, including a ticketing reminder system and a dedicated compliance coordinator, to ensure timely updates in the future. The case is currently resolved with commitments to improve compliance.

Model: gpt-4o-mini Generated: 2026-06-13 21:03 UTC Revised: 2026-06-16 18:51 UTC Confidence: 0.85 22 comments
Chronology
  1. Netlock acknowledged failure to provide weekly updates and opened a preliminary incident report.
  2. Netlock posted a full incident report detailing the root causes and corrective actions.
  3. Netlock confirmed implementation of new internal measures to ensure compliance.
Thread Activity
  1. Mozilla representative — Requesting Netlock to file an incident report regarding their failure to provide updates.
  2. Netlock — Netlock expressed intent to open a preliminary incident report.
  3. Netlock — Netlock committed to providing a report that meets community requirements.
  4. Netlock — Netlock provided an updated action item summary and confirmed completion of corrective actions.
  5. Netlock — Netlock submitted a report closure summary detailing the incident and corrective measures.
Participants
Community commenter
Related Bugzilla IDs Mentioned
Similar Local Cases
#2013400 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-04-17 · 86% similar
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
#2007948 RESOLVED Self Reported Incident Incident Opened 2025-12-29 · Closed 2026-04-20 · 83% similar
NETLOCK: Full Incident Report was not published within 14 days of notification
#1962426 RESOLVED Incident Opened 2025-04-24 · Closed 2025-07-16 · 81% similar
NETLOCK: CA/Browser Forum TLS BR Non-compliance
#2013395 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-05-26 · 81% similar
NETLOCK: Missing Related Incidents section in the bug report
#1819105 RESOLVED Incident Opened 2023-02-27 · Closed 2023-09-29 · 79% similar
NETLOCK: Disclosed CRL is expired
#1938167 RESOLVED Incident Opened 2024-12-18 · Closed 2025-06-10 · 79% similar
NETLOCK: CRL not published in DER Encoded Format
#1979287 RESOLVED Incident Opened 2025-07-25 · Closed 2025-08-30 · 79% similar
NETLOCK: Expired Test Website Certificate
#2001327 RESOLVED Incident Revocation Issue Opened 2025-11-20 · Closed 2026-01-05 · 79% similar
NETLOCK: Missing CDP Disclosure in CCADB

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

Confirm action