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

SECOM: Failure to disclose Unconstrained Intermediate within 7 Days

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 CO., LTD. failed to disclose an unconstrained intermediate certificate within the required 7-day timeframe, as mandated by Mozilla's policy. The issue was identified by an external party, leading to a request for an incident report. SECOM acknowledged the oversight, confirmed that the intermediate certificate did not meet the necessary technical constraints, and subsequently revoked the affected certificates. The CA committed to implementing procedural changes to prevent future occurrences and submitted an incident report detailing the timeline and corrective actions taken.

Model: gpt-4o-mini Generated: 2026-06-13 18:16 UTC Revised: 2026-06-16 18:44 UTC Confidence: 0.85 16 comments
Chronology
  1. SECOM was notified of the failure to disclose an unconstrained intermediate certificate.
  2. SECOM revoked the affected intermediate and server certificates.
Thread Activity
  1. Community commenter — The following certificate has been issued and is not disclosed within CCADB.
  2. Secom representative — We are now summarizing the detailed information regarding this issue.
  3. Community commenter — The certificate is required to be disclosed and audited due to insufficient constraints.
  4. Secom representative — We found that the control of the name constraints is insufficient.
  5. Secom representative — We have revoked this certificate and signing CA certificate.
  6. Fastly representative — It appears that all questions have been answered and remediation is complete.
Participants
Community commenter Secom representative Fastly representative
External References
Similar Local Cases
#1391064 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-08-16 · Closed 2023-02-22 · 100% similar
SECOM: Non-BR-Compliant Certificate Issuance
#1544712 RESOLVED Self Reported Incident Opened 2019-04-16 · Closed 2023-02-22 · 100% similar
SECOM: certificate for which “OU=-”
#1548714 RESOLVED Self Reported Incident Opened 2019-05-02 · Closed 2023-02-22 · 100% similar
SECOM: "Default City" in Subject:localityName
#1560234 RESOLVED Self Reported Incident Opened 2019-06-20 · Closed 2022-11-14 · 100% similar
SECOM: Ambiguity on KeyUsage with ECC public key
#1497703 RESOLVED Self Reported Incident Certificate Misissuance Closure Request Opened 2018-10-09 · Closed 2023-02-22 · 98% similar
SECOM: Undisclosed intermediate certificates
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 96% similar
SECOM: Non-BR-Compliant OCSP Responders
#1524452 RESOLVED Self Reported Incident Opened 2019-02-01 · Closed 2023-02-22 · 95% similar
SECOM: certificate for .test TLD
#1649962 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 84% similar
SECOM: Incorrect OCSP Delegated Responder Certificate

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

Confirm action