What is the Essential Eight?
The Essential Eight is a set of eight cybersecurity mitigation strategies developed by the Australian Signals Directorate (ASD). It helps organisations reduce their exposure to common cyberattacks, limit the damage caused by compromised accounts or devices, and improve their ability to recover from incidents.
For Australian GP clinics, medical centres and allied health practices, the framework provides a practical way to strengthen the systems that support patient care, including reception computers, clinical workstations, practice servers, cloud accounts and backups.
It covers eight areas: application control, patching applications, configuring Microsoft Office macros, user application hardening, restricting administrative privileges, patching operating systems, multifactor authentication and regular backups. The strategies work together rather than as eight isolated tasks.
The Essential Eight is a practical starting point for GP clinics, medical centres and allied health providers—but effective implementation requires more than ticking boxes.
Why the Essential Eight matters for healthcare
Australian healthcare practices depend on electronic health records, appointment systems, email, clinical software and connected devices. A cyber incident can expose sensitive information and interrupt patient care. The Australian Signals Directorate (ASD) recommends the Essential Eight to mitigate common cyberattack techniques.
Consider a receptionist opening a malicious attachment, an attacker using a stolen cloud password, or a practice discovering that its backups cannot be restored. These are different risks, but all demonstrate why layered security and tested recovery arrangements matter.
The eight Essential Eight strategies, explained for healthcare
Each strategy has detailed requirements in ASD's maturity model. The examples below illustrate practical applications, not the complete technical requirements.
Application control
Limit which applications and code can run on practice devices.
Clinic example: Prevent an unknown program downloaded from email from running on a reception computer.
Evidence: Application control policy, approved rules and exceptions.
Patch applications
Keep browsers, PDF readers, remote-access tools and clinical applications appropriately updated.
Clinic example: Coordinate vendor-approved updates for clinical management software.
Evidence: Software inventory, patch reports and exception register.
Configure Microsoft Office macro settings
Restrict potentially dangerous macro execution in Office documents.
Clinic example: Reduce the risk from a malicious invoice spreadsheet.
Evidence: Centrally enforced Office configuration and verification.
User application hardening
Reduce risky application functionality and attack surfaces.
Clinic example: Apply consistent browser security settings across consultation-room computers.
Evidence: Configuration policies and device checks.
Restrict administrative privileges
Give staff only the privileges necessary for their work.
Clinic example: Everyday clinician accounts should not have unrestricted local administrator rights.
Evidence: Privileged-account lists, reviews and access records.
Patch operating systems
Maintain supported, updated operating systems and manage exceptions.
Clinic example: Identify unsupported Windows devices linked to medical equipment.
Evidence: Device inventory, update reports and risk treatments.
Multifactor authentication (MFA)
Use additional authentication factors to protect relevant accounts and services.
Clinic example: Protect cloud email, privileged accounts and remote access from password-only compromise.
Evidence: MFA policies, coverage and documented exceptions.
Regular backups
Protect important data and verify that it can be restored.
Clinic example: Test restoration of clinical information after a simulated outage.
Evidence: Backup settings, monitoring and restoration-test results.
Where should a GP clinic assess its controls?
A meaningful review covers the actual clinical environment, not just an office laptop or cloud subscription.
| Environment | Key questions |
|---|---|
| Reception computers | Can unauthorised software run? Are browsers, operating systems and accounts securely managed? |
| Consultation-room workstations | Are clinical application dependencies understood? Are updates tested and access rights restricted? |
| Servers and shared systems | Are privileged accounts controlled, systems patched and recovery procedures tested? |
| Cloud email and remote access | Is MFA correctly configured and enforced for relevant accounts and services? |
| Medical devices and legacy systems | Are unsupported systems identified, risks assessed and compensating controls documented? |
| Backup infrastructure | Are backups protected from unauthorised change and are restorations regularly tested? |
Clearly assign responsibilities between practice management, IT support providers, cloud providers and clinical software vendors.
Understanding Essential Eight maturity levels
ASD's model defines Maturity Levels Zero, One, Two and Three. The levels describe progressively stronger implementation requirements against different adversary behaviours. The appropriate target depends on the organisation's risk context and applicable obligations.
Maturity Level Zero indicates weaknesses in implementing the mitigation strategies. Level One addresses common opportunistic attacks; Level Two addresses more capable adversaries; and Level Three addresses more sophisticated adversaries. These are summaries, not substitutes for ASD's detailed requirements.
What evidence should the practice retain?
| Control area | Example evidence |
|---|---|
| Software and operating systems | Asset inventory, patch reports, unsupported-system register |
| Application and macro controls | Enforced policies, approved rules, exception records |
| Privileges and MFA | Account lists, access reviews, authentication policy coverage |
| Backups | Backup configurations, access restrictions, successful restore tests |
Assessment reports should separate technically verified findings from supplier statements and self-reported answers.
What about legacy clinical software and medical devices?
Some medical equipment and clinical systems cannot be patched without vendor approval or disruption to patient services. Rather than silently excluding them, identify the system, confirm vendor support, assess network exposure, document compensating controls and assign an owner and remediation timeframe.
Network segmentation, restricted access and monitoring may reduce risk, but do not automatically satisfy a specific Essential Eight maturity requirement. Report any unmet requirement transparently.
Essential Eight versus APP 11: what is the difference?
The Essential Eight is a technical mitigation framework. Australian Privacy Principle 11 (APP 11) requires entities covered by the Australian Privacy Principles to take reasonable steps to protect personal information against specified risks, including misuse, interference, loss and unauthorised access, modification or disclosure.
Implementing Essential Eight controls can support broader security arrangements, but does not automatically establish APP 11 compliance. Healthcare providers should also consider governance, privacy policies, supplier arrangements, staff awareness, incident response and the information lifecycle.
Read more: APP 11 and healthcare cybersecurity obligations.
A five-stage improvement roadmap for healthcare practices
Scope: Identify devices, software, cloud services, clinical dependencies and ownership. Assess: Verify controls and document gaps. Prioritise: Consider likelihood, potential patient-care impact and vendor constraints. Implement: Apply and test changes with appropriate rollback arrangements. Review: Reassess following major changes and as part of routine security governance.
12-point Essential Eight readiness checklist
Use this as an awareness tool to guide discussions with your IT provider—not as a maturity-level certification.
- Do we have an accurate inventory of devices and important software?
- Can unauthorised software execute on practice computers?
- Are applications updated and exceptions tracked?
- Are Office macros appropriately restricted?
- Are browsers and user applications securely configured?
- Are administrative privileges limited and reviewed?
- Are operating systems supported and patched?
- Is MFA enforced for relevant accounts and services?
- Are unsupported clinical systems identified and risk-assessed?
- Are critical data and systems backed up appropriately?
- Have we tested restoring important clinical services and information?
- Are responsibilities and remediation actions documented?
Frequently asked questions
Is the Essential Eight mandatory for every private GP clinic?
No universal requirement makes the Essential Eight mandatory for every private GP clinic. Specific contractual, government or other obligations may apply, and privacy requirements must be assessed separately.
Does Microsoft 365 mean we meet the Essential Eight?
No. Security features must be configured, enforced and verified against the applicable requirements across the defined assessment scope.
Can our IT provider perform the assessment?
An IT provider can help assess and implement controls. Practice owners should understand the scope, evidence and limitations. Independent review may provide additional assurance.
How often should we review our controls?
Use a risk-based schedule and reassess after significant system, supplier or threat changes. Monitoring and maintenance should continue between formal reviews.
Does Essential Eight implementation prevent every cyberattack?
No. It mitigates selected attack pathways and should sit within broader cybersecurity, privacy and incident-response arrangements.
Further reading
Need help assessing your practice?
Veytrix Cyber Security provides scoped cybersecurity assessments for Australian healthcare providers, including Sydney onsite and remote services.
Request a consultation →