← SECOM Trust Systems CO., LTD. cases
Bugzilla #1398259 Self Reported Incident Incident Closure Request

SECOM: Non-BR-Compliant OCSP Responders

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

This case involves SECOM Trust Systems CO., LTD. disclosing a compliance issue related to their OCSP responders, which were found to be returning 'good' statuses for unissued certificates, violating the Baseline Requirements (BRs). The issue was initially reported in the mozilla.dev.security.policy forum, prompting SECOM to investigate and implement countermeasures. SECOM communicated their progress and actions taken, including revoking SHA-1 OCSP responder certificates and modifying their systems to comply with BR requirements. The issue was resolved, with confirmation that all OCSP responses are now compliant.

Model: gpt-4o-mini Generated: 2026-06-13 17:09 UTC Revised: 2026-06-16 18:36 UTC Confidence: 0.85 25 comments
Chronology
  1. Initial report of non-compliance with OCSP responders
  2. Confirmation that the issue for intermediate CAs was resolved
Thread Activity
  1. Mozilla representative — Reported problems with OCSP responders for SECOM.
  2. Secom representative — SECOM began examining details of countermeasures.
  3. Secom representative — Acknowledged failure to implement countermeasures in a timely manner.
  4. Secom representative — Informed that the issue for intermediate CAs was solved.
  5. Fastly representative — Confirmed that the problem has been fixed and marked the case as resolved.
Participants
Mozilla representative Secom representative Fastly representative
Related Bugzilla IDs Mentioned
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
#1497703 RESOLVED Self Reported Incident Certificate Misissuance Closure Request Opened 2018-10-09 · Closed 2023-02-22 · 100% similar
SECOM: Undisclosed intermediate certificates
#1548714 RESOLVED Self Reported Incident Opened 2019-05-02 · Closed 2023-02-22 · 99% similar
SECOM: "Default City" in Subject:localityName
#1560234 RESOLVED Self Reported Incident Opened 2019-06-20 · Closed 2022-11-14 · 96% similar
SECOM: Ambiguity on KeyUsage with ECC public key
#1563574 RESOLVED Self Reported Incident Opened 2019-07-04 · Closed 2023-02-22 · 96% similar
SECOM: Failure to disclose Unconstrained Intermediate within 7 Days
#1524452 RESOLVED Self Reported Incident Opened 2019-02-01 · Closed 2023-02-22 · 94% similar
SECOM: certificate for .test TLD
#1544712 RESOLVED Self Reported Incident Opened 2019-04-16 · Closed 2023-02-22 · 93% similar
SECOM: certificate for which “OU=-”
#2017840 RESOLVED Incident Self Reported Incident Opened 2026-02-19 · Closed 2026-04-30 · 88% similar
SECOM: Repository service disruption affecting subordinate CAs (CTJ)

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

Confirm action