Sectigo: Mismatch between organizationIdentifier and jurisdictionStateOrProvince
Categories
(CA Program :: CA Certificate Compliance, task)
Tracking
(Not tracked)
People
(Reporter: martijn.katerbarg, Assigned: martijn.katerbarg)
Details
(Whiteboard: [ca-compliance] [ev-misissuance])
Attachments
(1 file)
|
7.74 KB,
text/csv
|
Details |
Preliminary Incident Report
Summary
-
Incident description:
On October 31st, we received a CPR, outlining a mismatch between the organizationIdentifier and jurisdictionStateOrProvince subject attribute values in a single certificate. Specifically, the reported certificate included the jurisdictionStateOrProvince subject attribute, but the organizationIdentifier did not reference a registration at a state level.The certificate, as well as a second certificate identified during our preliminary investigation, are scheduled to be revoked.
We are currently working on further investigating this incident and will post a full incident report within the required timeline.
-
Relevant policies:
- Guidelines for the Issuance and Management of Extended Validation Certificates, Section 7.1.4.2.8
-
Source of incident disclosure: Third Party Reported
Updated•13 days ago
|
| Assignee | ||
Comment 1•4 days ago
|
||
| Assignee | ||
Comment 2•4 days ago
|
||
Full Incident Report
Summary
-
CA Owner CCADB unique ID: A000016
-
Incident description:
On October 31st, we received a CPR, outlining a mismatch between the organizationIdentifier and jurisdictionStateOrProvince subject attribute values in a single certificate. Specifically, the reported certificate included the jurisdictionStateOrProvince subject attribute, but the organizationIdentifier did not reference a registration at a state level.
Subsequent review revealed a total of 13 certificates affected by a similar symptom.
-
Timeline summary:
- Non-compliance start date: 2025-12-10
- Non-compliance identified date: 2026-10-31 – 13:13 UTC
- Non-compliance end date: 2026-11-07 – 20:09 UTC
-
Relevant policies:
- Guidelines for the Issuance and Management of Extended Validation Certificates, Section 7.1.4.2.8
-
Source of incident disclosure: Third Party Reported
Impact
- Total number of certificates: 13
- Total number of "remaining valid" certificates: 0
- Affected certificate types: TLS EV - QWAC
- Incident heuristic: The full corpus of affected certificates are disclosed in the Appendix.
- Was issuance stopped in response to this incident, and why or why not?: No. QWAC certificate issuance happens at a low issuance rate. As such we were able to update identifiers as quickly as we could have halted issuance.
- Analysis: N/A
Timeline
All times in UTC.
2026-10-31:
- 12:57 We receive a CPR highlighting a single TLS certificate with a mismatch between the jurisdictionStateOrProvince value, and the organizationIdentifier, which contains no state reference.
- 13:13 We acknowledge receipt of the CPR and start our investigation.
- 17:00 We confirm the misissuance.
- 17:02 A second certificate for the same subscriber is identified.
- 17:04 We update the registration reference regex for the location in question.
- 17:09 We schedule the revocation of the two initially identified certificates. Subscriber notifications are sent.
- 17:42 We send an internal email notifying responsible teams of the upcoming revocation of two certificates.
- 18:45 We reply to the CPR confirming the finding.
2026-11-02:
- 08:39 An internal request is created to extract all issued QWAC certificates for further review.
- 20:19 The report is delivered by our DBA team.
2026-11-03:
- 08:00 We review the DBA-generated report. An additional 11 certificates are identified.
- 08:43 The identified certificates are sent to our validation department for a complete review of the registration reference regexes used.
2026-11-04:
- 10:58 We schedule the revocation of the 11 additional identified certificates. Subscriber notifications are sent.
- 11:09 The two initially identified certificates are revoked.
2026-11-07:
- 20:09 The 11 additionally identified certificates are revoked.
Related Incidents
| Bug | Date | Description |
|---|---|---|
| 2074611 | 2026-09-22 | This bug raises a similar issue, but highlights partially a different root cause. |
Root Cause Analysis
Contributing Factor #1: Different requirements for organizationIdentifier between EVGs and S/MIME BRs
-
Description:
Within Sectigo, S/MIME certificates are the main product relying on the organizationIdentifier. As such, manual data entries for our guard rails around the organizationIdentifier have mainly been incorporated based on the understanding of the S/MIME BRs.
Within the EVGs, the requirement around the NTR-based organizationIdentifier state:
“where registrations are administrated at the subdivision (state or province) level, if required under Section 7.1.4.2.4, a plus "+" (0x2B (ASCII), U+002B (UTF-8)) followed by an up-to-three alphanumeric character ISO 3166-2 identifier for the subdivision of the nation in which the Registration Scheme is operated;”
This requirement differs from the S/MIME BRs, which state:
“If the Registration Reference is assigned at the subdivision (state or province) level and is not unique at the national level, the Registration Scheme SHALL be identified using the following structure in the presented order”.
The key difference here is that the S/MIMEs only require the inclusion of the state identifier, if the registration is done at the state level and the identifier is not unique at the country level. The EVGs do not state this second requirement, and thus require the state identifier even if the registration number is unique at the country level.
-
Timeline: This has been in place since the S/MIME BRs changed their requirements in May of 2025.
-
Detection: This was discovered during the investigation into this incident.
-
Interaction with other factors: This minor difference in requirements led to incorrect data entries as outlined in Contributing Factor #2.
Contributing Factor #2: Incorrect manual data entry for supporting automated guard rails
-
Description:
We have a guard rail in place to prevent incorrect values from being included in certificates in regards to their subject:serialNumber, organizationIdentifier and jurisdictionOfIncorporation attributes.
This (otherwise automated) guard rail, relies on manual data entry regarding its ruleset. This data includes regex-based organizationIdentifier formats.
Within Sectigo, S/MIME certificates are the main product relying on the organizationIdentifier. As such, the manual data entries have mainly been incorporated based on the understanding of the S/MIME BRs. As outlined in Contributing Factor #1, the requirements between both documents are different, a fact that was not well understood.
-
Timeline: This has been in place since the S/MIME BRs changed their requirements in May of 2025.
-
Detection: This was discovered during the investigation into this incident.
-
Interaction with other factors: S/MIME certificates are the main product relying on the organizationIdentifier for Sectigo. Due to this, and the difference in requirements as outlined in Contributing Factor #1, the manual data entries were added incorrectly.
Contributing Factor #3: No standing annual review of regex-based guard rail.
-
Description:
While ad-hoc reviews are being performed regarding the regex-based guard rail, no official annual review is in place.
-
Timeline: This has been the case since our initial creation of this guard rail several years ago.
-
Detection: This was discovered during the investigation into this incident.
-
Interaction with other factors: N/A.
Lessons Learned
- What went well: N/A.
- What didn’t go well:
- There was a gap in the understanding of the EVGs vs S/MIME BRs in terms of the organizationIdentifier.
- No recurring review of the regex-based guard rails is in place.
- Where we got lucky:
- Only a lower number of certificates were affected.
- Additional: N/A
Action Items
| Action Item | Kind | Corresponding Root Cause(s) | Evaluation Criteria | Due Date | Status |
|---|---|---|---|---|---|
| Instigate annual review of all jurisdictionOfIncorporation / organizationIdentifier regex entries. | Mitigate | Contributing Factor #2 & 3 | Adding an annual, tracked, review should prevent degradation of the existing data-set over time. | 2026-12-23 | Ongoing |
| Initiate Validation Subcommittee discussion around the use of the organizationIdentifier and get opinions around aligning with the S/MIME BRs. | Prevent | Contributing Factor #1 | Aligning the S/MIME BRs and EVGs, should make the requirements clearer and prevent a split-understanding between different policies. | 2026-12-23 | Ongoing |
Appendix
The affected certificates are listed in attachment #9682612 [details].
Description
•