← Netlock cases
Bugzilla #2013400
Self Reported Incident
Incident
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
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 received a third-party report on January 12, 2026, regarding a CRL reasonCode encoding issue. Although they initiated corrective actions, they failed to submit a Preliminary Incident Report within the required 72-hour timeframe as mandated by CCADB policy. The delay was attributed to a misconfiguration in their internal incident tracking system, which incorrectly calculated reporting deadlines. NETLOCK has since implemented corrective measures, including updating their incident tracking system to ensure compliance with reporting timelines and introducing automated alerts for future incidents. The case has been resolved with all action items completed.
Chronology
- NETLOCK received a third-party report regarding a CRL reasonCode encoding issue.
- NETLOCK submitted a Preliminary Incident Report, but it was late.
- NETLOCK completed all corrective measures and requested closure of the incident.
Thread Activity
- Netlock — NETLOCK acknowledged the failure to file a preliminary incident report within the required timeframe.
- Netlock — NETLOCK provided a full incident report detailing the non-compliance and corrective actions taken.
- Netlock — NETLOCK reported that all action items have been implemented and requested closure of the incident.
Participants
Netlock
Community commenter
CCADB representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
NETLOCK: Intermediate CA Certificate not disclosed to CCADB
NETLOCK: Missing CDP Disclosure in CCADB
Netlock: CA in AIA in PEM format
NETLOCK: Full Incident Report was not published within 14 days of notification
Netlock: unspecifed revocation code (0) in CRL
NETLOCK: Missing Related Incidents section in the bug report
NETLOCK: Unavailability of the document repository
NETLOCK: CRL not published in DER Encoded Format