KAMU SM: commonName not in SAN
KAMU SM identified a compliance issue where a certificate was issued without the commonName (CN) field included in the Subject Alternative Name (SAN) extension. Upon discovery on August 4, 2023, the affected certificate was revoked immediately. The CA conducted a thorough investigation, confirming that the misissuance was due to human error during the certificate issuance process. KAMU SM implemented additional controls in their checklist to prevent similar incidents and has since integrated pre-issuance linting into their certificate management infrastructure. As of September 27, 2023, all remediation actions have been completed, and the incident is now resolved.
- KAMU SM discovered a certificate was issued without a CN field in the SAN extension.
- Pre-issuance linting and other remediation measures became operational.
- Tubitak representative — Kamu SM discovered that a certificate was issued without a CN field in the SAN extension. The affected certificate was revoked immediately.
- Tubitak representative — KAMU SM provided a detailed timeline of actions taken in response to the misissuance.
- Tubitak representative — KAMU SM updated their checklist to include additional controls.
- Tubitak representative — KAMU SM confirmed that pre-issuance linting is operational in the production environment.