No — SMB1001 certification does not transfer with a change in ownership. The certificate is issued to a specific legal entity that has attested (or been audited) against the standard's controls; when that entity is sold, merged or restructured, the new owner must confirm the controls still hold under their direction or re-certify from their position. What does survive an ownership change is the underlying work: if the firewall, backups, MFA, access control and staff training are all still operating, re-establishing certification is a paperwork exercise rather than a rebuild.
TL;DR
- The certificate attaches to the legal entity, not the business's goodwill or its assets — it does not transfer automatically.
- At Bronze, Silver and Gold a director attests the controls; a new owner has to sign that attestation themselves.
- Platinum and Diamond add an independent audit, so a change of legal entity is a bigger event there.
- Continuous controls (backups, patching, training) carry over; the formal claim does not.
- Renaming the company or registering a new ACN mid-cycle usually means re-certifying under the new entity.
Why the certificate cannot simply change hands
SMB1001 is the cybersecurity standard for small and medium businesses, published through the DSI and administered by CyberCert, with five tiers: Bronze, Silver, Gold, Platinum and Diamond. At Bronze, Silver and Gold the mechanism is director attestation: a named director signs that the control set is in place and operating, backed by evidence. The signer is a person inside a specific legal entity — the certificate names that entity.
That is why a change of ownership is different from a change of logo. When the entity itself changes (a new company acquires the business, shares change hands, the registered entity is replaced), the party who made the attestation is no longer the party operating the business. A certification body cannot extend a claim made by one legal person to another — the new owner's statement has to be their own.
What happens at each tier
The mechanics differ by how the claim is verified:
- Bronze, Silver and Gold — self-attested. The new owner (or a director they appoint) signs the attestation and supplies current evidence that each control is in place. Because there is no external audit, this is typically a fast administrative step if the controls never stopped operating.
- Platinum and Diamond — independently verified. These tiers add verification by an independent auditor, so a change of legal entity is a materially bigger event: the new entity generally re-enters the assessment rather than inheriting the old one's audit result.
Either way, the practical sequence is the same: tell the certification body early, and expect the certificate to be reissued to the new entity rather than endorsed.
What carries over — and what has to be redone
Think of an ownership change as two layers:
- Carries over: the operating controls. Firewalls, automatic updates, MFA, backups, access reviews and staff awareness training are practices, not paperwork. If they kept running through the sale, they need no work — just evidence.
- Must be redone: the formal claim. The attestation signature, the entity named on the certificate, and any documentation addressed to the old entity. This is where the certificate is reissued.
The distinction matters most for staff training records. Named, per-person completion records — the kind Cyber Aware's awareness training produces by default — are evidence of a practice, so they remain valid across the transaction as long as the same people are still employed. What changes is whose name the evidence folder is submitted under.
A worked example
A 22-person logistics firm operating at SMB1001 Silver is acquired by a larger group. The sale completes on 1 March; the target company's registration is retained (same legal entity, new shareholders). Because the legal entity did not change, certification survives the transaction — but the director who signed the attestation has resigned, so the new appointee must re-sign the attestation with fresh evidence before the next reporting point.
Contrast a different deal: the buyer instead incorporates a new company and transfers the business into it. The certificate named the old entity, so it ends with the old entity. The good news is that nothing operational changed — the same IT stack, the same staff, the same training records. Under the new entity, the team re-runs the Bronze or Silver checklist, re-signs the attestation, and is re-certified in weeks, using the existing gap assessment results as the evidence base rather than starting from zero.
The pattern holds across both cases: the certificate is the paperwork layer, the controls are the real layer, and an ownership change touches only the first.
The 90-day action list for buyers and sellers
Whoever is doing the deal should put these on the transaction plan:
- Due diligence (pre-sale). Ask for the current certificate tier, the most recent evidence pack and any audit findings. A lapsed certification is a finding worth pricing.
- Completion day. Notify the certification body of the transaction. Confirm which legal entity the business now operates as.
- Within 30 days. Appoint the new signing director, re-attest the controls (Bronze to Gold) or open the re-verification conversation (Platinum and Diamond).
- Within 90 days. Refresh the evidence pack: current staff training completion, current access list, current backup and patching logs. Cyber Aware's human risk reporting exports per-learner completion and risk in one branded pack, which is the fastest way to evidence that training carried over intact.
Deals that skip the notification step are the ones that end up re-certifying from scratch at renewal — avoidable with a one-line email at completion.
Common traps
- Assuming "the business" and "the entity" are the same thing. A share sale and a business sale are different events for certification. Ask which entity is named on the certificate before you plan the transfer.
- Letting the controls pause during handover. If MFA rollout, backups or training stop for a quarter while everyone focuses on the deal, the new owner inherits control debt, not just paperwork.
- Forgetting the contract chain. Insurers and enterprise customers often require certification in the name of the contracting entity. A certificate in the old entity's name can fail a contract check even while it technically remains valid.
FAQ
Does SMB1001 certification transfer with a change in ownership? No. The certificate is issued to a named legal entity. When the entity itself changes — through sale, merger or incorporation of a new company — the new owner must re-attest the controls or re-enter verification; the certificate is reissued rather than endorsed.
What if the shares change hands but the company stays the same? The legal entity is unchanged, so the certification survives — but if the signing director leaves, a new director must re-sign the attestation with current evidence at the next reporting point.
How long does re-certification take after a business sale? At Bronze and Silver, usually weeks, because the controls carry over and the process is self-attested. Gold is a larger control set; Platinum and Diamond involve independent verification, which takes longer.
Does the new owner need to retrain all staff? No. Training completion records are evidence of a practice and stay valid while the same people are employed. New owners should confirm records are current, not start training from zero.
Can we certify the new entity at a higher tier during the transition? Yes, and transitions are often the natural moment to re-assess: the same evidence base supports a re-run of the gap assessment, which shows whether a higher tier is reachable without new spend.
One last thing
If a deal is even being discussed, keep the evidence pack continuously current — training exports, access reviews, backup logs — rather than assembling one when the lawyers ask. A business that can produce 12 months of unbroken evidence on a day's notice changes hands without a certification gap, whatever the structure of the transaction.