What happened
The archive crossed two boundaries
DigiCert says an internal business system used to archive customer-provided information became externally reachable after a February 2025 migration. An account-registration feature intended for other uses then became available to the archive. Accounts created through it were not subject to staff MFA and were assigned read-only status, yet could access archived data.
DigiCert fixed the registration and authorization path in July 2026. In October, it confirmed that an unauthorized account had accessed a subset of records before that fix. Most affected information was business contact data; a small minority of customer accounts included documents such as passports, driver's licenses or utility bills. DigiCert says certificate issuance, active certificates, CertCentral and DigiCert ONE were unaffected.
Do not infer certificate compromise
Defender workflow
Test effective access after a migration
- 1
Review reachability changes. When moving an internal application, verify its external exposure and the registration and authentication paths that become reachable with it.
- 2
Test actual permissions. Create low-privilege and unassigned test accounts, then check the records and endpoints they can really access. A role label is not an access-control test.
- 3
Look back after fixing. Preserve account, session and resource-access logs. Determine what unexpected accounts read before the permission failure was closed.
Defender note
Closing access and understanding past access are separate jobs
This incident illustrates a common investigative gap: a team can correct a route and still need time to discover what happened while it was open. The review should cover effective permissions and past requests, not just the current account state.