SwissSign incident report on stateOrProvinceName formatting closed INVALID

RESOLVED INVALID SwissSign AG

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

SwissSign opened this bug as a preliminary incident report after a third party asked about unexpected stateOrProvinceName formatting in OV and EV certificates. SwissSign said its certificates used state shortcodes without the ISO 3166-1 country-code prefix and that it had started an investigation. After reviewing the relevant TLS Baseline Requirements, EV Guidelines, and its CP/CPS, SwissSign concluded that using either the state name or the shortcode was compliant. CCADB Support asked whether the bug should be closed as INVALID, and SwissSign agreed that it could be closed as INVALID if there were no further questions. The bug is now RESOLVED with resolution INVALID.

Model: gpt-5.4-mini Generated: 2026-08-26 10:55 UTC Revised: 2026-09-06 07:01 UTC Confidence: 0.96 6 comments

Chronology

2026-08-20 SwissSign opened a preliminary incident report about OV and EV certificates using state shortcodes without the ISO country-code prefix.
2026-08-21 SwissSign concluded that the formatting was compliant with the TLS BR, EV Guidelines, and SwissSign CP/CPS.
2026-09-01 The bug was resolved as INVALID.

Thread Activity

2026-08-20 SwissSign AG — Roman Fischer reported a third-party inquiry about certificate attribute formatting and said SwissSign had started an investigation.
2026-08-21 SwissSign AG — Roman Fischer explained SwissSign's analysis and said the use of the state shortcode without the country-code prefix was compliant.
2026-08-21 CCADB representative — CCADB Support said it would continue monitoring the bug and consider additional information.
2026-08-25 CCADB representative — CCADB Support asked whether the bug should be closed as INVALID.
2026-08-25 SwissSign AG — Roman Fischer agreed the bug could be closed as INVALID if there were no questions or discussion.
2026-08-25 CCADB representative — CCADB Support issued a final call for comments and said the bug would be closed as INVALID on or about 2026-09-01.

Participants

SwissSign AG CCADB representative

External References

Original Bugzilla Case www.iso.org www.iso.org repository.swisssign.com

Similar Local Cases

#2033000 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-04-17 · Closed 2026-07-09 · 96% similar

SwissSign: Certificate Profile error for S/MIME MV

AI Summary CA Owner

#2057448 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2026-07-24 · Closed 2026-10-02 · 88% similar

SwissSign: Invalid Entry in State field

AI Summary CA Owner

#1860750 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2023-10-24 · Closed 2023-11-08 · 87% similar

SwissSign: EV code in JurisdiktionStateOrProvinceName

AI Summary CA Owner

#1965828 RESOLVED Self Reported Incident Security Incident Opened 2025-05-12 · Closed 2025-08-19 · 84% similar

SwissSign: OCSP outage

AI Summary CA Owner

#1995252 RESOLVED Incident Opened 2025-10-20 · Closed 2025-12-11 · 84% similar

SwissSign: Attribute Change process did not revoke single-domain certificates

AI Summary CA Owner

#1929189 RESOLVED Certificate Misissuance Policy Document Issue Opened 2024-11-05 · Closed 2025-07-01 · 83% similar

SwissSign: S/MIME certificates deviate from CPR

AI Summary CA Owner

#1990282 RESOLVED Audit Finding Self Reported Incident Opened 2025-09-23 · Closed 2026-05-11 · 82% similar

SwissSign: recommendation on linting software updates

AI Summary CA Owner

#2056223 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-07-20 · Closed 2026-08-08 · 81% similar

D-Trust OCSP Responder Certificates Include CA/B Forum DV Policy OID

AI Summary CA Owner