Essential Eight Penetration Testing
An Essential Eight penetration test is a senior tester attacking your environment to show whether ASD's eight mitigation strategies actually stop the tradecraft your target maturity level is meant to stop. It is not a maturity assessment. It produces the strongest evidence ASD describes, testing a control with a simulated activity, with every finding mapped to the strategy it affects.
Does the Essential Eight require a penetration test?
No. And most of what you'll read says otherwise.
The Essential Eight maturity model lists eight mitigation strategies and the requirements for each maturity level. None of them is "have a penetration test". ASD is also plain about certification: "there is no requirement for organisations to have their Essential Eight implementation certified by an independent party. However, Essential Eight implementations may need to be assessed by an independent party if required by a government directive or policy, by a regulatory authority, or as part of contractual arrangements."
So why test at all? Because of how ASD tells assessors to weigh evidence. The Essential Eight assessment process guide ranks evidence in four grades;
Excellent: Testing a control with a simulated activity designed to confirm it is in place and effective
Good: Reviewing the configuration of a system through the system's interface
Fair: Reviewing a copy of a system's configuration, such as reports or screenshots
Poor: A policy or verbal statement of intent
A self-assessment built on screenshots and policy documents sits at fair or poor. A penetration test sits at the top of that scale for every control it touches, because it is the simulated activity.
What are the eight mitigation strategies?
The current Essential Eight maturity model is the November 2023 version (cyber.gov.au lists it as first published 30 June 2017, last reviewed 27 November 2023). The eight strategies are;
- Patch applications
- Patch operating systems
- Multi-factor authentication
- Restrict administrative privileges
- Application control
- Restrict Microsoft Office macros
- User application hardening
- Regular backups
ASD designed them for internet-connected IT networks. Its own words: the principles "may be applied to enterprise mobility and operational technology networks, it was not designed for such purposes and alternative mitigation strategies may be more appropriate".
Which maturity level are you testing against?
There are four, Maturity Level Zero to Maturity Level Three. Apart from Zero, each one is defined by the attacker it is meant to stop, not by a checklist score;
Maturity Level One: opportunistic attackers using commodity tradecraft, such as a public exploit for an unpatched online service, or stolen, reused or guessed credentials.
Maturity Level Two: a modest step up. Attackers invest more time in a target, target credentials with phishing, and use technical and social engineering to get around weak multi-factor authentication.
Maturity Level Three: adaptive attackers, much less reliant on public tools, who exploit older software and weak logging, and who will steal authentication tokens to get around stronger multi-factor authentication.
That is why the target level sets the scope of the test. A Maturity Level One test asks whether a commodity attacker gets in. A Maturity Level Three test assumes they will try harder and asks what happens after the foothold.
ASD also says the Essential Eight "is required to be implemented and assessed as a package", and that you should not be assessed against Maturity Level Two before you have shown Maturity Level One. We scope the same way.
Which Core Sentinel tests cover the Essential Eight?
Most Essential Eight work combines three engagements;
-
External infrastructure penetration testing
What an attacker with no credentials can reach. This is where unpatched internet-facing services and missing MFA show up.
-
Internal penetration testing
What happens after a phishing click. This is where application control, macros, hardening and administrative privileges are tested.
-
Web application penetration testing
For in-scope applications, including the authentication your customers use.
For how the Essential Eight sits beside ISO 27001, SOC 2, APRA CPS 234, PCI DSS and the rest, see our penetration testing compliance guide for Australia. If you're APRA-regulated, CPS 234 has its own testing obligations: see APRA CPS 234 penetration testing.
How does an Essential Eight penetration test run?
The same way every Core Sentinel engagement runs, with the scope set by your target maturity level;
- 01
Scope
Your target maturity level, your internet-facing ranges and domains, an internal starting point (a standard user on a standard workstation), and any applications in scope.
- 02
Rules of engagement
Targets, testing windows, credentials and escalation contacts are agreed in writing.
- 03
Testing
A senior OSCE/OSCP-certified tester attacks from outside, then from the internal foothold, and tries to defeat each control in scope.
- 04
Report
A plain-language executive summary, and technical findings with reproducible evidence, each mapped to the Essential Eight strategy it affects.
- 05
Free retest and letter of attestation
After you fix the findings, we retest every one at no extra cost and issue a letter of attestation you can hand to an assessor, a customer or your board.
What can a penetration test evidence, and what can't it?
This is the part most providers skip. Here it is, strategy by strategy.
| Strategy | What a penetration test can show | What it can't show |
|---|---|---|
| Patch applications / patch operating systems | Whether an exposed or internal service is exploitable through a missing patch | Whether your patching meets the maturity model's timeframes across every asset |
| Multi-factor authentication | Whether internet-facing services, including portals you forgot to mention, accept a login without MFA | Every third-party service your staff use |
| Restrict administrative privileges | Whether a standard user foothold can escalate to privileged access | Whether privileged access requests are validated and reviewed as the model requires |
| Application control | Whether an unapproved program or script runs from a user-writable location | Whether the ruleset is reviewed on the required cadence |
| Restrict Microsoft Office macros / user application hardening | Whether a macro or hardened-browser control can be bypassed on the workstations in scope | Configuration across the whole fleet |
| Regular backups | Whether a compromised account can reach and alter backups, where backups are in scope | Whether restores are tested and backups are retained to business requirements |
The honest summary; a penetration test tells you whether your controls fail under attack. It does not give you a maturity level. That comes from an Essential Eight assessment run against ASD's assessment process guide, which tests across a representative sample of workstations, servers and network devices and reports each control as effective, ineffective, alternate control, no visibility, not implemented or not assessed.
The two work together. The assessment tells you where you are. The test proves whether that is true.
What teams ask before an Essential Eight test.
Is a penetration test the same as an Essential Eight assessment?
No. An Essential Eight assessment follows ASD's assessment process guide and rates every control at a target maturity level. A penetration test attacks your controls to prove whether they hold. The assessment tells you where you are; the test shows whether that is true. Our report maps every finding to the Essential Eight strategy it affects.
Do we need an independent party to assess our Essential Eight?
Not by default. ASD states there is no requirement to have an Essential Eight implementation certified by an independent party, unless a government directive or policy, a regulator or a contract requires an independent assessment. Independent testing still gives you the strongest grade of evidence ASD describes.
Which maturity level should we test against?
The one you are targeting. ASD says the Essential Eight is implemented and assessed as a package, and that you should show Maturity Level One before being assessed against Maturity Level Two. We scope the test to the tradecraft your target level is meant to stop.
Does the Essential Eight cover cloud, mobile or operational technology?
ASD designed the Essential Eight for internet-connected IT networks. It says the principles may be applied to enterprise mobility and operational technology, but the model was not designed for them and other mitigation strategies may fit better. We scope those environments separately.
Do you retest after we fix the findings?
Yes. Every engagement includes a free remediation retest, and a letter of attestation once the fixes are confirmed.
What does an Essential Eight quote need?
Send us these and a senior tester sends back a fixed-price quote from your scope, before you commit. No rate card, no day-rate maths. See how a fixed-price quote works and penetration testing across Australia.
- Your target maturity level, and whether you've been assessed before.
- Your internet-facing IP ranges, domains and login portals.
- Whether we test from an internal foothold, and how many sites or network segments.
- Any applications in scope.
- Who needs the result (an assessor, a regulator, a customer contract or your board) and by when.