Essential Eight, NIST CSF or ISO 27001: which fits your business?
31 October 2026
Compare cybersecurity frameworks for Australian businesses. Understand Essential Eight, NIST CSF and ISO 27001, then choose by risk, resources and contracts.
Huntress has published a guide to cybersecurity frameworks for 2027, raising a practical question for Australian business owners: which approach deserves your limited time and budget? The guide is a useful discussion starter, not an announcement of new government requirements or standards.
For most small and medium businesses, the decision is not about comparing 13 options. It is about understanding three different tools: the ACSC’s Essential Eight for prioritised technical protection, NIST CSF for organising cyber risk, and ISO/IEC 27001 for managing information security systematically. This article draws on the organisations responsible for those approaches.
Cybersecurity frameworks serve different purposes
These approaches overlap, but they are not interchangeable. Start with the problem you need to solve rather than the framework with the longest checklist.
| Approach | Main role | Useful starting point when | Important limitation | |---|---|---|---| | Essential Eight | Prioritised technical mitigation strategies | You need to improve core protection and assess implementation maturity | It is not a complete information security programme | | NIST CSF 2.0 | Outcomes for governing and managing cyber risk | You need a shared plan across management, IT and suppliers | It does not prescribe every technical configuration | | ISO/IEC 27001 | Requirements for an information security management system | You need a formal management system or customers require certification | Certification applies to a defined scope and does not mean incidents cannot happen |
You can combine cybersecurity frameworks without maintaining three separate programmes. A business might organise its roadmap using NIST CSF, implement relevant Essential Eight controls, and later pursue ISO 27001 certification where there is a clear commercial reason.
Essential Eight: establish and verify technical protection
The Australian Signals Directorate’s Australian Cyber Security Centre publishes the Essential Eight. Its mitigation strategies cover application control, application patching, Microsoft Office macro restrictions, user application hardening, restricted administrative privileges, operating system patching, multi-factor authentication and regular backups.
The accompanying maturity model helps organisations assess how thoroughly these strategies are implemented. Maturity is not simply a count of products purchased. Coverage, configuration and operating practices matter.
For an owner, the useful question is: “Can we demonstrate that these protections work across the systems in scope?”
Ask your IT team or provider to:
- Identify which devices, accounts and applications are covered, including remote workers and privileged accounts.
- Compare actual settings with the applicable maturity requirements, rather than relying on a general statement of alignment.
- Record unsupported software, patching delays and exceptions, with an owner and review date.
- Test backup restoration and document what can be recovered, by whom and within what timeframe.
- Set a target maturity level based on risk and requirements, with a coordinated plan across all eight strategies.
Essential Eight is designed primarily for internet-connected IT networks. Do not assume it fully addresses cloud services, operational technology or every business risk. Supplier governance, incident response, privacy obligations and payment verification still need attention.
For a related practical starting point, see our ASD Essentials checklist.
NIST CSF: connect technical work to business risk
The US National Institute of Standards and Technology publishes the Cybersecurity Framework. CSF 2.0 groups outcomes into six functions: Govern, Identify, Protect, Detect, Respond and Recover. It is intended for organisations of different sizes and sectors, not only US government agencies.
Its value is breadth. It helps management discuss security beyond patching and antivirus: who makes decisions, which services matter, how suppliers are assessed, how suspicious activity is detected, and what happens during an incident.
A practical implementation starts with a Current Profile and a Target Profile. These describe relevant outcomes today and the outcomes the business wants to achieve. The gap becomes a prioritised improvement plan.
For example, a distributor could identify order processing as a critical service, name its business owner, map supporting systems and suppliers, and document an acceptable recovery time. That makes technical investment easier to explain in operational terms.
Useful checks include:
- Is someone accountable for cyber risk at management level?
- Are important systems, data and dependencies documented?
- Are alerts reviewed, with clear escalation responsibilities?
- Can staff contact the right people if email is unavailable?
- Have recovery arrangements been tested against business needs?
NIST CSF Implementation Tiers describe the rigour of risk governance and management practices. They are not equivalent to Essential Eight maturity levels, and NIST does not certify businesses as CSF compliant.
ISO 27001: build a management system with a defined scope
The International Organization for Standardization explains ISO/IEC 27001 as the requirements standard for an information security management system, or ISMS. ISO/IEC 27001:2022 addresses how an organisation establishes, maintains and continually improves that system.
This means more than implementing security software. The organisation needs a defined scope, risk assessment and treatment processes, responsibilities, documented information, performance evaluation, internal audits and management review.
Controls are selected according to risk and applicable requirements. A Statement of Applicability records the necessary controls, explains inclusion and exclusion decisions for Annex A controls, and records implementation status. It is not a requirement to implement every Annex A control regardless of relevance.
Before committing to certification, check:
- Customer wording: Does the contract require certification, alignment, or evidence of particular controls?
- Scope: Which legal entities, services, locations and systems must be included?
- Ownership: Who will maintain the ISMS and secure management participation?
- Evidence: Can you demonstrate that processes operate consistently, not just that policies exist?
- Ongoing effort: Have you allowed for internal audits, management reviews, corrective actions and external assessment?
Independent certification bodies perform certification; ISO itself does not. A certificate covering one service or entity should not be presented as covering the entire business.
Choose cybersecurity frameworks by risk, contracts and capacity
Use three decision filters before approving a project.
First, identify the business harm. Consider lost access to essential systems, fraudulent payments, exposure of sensitive records and disruption caused by a supplier. Prioritise protections against those scenarios. Our guide to downtime costs and recovery priorities can help make those discussions concrete.
Second, verify external requirements. Read tender documents, contracts, insurance questions and applicable regulatory obligations. Ask customers to clarify ambiguous phrases such as “ISO compliant”. A framework does not automatically satisfy privacy law, sector obligations or every contractual condition.
Third, assess delivery capacity. Identify the staff time, technical capability and ongoing evidence collection each approach needs. A managed provider can support implementation, but business leaders still own decisions about risk, budget and acceptable exceptions.
If basic protections are inconsistent, prioritise those gaps while establishing simple governance. If responsibilities and priorities are unclear, NIST CSF can organise the plan. If certification is a genuine customer requirement, scope an ISO 27001 programme early rather than treating the audit as a final paperwork exercise.
Turn the choice into an actionable first quarter
Avoid launching several disconnected compliance projects. Build one improvement register that maps work to relevant cybersecurity frameworks.
In the first month, confirm critical services, customer requirements, current controls and major gaps. Assign a business sponsor and a technical owner.
During the second month, address high-risk gaps such as exposed privileged accounts, unsupported systems or untested backups. Record evidence, exceptions and residual risks.
In the third month, test an incident scenario and a recovery process. Review progress with management, update priorities and confirm the next investment decisions.
For each action, record the risk addressed, owner, deadline, evidence and review frequency. A configuration report, restoration result or approved access review is more useful than an unsupported claim that a control is complete. Our BCDR evidence guide explains how recovery records can support this work.
The best choice is the approach your business can operate and demonstrate, not merely describe in a policy.
Tech Engine can help you review your cyber security, assess control gaps and develop a practical improvement roadmap. Call 1300 088 324 or email sales@techengine.au to discuss your priorities.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint