← Netlock cases
Bugzilla #2007948 Self Reported Incident Incident

NETLOCK: Full Incident Report was not published within 14 days of notification

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

NETLOCK failed to publish a Full Incident Report within the required 14-day timeframe following an external notification received on December 27, 2025. This oversight was identified through a third-party report and was linked to a lack of enforced internal controls for tracking compliance with CCADB reporting deadlines. NETLOCK conducted a root cause analysis and implemented a new incident reporting system to ensure timely publication of reports in the future. The corrective actions included assigning accountability for report publication and introducing automated reminders. As of April 2026, the new system is operational, and NETLOCK has committed to ongoing monitoring and improvements.

Model: gpt-4o-mini Generated: 2026-06-13 21:03 UTC Revised: 2026-06-16 18:53 UTC Confidence: 0.90 20 comments
Chronology
  1. External concern raised regarding NETLOCK's incident reporting compliance.
  2. Deadline for publishing the Full Incident Report was missed.
  3. NETLOCK completed corrective actions and requested closure of the incident.
Thread Activity
  1. Netlock — NETLOCK acknowledged the report and initiated an internal investigation.
  2. Netlock — NETLOCK provided a Full Incident Report detailing the incident and corrective actions.
  3. Netlock — NETLOCK submitted a closure report summarizing the incident and remediation steps.
Participants
Netlock Community commenter
Related Bugzilla IDs Mentioned
Similar Local Cases
#2011314 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Externally Reported Incident Opened 2026-01-19 · Closed 2026-06-23 · 100% similar
Netlock: unspecifed revocation code (0) in CRL
#1904041 RESOLVED Ca Documents Self Reported Incident Opened 2024-06-21 · Closed 2025-07-01 · 100% similar
NETLOCK: Intermediate CA Certificate not disclosed to CCADB
#2004699 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2025-12-08 Still Open · 100% similar
Netlock: CA in AIA in PEM format
#2013395 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-05-26 · 100% similar
NETLOCK: Missing Related Incidents section in the bug report
#2013400 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-04-17 · 100% similar
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
#1962426 RESOLVED Incident Opened 2025-04-24 · Closed 2025-07-16 · 97% similar
NETLOCK: CA/Browser Forum TLS BR Non-compliance
#2001327 RESOLVED Incident Revocation Issue Opened 2025-11-20 · Closed 2026-01-05 · 96% similar
NETLOCK: Missing CDP Disclosure in CCADB
#2021559 RESOLVED Self Reported Incident Opened 2026-03-06 · Closed 2026-05-28 · 95% similar
NETLOCK: Unavailability of the document repository

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

Confirm action