Latest / Decrypted: The UK Cyber Briefing / DigiCert's archived customer data sat behind a door nobody checked
Transcript
- 0:03Good morning, and welcome to Decrypted.
- 0:05I'm Belinder. It's Friday, the sixth of November, twenty twenty-six, and this is the morning edition.
- 0:11DigiCert's archived customer data sat behind a door nobody checked.
- 0:18DigiCert, the company whose certificates put the padlock in your browser, has told customers about a problem
- 0:24with a business system. It held archived customer records, and it sat reachable from the internet for about 17
- 0:31months. Outsiders read some of it over five days.
- 0:34DigiCert's own incident report blames a routine server migration.
- 0:39The company says no certificates were issued or altered.
- 0:42And nothing in this needed a clever attacker.
- 0:45So, what actually happened?
- 0:47In February 2025, DigiCert moved an internal business system.
- 0:52It had been on a network segment reachable only over a V P N.
- 0:56It went to a different availability zone, and that made it reachable from the internet.
- 1:00The system had a self-registration feature meant for other uses, so anyone could create an account.
- 1:06Those accounts skipped the multi-factor authentication, the second check on top of a password, that DigiCert
- 1:12normally requires. They were read-only.
- 1:15But an authorisation flaw let them read archived customer data.
- 1:19Think of moving a filing room from inside a locked office suite to a unit on the high street.
- 1:24The cabinets are unchanged.
- 1:26But the suite's front door was the only lock that mattered, and nobody checked the new door had one.
- 1:32Now, how did it look from the defenders' side?
- 1:35Staff noticed unfamiliar accounts on 18 June 2026.
- 1:39They concluded the accounts couldn't reach customer data.
- 1:42So they put a web application firewall, a filter in front of a website, in front of the system to block new sign-ups.
- 1:49The root cause was found on 30 June, and the fix shipped on 2 July.
- 1:54But DigiCert's report says the incident "was initially handled as an account-creation issue rather than a data-access
- 2:01event." Data access had run from about 27 June to 2 July.
- 2:05DigiCert first suspected it on 12 October, and confirmed a reportable event on 19 October.
- 2:12What was exposed? Mostly business contact details: names, business emails, phone numbers and addresses.
- 2:19A small minority of customer accounts also held a customer-provided document, such as a driving licence, passport
- 2:26or utility bill. DigiCert hasn't published how many customers are affected.
- 2:30It says it's still reviewing documents to work out who to notify.
- 2:34Treat the identity documents as the real exposure.
- 2:38A business email can be changed.
- 2:40A passport can't. So, what's the Secure by Design lesson?
- 2:45DigiCert names three root causes.
- 2:48The network change had no security review.
- 2:51Monitoring and alerting were insufficient.
- 2:53And the authorisation model didn't account for self-registration.
- 2:57Network changes now need security sign-off, and file-access and request-volume alerts went live on 15 October.
- 3:04Each fix is a decision that could have been made before the migration.
- 3:09A network boundary was doing the job of access control, so when the boundary moved, nothing else was left.
- 3:15Secure by Design means a system that stays safe when someone exposes it by accident.
- 3:20Ask your own teams what the last system they moved quietly relied on.
- 3:24And ask whether you still hold archived identity documents you no longer need.
- 3:29Data you've deleted can't be read through a forgotten door.
- 3:32As always, this is opinion, not advice.
- 3:36That was Decrypted, with me, Belinder.
- 3:40The written version and every source are linked in the show notes.
- 3:44Thanks for listening. Stay patched, and stay sceptical.