Exceptions and compensating controls in an Essential Eight assessment

Facts read 18 Nov 2026

A compensating control can stand in for an Essential Eight requirement if the system owner shows it gives equivalent protection. A documented, approved exception with strong compensating controls need not stop an organisation reaching its target level. Risk acceptance or cyber insurance alone, for a whole strategy, is assessed as Maturity Level Zero for that strategy and overall. Exceptions should not be approved beyond one year.

Can compensating controls replace an Essential Eight requirement?

Yes, according to ASD's maturity model FAQ. System owners must demonstrate that a compensating control gives an equivalent level of protection to the requirement it replaces, against the same level of adversary tradecraft and targeting. A strategy then counts as fully implemented when every requirement is either implemented or covered by a suitable compensating control.

If an assessor finds a compensating control unsuitable, the strategy is assessed at the next lowest maturity level it qualifies for, or at Level Zero. In ASD's assessment outcomes, a control met this way is recorded as an alternate control, which counts as effective for the purpose of claiming the strategy.

What happens if the risk is simply accepted?

Risk acceptance without compensating controls fails the strategy. ASD's FAQ says an owner who uses risk acceptance, or risk transfer such as buying cyber insurance, to justify not implementing a whole strategy, such as application control or multi-factor authentication, is treated as not protected against that class of threat. The result is Maturity Level Zero for that strategy and for the overall Essential Eight implementation.

The assessment guide repeats the point to assessors: do not allow risk acceptance as a reason for not implementing an entire strategy. Its second example is a cloud service with no multi-factor authentication where the owner judged enabling it not worth the effort or the user complaints. With no strong compensating controls and no managed exception, the assessor decided that the organisation should be precluded from reaching its target maturity level.

What does a good exception look like?

The guide's first example is a low-risk Windows server that could not be patched and was due to be decommissioned within two months. The organisation assigned a risk owner and applied strong compensating controls, so the assessor found the exception should not stop the organisation reaching its target. The guide says an appropriate formal exception process, with compensating controls, should not preclude being assessed as meeting the target level.

Exceptions must be documented and approved through a formal process by an appropriate authority. The record should hold the detail, scope and justification, the compensating controls with their scope, justification, expected lifetime and next review, the system risk rating before and after, any caveats on use of the system, acceptance of the residual risk, and when the need for the exception is next considered. The guide says exceptions should not be approved beyond one year.

What about legacy systems?

Legacy systems are not out of scope. ASD's FAQ says it is often difficult to implement the Essential Eight, in part or in full, on legacy systems, strongly encourages upgrading them as a priority, and says to apply compensating controls where possible while an upgrade is under way. An exception is a bridge to the upgrade and not a permanent state, which is what the one year limit enforces. Record each legacy system, its owner and its replacement date in the same exception record, so the review has something to check.

Government policy points the same way. PSPF Direction 002-2026, issued on 29 September 2026, requires Australian Government entities to reduce the cyber security risk from vulnerable legacy technology. In the Essentials for enterprise IT, legacy system management is a principle in the Governance and culture domain, which the Essential Eight did not assess. The PSPF guide covers who is bound.

Which exceptions do assessors see most?

The assessment guide's two examples are unpatched servers and cloud services without multi-factor authentication. The FAQ adds customers who cannot use multi-factor authentication because of personal circumstances, with security questions plus a passphrase and enhanced monitoring as a possible compensating control, subject to risk acceptance by an appropriate authority. Phishing-resistant MFA covers the method rules.

6clicks names application allow-listing gaps on servers and operational technology, MFA gaps for privileged accounts and inconsistent patching evidence as common Level Two gaps in its May 2026 blog. Each is a likely place for an exception, and each needs the documentation above.

What can a platform record for exceptions?

A platform can hold the exception record and its review date. Drata publishes evidence examples that include a time-limited MFA exception process. 6clicks lists remediation tracking with automated reminders on its Essential Eight page. The decision on whether a compensating control is equivalent belongs to the assessor, so ask any platform how it stores the reasoning and the approval, and not only the control. For the rest of the first-assessment work, see the checklist.

Frequently asked questions

Can I implement compensating controls instead of specific Essential Eight requirements?

Yes, if the system owner can show equivalent protection. Risk acceptance or cyber insurance alone, used to skip a whole strategy, leads to a Maturity Level Zero assessment for that strategy and overall.

Are legacy systems out of scope?

No. ASD strongly encourages upgrading legacy systems as a priority so the Essential Eight can be implemented in full. While an upgrade is under way, organisations should apply compensating controls where possible.

Sources

Last reviewed 18 Nov 2026