ASD Essentials for Small Business: Where to Start
Skip to content

ASD Essentials for Small Business

A small business can apply ASD Essentials without a security team of its own.

ASD Essentials for Small Business

Most of the work is switching on controls in the cloud services it already pays for and agreeing with its IT provider who does what. Responsibility for the security outcome stays with the business.

ASD published ASD Essentials on October 15, 2026 as its evolution of the Essential Eight, written primarily for Commonwealth entities, critical infrastructure and large organisations. Small and medium businesses can apply the guidance where relevant. It tends to matter first when a larger customer asks for evidence of security controls or a contract calls for formal assurance.

Every chapter of ASD Essentials includes guidance for smaller organisations, and ASD says the outcomes its principles describe remain equally important at any size. A small firm and a federal department both need to know who can sign in, whether backups restore and who acts when something goes wrong.

In ASD’s words, What differs is how those outcomes are achieved and how much responsibility sits with service providers and vendors.

For a very small business, ASD’s small business cyber security handbook is often the simpler place to begin. ASD Essentials becomes more useful as the business grows, depends on more complex systems or has to show its security controls to larger customers.

Having no internal security team does not block any of this. The business can still name who manages access, who checks backups and who responds to incidents, and keep the records showing those jobs get done.

Requirements for Small Business

As of late 2026, ASD Essentials is mandatory for no one. The obligations a small business is likely to face still name the Essential Eight, and they still apply.

DriverWhat applies today
Defence supply chain (DISP)The full Essential Eight at Maturity Level Two. DISP does not reference ASD Essentials.
Critical infrastructure (SOCI rules)One of several frameworks, including the Essential Eight at Maturity Level One. The rules do not reference ASD Essentials.
Customer contractsThe framework and maturity level specified in the contract.
Cyber insuranceNo published regulatory requirement names the Essential Eight. Insurers set their own questions; see below.

Start from the requirement the business actually faces. A Defence supplier subject to DISP keeps meeting its Essential Eight obligations, and an ASD Essentials assessment is no substitute. A supplier answering customer security questionnaires first finds out which controls the customer expects and what evidence it will accept.

ASD’s maturity model FAQ suggests Maturity Level One may suit small to medium enterprises. That is general guidance. A higher target set by a contract or program takes precedence.

ASD Essentials for Critical Infrastructure covers the SOCI options.

Evidence to Collect for Customer Assurance

Most of the evidence a customer asks for already sits in systems the business pays for: the identity service, device management, backup and the IT provider’s reports. The work is exporting it on a schedule and keeping it dated.

Larger customers may ask suppliers to show that security controls keep operating. Customer assurance is one of the more likely ways ASD Essentials will reach small businesses before any regulatory transition.

The enterprise IT chapter includes Supplier cyber security assurance (GOV-11). It asks organisations to select suppliers through a proportionate risk assessment and keep assurance current. ASD has not yet published a supplier assessment method, so each customer writes its own questions.

The evidence pack below covers the controls customers and insurers ask about most. The collection methods are common practice rather than ASD requirements.

EvidenceHow to get itWhat it should show
MFA reportExport the MFA or sign-in methods report from the email and identity service’s admin console. Include every account, its registered authentication method and exceptions with expiry dates.Phishing-resistant MFA enforced for all routine interactive sign-ins (IT.PRO-13.4.FE-1), with no account relying on SMS, voice or push-only methods (IT.PRO-13.4.NE-2).
Patch reportExport update compliance records from the device management console, or request them from the IT provider. Include each device, missing updates and days outstanding.Patching timeframes the business has defined, consistently met, with excluded devices identified and their risks accepted (IT.PRO-06.2.FE-1, FE-4).
External scan reportRun or commission a vulnerability scan of public IP addresses and domains. Keep the dated results and the list of internet-facing services discovered.Every internet-facing service included in routine scanning, with results reviewed and prioritised within set timeframes (IT.PRO-06.1.FE-1, FE-3).
Backup restore testRestore a sample mailbox, shared folder or business file. Record the test date, restored item, time taken and restore point.Restoration tested within the business’s test cycle and meeting its recovery time and recovery point objectives (IT.PRO-10.3.FE-1, FE-2).
Incident contact sheet and exercise noteMaintain a one-page response procedure naming who does what in an incident and how the insurer and customers are notified. Add a dated record of the latest tabletop exercise or real incident.A procedure exercised or invoked within the test cycle (IT.RES-03.1.FE-2), with notification triggers, contacts and timeframes defined (IT.RES-05.1.FE-1).
Provider reportsDownload current security certificates or assurance reports published by each main provider. Keep the managed IT provider’s monthly service reports for the relevant period.Current assurance for each provider the business depends on, and the provider’s own record of the work it performed.
Provider responsibility registerKeep one page per provider, as described below, and date each review.Which protections each provider implements, which the business must enable and the record that proves each one.
Exception registerMaintain a short list of exceptions with an owner, approval, review date and expiry date.Approved, time-bound exceptions with expiry dates, which ASD’s implementation planning guide treats as evidence of currency.

A dated export or provider report is generally stronger evidence than a lone screenshot. A screenshot still helps when it shows the account or device, the service and the date.

