Black Shard

Essential Eight assessment and uplift.

Each of the eight mitigation strategies rated against the Australian Signals Directorate maturity model, Maturity Level 0 to Maturity Level 3, with the evidence behind every rating and an uplift plan to the level your buyers ask for.

We assess each of the eight mitigation strategies against the ASD maturity model and document the evidence supporting the rating. Where controls fall short of the target level, the assessment becomes an implementation plan covering the technical and procedural changes required. Black Shard can perform the uplift directly or work with your existing IT provider.

The Essential Eight appears in tenders, insurance renewals, supply-chain questionnaires and board papers, and the question each time is the maturity level and the evidence behind it. Black Shard is an Australian software engineering and cybersecurity firm headquartered in Brisbane, and runs its own estate at self-assessed Maturity Level 2. The maturity model the Australian Signals Directorate published in November 2023 sets the requirements.

What is the Essential Eight?

The Essential Eight is a set of eight mitigation strategies published by the Australian Signals Directorate, selected because they interrupt the intrusion techniques used against Australian organisations. The ASD publishes the model and its maturity requirements; it does not certify businesses against it.

The strategies fall into three groups: four that stop attacks landing, three that limit how far an attacker gets, and one that recovers the business afterwards.

  • Application control: only approved software runs on your machines, and everything else is blocked.
  • Patch applications: security fixes for the software you run, applied within timeframes that match how fast the flaw is being exploited.
  • Configure Microsoft Office macro settings: macros from the internet are blocked, and the ones the business relies on are vetted and signed.
  • User application hardening: browsers and productivity tools with the risky features switched off and legacy components removed.
  • Restrict administrative privileges: admin rights held by the people who need them, in separate accounts, reviewed as roles change.
  • Patch operating systems: the same patching discipline applied to workstations, servers and network devices.
  • Multi-factor authentication: a second factor on the services that matter, including remote access and administrative portals.
  • Regular backups: backups tested by restoring them, held where a compromised account cannot delete them.

The four maturity levels, and who each one is built to stop

The model rates each strategy at one of four levels. Maturity Level 0 means significant weaknesses in a strategy that an adversary could exploit. The three levels above it are defined by the adversary they counter, and every requirement in the model follows from that framing.

Maturity Level 1 counters adversaries content to use commodity tradecraft that is widely available: a public exploit against an unpatched online service, or a login with credentials that were stolen, reused, brute forced or guessed. They want any victim, not a particular one. Maturity Level 2 counters adversaries with a modest step up in capability, who invest time in a target and in the effectiveness of their tools, phish for credentials, and work around weak multi-factor authentication. Maturity Level 3 counters adversaries who are adaptive and far less reliant on public tools, who exploit older software and thin logging to extend access and evade detection, and who steal authentication tokens to get past stronger multi-factor authentication.

Two points to note. The rating is per strategy, and the ASD's guidance is to reach the same level across all eight before targeting the next one, so seven strategies at Maturity Level 2 and one at Level 0 is a Level 0 result in practice. The right target follows the obligation: Maturity Level 1 across all eight is the baseline supplier questionnaires commonly have in mind, and contracts touching government supply chains increasingly specify Level 2.

Application control, level by level

At Maturity Level 1, application control runs on workstations, covers user profiles and the temporary folders used by operating systems, browsers and email clients, and restricts executables, software libraries, scripts, installers, compiled HTML, HTML applications and control panel applets to an approved set.

Maturity Level 2 extends it to internet-facing servers and to every location on the machine, applies Microsoft's recommended application blocklist, validates the ruleset at least annually, and logs allowed and blocked events centrally. Maturity Level 3 extends it to every server, restricts drivers to an approved set, and applies Microsoft's vulnerable driver blocklist.

This is the strategy most often found at Level 0 in an assessment, because it is the one most often deferred: switched on in enforce mode without an audit period it removes the finance team's macros and the operations team's utilities the same afternoon.

Patching applications and operating systems, level by level

Every level starts with the same two disciplines: an automated asset discovery run at least fortnightly, and a vulnerability scanner with a current database. What changes between levels is how much of the estate the scanner covers and how fast a patch has to land.

For applications, online services are scanned daily and patched within 48 hours when the vendor rates the flaw critical or a working exploit exists, otherwise within two weeks, at every level. Office suites, browsers and their extensions, email clients, PDF software and security products are scanned weekly and patched within two weeks at Levels 1 and 2; Level 3 pulls the critical and exploited cases to 48 hours. Level 2 adds fortnightly scanning and a one-month patch window for every other application. Unsupported software is removed at every level.

