Security

DigiCert breach: ID documents exposed by botched migration

Key takeaways

  • A February 2025 move from behind a VPN to a public network zone exposed an internal archive for over a year
  • Self-registered accounts skipped multifactor authentication and read-only access was enough to pull data
  • Affected customers should assume ID scans will be reused for account recovery and lock down carrier and bank accounts

DigiCert, a certificate authority (an organisation that vouches for a website or organisation's identity so browsers will trust it), has notified customers that an internal archive of customer records sat exposed to the internet for more than a year. The data includes names, business contact details and, in some cases, scans of passports, driving licences and utility bills. The cause was a system migration made without a security review.

DigiCert moved the affected internal system from behind a VPN to a publicly accessible network zone in February 2025. It detected the intrusion in June 2026 and deployed a fix the following month. That is a long window, and the cause was mundane.

What it does well

DigiCert's response included some sensible remedial steps. Once the attack path was understood, the company placed the archive behind a web application firewall (a filter that inspects web traffic for malicious requests) and blocked account creation through external access. It also added a security information and event management (SIEM) alert for blocked access attempts, closing a monitoring gap.

The company also published a root cause analysis that names its own failure plainly: it changed the system's network accessibility without a security review of the resulting attack surface. DigiCert says it has notified affected customers and partners and is reviewing the information involved. Its core services were not affected. Login credentials were not affected, no DigiCert-issued certificates were affected, and CertCentral and DigiCert ONE were not touched.

Where it falls short

The migration exposed an account registration feature that let outsiders create accounts with access to the archive. The system was meant to store information, not onboard users, so accounts created through the external endpoint were not subject to multifactor authentication. Those accounts had read access only. That was enough to exfiltrate customer data.

Detection was also slow and initially wrong. When the intrusion was first spotted, DigiCert concluded the unauthorised account could not reach data because it was not assigned to any application. A managed security programme flagged the flaw a few days later. Security architect Fabian Bader, whose own data was caught up, said on X that the "limited" leak covered his full personal data and potentially any verification documents he had submitted for a certificate.

The sensitive part is the documents. Security engineer Donovan Farrell warned that a passport scan plus a utility bill is close to what some help desks accept to reset an account, and advised putting a PIN or passphrase on mobile carrier and bank accounts.

How it compares

The useful comparison is between the controls that failed and the ones that would have caught the problem:

ControlWhat happened at DigiCertWhat would have helped
Pre-migration security reviewNot performed on the new network exposureAttack surface review before the move from VPN to public zone
Multifactor authenticationNot applied to self-registered accountsMFA on every route into the archive
Monitoring and triageIntrusion detected in June 2026; first assessment was wrongSIEM alerts on blocked access attempts, added after the event
Network placementArchive moved out from behind a VPN in February 2025Web application firewall and blocked external registration, now in place

Pricing and value

No price applies here, but the cost falls on customers who handed over identity documents to get a certificate. They pay in exposure rather than fees, and cannot rotate a passport scan the way they rotate a password. IT teams can check their own estate for the same mistake; a guide on how to check if a server is exposed to the internet is a good place to start.

UK angle

Who should use it

Anyone who has submitted identity verification documents to DigiCert should check whether they have been notified, and consider their data possibly exposed. That means a PIN or passphrase on mobile carrier and bank accounts, as Farrell advised. Security teams should audit what internal archives they hold, especially ones that were once VPN-only.

Verdict

DigiCert's trust infrastructure was untouched, but its handling of customer identity documents was not. The fix list is sensible, though it arrived after the data had been exposed. For IT teams, the lesson is cheap to apply: put a review gate on any move from private to public network zones, and enforce MFA on every account path, including ones nobody meant to create. For affected customers, the practical step is to lock down carrier and bank accounts now.

Frequently asked questions

Were DigiCert certificates or logins compromised?

DigiCert said no login credentials or DigiCert-issued certificates were affected, and its CA services, CertCentral and DigiCert ONE were not affected.

What data was exposed?

Names, business email addresses, phone numbers and business addresses, plus identity verification documents such as driver's licences, passports and utility bills in some records.

More from Future Technology HQ