What evidence an SMB1001 attestation or audit relies on
An SMB1001 attestation or audit relies on a record behind every control at the tier: a configuration export, a console report, a written policy or a dated test. At Levels 1 to 3 a director attests that the controls are in place and the attestation completes the requirements, so the records are what the director relies on when signing. At Levels 4 and 5 an external auditor tests the controls against those records before CyberCert can issue the certificate. The same pack serves both, indexed by the control numbers in CyberCert's requirements workbook.

On this page
- What evidence an SMB1001 attestation or audit relies on
- Where evidence sits in SMB1001 certification
- What evidence to hold behind each SMB1001 control
- What makes a record usable as evidence
- How to index the evidence pack by control number
- Keeping evidence current through the 12 months
- How SMB1001 evidence carries into Essential Eight and ISO 27001
- SMB1001 evidence checklist and where readiness support fits
What evidence an SMB1001 attestation or audit relies on
An SMB1001 attestation or audit relies on a record behind every control at the tier: a configuration export, a console report, a written policy or a dated test. At Levels 1 to 3 a director attests that the controls are in place and the attestation completes the requirements, so the records are what the director relies on when signing. At Levels 4 and 5 an external auditor tests the controls against those records before CyberCert can issue the certificate.
The same pack serves both, indexed by the control numbers in CyberCert's requirements workbook.
Where evidence sits in SMB1001 certification
SMB1001 has five cumulative tiers, Bronze to Diamond (Levels 1 to 5), published by Dynamic Standards International and certified by CyberCert, and every certificate is valid for 12 months. The tiers, the five control areas and the certification steps are set out on the SMB1001 certification page.
Four parties rely on the records, and each one confirms something different.
The technical support specialist is the person engaged under Bronze control 1.1. The same person gives the technical confirmation in the portal, so their engagement letter should name the systems they look after. A control outside that engagement still needs an owner and a record. The auditor cannot issue certificates. CyberCert issues the certificate to the registered legal entity and lists it on the public registry.
Party: Technical support specialist
- What they confirm
- In the portal, that the technical controls within their engagement are in place
- What they rely on
- Configuration exports, console reports, patch and backup records
Party: Director, owner or authorised senior executive
- What they confirm
- That every control at the tier is implemented
- What they rely on
- The full evidence pack
Party: External auditor, Levels 4 and 5
- What they confirm
- That the controls operate as recorded
- What they rely on
- The full pack, sampled and tested against the live environment
Party: CyberCert
- What they confirm
- That the submission is complete
- What they rely on
- The attestation, and at Levels 4 and 5 a successful audit
| Party | What they confirm | What they rely on |
|---|---|---|
| Technical support specialist | In the portal, that the technical controls within their engagement are in place | Configuration exports, console reports, patch and backup records |
| Director, owner or authorised senior executive | That every control at the tier is implemented | The full evidence pack |
| External auditor, Levels 4 and 5 | That the controls operate as recorded | The full pack, sampled and tested against the live environment |
| CyberCert | That the submission is complete | The attestation, and at Levels 4 and 5 a successful audit |
What evidence to hold behind each SMB1001 control
The requirements workbook lists the controls for the tier. Each control needs a record the business can produce on request, whether a director is signing from it or an auditor is sampling it. Tiers are cumulative, so a Gold pack carries every Bronze and Silver record as well as the Gold ones.
Silver targets business email compromise, credential harvesting and basic ransomware. Its records centre on identity: who can sign in, by what method, and with what privilege. CyberCert describes Silver as the cyber-insurable tier.
Gold adds the written governance layer and detection on endpoints and email, so most of its records are documents a director approves. Platinum and Diamond keep every Gold record and add test output, which an auditor reads for remediation as closely as for findings.
Tier: Bronze
- Evidence to hold behind each control
- Engagement record for the technical support specialist; firewall configuration export; anti-virus console showing every organisation device; patch compliance report; password policy and the enforced settings; backup schedule and a dated restore test; training completion records for all staff
Tier: Silver
- Evidence to hold behind each control
- Multi-factor authentication registration report per user; account list showing no shared logins; administrative role assignments; server patch report; published SPF record; written invoice and bank-detail change procedure
Tier: Gold
- Evidence to hold behind each control
- Endpoint detection coverage report reconciled to the asset register; DKIM selectors and the DMARC record with its policy; incident response plan with named owners; digital asset register; data protection measures; responsible AI use policy; cyber insurance policy schedule
Tier: Platinum
- Evidence to hold behind each control
- Vulnerability scan reports and test findings with remediation records; multi-factor authentication method configuration showing the stronger methods in force
Tier: Diamond
- Evidence to hold behind each control
- Supplier assurance records; police vetting records; report from a live incident response exercise; application control policy and enforcement logs
| Tier | Evidence to hold behind each control |
|---|---|
| Bronze | Engagement record for the technical support specialist; firewall configuration export; anti-virus console showing every organisation device; patch compliance report; password policy and the enforced settings; backup schedule and a dated restore test; training completion records for all staff |
| Silver | Multi-factor authentication registration report per user; account list showing no shared logins; administrative role assignments; server patch report; published SPF record; written invoice and bank-detail change procedure |
| Gold | Endpoint detection coverage report reconciled to the asset register; DKIM selectors and the DMARC record with its policy; incident response plan with named owners; digital asset register; data protection measures; responsible AI use policy; cyber insurance policy schedule |
| Platinum | Vulnerability scan reports and test findings with remediation records; multi-factor authentication method configuration showing the stronger methods in force |
| Diamond | Supplier assurance records; police vetting records; report from a live incident response exercise; application control policy and enforcement logs |
What makes a record usable as evidence
A record is usable when someone outside the team can read it and reach the same conclusion. Four properties carry most of that.
The common failure is a record produced once for the attestation. The multi-factor authentication report was clean on the day, then a new starter joined without it, or a service account was added with administrative rights. The director signed against a state that no longer holds.
- Dated. Every export, report and test shows when it was produced. A restore test records the date, the system restored, the data checked and who ran it.
- From the system. A configuration export or an admin console report is stronger than a description of the setting. Where a screenshot is the only option, it shows the tenant or device name and the date.
- Reconciled to scope. Device counts match the asset register, account lists match the staff list, and the legal entity on the pack matches the entity being certified. An endpoint on the register with no detection agent is a gap.
- Owned. Each policy and plan names an owner and an approval date. An incident response plan with no named owners fails at the first question an auditor asks.
How to index the evidence pack by control number
Organise the pack by the workbook's control numbers. A pack indexed that way lets the director sign against named records and lets an auditor sample without a hunt. The Bronze workbook numbers its seven controls 1.1 to 1.4, 2.1, 3.1 and 5.1.
Use the same numbers for folder names, file names and the index sheet, and keep one line per control with its record, its date and its owner. Where one record serves two controls, file it once and point to it from both lines.
Control: 1.1
- Bronze control
- Engage a technical support specialist
- Record to file against it
- Engagement letter naming the systems in scope
Control: 1.2
- Bronze control
- Install and configure a firewall
- Record to file against it
- Firewall configuration export, dated
Control: 1.3
- Bronze control
- Anti-virus on all organisation devices
- Record to file against it
- Console device list reconciled to the asset register
Control: 1.4
- Bronze control
- Automatic tested and approved updates and patches
- Record to file against it
- Patch compliance report per device
Control: 2.1
- Bronze control
- Strong password hygiene
- Record to file against it
- Password policy and the enforced settings
Control: 3.1
- Bronze control
- Backup and recovery strategy for important digital assets
- Record to file against it
- Backup schedule and a dated restore test
Control: 5.1
- Bronze control
- Awareness training for all employees
- Record to file against it
- Training completion records per staff member
| Control | Bronze control | Record to file against it |
|---|---|---|
| 1.1 | Engage a technical support specialist | Engagement letter naming the systems in scope |
| 1.2 | Install and configure a firewall | Firewall configuration export, dated |
| 1.3 | Anti-virus on all organisation devices | Console device list reconciled to the asset register |
| 1.4 | Automatic tested and approved updates and patches | Patch compliance report per device |
| 2.1 | Strong password hygiene | Password policy and the enforced settings |
| 3.1 | Backup and recovery strategy for important digital assets | Backup schedule and a dated restore test |
| 5.1 | Awareness training for all employees | Training completion records per staff member |
Keeping evidence current through the 12 months
Recertification each year produces a new certificate against the tier's controls, so a control that was set up for the attestation and then drifted becomes a gap at renewal. DSI revises the standard and dates each edition, and the current edition is SMB1001:2026. Check the workbook for the edition in force when renewal opens, and map the existing pack to it before refreshing records.
CyberCert gives at least three months' notice of expiry. Set the refresh points earlier than that: re-run the multi-factor authentication and account reports when staff change, repeat the restore test inside each certificate period, and reconcile endpoint coverage to the asset register whenever devices are added.
How SMB1001 evidence carries into Essential Eight and ISO 27001
Multi-factor authentication, patching, backups and restricted administrative privilege sit at the centre of SMB1001 and the Essential Eight, so the same exports and reports serve both. The control-by-control comparison is at Essential Eight vs SMB1001. Whether to do SMB1001 or the Essential Eight first is at SMB1001 or Essential Eight first.
A business that holds SMB1001 Gold has policies, an incident response plan and an asset register to build from. ISO 27001 then adds the management system clauses: scope, risk assessment and treatment, a statement of applicability, internal audit and management review. The comparison is at SMB1001 vs ISO 27001.
Attribute: What the business gets
- SMB1001
- A dated certificate and a public registry listing
- Essential Eight
- A maturity level; no certificate exists
- ISO 27001
- A certificate from an accredited certification body
Attribute: Verification
- SMB1001
- Director attestation at Levels 1 to 3; attestation plus external audit at Levels 4 and 5
- Essential Eight
- Assessment of each strategy against the ASD Essential Eight Maturity Model
- ISO 27001
- External certification audit
Attribute: Renewal
- SMB1001
- 12 months, then recertification
- Essential Eight
- Reassessment when the business or a counterparty requires it
- ISO 27001
- Three-year certification cycle with annual surveillance audits
| Attribute | SMB1001 | Essential Eight | ISO 27001 |
|---|---|---|---|
| What the business gets | A dated certificate and a public registry listing | A maturity level; no certificate exists | A certificate from an accredited certification body |
| Verification | Director attestation at Levels 1 to 3; attestation plus external audit at Levels 4 and 5 | Assessment of each strategy against the ASD Essential Eight Maturity Model | External certification audit |
| Renewal | 12 months, then recertification | Reassessment when the business or a counterparty requires it | Three-year certification cycle with annual surveillance audits |
SMB1001 evidence checklist and where readiness support fits
Run this before the attestation, or before booking the auditor at Platinum and Diamond:
Get support where the gap register shows technical controls the team has not configured before or a tender fixes the certificate date. Platinum and Diamond also need support through the external audit.
Black Shard holds SMB1001:2026 Gold and runs its own estate at Essential Eight Maturity Level 3. Its readiness engagement runs a scoping call, a control-by-control gap review, hands-on remediation by our engineers, the written policies and plans, an indexed evidence pack, and support through the director's attestation or the auditor's fieldwork. The attestation belongs to the director and the certificate to CyberCert.
- [ ] Target tier recorded, with the contract, tender or insurer clause that sets it
- [ ] Legal entity name on the pack matches the entity being certified
- [ ] Technical support specialist engaged in writing, with the systems in scope named
- [ ] Gap check run before attesting, with every control at the tier marked met, partial or missing
- [ ] Multi-factor authentication report current, with no shared accounts on the account list
- [ ] Backup restore tested and dated within the certificate period
- [ ] SPF published, and from Gold, DKIM signing and a DMARC record in place
- [ ] Endpoint detection coverage reconciled to the asset register (Gold, Platinum and Diamond)
- [ ] Incident response plan, responsible AI use policy and asset register approved by a director, with owners named (Gold, Platinum and Diamond)
- [ ] Evidence pack indexed by control number, one line per control with record, date and owner
- [ ] Auditor booked, with fieldwork dates inside the 12-month window (Platinum and Diamond)
- [ ] Expiry date diarised, with record refresh scheduled ahead of CyberCert's notice