Evidence has to cover the period the customer asks about. An MFA policy exported today says nothing about whether it was enforced throughout the previous reporting period. Patch history and monthly provider reports fill that gap.

The pack should show what is implemented, what is operating and what is still incomplete. A list of passed checks is no ASD Essentials rating without an assessment behind it, and ASD certifies no organisation under either framework.

Maintain a Provider Responsibility Register

A small business can outsource most of its IT operations. Accountability for the security outcome stays where it was. ASD Essentials for cloud explains this split for cloud services.

One page per provider is enough to record where responsibilities sit:

Provider responsibilities

The protections the provider implements, operates and maintains.

Business responsibilities

The security features the business must enable, configure, approve or operate.

Evidence

The reports or records that show the provider is meeting its responsibilities.

Incident support

Who investigates, who can take response actions and who must be contacted.

Outstanding gaps

Unavailable controls, incomplete configurations and work awaiting action.

The register matters most where the provider manages an identity service or backup system but the business controls the subscription settings and authorises changes. That is where each side can assume the other has switched a feature on.

Review the register when subscriptions, providers or managed services change. A provider’s general assurance report covers the provider’s own operations. It does not show that every security feature available to the business has been enabled.

Do Cyber Insurers Require the Essential Eight?

No published regulatory requirement makes the Essential Eight, or a particular maturity level, a condition of purchasing cyber insurance. The claim that insurers universally require Maturity Level Two has no published requirement behind it.

Cyber insurance questionnaires commonly ask about MFA, backups, patching, privileged access and incident response. The exact questions and acceptance criteria vary between insurers, so a business answers the questions on its own policy form. An Essential Eight maturity rating does not answer them by default.

Insurance also cannot stand in for a control. ASD’s Essential Eight maturity model FAQ states that risk transfer, including cyber insurance, cannot justify leaving an entire Essential Eight mitigation strategy unimplemented.

Doing so results in Maturity Level Zero for that strategy and for the overall Essential Eight assessment. Under ASD Essentials, insurance does not change whether an action achieves its intended outcome.

The evidence pack above is the basis for insurance applications and renewals. Answers describe the controls operating at the time of the application, including coverage limits and exceptions.

When presenting an assessment to an insurer:

Scope and date

Identify the domains and assets assessed, the assessment date and exclusions. An early-phase assessment should not be presented as a conclusion about the entire environment.

Not assessed areas

ASD uses “not assessed” for actions or domains that have not been assessed or lack sufficient evidence for a rating. Keep planned work separate from assessed results.

Control-level answers

If the insurer asks about MFA, provide the rating for IT.PRO-13.4 with its scope and exceptions. A favourable overall score does not show that the specific MFA action is fully effective.

A business can score well on backups and patching and still have accounts without the required authentication protection. The insurer’s MFA question is answered from the MFA evidence, whatever the overall assessment result.

Keep Governance Proportionate to Size

Small business security governance comes down to named people: who decides, who accepts risk and who runs each control. The accountable executive may be the owner or a director, with technical work performed by an external IT provider.

The Governance and culture principles can be recorded without extensive documentation:

Accountability (GOV-01)

Name the director accountable for cyber security, record the risk the business is prepared to accept and set a review interval.

Risk management (GOV-03)

Maintain a risk register with an owner, treatment and review date for each identified risk.

Resourcing (GOV-04)

Record who operates and monitors each security control, including responsibilities assigned to external providers.

AI use (GOV-08)

Decide who approves AI tools and features and what business information they may access.

Legacy systems (GOV-14)

Identify unsupported systems, their compensating controls and the planned replacement date.

The records should describe how decisions are made in practice. When a provider reports an unsupported device, for example, the business can show who accepted the temporary risk, what protection remains and when the decision comes up for review.

Dated decisions with a named owner and a completed review carry more weight than a policy that does not match how the business runs.

Budget for Implementation and Operations

Budgeting for ASD Essentials in a small business separates the one-off work of setting a control up from the recurring cost of running and reviewing it. Existing subscriptions may already include some of the capability, but it still has to be configured, monitored and evidenced.

ASD suggests working through one domain at a time from priority phase 1, with funding released in tranches aligned with implementation phases. The ASD Essentials checklist lists actions by domain.

Cost typeWhat ASD includesSmall business form
Capability buildTooling, licensing and engineering.Configuration of existing subscription features, plus any additional tools or services required.
Operating upliftOngoing people and process costs.Managed provider fees, monitoring and the business owner’s time for reviews and decisions.
AssessmentInternal assessment effort plus periodic independent assessment.Periodic self-assessment, with an independent review where a customer or contract requires one.

Review existing subscriptions before purchasing more technology. The first round of work may be enabling available controls, collecting provider reports and listing gaps, with the systems already in use left in place.

Independent assessment is optional. ASD’s implementation planning guide says organisations may engage an assessor where proportionate and affordable, but this is not required.

Between formal reviews, the guide suggests classifying actions as addressed, partially addressed or not addressed. Domains not yet reached are reported as not assessed, which is neither a pass nor a fail.

