Yes — a sole director can implement the Essential Eight without an IT team, because the framework assesses how well eight mitigation strategies are applied, not how many staff run them. What actually stands between a one-person business and each maturity level is whether the controls exist and can be evidenced; with cloud services covering most of the technical work, the realistic path is fewer tools, more documentation discipline.
TL;DR
- Essential Eight measures control implementation across four maturity levels, not headcount.
- A sole director can meet lower maturity levels using cloud services and a documented routine.
- The hard part is patching discipline, backups and evidence — not installing software.
- ASD publishes the maturity model; target the level your risk actually demands.
- Awareness training counts toward the human side of the controls and can be evidenced per person.
What the Essential Eight actually asks of you
The Essential Eight is ASD's set of eight mitigation strategies: application control, patching applications, patching operating systems, multi-factor authentication, restricting administrative privileges, Microsoft Office macro control, user application hardening and regular backups. The Essential Eight maturity model (ASD, accessed November 2026) defines four maturity levels — Zero through Three — and advises organisations to reach the same maturity level across all eight strategies before moving higher.
ASD's own FAQ positions Maturity Level One as generally suitable for small to medium enterprises, Level Two for large enterprises and Level Three for critical infrastructure and high-threat environments. A sole director targeting Level One is not cutting corners — that is the level the framework's authors point SMBs at.
None of the eight strategies requires a helpdesk. Each requires a control that is on, configured and provable.
Where a one-person business is actually strong
Running the controls solo has real advantages that IT-heavy organisations lack:
- No privilege sprawl. Restricting administrative privileges is trivial when there is one admin account and it is yours. Most organisations fail this one badly.
- One patch cadence. You patch your devices when you patch your devices — no coordination across teams and locations.
- Cloud-native stack. M365 or Google Workspace delivers MFA, macro control and application hardening as settings you toggle, not projects you run.
- One training audience. The human side — recognising phishing, handling credentials — is one person, and that person is motivated.
These strengths matter because the strategies that sink large organisations (privilege management, consistent patching across fleets) are structurally simple for you.
The strategies that need a routine, not a team
The gap between a sole director and Maturity Level One is rarely technical skill; it is consistency. Three strategies demand a calendar entry, and two demand evidence habits:
- Patching (applications and operating systems). Put a recurring block in your calendar — weekly for OS, fortnightly for applications — and run it even on quiet weeks. Level One requires patching within a defined window; the window only holds if the routine does.
- Regular backups. Enable automatic cloud backup for every device and service, then test a restore once. A backup you have never restored is a hope, not a control.
- Application control and hardening. On a single-user device this is configuration: restrict macros in Office settings, remove or disable unused browser extensions, keep the browser auto-updating.
- Multi-factor authentication. Turn it on everywhere it exists — email, accounting software, bank, domain registrar. This is the highest-value hour you will spend.
- Evidence. Note the date you enabled each control and keep screenshots or export logs. Assessment is evidence-based; a control you cannot show is a control that does not count.
The human layer and how to evidence it
Two of the biggest real-world entry points — phishing and credential theft — are behavioural, and the framework expects them mitigated. For a sole director there is no workforce to train, but there is still you: keeping your own phishing recognition current is part of the control set, and if you use contractors or a virtual assistant, it is part of theirs.
Structured awareness training makes this evidence rather than assertion. A programme like Cyber Aware's security awareness training issues per-person completion records and runs monthly phishing simulations with no credential harvesting, so a one-person business can demonstrate both training and testing without any IT overhead. If you want to show where your human risk stands before investing, the gap assessment approach — score your posture, fix the gaps in priority order — works identically at a one-person scale.
When to bring in outside help
Plenty of sole directors reach Maturity Level One alone. Consider outside help in three cases:
- You are targeting Level Two or Three. Requirements scale sharply — Level Two expects mitigations against more capable tradecraft, and the evidence burden grows with it.
- An assessment is contractually required. Some tenders, insurance policies and government work require an independent assessor's sign-off rather than self-assessment.
- Legacy systems are in play. If a business-critical application cannot be patched or replaced, an assessor or MSP can confirm whether the framework's documented exceptions apply to you.
An MSP-led gap assessment or certification (for example through SMB1001 alongside the Essential Eight) is also the path to a certificate you can hand to a client or insurer — useful when self-assessed spreadsheets carry no weight.
FAQ
Can a sole director meet Essential Eight without an IT team? Yes. The framework assesses controls and evidence, not staffing. A sole director using cloud services and a documented patching and backup routine can realistically reach Maturity Level One, which ASD positions as suitable for SMBs.
Which maturity level should a one-person business target? Maturity Level One is the conventional starting point — ASD's own FAQ suggests Level One may suit small to medium enterprises. Target higher only if a contract, insurer or risk assessment demands it.
Do I need special software for the Essential Eight? Mostly no at Level One. MFA, macro control and hardening are settings in mainstream cloud suites; patching and backups are routines over software you already own. Application control is the one strategy that may need extra tooling depending on your platform.
How do I prove compliance as a sole director? Keep dated evidence: screenshots of MFA and macro settings, patch logs, a backup restore test, and per-person training records. An assessment walks through evidence, so build the folder as you implement.
Is self-assessment accepted? For internal risk management and many commercial conversations, yes. Tenders, insurers or government directives sometimes require independent assessment — check the requirement's wording before assuming self-assessment suffices.
One last thing
Do the MFA sweep first. Of the eight strategies, multi-factor authentication is the cheapest to implement, the fastest to complete and the one that defeats the largest share of real attacks — an afternoon of turning it on moves your posture more than a month of planning.