For operating systems, internet-facing servers and network devices follow the same 48 hours or two weeks rule at every level. Workstations and internal servers are patched within one month at Levels 1 and 2; Level 3 pulls their critical and exploited cases to 48 hours, adds fortnightly scanning and the same windows for drivers and firmware, and requires the latest or previous operating system release. Unsupported operating systems are replaced at every level.

Macros and user application hardening, level by level

Macros at Maturity Level 1 are disabled for anyone without a demonstrated business need, blocked in files from the internet, scanned by antivirus, and locked so users cannot change the settings. Level 2 blocks macros from making Win32 API calls. Level 3 allows a macro to run only from a sandbox, a Trusted Location or under a trusted publisher's digital signature, requires each macro to be checked for malicious code before it is signed or placed in a Trusted Location, restricts who can write to those locations, and validates the trusted publisher list at least annually.

Hardening at Level 1 removes Internet Explorer 11, stops browsers processing Java and web advertisements from the internet, and locks browser security settings. Level 2 hardens browsers, office suites and PDF software to ASD and vendor guidance with the most restrictive setting winning, blocks Office from creating child processes, creating executable content, injecting code into other processes and activating OLE packages, blocks PDF software from creating child processes, and centrally logs PowerShell module, script block and transcription events and command line process creation. Level 3 removes .NET Framework 3.5 and Windows PowerShell 2.0 and runs PowerShell in Constrained Language Mode.

Administrative privileges and multi-factor authentication, level by level

Privilege at Maturity Level 1 means every request for privileged access is validated when first made, privileged users hold a dedicated account used only for privileged duties, those accounts cannot reach the internet, email or web services unless explicitly authorised, and privileged and unprivileged operating environments are kept apart with no logon across the line. Level 2 revalidates privileged access after 12 months and disables it after 45 days without use, forbids privileged environments virtualised inside unprivileged ones, routes administration through jump servers, requires long, unique, managed credentials for break glass, local administrator and service accounts, and centrally logs privileged access and security group management events. Level 3 limits privileged access to what each duty requires, uses Secure Admin Workstations and just-in-time administration, and enables memory integrity, Local Security Authority protection, Credential Guard and Remote Credential Guard.

Multi-factor authentication at Level 1 covers users of the organisation's own and third-party online services holding sensitive data, and customers of online customer services holding sensitive customer data, using something the user has together with something they know or are. Level 2 extends it to privileged and unprivileged users of systems, requires it to be phishing-resistant for users of online services and systems, offers customers a phishing-resistant option, and centrally logs every successful and failed authentication. Level 3 extends it to users of data repositories and makes it phishing-resistant everywhere, customers included.

Backups, level by level

At every level, backups of data, applications and settings are performed and retained according to business criticality, synchronised so the estate can be restored to a common point in time, held in a secure and resilient manner, and tested by restoring them during disaster recovery exercises. Maturity Level 1 stops unprivileged accounts reading other users' backups or modifying and deleting any backup.

Level 2 places the same limits on privileged accounts, with only backup administrator accounts exempt. Level 3 stops every account, privileged or not, reading even its own backups, and stops backup administrators modifying or deleting a backup during its retention period. The intent is the same at each step: a compromised account, whatever its rights, cannot destroy the copy the business recovers from.

Logging and incident handling from Maturity Level 2

From Maturity Level 2 the model adds a logging and incident layer to every strategy. Event logs are protected from unauthorised modification and deletion. Logs from internet-facing servers are analysed in a timely manner to detect cyber security events, events are analysed to identify incidents, incidents are reported to the chief information security officer or a delegate and to the ASD as soon as possible, and the incident response plan is enacted when one is identified.

In practice this is the requirement that separates a Level 1 estate from a Level 2 one. The Level 1 controls are configuration; the Level 2 layer is an operating discipline that has to be running, with records, before it can be evidenced.

What an assessment involves

An assessment is a technical exercise. We collect the data behind each strategy: what application control blocks, which accounts enforce multi-factor authentication and whether it is phishing-resistant, who holds administrative privilege and when it was last revalidated, the age of the oldest unpatched exploitable flaw against the windows above, and whether a backup restore has been performed.

Each strategy is rated against the requirements of the target level. For every strategy the report records the requirement, what was observed, and the gap between the two. The deliverables are a current maturity rating across all eight strategies with the observations behind each, an uplift plan to the target level sequenced by risk and effort, and an evidence trail for each mitigation that can be handed to a customer, auditor or insurer.

