← Krajowa Izba Rozliczeniowa S.A. (KIR) cases
Bugzilla #2047952 Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Ccadb Disclosure Issue

KIR incident report closed after fixing OCSP coverage and CPR triage for a precertificate-only issuance

RESOLVED FIXED Krajowa Izba Rozliczeniowa S.A. (KIR)
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

Krajowa Izba Rozliczeniowa S.A. (KIR) is the subject of a third-party Certificate Problem Report about an OCSP responder returning `unknown` for one precertificate. KIR explained that the precertificate was signed and logged to CT, but no final certificate was issued, so its OCSP process had no entry for that serial. The thread also records that KIR’s acknowledgement to the reporter took more than 24 hours, and KIR accepted that this response time was non-conformant. KIR said it maintains a continuous 24x7 channel to accept CPRs, but its intake and triage initially checked only final certificates, which delayed recognition of the report as a valid CPR. KIR later completed the CPR intake/triage update, published the affected serial to OCSP with authoritative `good` status, and stated that all action items were complete. On 2026-07-27, KIR posted a closure summary requesting closure of the incident report, and CCADB issued a final call for comments with a planned closure date of about 2026-08-03.

Model: gpt-5.4-mini Generated: 2026-06-19 19:40 UTC Revised: 2026-08-09 06:01 UTC Confidence: 0.97 11 comments
Chronology
  1. A precertificate was signed without a corresponding final certificate being issued.
  2. KIR received a CPR email reporting that its OCSP responder returned `unknown` for the precertificate.
  3. KIR replied to the reporter after more than 24 hours.
  4. KIR published the precertificate serial to OCSP with authoritative `good` status.
  5. KIR stated that all action items were completed and requested closure of the incident report.
Thread Activity
  1. Kir representative — Opened a preliminary incident report saying KIR received a problem report about an OCSP response of `unknown` for one precertificate and had started analysis.
  2. Kir representative — Filed the full incident report explaining that the precertificate had no final certificate and that OCSP status was created only at final issuance.
  3. Community commenter — Asked KIR to explain the delay beyond 24 hours and whether it maintained the required continuous 24x7 ability to accept and respond to CPRs.
  4. Kir representative — Accepted that the response exceeded 24 hours and said the report was not initially recognized as a valid CPR because it did not match final-certificate inventory.
  5. Kir representative — Posted a weekly update saying there were no changes and activities were progressing as planned.
  6. Kir representative — Reported completion of the CPR intake/triage update so serials not found among final certificates are also checked against precertificates and all reports are acknowledged within 24 hours.
  7. Kir representative — Stated that all key activities were on track and progressing as planned.
  8. Kir representative — Posted a weekly update repeating that all key activities were on track and progressing as planned.
  9. Kir representative — Posted a closure summary stating that all action items were completed and requesting closure of the incident report.
  10. CCADB representative — Issued a final call for comments or questions and said the report would be closed on approximately 2026-08-03.
Participants
Kir representative Community commenter CCADB representative
Similar Local Cases
#2032482 RESOLVED Ca Certificate Compliance Incident Certificate Misissuance Problem Reporting Failure Opened 2026-04-16 · Closed 2026-07-30 · 86% similar
OATI: Misissuance detected by PKIMetal
#2055539 RESOLVED Problem Reporting Failure Incident Externally Reported Incident Revocation Issue Opened 2026-07-16 · Closed 2026-08-11 · 82% similar
DigiCert: Delayed availability of OCSP responses
#2059735 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Audit Finding Opened 2026-07-31 Still Open · 81% similar
Asseco DS / Certum: Delayed publication of Full Incident Report for Bug 2055775
#2050274 RESOLVED Incident Ccadb Disclosure Issue Problem Reporting Failure Remediation Tracking Opened 2026-06-24 · Closed 2026-08-04 · 81% similar
FNMT: Delay in incident disclosure reporting for Bug 2049012
#2041774 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2026-05-22 · Closed 2026-08-13 · 80% similar
OATI: AIA CA Issuer field pointing to PEM encoded cert
#2048995 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-06-19 · Closed 2026-07-30 · 80% similar
eMudhra emSign PKI Services: OCSP Responder Returned "Unauthorized" for Some Pecertificates
#2055542 RESOLVED Incident Problem Reporting Failure Ccadb Disclosure Issue Opened 2026-07-16 · Closed 2026-08-17 · 79% similar
DigiCert: Delayed response to problem report related to Bug 2055539
#2049179 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-06-21 · Closed 2026-08-04 · 79% similar
CFCA: OCSP Service return unauthorized responses

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

Confirm action