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

SECOM: certificate for which “L” and “ST” not set

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. identified a compliance issue involving a certificate that lacked the 'L' and 'ST' fields. The CA discovered the problem during an internal investigation on March 6, 2019, and subsequently contacted the customer to revoke the certificate, which was completed on March 15, 2019. Following this incident, SECOM found an additional seven certificates with similar issues and committed to revoking them by the end of June 2019. The CA has since updated its procedures to ensure compliance with revocation timelines as outlined in the Baseline Requirements.

Model: gpt-4o-mini Generated: 2026-06-13 18:11 UTC Revised: 2026-06-16 18:42 UTC Confidence: 0.85 17 comments
Chronology
  1. Certificate issued without 'L' and 'ST' fields.
  2. Problem certificate discovered during internal investigation.
  3. Problem certificate revoked.
  4. All seven problematic certificates revoked.
Thread Activity
  1. Secom representative — SECOM reported the discovery of a certificate without 'L' and 'ST' and outlined the revocation process.
  2. Fastly representative — Requested clarification on the timeline for revocation of additional problematic certificates.
  3. Secom representative — Updated that three out of seven problematic certificates had been revoked.
  4. Secom representative — Confirmed that all seven problematic certificates had been revoked.
  5. Secom representative — Informed that the validation manual had been updated to prevent future delays.
Participants
Secom representative Fastly representative Community commenter
External References
Similar Local Cases
#1539358 RESOLVED Self Reported Incident Opened 2019-03-27 · Closed 2023-02-22 · 100% similar
SECOM: Insufficient Serial Number Entropy
#1576133 RESOLVED Self Reported Incident Opened 2019-08-23 · Closed 2023-02-22 · 83% similar
SECOM: Mis-issued EV Certificates
#1548714 RESOLVED Self Reported Incident Opened 2019-05-02 · Closed 2023-02-22 · 82% similar
SECOM: "Default City" in Subject:localityName
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 81% similar
SECOM: Non-BR-Compliant OCSP Responders
#1544712 RESOLVED Self Reported Incident Opened 2019-04-16 · Closed 2023-02-22 · 81% similar
SECOM: certificate for which “OU=-”
#1560234 RESOLVED Self Reported Incident Opened 2019-06-20 · Closed 2022-11-14 · 81% similar
SECOM: Ambiguity on KeyUsage with ECC public key
#1649962 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 81% similar
SECOM: Incorrect OCSP Delegated Responder Certificate
#1391064 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-08-16 · Closed 2023-02-22 · 80% similar
SECOM: Non-BR-Compliant Certificate Issuance

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

Confirm action