What uplift involves

Uplift is configuration work. A typical program: multi-factor authentication enforced on remote access and administrative portals first, phishing-resistant where Level 2 is the target. Administrative privilege separated into dedicated accounts, limited to the people who need it, and put on the 12-month revalidation and 45-day inactivity clocks. A patch cadence with owners and the model's timeframes, driven by exploitability. Application control rolled out in audit mode, then switched to enforce once the exceptions are understood. Office macros blocked from the internet, with the business macros that remain vetted and signed. Backups restructured so a restore is rehearsed and a compromised administrator cannot delete them.

Sequencing matters because several of these controls break things when switched on carelessly. Uplift runs as a milestone program: each mitigation lands, is evidenced and is confirmed working before the next one tightens. Black Shard can do the hands-on work or hand your IT provider a plan precise enough to execute, and verify each milestone.

Evidence when a customer or insurer asks

There is no Essential Eight certificate. What exists is the organisation's claim and the evidence behind it: a dated assessment and per-mitigation artefacts such as configuration exports, patch reports, privileged-account registers and restore-test records. We build that trail as part of the work, one body of evidence per mitigation.

Black Shard's own estate is self-assessed at Maturity Level 2, labelled as a self-assessment alongside the SMB1001:2026 Gold certification the firm holds, verifiable on CyberCert's public registry. The controls overlap substantially with SMB1001, so much of the evidence serves both.

What does an Essential Eight assessment cost?

Cost follows the size of the environment: how many environments and tenancies, the size of the endpoint fleet, the attack surface in scope, and whether Black Shard executes the uplift or plans it. The work runs as a fixed-scope assessment with a defined target, timeframe and deliverable, or as a program with milestones toward the target maturity level or an audit date.

Send a brief to info@blackshard.com.au with the rough shape of the environment and the maturity level being asked for.

Questions, answered

Is the Essential Eight mandatory in Australia?
It is mandated for many Australian government entities. Agencies and large enterprises increasingly require a stated maturity level from suppliers, and insurers ask about the same controls at renewal. For a private business it is rarely a legal obligation and often a commercial one.
Does the ASD certify Essential Eight compliance?
No. The ASD publishes the model and its maturity requirements and does not certify or endorse anyone against it. A maturity claim rests on assessment evidence, which is why the evidence trail is part of the engagement.
What maturity level should we target?
The level being asked for. Maturity Level 1 is the common baseline for small and mid-sized businesses, and contracts in government supply chains increasingly specify Level 2. Targeting higher than the obligation is a risk decision to make deliberately.
What is the difference between Maturity Level 1 and Maturity Level 2?
Level 1 is configuration: multi-factor authentication on the services that hold sensitive data, dedicated admin accounts, patching within the model's windows, application control on workstations, macros and browsers locked down, backups tested. Level 2 widens each control (servers, phishing-resistant authentication, privilege revalidation, Microsoft's blocklists) and adds an operating layer: protected event logs, timely analysis, incident reporting and a response plan that is enacted. Level 2 has to be running, with records, before it can be evidenced.
Which version of the maturity model do you assess against?
The model the Australian Signals Directorate published in November 2023. Every rating in the assessment report cites that edition.
Can you do the uplift work, or only the assessment?
Both. Black Shard can perform the uplift directly: MFA enforcement, privilege separation, application control rollout, patch cadence and backup restructuring. Where an IT provider is in place, we hand over the plan and verify the work at each milestone.
How is the Essential Eight different from SMB1001 or ISO 27001?
The Essential Eight is a maturity model with no certificate attached. SMB1001 and ISO 27001 are certifiable standards. The controls overlap substantially, so an Essential Eight uplift produces much of the evidence an SMB1001 tier expects.
Do you assess businesses outside Brisbane?
Yes. Black Shard is an Australian firm headquartered in Brisbane and assesses Australia-wide. Most of an assessment runs remotely against cloud tenancies, directories and endpoint management tooling.
How often should maturity be re-assessed?
After significant change to the environment, and before the rating is relied on commercially in a tender response or an insurance renewal. Environments drift: admin rights accumulate, patch cadences slip, temporary exceptions become permanent.
What is Black Shard's own Essential Eight position?
Self-assessed Maturity Level 2, following an uplift completed in August 2026.

Tell us what you need built, reviewed or secured.

Brisbane head office. Work delivered across Australia.

Open a briefinfo@blackshard.com.au