← SECOM Trust Systems CO., LTD. cases
Bugzilla #2017840 Incident Self Reported Incident

SECOM: Repository service disruption affecting subordinate CAs (CTJ)

RESOLVED FIXED SECOM Trust Systems CO., LTD.
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

SECOM Trust Systems reported a service disruption affecting repository services for its subordinate CA, Cybertrust Japan (CTJ). The incident occurred from February 17 to February 18, 2026, due to a sudden surge in access requests that led to a temporary denial of service condition. SECOM self-reported the incident and confirmed that no certificates were affected. The root cause was identified as inadequate risk assessment regarding the cloud service provider's capacity to handle traffic spikes. Remediation actions included redesigning the system architecture and implementing automated mechanisms to ensure service continuity. All action items have been completed, and a closure report is being prepared.

Model: gpt-4o-mini Generated: 2026-06-13 21:08 UTC Revised: 2026-06-16 18:56 UTC Confidence: 0.90 12 comments
Chronology
  1. Service disruption began due to a surge in access requests.
  2. Service disruption ended after the affected server was isolated.
  3. Closure report prepared after all remediation actions were completed.
Thread Activity
  1. Ml representative — Preliminary incident report submitted detailing the service disruption.
  2. Ml representative — Full incident report provided with detailed analysis and timeline.
  3. Ml representative — All action items completed; closure report preparation initiated.
  4. Ml representative — Final incident report and closure summary submitted.
  5. CCADB representative — Final call for comments on the incident report before closure.
Participants
Ml representative CCADB representative
External References
Similar Local Cases
#1975624 RESOLVED Self Reported Incident Opened 2025-07-04 · Closed 2025-09-24 · 97% similar
SECOM: Cybertrust Japan's CRL lacks the critical flag in the issuingDistributionPoint extension
#1950574 RESOLVED Self Reported Incident Opened 2025-02-26 · Closed 2025-09-15 · 96% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#1391064 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-08-16 · Closed 2023-02-22 · 88% similar
SECOM: Non-BR-Compliant Certificate Issuance
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 88% similar
SECOM: Non-BR-Compliant OCSP Responders
#1539358 RESOLVED Self Reported Incident Opened 2019-03-27 · Closed 2023-02-22 · 82% similar
SECOM: Insufficient Serial Number Entropy
#1563574 RESOLVED Self Reported Incident Opened 2019-07-04 · Closed 2023-02-22 · 80% similar
SECOM: Failure to disclose Unconstrained Intermediate within 7 Days
#1544722 RESOLVED Self Reported Incident Opened 2019-04-16 · Closed 2023-02-22 · 79% similar
SECOM: certificate for which “L” and “ST” not set
#1548714 RESOLVED Self Reported Incident Opened 2019-05-02 · Closed 2023-02-22 · 79% similar
SECOM: "Default City" in Subject:localityName

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

Confirm action