Reassess when a provider changes, systems are replaced or an incident reveals a control weakness. The same evidence pack carries over: update the affected records and leave the rest.

Small Business Security With ThreatDefence

ThreatDefence runs a 24x7 SOC with its team based in Australia and a 3 min average response under guaranteed SLAs. Threat hunting and an incident response retainer are included in the standard service.

Response actions remain within the authority each customer approves. Case records can be exported for an assessor or at the end of a contract. Australian customers’ data and AI processing stay in Australia.

Through the 24x7 SOC service, analysts can disable an account or block a sender outside business hours. A small business can also check the included incident response retainer against its cyber insurance policy’s responder and consent conditions before an incident occurs.

ThreatDefence does not certify organisations. An assessor determines ASD Essentials ratings based on the applicable scope and evidence.

The free ASD Essentials Navigator maps every principle and action by chapter and priority phase, and turns entered ratings into a board summary. Readers new to the framework can start with the five-minute ASD Essentials explainer, which walks through principles, actions, domains, priority phases and ratings.

Auto triage in the ThreatDefence portal, with alerts triaged by AI, verdicts, confidence and the alerts escalated to an analyst

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    Is ASD Essentials meant for small business?

    Partly. ASD developed the framework primarily for Commonwealth entities, critical infrastructure and large organisations, while recognising that small and medium businesses can apply it where relevant. The security outcomes remain important regardless of size. In ASD’s words, What differs is how those outcomes are achieved, including the responsibilities carried by service providers and vendors. Very small businesses may find ASD’s small business guidance a simpler place to begin.

    Where should a small business start?

    A small business using the enterprise IT chapter starts with the priority phase 1 domains, Boundary services and Identity services, alongside Governance and culture and Visibility and response. Review existing subscriptions and provider responsibilities before purchasing additional tools. A business running entirely on SaaS and PaaS, with no servers or networks of its own, may find the cloud chapter the better starting point. The technology the business actually runs decides which guidance applies.

    Is the Essential Eight still worth doing?

    Yes, particularly where a customer, contract or regulator still requires it. Existing Essential Eight controls also provide a foundation for ASD Essentials. Every Essential Eight mitigation strategy maps to at least one ASD Essentials principle, so much of the implementation and its evidence carries over. ASD advises against pursuing a superseded Essential Eight target that neither an obligation nor current security needs justify. Existing contractual or regulatory requirements should still be met.

    Can cyber insurance replace an Essential Eight control?

    No. ASD’s Essential Eight maturity model FAQ says risk transfer, including cyber insurance, cannot justify leaving an entire mitigation strategy unimplemented. An organisation relying on insurance instead of implementing a strategy receives Maturity Level Zero for that strategy and for its overall Essential Eight assessment. The same logic carries into ASD Essentials outcomes: insurance may transfer financial risk, but it does not make a security action effective.

    What do cyber insurers ask about security controls?

    Cyber insurance questionnaires commonly ask about MFA, backups, patching, privileged access and incident response, although requirements vary between insurers. No published regulatory requirement names the Essential Eight or a particular maturity level. Answer each question from dated evidence of controls currently operating, including exceptions. For an MFA question, provide the scope, exceptions and rating for IT.PRO-13.4 phishing-resistant MFA. A favourable overall assessment does not show that this specific action is fully effective.

    Which Essential Eight maturity level suits a small business?

    In ASD’s general guidance, Maturity Level One may suit small to medium enterprises. ASD’s Essential Eight maturity model FAQ also suggests Maturity Level Two for large enterprises and Maturity Level Three for critical infrastructure and high-threat environments. Those are general indications and do not replace a business’s risk assessment or contractual obligations. A customer or program may require a higher level. ASD advises reaching the same level across all eight strategies before progressing, because the least mature strategy determines overall maturity.

    Do small Defence suppliers need Essential Eight Maturity Level Two?

    Yes, if they are DISP members. Defence’s cyber assessments against the Essential Eight “top 4” concluded on November 15, 2025, and all DISP members must now achieve and maintain the full Essential Eight at Maturity Level Two. Part B of the DISP Cyber Security Questionnaire contains 107 Essential Eight controls aligned with that level. DISP does not reference ASD Essentials, so the existing Essential Eight requirement remains the relevant measure for those suppliers.

    Does a small business need an independent ASD Essentials assessment?

    No, unless a customer or contract requires one. ASD’s implementation planning guide says organisations may engage an independent assessor where proportionate and affordable, but this is not required. The assessment process guide supports organisations assessing their own environment, so in our view periodic self-assessment with dated evidence suits most small businesses. An independent review may still be useful for customer assurance. Neither an internal nor an independent assessment results in ASD certification, because ASD certifies no organisation under either framework.

    Will customers ask small suppliers for ASD Essentials evidence?

    Likely, in our view, potentially before a regulatory transition. The enterprise IT chapter’s GOV-11 Supplier cyber security assurance principle asks organisations to select suppliers using a risk assessment proportionate to the risk introduced and to keep assurance current. ASD has not yet published a supplier assessment method, so each customer sets its own questions and evidence expectations. A short, dated pack covering MFA, internet-facing services, backups, provider responsibilities and incident response prepares a small business to respond.