← Netlock cases
Bugzilla #1962426 Incident

NETLOCK: CA/Browser Forum TLS BR Non-compliance

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 reported a compliance issue involving an expired TLS certificate served on its designated test website, https://valid.ev.tanusitvany.hu/. The incident was triggered by a community report on April 21, 2025, which highlighted that the expired certificate violated CA/Browser Forum TLS Baseline Requirements. NETLOCK acknowledged the non-compliance, attributed it to an under-configured monitoring system during a transition to automated workflows, and took corrective actions. A new valid certificate was issued and deployed by April 28, 2025. The CA has since implemented enhanced monitoring and operational responsibilities to prevent future occurrences.

Model: gpt-4o-mini Generated: 2026-06-13 21:03 UTC Revised: 2026-06-16 18:52 UTC Confidence: 0.85 24 comments
Chronology
  1. Certificate for the test website expired.
  2. Community member reported the expired certificate.
  3. New valid certificate issued and deployed.
Thread Activity
  1. Netlock — Opened a preliminary incident report regarding the expired certificate.
  2. Netlock — Submitted a full incident report detailing the compliance failure.
  3. Netlock — Provided an update on the implementation of monitoring systems.
  4. Netlock — Submitted an incident closure summary confirming all action items were completed.
Participants
Netlock Community commenter Internet Security Research Group
Similar Local Cases
#2007948 RESOLVED Self Reported Incident Incident Opened 2025-12-29 · Closed 2026-04-20 · 97% similar
NETLOCK: Full Incident Report was not published within 14 days of notification
#2013400 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-04-17 · 97% similar
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
#2013395 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-05-26 · 96% similar
NETLOCK: Missing Related Incidents section in the bug report
#1979287 RESOLVED Incident Opened 2025-07-25 · Closed 2025-08-30 · 90% similar
NETLOCK: Expired Test Website Certificate
#1938167 RESOLVED Incident Opened 2024-12-18 · Closed 2025-06-10 · 88% similar
NETLOCK: CRL not published in DER Encoded Format
#2001327 RESOLVED Incident Revocation Issue Opened 2025-11-20 · Closed 2026-01-05 · 88% similar
NETLOCK: Missing CDP Disclosure in CCADB
#2011314 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Externally Reported Incident Opened 2026-01-19 · Closed 2026-06-23 · 87% similar
Netlock: unspecifed revocation code (0) in CRL
#2004699 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2025-12-08 Still Open · 86% similar
Netlock: CA in AIA in PEM format

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

Confirm action