← Netlock cases
Bugzilla #2013400
Policy Compliance
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
RESOLVED
FIXED
Netlock
AI Summary
NETLOCK failed to submit a Preliminary Incident Report within the required 72-hour timeframe after receiving a third-party report regarding a CRL reasonCode encoding issue. The organization initiated corrective actions promptly but miscalculated the reporting deadlines due to a misconfiguration in their internal incident tracking system. This incident highlights procedural non-compliance with CCADB guidelines, specifically regarding timely incident reporting. NETLOCK has since implemented corrective measures, including an updated incident tracking system and automated alerts to prevent future occurrences.
Chronology
- Third-party report received regarding CRL reasonCode encoding issue.
- 72-hour reporting deadline expired without Preliminary Incident Report submission.
- Preliminary Incident Report submitted (late).
- Closure report prepared and submitted.
Participants
Roland Kaluha
Nikolett Nagy
External References
Similar Local Cases
NETLOCK: Missing Related Incidents section in the bug report
NETLOCK: CA/Browser Forum TLS BR Non-compliance
NETLOCK: Expired Test Website Certificate
NETLOCK: CPS 1.5.2. problem and contact information update
NETLOCK: Transition Plan for Mozilla Root Store Policy 7.5 by Deadline
NetLock: Issuance of intermediates after 2019-01-01 that do not comply with Mozilla Policy
NetLock: Replacement of enduser certificates after the EVGL 1.7.4 self-audit
NetLock: Cumulative report connected to EV verification