Self-registration on an internet-facing internal archive minted DigiCert accounts that never faced the MFA staff logins required. According to DigiCert’s full incident report on Mozilla Bugzilla 2084460, those principals later read archived customer business contacts and, for a small minority of records, customer-supplied identity documents between 27 June and 2 July 2026. Certificate operations stayed clean: zero certificates were affected. Preventing MFA-less self-registration on an exposed internal enterprise archive starts at verified enrollment, not at a second prompt after a disposable account already exists.

What DigiCert put on the public internet

DigiCert moved its internal business archive on 4 February 2025 from a VPN-restricted segment into an externally accessible availability zone. The change improved availability and also left an internal system reachable from the open internet for well over 500 days. A self-registration feature intended for other products or use cases remained available on that host. Anyone who found the endpoint could create a non-staff account.

According to DigiCert’s report, accounts registered through that endpoint were not subject to the multi-factor authentication DigiCert otherwise requires for staff accounts, and those accounts were assigned read-only mode by default. Staff paths still demanded MFA. The unintended path did not. Unauthorized read access of archived customer data ran from 27 June through 2 July 2026. DigiCert states the access could not write records, act as a validation approver, or issue certificates. Most reachable material was business contact information: names, business emails, phone numbers, and business addresses. A small minority of records included customer-supplied identity documents such as passports, driver’s licenses, or utility bills. DigiCert has not published an exact record or customer count.

Remediation stacked network, authorization, and account controls: a WAF blocked new external account creation on 18 June 2026, an authorization patch on 2 July 2026 disallowed archived-data access by unassigned accounts, password resets for all business system users landed on 17 October 2026, and self-registration was later deactivated with endpoints moved behind private-IP load balancers. For the step-by-step exposure timeline and what the MFA-less principal could read, see the companion write-up on legacymfa.sucks.

Why staff MFA never covered the self-registered account

Workforce MFA only evaluates principals that must enroll under it. DigiCert’s staff accounts did. The inadvertent self-registration path created accounts outside that rule set on a host that no longer sat behind VPN. The first failure was enrollment policy on an internet-reachable internal system, not a missing push on a staff identity that already existed.

Once a self-registered principal signed in, a second failure sat in authorization. Unassigned accounts retained permission to read archived data until the 2 July 2026 patch. DigiCert describes those accounts as read-only by default, yet unassigned readers still reached archives until that fix. Login factors never argued with a principal that was already inside with archive read rights. The company later completed a least-privilege review of the permissions model and clarified ownership on the disclosure thread, which also names adjacent CA-program privacy and archive-data incidents at TWCA and D-Trust as separate context, not the same intrusion path.

Stage What failed Login MFA reach
Enrollment Self-reg without staff MFA Never applied to new principal
Network VPN removed 4 Feb 2025 Exposure, not a second factor
Authorization Unassigned accounts still read archives After sign-in, outside login MFA
CA issuance path Not in the access path Zero certificates affected

Staff MFA looking correct on paper while a parallel signup path skipped it is a common enterprise pattern. The archive did not need a novel relay kit. It needed a cheap account on a host that should not have been public and should not have offered open registration.

How verified enrollment stops the MFA-less principal

Device-bound, phishing-proof authentication removes transferable secrets at registration, device onboarding, authorisation, authentication, and decommissioning. There is no password to type into a self-serve form, no OTP or recovery code for a stranger to complete, and no enrollment shortcut that mints a usable archive identity without an already-enrolled device under policy. A verified enrollment model that refuses MFA-less self-registration on enterprise archives simply does not create that principal.

Against DigiCert’s initial-access stage, that is prevention before a session exists. The self-registration endpoint cannot hand out a working non-staff login if every archive identity must be bound to hardware-held keys under controlled onboarding. Public keys live at the identity provider; private keys never leave the device. An attacker who only finds an open signup URL has nothing transferable to finish.

Against the data-access stage, login cryptography does not rewrite an authorization matrix. After any legitimate session exists, unassigned roles that still read archives are an authorization problem. Least privilege, continuous review of unassigned permissions, and keeping internal archives off public address space close that layer. DigiCert’s 2 July 2026 patch and later private-IP load balancer move are that class of control. Prevention, not detection applies to stopping the MFA-less account from being born; revoke, monitoring, and permission repair apply after a session already holds read rights.

Control MFA-less self-reg login Unassigned archive read after sign-in
Staff OTP or push only Misses parallel signup path No effect on role grants
Passkeys at login only Hardens staff ceremony Enrollment gap can remain
Phishing-proof device-bound enrollment Blocks MFA-less principal Does not fix authorization
Least privilege + private network Reduces blast radius Required after any session

