
On 26 October 2026, DigiCert, one of the world’s largest certificate authorities, announced its ISO/IEC 27001:2022 certification. The independent audit covered the information security management system behind its global certification authority and trust services, across operations in 11 countries including Australia. A week earlier, on 19 October, DigiCert had determined that an incident on one of its internal business systems was reportable to the browser root programs, and its full incident report is now public.
Both things can be true at once, and that is the useful lesson. A supplier’s ISO 27001 certificate is real evidence. It is just not the evidence many buyers think it is.
Short answer
An ISO 27001 certificate tells you that an accredited certification body sampled an organisation’s information security management system, within a defined scope and at a point in time, and found it conformed to the standard. It does not tell you the organisation has never had an incident, that every system is inside the scope, or that a control working on audit day was working a year earlier. Treat it as the starting point for supplier assurance under ISO 27001 controls 5.19 to 5.22, not the end of it.
What happened at DigiCert
DigiCert’s own incident report, filed with Mozilla’s root program, sets out the timeline in unusual detail:
- 4 February 2025: during an infrastructure migration, an internal business system moved from a network segment reachable only by VPN into one reachable from the internet. That made an account registration page publicly accessible.
- Accounts created through that page were not subject to the multi-factor authentication DigiCert normally requires, and the system’s authorisation model let them read archived data.
- 18 June 2026: an internal team noticed accounts that did not belong to DigiCert staff, concluded they had no access to data, and put the system behind a web application firewall.
- 21 to 24 June: DigiCert’s managed security program reported possible external account creation, and DigiCert verified it.
- 27 June to 2 July: the window in which, a later investigation found, the archived data was accessed. An authorisation fix released on 2 July closed it.
- 12 to 24 October: DigiCert first suspected access to the archived data, reset passwords, determined on 19 October that the incident was reportable, and turned off self-registration.
Most of the data was business contact information: names, business email addresses, phone numbers and addresses. For a small minority of customer accounts it included a document the customer had supplied, such as a driver licence, passport or utility bill. DigiCert says its certification authority systems run on separate network segments and that no certificates were issued, revoked or affected.
Two things are worth saying plainly. DigiCert deserves credit for publishing a root cause analysis this open; most organisations never do. And nothing public says when the certification audit took place or what it sampled, so nothing here suggests the certification body missed anything. The point is about what a certificate can and cannot carry.
Four root causes, four controls an auditor tests
DigiCert’s report lists its contributing factors and lessons. Each lines up with an ISO 27001 control, and each is the kind of thing an audit samples rather than proves everywhere:
| What DigiCert found | ISO 27001:2022 control | What an auditor would sample |
|---|---|---|
| The migration changed the system’s network exposure without a security review; it was treated as an infrastructure change rather than a security change. | 5.9 inventory of assets, 8.32 change management | A handful of network and infrastructure changes from the last year: was each risk-assessed and signed off by someone with security authority? |
| Monitoring and alerting on account activity were not enough to flag new external accounts. | 8.16 monitoring activities | Which events raise an alert, who reviews them, and the record of a recent review. |
| The June sighting was handled as an account-creation issue rather than a data-access event. | 5.25 assessment and decision on information security events, 5.26 response | One closed security event: who classified it, on what evidence, and whether anyone checked what the accounts could actually reach. |
| Authorisation relied on the system sitting behind the VPN; once that changed, the application did not stop unassigned accounts reading data. | 5.15 access control, 8.3 information access restriction | A test with a low-privilege or unassigned account: what can it read? |
The third row is the same pattern as the federal agencies that called a supplier incident a near miss, covered in The Contract Said No Offshoring. Nobody Checked. The first classification of an event tends to stick, so it should rest on evidence about what was reachable, not on what the accounts appeared to be.
What a certificate is, and is not
- It is sampled. A certification audit tests a selection of processes, records and controls over a few days. It is designed to give confidence that the system works, not to inspect every system and change.
- It is scoped. The scope statement on the certificate says which parts of the organisation, which services and which locations were assessed. Whether a particular system sits inside that boundary is answered by the scope and the Statement of Applicability, not by the logo.
- It is a point in time. Surveillance audits follow roughly annually. A certificate dated this year says little about how a control operated eighteen months ago.
- It certifies conformity to a standard that expects incidents. ISO 27001 requires an organisation to detect, assess, respond to and learn from incidents. A well-run certified system will still have them; what should differ is how they are found and handled. Our article on compliance vs conformity explains why ISO talks about conformity at all.
None of this makes a certificate worthless. It means a certificate is one piece of evidence, and the scope and dates matter as much as the badge. To confirm a certificate is genuine and current in the first place, see how to check if an ISO certificate is real or fake.
Six things to ask a certified supplier
- The scope statement. Does it name the service you buy and the locations and systems that handle your data?
- The relevant part of the Statement of Applicability. Which supplier, access, monitoring and change controls apply, and are any excluded?
- The date of the last surveillance audit, and whether any major nonconformities are still open.
- The incident notification clause. How many hours after detection will they tell you, and who receives it? Our article on supplier data breaches shows how long that gap can run without one.
- Recent incidents affecting customer data, and how each was classified. A supplier that can describe its last incident clearly is usually more reassuring than one that claims never to have had one.
- Who owns the security of the system holding your data. One of DigiCert’s own corrective actions was to name a single owner for that system’s security posture.
Record the answers in the supplier register and set a review date. That is what control 5.22, monitoring and review of supplier services, looks like when it is working.
And in your own system
The same causes sit inside most organisations. In your next ISO 27001 internal audit, pick three infrastructure or network changes from the past year and check each had a security review before it went live. Pick one closed security event and re-test the classification. And list every system that relies on being behind the VPN for its access control, because if the network position changes, the control goes with it. A gap analysis against those three questions is a short, useful exercise even for a certified system.
How Streamline helps
Streamline develops, implements and internally audits ISO 27001 information security management systems for Australian organisations, including supplier assurance, change management and incident processes that hold up when they are tested. The aim is a system that supports how your business operates and makes certification simple. Our Lead Auditors can run the internal audit, or mentor your team to run it. Get in touch for a conversation.
Frequently asked questions
Does an ISO 27001 certificate mean a company has never had a data breach?
No. It means an accredited certification body found the information security management system conformed to ISO 27001 within the certificate’s scope when it was audited. The standard expects incidents to be detected, assessed and handled, not that they never occur.
How do I check what a supplier’s ISO 27001 certificate covers?
Read the scope statement on the certificate and ask for the relevant part of the Statement of Applicability. Check the service you buy, the locations and the systems that handle your data are inside the scope, and confirm the certificate is current with the issuing certification body.
Can a certified organisation lose its certificate after a breach?
A breach does not automatically end certification. The certification body can review it at the next surveillance audit or a special audit. If it finds the system no longer conforms and major nonconformities are not corrected, the certificate can be suspended or withdrawn.
What should a supplier contract say about incident notification?
A set number of hours from the supplier’s own detection of a suspected incident, not from the end of its investigation, along with what information it must provide, who receives the notice and who decides on notifying regulators and affected people.
Sources: DigiCert incident report, Mozilla Bugzilla 2084460 (preliminary report 20 October 2026, full report November 2026); DigiCert press release, 26 October 2026; Cyber Daily, 28 October 2026.
Facts checked 8 November 2026. Next review if DigiCert publishes further findings or notification details.
Stay in the Loop
Get an email when we post an article. Your email address will not be used for marketing, and you can unsubscribe at any time.
We handle your details in line with our privacy policy.












