NETLOCK: Missing Related Incidents section in the bug report
NETLOCK submitted an incident report related to Bug 2004699, which initially limited the 'Related Incidents' section to incidents within its own operations. Community feedback clarified that the CCADB Incident Reporting Guidelines require consideration of ecosystem-wide incidents. NETLOCK acknowledged this deficiency and submitted a separate incident report to address the IRG non-compliance. The CA has since completed corrective actions, including updating its Incident Reporting Procedure and conducting internal training. All planned actions were fulfilled by April 30, 2026, and NETLOCK is now testing the effectiveness of these processes.
- NETLOCK submitted a separate incident report addressing IRG non-compliance.
- All planned corrective actions were completed.
- Netlock — NETLOCK submitted a preliminary incident report acknowledging the need for broader ecosystem consideration.
- Netlock — Full incident report submitted detailing the IRG compliance issue.
- Netlock — NETLOCK provided a closure summary confirming completion of all corrective actions.