Secure explicit per-app sign-on is not the center of this incident. DigiCert’s path was not classic SSO token replay across a fleet of apps. The blast radius came from one archive product’s enrollment and permission model on a host that left the VPN.

Passkeys harden login; open self-reg still decides who enrolls

Passkeys and WebAuthn put a key pair on the device, keep the private key in hardware, and produce an origin-bound signature at authentication. That design is origin-bound at the login ceremony: a fake origin cannot complete a meaningful signature, and there is no reusable OTP to relay. On a generic enterprise identity provider that issues only hardware-bound signatures, staff who already hold passkeys get a much harder login to steal than passwords plus SMS.

Passkeys alone do not automatically police every registration path. If an application still offers self-registration that creates an account without binding a device under the same hardware policy, the login-hardening story never starts for that principal. DigiCert’s staff MFA requirement and the self-registered archive accounts show the split: stronger staff login would not have evaluated identities born on the unintended endpoint. origin-bound login hardening and phishing-proof full-lifecycle enrollment are adjacent rungs on the control ladder, not synonyms.

Closing the registration gap DigiCert left open

DigiCert’s enrollment failure was concrete. A feature meant for other products stayed enabled on the business archive. Self-registered accounts skipped staff MFA. Default read-only assignment still left unassigned accounts able to read archives until the July authorization patch. Network exposure from 4 February 2025 made that endpoint reachable without VPN. Later deactivation of self-registration, password resets on 17 October 2026, WAF hostname rules, private-IP load balancers, security sign-off for internal network access changes, and an external penetration test of the business system closed operational holes that enrollment policy should have made expensive from day one.

Phishing-proof enrolment across registration, onboarding, authorisation, authentication, and decommissioning is what turns “staff have MFA” into “no archive identity exists without a verified device.” MFA 2.0 is phishing-proof across that full identity lifecycle. That coverage is stronger than origin-bound login hardening alone. DigiCert’s residual authorization work after any session still matters. The cheap win is never minting the MFA-less reader on an internet-facing internal archive.

Key takeaways for defenders

Archive privacy incidents at a certificate authority draw attention because trust brands live on identity hygiene. DigiCert showed that issuance can stay untouched while enrollment on a side system still leaks contacts and a minority of ID documents. The authentication lesson is upstream of that read: if the principal cannot be created without a hardware-bound, policy-checked enrollment, the June to July window never opens for an MFA-less stranger.

FAQ

Would phishing-proof device-bound enrollment have stopped DigiCert’s archive access?

Phishing-proof device-bound enrollment would have blocked DigiCert’s MFA-less self-registration path that created non-staff archive accounts without the MFA staff accounts required. According to DigiCert’s Bugzilla 2084460 report, that enrollment gap was the initial access route. Authorization that still allowed unassigned accounts to read archives until 2 July 2026 sits after sign-in and needs least privilege and network isolation, which login enrollment alone does not rewrite.

Why wasn’t DigiCert staff MFA enough on the business archive?

DigiCert staff MFA was not enough because it applied to staff accounts, while self-registered accounts created through the inadvertent endpoint were not subject to that MFA requirement. The February 2025 migration also placed the archive on an internet-reachable segment, so the weak enrollment path was externally reachable. Staff MFA never evaluated principals born outside the staff enrollment rule set.

Do passkeys alone fix MFA-less self-registration on internal archives?

Passkeys alone do not fix MFA-less self-registration if the application still mints accounts without hardware-bound, policy-checked enrollment. Passkeys are origin-bound at login for identities that already hold them. DigiCert’s failure was an open self-registration feature on an exposed archive that created accounts outside staff MFA. Full-lifecycle phishing-proof enrollment is what closes that registration gap beyond login-only passkeys.

What still fails after a verified archive login exists?

After a verified archive login exists, authorization and data-plane controls still decide what that session can read. DigiCert’s unassigned accounts retained archived-data read permission until the 2 July 2026 authorization patch, and the company later moved endpoints behind private-IP load balancers and deactivated self-registration. Device-bound login prevents the cheap MFA-less principal; it does not replace least privilege, monitoring, or keeping internal archives off public address space.

Did the DigiCert archive incident affect certificate issuance?

No. DigiCert reported zero certificates affected and stated that certificate operations were not impacted. The archive access could not write records, act as a validation approver, or issue certificates. CertCentral, DigiCert ONE, CA services, customer credentials for those services, and already-issued certificates were outside the compromised path described in the Bugzilla full incident report.