Essential 8 Australian cyber security strategies with maturity levels

version
0.1.0
GitHub stars
436

Install

/plugin install essential8@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

Essential 8 Expert

Deep expertise in Australian Cyber Security Centre (ACSC) Essential Eight mitigation strategies for cyber security.

Expertise Areas

Essential Eight Overview

Authority: Australian Cyber Security Centre (ACSC) Purpose: Mitigate cyber security incidents through prioritized mitigation strategies Structure: 8 mitigation strategies, 3 maturity levels Applicability: All Australian organizations, mandatory for government Current Version: Updated regularly (latest guidance 2024)

Key Principles:

  • Risk-based approach
  • Prioritized mitigation strategies
  • Maturity progression model
  • Implementation flexibility
  • Continuous improvement

Background:

  • Based on top 35 mitigation strategies (now Strategies to Mitigate Cyber Security Incidents)
  • Focused on most effective controls
  • Evidence-based effectiveness (from real incidents)
  • Addresses 85%+ of intrusion techniques

Maturity Levels

LevelNameDescriptionTimelineUse Case
Level 1Partly AlignedBasic implementation6-9 monthsStarting point, small orgs
Level 2Mostly AlignedEnhanced security9-12 monthsRecommended baseline
Level 3Fully AlignedAdvanced security12-18 monthsGovernment, critical infra

Maturity Level 1 (Partly Aligned):

  • Intent: Partial protection against commodity attacks
  • Threats: Opportunistic attackers, mass malware
  • Protection: Basic ransomware defense, common exploits
  • Implementation: Foundational controls
  • Validation: Self-assessment
  • Characteristics:
    • Entry-level baseline
    • Cost-effective
    • Manageable operational impact
    • Foundation for progression

Maturity Level 2 (Mostly Aligned):

  • Intent: Protection against sophisticated adversaries
  • Threats: Targeted attacks, advanced persistent threats (APTs)
  • Protection: Most attack techniques, zero-day exploitation
  • Implementation: Enhanced controls, automation
  • Validation: Internal assessment with external validation recommended
  • Characteristics:
    • Industry standard
    • Balanced security vs usability
    • Reasonable resource requirements
    • Recommended for most organizations

Maturity Level 3 (Fully Aligned):

  • Intent: Maximum protection against advanced adversaries
  • Threats: Nation-state actors, sophisticated cybercriminals
  • Protection: Advanced techniques, zero-day, supply chain
  • Implementation: Hardened controls, comprehensive monitoring
  • Validation: Independent third-party assessment
  • Characteristics:
    • Highest security posture
    • Significant operational controls
    • Substantial resources required
    • Mandatory for Commonwealth government

The 8 Mitigation Strategies

Strategy 1: Application Control

Purpose: Prevent execution of unapproved/malicious programs including malware

Risk Addressed:

  • Malware execution
  • Unauthorized software
  • Ransomware
  • Backdoors and remote access tools

Implementation Approach:

  • Whitelist approved applications
  • Block execution from user-writable locations
  • Control drivers and kernel modules
  • Manage scripts and macros
Maturity Level 1 Requirements

Workstation Controls:

  • Application control implemented on all workstations to block unapproved applications
  • Microsoft's recommended application blocklist implemented
  • Approved applications allowed to execute
  • Application control events logged

Technical Implementation:

  • Windows: AppLocker, Windows Defender Application Control (WDAC)
  • macOS: Gatekeeper, application allowlisting
  • Linux: AppArmor, SELinux, fapolicyd

Allowed Execution:

  • Publisher certificate rules (preferred)
  • Path rules for IT-controlled locations
  • Hash rules (for unchanging apps)

Blocked Execution:

  • User-writable directories (%TEMP%, %APPDATA%, Downloads)
  • Removable media (USB drives)
  • Email attachments (direct execution)

Logging:

  • All blocked execution attempts
  • Application control rule updates
  • Enforcement mode changes
Maturity Level 2 Requirements

Server Controls:

  • Application control on all servers
  • Internet-facing servers prioritized
  • Application control events logged centrally

Driver/Script Controls:

  • Driver and kernel module controls
  • PowerShell execution controlled (Constrained Language Mode)
  • Command-line interpreters restricted
  • Scripting languages blocked unless required

Technical Additions:

  • PowerShell Constrained Language Mode
  • Script execution policies enforced
  • Driver signature enforcement
  • Windows Defender Application Control (WDAC) policies

Centralization:

  • Central policy management
  • SIEM integration for logging
  • Automated rule deployment
Maturity Level 3 Requirements

Validation and Hardening:

  • Application control configuration validated at least annually
  • Extremely hardened configuration
  • Application control events analyzed for indicators of compromise
  • Annual penetration testing of controls

Advanced Capabilities:

  • Automated compliance checking
  • Threat hunting using control events
  • Machine learning for anomaly detection
  • Integration with threat intelligence

Testing:

  • Penetration testing of bypass techniques
  • Red team exercises
  • Independent validation

Strategy 2: Patch Applications

Purpose: Remediate security vulnerabilities in office productivity suites, web browsers, email clients, PDF readers, Flash Player, and other applications

Risk Addressed:

  • Exploitation of known vulnerabilities
  • Zero-day attacks (limited window)
  • Remote code execution
  • Privilege escalation

Critical Applications (Prioritize):

  • Web browsers (Chrome, Edge, Firefox, Safari)
  • Office productivity (Microsoft Office, LibreOffice)
  • PDF readers (Adobe Acrobat, alternative readers)
  • Email clients
  • Java (if required)
  • Adobe Flash Player (deprecated, remove)
  • Media players
  • Compression tools
Maturity Level 1 Requirements

Patching Timeline:

  • Security vulnerabilities in applications patched within one month of release
  • Extreme risk vulnerabilities patched within 48 hours

Extreme Risk Definition:

  • CVSS base score 9.0-10.0 (critical)
  • Actively exploited in the wild
  • Exploit code publicly available
  • No effective mitigating controls
  • Affects internet-facing or critical systems

Prioritization:

  1. Internet-facing applications
  2. Applications processing untrusted data
  3. Privileged applications
  4. All other applications

Process:

  • Maintain application inventory
  • Subscribe to vendor security advisories
  • Assess vulnerability severity (CVSS scoring)
  • Test patches in non-production
  • Deploy patches within timeline
  • Verify successful installation
  • Document exceptions and risk acceptance
Maturity Level 2 Requirements

Accelerated Timeline:

  • Security vulnerabilities patched within two weeks of release
  • Extreme risk still 48 hours

Automation:

  • Automated patch deployment where possible
  • Automated testing procedures
  • Automated compliance reporting

Enhancements:

  • Reduced testing cycle
  • Staged deployment
  • Enhanced monitoring for failures
  • Metrics tracking (mean time to patch)
Maturity Level 3 Requirements

Rapid Timeline:

  • All vulnerabilities patched within 48 hours of release

Comprehensive Automation:

  • Fully automated patch testing
  • Rapid deployment capabilities
  • Automated rollback on failure
  • Continuous vulnerability scanning

Advanced Capabilities:

  • Real-time vulnerability feeds
  • Automated risk assessment
  • Integration with threat intelligence
  • Predictive patching (pre-release testing)

Strategy 3: Configure Microsoft Office Macro Settings

Purpose: Prevent malicious macros from executing (common malware delivery vector)

Risk Addressed:

  • Macro-based malware (Emotet, Qbot, etc.)
  • Phishing email attachments
  • Social engineering attacks
  • Initial access for ransomware

Context:

  • Macros are a primary malware delivery mechanism
  • Often delivered via email attachments
  • Social engineering convinces users to enable
  • Can disable security controls, download payloads
Maturity Level 1 Requirements

Macro Restrictions:

  • Microsoft Office macros disabled for files from the internet
  • Only macros in Trusted Locations allowed to execute
  • Macro antivirus scanning enabled (AMSI)
  • OLE package activation blocked

Technical Implementation:

  • Group Policy: "Block macros from running in Office files from the Internet"
  • Define limited Trusted Locations (IT-controlled only)
  • Enable Antimalware Scan Interface (AMSI) for Office
  • Block Object Linking and Embedding (OLE) packages

Trusted Locations:

  • IT-controlled network shares (read-only for users)
  • Centrally managed application directories
  • NOT user-writable locations
  • Limited and documented

User Education:

  • Why macros are blocked
  • How to request macro-enabled document approval
  • Recognizing malicious macro prompts
  • Reporting suspicious emails
Maturity Level 2 Requirements

Enhanced Validation:

  • Only macros from Trusted Locations with validation
  • AMSI enabled for all Office applications
  • All macro execution attempts logged

Technical Additions:

  • Macro validation before execution
  • Central logging of macro events
  • Regular review of Trusted Locations
  • Attestation process for macro requirements
Maturity Level 3 Requirements

Comprehensive Controls:

  • Validated macro execution only
  • Digital signature requirements
  • Comprehensive monitoring and alerting
  • Annual validation of controls

Advanced Protection:

  • Publisher certificate validation
  • Macro code review process
  • Automated threat detection
  • Integration with SIEM for analysis

Strategy 4: User Application Hardening

Purpose: Reduce the attack surface of web browsers and office productivity applications

Risk Addressed:

  • Exploitation via web content
  • Drive-by downloads
  • Malicious advertisements
  • Browser-based attacks
  • Vulnerable plugins

Applications in Scope:

  • Web browsers (all)
  • Microsoft Office suite
  • PDF readers
  • Email clients
  • Other productivity applications
Maturity Level 1 Requirements

Web Browser Hardening:

  • Flash content blocked or disabled (Flash is deprecated)
  • Web advertisements blocked (enterprise ad-blocking)
  • Java disabled or removed from web browsers

PDF Reader Hardening:

  • JavaScript disabled in PDF files
  • Embedded content launching blocked
  • Secure reading mode enabled

Office Application Hardening:

  • Unnecessary add-ins disabled
  • ActiveX controls restricted
  • External content prompts enabled

Technical Implementation:

  • Group Policy for browser configuration
  • Enterprise browser extensions (ad-blocking)
  • Standardized browser deployment
  • PDF reader security settings
  • Office Trust Center configuration

Recommended Browsers:

  • Microsoft Edge (Chromium)
  • Google Chrome (enterprise)
  • Mozilla Firefox ESR

Deprecated/Removed:

  • Internet Explorer (unsupported)
  • Adobe Flash Player (end-of-life 2020)
  • Java browser plugins
Maturity Level 2 Requirements

Enhanced Hardening:

  • Web-based Java execution blocked
  • All unnecessary features disabled
  • Centrally managed configuration
  • Configuration compliance monitoring

Additional Controls:

  • Safe Browsing enabled
  • Password managers (enterprise)
  • Credential Guard enabled
  • Application Guard (where applicable)
Maturity Level 3 Requirements

Comprehensive Validation:

  • Hardened configuration validated
  • Regular recertification
  • Advanced exploit protections enabled
  • Security feature compliance enforced

Advanced Protections:

  • Microsoft Defender Application Guard
  • Browser isolation technologies
  • Zero Trust browsing
  • Continuous monitoring and alerting

Strategy 5: Restrict Administrative Privileges

Purpose: Prevent privilege escalation and lateral movement by restricting administrative privileges

Risk Addressed:

  • Privilege escalation attacks
  • Lateral movement
  • Credential theft
  • System-wide compromise
  • Ransomware spread

Context:

  • Most users don't need admin rights
  • Admin credentials are high-value targets
  • Malware with admin rights can disable security
  • Lateral movement requires privileged access
Maturity Level 1 Requirements

Privilege Separation:

  • Privileged users use separate privileged and unprivileged accounts
  • Privileged accounts cannot access internet, email, web
  • Unprivileged accounts cannot perform admin tasks
  • Standard users not members of local administrators group

Technical Implementation:

  • Remove local administrator group membership for users
  • Create separate admin accounts (e.g., user vs user_admin)
  • Deny privileged accounts internet/email access (Group Policy)
  • Implement "Run as administrator" prompts
  • Log all administrative actions

Privileged Account Usage:

  • Administrative tasks only
  • No daily productivity use
  • No internet browsing
  • No email access
  • Dedicated privileged access workstations (recommended)

Logging:

  • All privileged account logons
  • Administrative action audit logs
  • Privileged account usage monitoring
Maturity Level 2 Requirements

Enhanced Controls:

  • Privileged accounts used only for administrative activities
  • Privileged operating environment hardening
  • Privileged access centrally managed and monitored
  • Just-in-time administration preferred

Technical Additions:

  • Privileged Access Management (PAM) solution
  • Time-limited admin elevation
  • Hardened privileged access workstations (PAWs)
  • Session recording for administrative actions
  • Multi-person authorization for critical changes

PAM Solutions:

  • Microsoft Identity Manager (MIM)
  • CyberArk Privileged Access Security
  • BeyondTrust Privileged Remote Access
  • Delinea Secret Server

Privileged Workstation Hardening:

  • Dedicated hardware or VMs
  • No internet/email access
  • Enhanced monitoring
  • Limited software installation
  • Multi-factor authentication required
Maturity Level 3 Requirements

Maximum Restriction:

  • Privileged access disabled by default
  • Just-in-time (JIT) administration required
  • Comprehensive validation and monitoring
  • Annual independent assessment

Advanced Capabilities:

  • Zero standing privileges
  • JIT elevation with approval workflow
  • Privileged session management
  • Behavioral analytics on privileged accounts
  • Automated anomaly detection

JIT Implementation:

  • On-demand privilege elevation
  • Approval workflow (automated or manual)
  • Time-limited access (hours)
  • Automatic de-elevation
  • Full session audit trail

Strategy 6: Patch Operating Systems

Purpose: Remediate security vulnerabilities in operating systems to prevent exploitation

Risk Addressed:

  • OS-level exploitation
  • Kernel vulnerabilities
  • Privilege escalation
  • Remote code execution
  • Zero-day attacks (limited window)

Operating Systems in Scope:

  • Windows (Desktop, Server)
  • Linux (all distributions)
  • macOS
  • Mobile operating systems (iOS, Android)
  • Network device firmware
  • Hypervisors
Maturity Level 1 Requirements

Patching Timeline:

  • OS vulnerabilities patched within one month of release
  • Extreme risk vulnerabilities patched within 48 hours

Prioritization:

  1. Internet-facing systems
  2. Critical infrastructure
  3. Servers
  4. Workstations
  5. Network devices

Process:

  • Maintain inventory of all operating systems
  • Enable automatic updates or WSUS/SCCM
  • Subscribe to OS vendor security advisories
  • Assess vulnerability severity (CVSS)
  • Test patches in non-production environment
  • Deploy within required timeline
  • Verify successful installation
  • Document exceptions

Vendor Advisories:

  • Microsoft Security Update Guide
  • Red Hat Security Advisories
  • Ubuntu Security Notices
  • Apple Security Updates
  • Vendor-specific notification lists

Unsupported OS:

  • Windows 7, Server 2008 (end-of-life)
  • Plan migration to supported versions
  • Isolate if migration not possible
  • Compensating controls required
Maturity Level 2 Requirements

Accelerated Timeline:

  • OS vulnerabilities patched within two weeks
  • Extreme risk still 48 hours

Automation:

  • Automated patch deployment (WSUS, SCCM, Ansible)
  • Automated testing procedures
  • Staged deployment (pilot → production)
  • Automated verification
  • Compliance reporting

Enhancements:

  • Reduced testing window
  • Pre-approved maintenance windows
  • Enhanced rollback procedures
  • Metrics and KPIs (MTTP - Mean Time To Patch)
Maturity Level 3 Requirements

Rapid Timeline:

  • All OS vulnerabilities patched within 48 hours

Comprehensive Automation:

  • Fully automated testing (sandbox)
  • Rapid deployment capabilities
  • Automated rollback on detection of issues
  • Continuous vulnerability scanning
  • Real-time compliance dashboards

Advanced Capabilities:

  • Pre-release patch testing (beta programs)
  • Vulnerability prediction and pre-positioning
  • Integration with threat intelligence
  • Zero-day response procedures
  • Automated risk assessment

Strategy 7: Multi-Factor Authentication

Purpose: Prevent unauthorized access using compromised credentials

Risk Addressed:

  • Credential theft (phishing, keylogging, breach dumps)
  • Brute force attacks
  • Password spraying
  • Compromised passwords
  • Unauthorized access to systems and data

Context:

  • Passwords alone are insufficient
  • Phishing is extremely effective
  • Credential stuffing attacks common
  • MFA significantly reduces risk
Maturity Level 1 Requirements

MFA Scope:

  • MFA used to authenticate all users to their organization's online services providing access to important data repositories
  • MFA used to authenticate all privileged users
  • MFA used to authenticate all remote access

Important Data Repositories:

  • File servers with sensitive/business data
  • SharePoint sites
  • Cloud storage (OneDrive, Google Drive)
  • Customer/patient data systems
  • Financial systems
  • Email servers

Privileged Users:

  • Domain administrators
  • Local administrators
  • Database administrators
  • Security administrators
  • Application administrators
  • Any elevated privileges

Remote Access:

  • VPN connections
  • Remote Desktop (RDP)
  • SSH access to servers
  • Web-based admin consoles
  • Cloud service access

Acceptable MFA Methods:

  • Authenticator apps (Microsoft Authenticator, Google Authenticator, Authy)
  • Hardware tokens (YubiKey, RSA tokens)
  • Smart cards
  • SMS/phone call (less secure, use sparingly)
  • Biometrics combined with another factor

Technical Implementation:

  • Azure AD MFA (Microsoft 365)
  • Duo Security
  • Okta Verify
  • RSA SecurID
  • Google Authenticator
  • FIDO2 security keys

User Enrollment:

  • Mandatory MFA enrollment
  • Multiple backup methods
  • Self-service enrollment portals
  • Help desk support for issues
  • User training on MFA
Maturity Level 2 Requirements

Extended Scope:

  • MFA used to authenticate all users
  • Phishing-resistant MFA preferred where possible
  • MFA for all access to important data

All Users:

  • Not just privileged or remote
  • All employees, contractors, partners
  • All authentication events
  • No exceptions without risk acceptance

Phishing-Resistant MFA (Preferred):

  • FIDO2 security keys (YubiKey, Titan Key)
  • Smart cards (PIV, CAC)
  • Windows Hello for Business
  • Certificate-based authentication
  • Device-based authentication

Technical Enhancements:

  • Conditional access policies
  • Risk-based authentication
  • Device compliance checks
  • Location-based policies
  • Disable legacy authentication protocols

Exception Management:

  • Documented exceptions
  • Risk acceptance by management
  • Compensating controls
  • Regular review of exceptions
Maturity Level 3 Requirements

Mandatory Phishing-Resistant MFA:

  • Phishing-resistant MFA required for all users
  • No exceptions (or very limited with compensating controls)
  • Comprehensive monitoring and logging

Phishing-Resistant Only:

  • FIDO2 security keys mandatory
  • Smart cards required
  • Windows Hello for Business
  • Certificate-based authentication
  • NOT acceptable: SMS, voice call, push notifications, TOTP apps

Rationale for Phishing-Resistant:

  • SMS can be intercepted (SIM swapping)
  • Push notifications can be fatigued ("MFA fatigue attack")
  • TOTP codes can be phished in real-time
  • FIDO2 cryptographically verifies the service
  • Prevents man-in-the-middle attacks

Implementation Considerations:

  • FIDO2 key procurement for all users
  • Backup key issuance
  • Lost key replacement process
  • Privileged account recovery procedures
  • Break-glass account procedures

Advanced Capabilities:

  • Device attestation
  • Continuous authentication
  • Behavioral biometrics
  • Zero Trust architecture
  • Integration with identity governance

Strategy 8: Regular Backups

Purpose: Ensure availability of important data and system restoration capability after cyber security incidents

Risk Addressed:

  • Ransomware attacks
  • Data destruction
  • Accidental deletion
  • Hardware failure
  • Natural disasters
  • Insider threats

Context:

  • Backups are the last line of defense
  • Ransomware specifically targets backups
  • Recovery depends on backup integrity
  • Testing is critical - untested backups fail
Maturity Level 1 Requirements

Backup Scope:

  • Backups of important data, software, and configuration settings performed and retained in accordance with business continuity requirements

Minimum Requirements:

  • Daily backups (minimum weekly)
  • Retention: at least 3 months
  • Important data identified and scoped
  • Backup storage offline or offsite
  • Restoration tested at least quarterly

Important Data Definition:

  • Business-critical data
  • Customer/patient records
  • Financial data
  • Intellectual property
  • Configuration data
  • System images for critical servers

3-2-1 Backup Rule:

  • 3 copies of data (production + 2 backups)
  • 2 different media types (disk, tape, cloud)
  • 1 copy offsite or offline (air-gapped)

Offline/Offsite Storage:

  • Tape backups physically removed
  • Cloud backups in separate account
  • Network-disconnected storage
  • Immutable backups (cannot be modified/deleted)

Restoration Testing:

  • Quarterly full restoration test
  • Document restoration procedures
  • Measure recovery time
  • Validate data integrity
  • Test different failure scenarios

Technical Implementation:

  • Veeam Backup & Replication
  • Azure Backup
  • AWS Backup
  • Acronis Cyber Backup
  • Commvault
  • Native tools (Windows Backup, Time Machine)
Maturity Level 2 Requirements

Enhanced Protection:

  • Backups disconnected from networks when not being performed
  • Backup processes improved through automation
  • More frequent restoration testing

Air-Gapped Backups:

  • Network segmentation for backup infrastructure
  • Automated connect/disconnect procedures
  • Separate administrative credentials
  • No persistent network connectivity

Immutable Backups:

  • Write-once-read-many (WORM) storage
  • Cloud immutability features (Azure, AWS)
  • Legal hold/retention lock
  • Cannot be deleted by ransomware

Automation:

  • Automated backup verification
  • Automated restore testing
  • Backup job monitoring and alerting
  • Automated failover procedures

Testing Frequency:

  • Monthly restoration testing (instead of quarterly)
  • Different data sets each test
  • Varied failure scenarios
  • Tabletop exercises

Privileged Access Controls:

  • Separate admin accounts for backups
  • MFA for backup administration
  • Logging of all backup access
  • Least privilege access model
Maturity Level 3 Requirements

Comprehensive Protection:

  • Unprivileged accounts cannot access backups
  • Privileged accounts required, MFA enforced
  • Backups tested annually in a full disaster recovery scenario
  • Comprehensive automation and monitoring

Hardened Backup Environment:

  • Fully isolated backup infrastructure
  • Separate domain/forest for backup admins
  • Hardened backup servers
  • Network segmentation enforced
  • Monitoring and alerting (SIEM integration)

Full Disaster Recovery Testing:

  • Annual DR exercise
  • Complete system restoration
  • Alternate site failover
  • Business continuity integration
  • Lessons learned and improvements

Advanced Capabilities:

  • Automated backup integrity checking
  • Malware scanning of backups
  • Versioning and point-in-time recovery
  • Rapid recovery capabilities (instant VM recovery)
  • Geo-redundant backups

Backup Security:

  • Encryption at rest and in transit
  • Key management (separate from backup system)
  • Access auditing and alerting
  • Behavioral analytics on backup access
  • Threat detection in backup environment

Australian Government Requirements

Non-Corporate Commonwealth Entities (NCEs)

Mandatory Requirements:

  • Must implement Essential Eight at Maturity Level 3
  • Annual self-assessment required
  • Report to Attorney-General's Department
  • Published in annual cyber security posture report

Entities Included:

  • Commonwealth departments
  • Executive agencies
  • Statutory authorities (non-corporate)
  • Parliamentary departments

Compliance:

  • Protective Security Policy Framework (PSPF) Policy 10
  • ISM (Information Security Manual) controls
  • ACSC guidance mandatory
  • Annual attestation by Agency Head

Corporate Commonwealth Entities (CCEs)

Requirements:

  • Must implement Essential Eight (maturity level based on risk)
  • Risk assessment determines target maturity level
  • Governance and reporting through entity boards
  • Cyber security strategy required

Risk-Based Approach:

  • Risk assessment methodology
  • Maturity level selection justified
  • Board oversight and approval
  • Regular reassessment

State and Territory Government

Variability:

  • Requirements vary by jurisdiction
  • Many have Essential Eight mandates
  • Maturity levels differ (typically ML2 or ML3)
  • Check specific state policies

Examples:

  • NSW: Essential Eight compliance required, ML varies
  • Victoria: Mandatory for some agencies
  • Queensland: Risk-based approach
  • WA, SA, TAS, NT, ACT: Varying requirements

Critical Infrastructure

Security of Critical Infrastructure (SOCI) Act 2018:

  • Enhanced cyber security obligations
  • Risk management programs required
  • Incident reporting mandatory
  • Essential Eight strongly recommended

Critical Infrastructure Sectors:

  1. Communications
  2. Financial services and markets
  3. Data storage or processing
  4. Defense industry
  5. Higher education and research
  6. Energy
  7. Food and grocery
  8. Health care
  9. Space technology
  10. Transport
  11. Water and sewerage

Cyber Security Obligations:

  • Adopt and maintain a risk management program
  • Report cyber security incidents
  • Comply with directions (government-issued)
  • Essential Eight implementation recommended/required

Implementation Guidance

Assessment Process

Step 1: Current State Assessment

  • Document existing controls
  • Map to Essential Eight requirements
  • Identify current maturity level (per strategy)
  • Gap analysis (current vs target)

Step 2: Prioritization

  • Risk-based prioritization
  • Quick wins identification
  • Resource allocation
  • Phased approach planning

Step 3: Remediation Planning

  • Detailed implementation plan
  • Resource requirements (staff, budget, tools)
  • Timeline and milestones
  • Stakeholder communication

Step 4: Implementation

  • Strategy-by-strategy rollout
  • Testing and validation
  • User training and awareness
  • Documentation

Step 5: Validation

  • Control effectiveness testing
  • Independent assessment (for ML3)
  • Gap remediation
  • Continuous improvement

Step 6: Reporting

  • Self-assessment documentation
  • Management reporting
  • Compliance attestation (if required)
  • Annual reassessment

Common Challenges

  1. Application Control Complexity

    • Most difficult to implement
    • Application inventory challenges
    • Legacy application issues
    • User resistance
    • Mitigation: Start in audit mode, gradual enforcement, user engagement
  2. Patching Windows (48 hours at ML3)

    • Testing time constraints
    • Production change windows
    • Rollback concerns
    • Mitigation: Automation, pre-approved processes, robust testing
  3. MFA User Experience

    • User friction and resistance
    • Legacy application compatibility
    • Helpdesk burden
    • Mitigation: User training, phased rollout, modern authentication
  4. Privileged Access Restrictions

    • Operational efficiency concerns
    • Admin resistance
    • Help desk implications
    • Mitigation: PAM solutions, JIT administration, clear policy
  5. Resource Constraints

    • Budget limitations
    • Staff expertise
    • Competing priorities
    • Mitigation: Phased approach, MSPs, automation, executive support

Tools and Technologies

Application Control:

  • Windows Defender Application Control (WDAC)
  • AppLocker
  • CrowdStrike Application Control
  • Carbon Black App Control

Patching:

  • Windows Server Update Services (WSUS)
  • System Center Configuration Manager (SCCM)
  • Microsoft Endpoint Manager (Intune)
  • Ansible, Puppet, Chef
  • Ivanti Patch Management
  • ManageEngine Patch Manager

MFA:

  • Microsoft Azure AD MFA
  • Duo Security
  • Okta
  • Ping Identity
  • YubiKey (FIDO2)
  • RSA SecurID

PAM (Privileged Access Management):

  • CyberArk Privileged Access Security
  • BeyondTrust Privileged Remote Access
  • Delinea (Thycotic) Secret Server
  • Microsoft Identity Manager

Backup:

  • Veeam Backup & Replication
  • Azure Backup
  • AWS Backup
  • Commvault
  • Rubrik
  • Cohesity

SIEM/Logging:

  • Microsoft Sentinel
  • Splunk
  • IBM QRadar
  • LogRhythm
  • Elastic Stack

Vulnerability Management:

  • Tenable Nessus
  • Qualys VMDR
  • Rapid7 InsightVM
  • Microsoft Defender Vulnerability Management

Cost Estimates

Maturity Level 1:

  • Small org (50-100 users): $50K-$150K
  • Medium org (500 users): $150K-$350K
  • Large org (5000+ users): $500K-$1M+

Maturity Level 2:

  • Small org: $100K-$300K
  • Medium org: $300K-$700K
  • Large org: $1M-$3M+

Maturity Level 3:

  • Small org: $200K-$500K
  • Medium org: $500K-$1.5M
  • Large org: $2M-$5M+

Costs include tools, consulting, labor, training, ongoing operations


Threat Landscape Context

Threats Mitigated

Ransomware (Primary Focus):

  • 85%+ of ransomware prevented by Essential Eight
  • Application control blocks execution
  • Backups enable recovery
  • MFA prevents initial access
  • Patching closes vulnerabilities

Examples: LockBit, ALPHV/BlackCat, Cl0p, Royal, Play

Phishing and Credential Theft:

  • MFA prevents compromised credential use
  • Application hardening blocks malicious content
  • Macro settings prevent malicious documents

Malware Delivery:

  • Application control blocks execution
  • Email/web filtering (hardening)
  • Macro blocking

Examples: Emotet, Qbot, IcedID, Dridex

Web-Based Exploits:

  • Browser hardening reduces attack surface
  • Patching closes vulnerabilities
  • Application control prevents downloads

Exploitation of Vulnerabilities:

  • Patching remediates known vulnerabilities
  • Reduced attack window
  • Prioritization of critical/exploited flaws

Privilege Escalation:

  • Admin privilege restrictions limit impact
  • Lateral movement prevented
  • Credential theft mitigated

Insider Threats:

  • Application control limits actions
  • Privileged access restrictions
  • Logging and monitoring
  • Backup protection

Recent Threat Examples

Medibank Breach (2022):

  • Essential Eight would have prevented initial access (MFA)
  • Privileged access restrictions would limit lateral movement
  • Exfiltration detection (monitoring)

Australian Organizations Ransomware (Ongoing):

  • Application control blocks ransomware execution
  • Backups enable recovery without paying
  • MFA prevents VPN compromise
  • Patching closes initial access vulnerabilities

Business Email Compromise (BEC):

  • MFA prevents account takeover
  • Application hardening (email security)
  • User training and awareness

Relationship to Other Frameworks

ISM (Information Security Manual)

Integration:

  • Essential Eight is subset of ISM
  • ISM provides comprehensive security controls
  • Essential Eight are prioritized ISM controls
  • Both published by ACSC

Relationship:

  • Essential Eight: 8 strategies, focused mitigation
  • ISM: Comprehensive security framework, 100s of controls
  • Essential Eight compliance doesn't equal ISM compliance
  • Essential Eight is foundation for ISM

NIST Cybersecurity Framework

Alignment:

  • Essential Eight maps to NIST CSF functions
  • Identify: Asset management, risk assessment
  • Protect: Application control, patching, hardening, MFA, privileges
  • Detect: Logging, monitoring
  • Respond: Incident response
  • Recover: Backups

ISO 27001

Mapping:

  • Essential Eight controls map to ISO 27001 Annex A
  • A.9 Access Control → MFA, Admin Privileges
  • A.12 Operations Security → Patching, Application Control
  • A.12.3 Backups → Regular Backups
  • A.14 System Acquisition → Application Hardening

CIS Controls

Alignment:

  • Essential Eight similar to CIS Critical Security Controls
  • Many overlapping requirements
  • CIS Controls more comprehensive (153 safeguards)
  • Essential Eight more focused (8 strategies)

Capabilities

  • Essential Eight maturity assessment (ML1, ML2, ML3)
  • Strategy-by-strategy implementation guidance
  • Gap analysis and remediation roadmaps
  • Australian government compliance requirements
  • Risk assessment and maturity level selection
  • Tool and technology recommendations
  • Cost estimation and budgeting
  • Timeline and project planning
  • Policy and procedure development
  • User training and awareness materials
  • Control testing and validation
  • Incident response integration
  • Continuous improvement planning
  • Compliance reporting and attestation
  • Integration with ISM and other frameworks

Commands 5

Essential 8 Assessment

Evaluates organizational readiness for Australian Cyber Security Centre (ACSC) Essential 8 mitigation strategies.

Arguments

  • $1 - Target maturity level (required: 1, 2, or 3)
  • $2 - Assessment scope (optional: full, gap-analysis, specific-strategy)

Essential 8 Maturity Levels

LevelNameDescriptionRequirements
1Maturity Level OnePartly alignedMinimum implementation, basic hygiene
2Maturity Level TwoMostly alignedEnhanced security posture
3Maturity Level ThreeFully alignedAdvanced security, adversary resilience

The 8 Mitigation Strategies

1. Application Control

Purpose: Prevent execution of unapproved/malicious programs ML1: Application control on workstations ML2: Application control on servers, block drivers/scripts ML3: Hardened configuration, validated software

2. Patch Applications

Purpose: Remediate vulnerabilities in applications ML1: Patch within one month (extreme risk 48 hours) ML2: Patch within two weeks (extreme risk 48 hours) ML3: Patch within 48 hours (extreme risk 48 hours)

3. Configure Microsoft Office Macro Settings

Purpose: Prevent malicious macros from executing ML1: Disable macros from internet, block OLE packages ML2: Only macros from trusted locations, AMSI enabled ML3: Validate macro execution, publisher certificates

4. User Application Hardening

Purpose: Reduce attack surface of applications ML1: Web browser hardening, block Flash/ads ML2: Block web-based Java, disable unneeded features ML3: All hardening applied, validated configuration

5. Restrict Administrative Privileges

Purpose: Prevent lateral movement and privilege escalation ML1: Remove local admin for standard users ML2: Admin for admin duties only, privileged OS hardening ML3: Admin disabled by default, JIT admin, validated

6. Patch Operating Systems

Purpose: Remediate OS vulnerabilities ML1: Patch within one month (extreme risk 48 hours) ML2: Patch within two weeks (extreme risk 48 hours) ML3: Patch within 48 hours (extreme risk 48 hours)

7. Multi-Factor Authentication (MFA)

Purpose: Prevent unauthorized access ML1: MFA for remote access, privileged users, important data ML2: MFA for all users, phishing-resistant preferred ML3: Phishing-resistant MFA required (FIDO2, smart cards)

8. Regular Backups

Purpose: Recover from cyber security incidents ML1: Daily backups, retention (3 months), test restoration ML2: Backups offline/offsite, process improvements ML3: Hardened backups, 3-2-1 rule, tested recovery

Assessment Output

  1. Overall Maturity Score: Percentage compliance by level
  2. Strategy-by-Strategy Status: Compliance for each of the 8 strategies
  3. Maturity Level Readiness: Current vs target level gap
  4. Critical Gaps: High-priority deficiencies
  5. Implementation Roadmap: Prioritized remediation plan
  6. ACSC Alignment: Compliance with latest guidance (2024)
  7. Estimated Timeline: Maturity improvement timeline
  8. Risk Assessment: Cyber threats mitigated at each level

ACSC Guidance References

  • Essential Eight Maturity Model (Latest version)
  • Strategies to Mitigate Cyber Security Incidents
  • ACSC Cyber Threat Reports
  • ISM (Information Security Manual) - Essential Eight sections

Examples

# Full Maturity Level 2 assessment
/essential8:assess 2 full

# Gap analysis for Maturity Level 1
/essential8:assess 1 gap-analysis

# Specific strategy assessment
/essential8:assess 3 "Multi-Factor Authentication"

Essential Eight Evidence Checklist

Generates comprehensive evidence collection checklists for Australian Cyber Security Centre (ACSC) Essential Eight mitigation strategies with maturity level progression (ML1-ML3).

Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. .gitignore covers evidence/ by default so git add -A will not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).

Usage

/essential8:evidence-checklist <strategy> [--maturity-level <1|2|3>] [--export <format>]

Arguments

  • <strategy>: Essential Eight strategy number (e.g., "1", "2", "3") or name (e.g., "Application Control", "Patch Applications")
  • --maturity-level: Target maturity level (1, 2, or 3). Default: 3
  • --export: Export format (json, csv, markdown). Default: markdown

Example: Application Control Evidence (Maturity Level 3)

/essential8:evidence-checklist 1 --maturity-level 3

Output:

Essential Eight Evidence Checklist
Strategy: #1 - Application Control
Maturity Level: ML3 (Target)
ACSC Guidance: ISM Control ASD-0843, ASD-1490-1507
Assessment Framework: ACSC Essential Eight Maturity Model (June 2024)

## Strategy Description

Application control is implemented on workstations and internet-facing servers to prevent execution of unapproved/malicious programs including .exe, DLL, scripts (e.g., Windows Script Host, PowerShell), installers, compiled HTML, HTML applications and drivers.

## Maturity Level Progression

### ML1 (Baseline)
- Application control implemented on workstations
- Microsoft's "recommended block rules" or equivalent

### ML2 (Improved)
- Application control on workstations and internet-facing servers
- Microsoft's "recommended block rules" + "recommended driver block rules"
- Validated at least annually

### ML3 (Advanced) - TARGET
- ML2 + validation at least every six months
- Application control events logged and centrally captured
- Cryptographic hash validation (not path-based rules)
- Incident response process for blocked applications

## Evidence Requirements (ML3)

### Required Documentation

□ **Application Control Policy**
  - Scope: All Windows workstations, internet-facing servers
  - Required elements:
    - Approved application whitelisting approach (AppLocker, WDAC, etc.)
    - Exception request and approval process
    - Cryptographic hash rules (not path/publisher only)
    - Audit and enforcement mode definitions
    - Frequency of validation (every 6 months minimum)
  - Update frequency: Annually
  - Approver: CISO or Chief Technology Officer
  - Evidence: Approved Application Control Policy v1.x

□ **Application Control Standard Operating Procedure (SOP)**
  - Step-by-step implementation guide
  - Exception approval workflow (screenshots)
  - Testing procedures before deployment
  - Troubleshooting common issues
  - Evidence: SOP document with diagrams

□ **Approved Application List (Whitelist)**
  - Complete list of approved applications
  - Business justification for each application
  - Cryptographic hash values for each approved binary
  - Approval date and approver
  - Evidence: Application whitelist register (Excel/database export)

### Automated Evidence Collection

✓ **Application Control Policy Status (All Endpoints)**
```powershell
# Windows - AppLocker Status
Get-AppLockerPolicy -Effective -Xml | Out-File "evidence/e8-1-applocker-policy-$(Get-Date -Format 'yyyyMMdd').xml"

# Get AppLocker rule count
$policy = Get-AppLockerPolicy -Effective
$ruleCount = ($policy.RuleCollections | Measure-Object).Count
Write-Host "AppLocker rules configured: $ruleCount"

# Export all AppLocker rules
$policy.RuleCollections | ForEach-Object {
    $_ | Export-Csv "evidence/e8-1-applocker-rules-$(Get-Date -Format 'yyyyMMdd').csv" -Append -NoTypeInformation
}

# Windows Defender Application Control (WDAC) status
Get-CIPolicy -PolicyId * | Export-Csv "evidence/e8-1-wdac-policies-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

# Check enforcement mode (audit vs enforce)
Get-AppLockerPolicy -Effective | Select-Object -ExpandProperty RuleCollections |
    Select-Object RuleCollectionType, EnforcementMode |
    Export-Csv "evidence/e8-1-enforcement-mode-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

Collection Frequency: Monthly Retention: 18 months (ACSC recommendation) Purpose: Demonstrates application control is active

✓ Application Control Event Logs (Blocked Attempts)

# AppLocker blocked events (last 30 days)
Get-WinEvent -FilterHashtable @{
    LogName='Microsoft-Windows-AppLocker/EXE and DLL';
    ID=8004,8007;  # Denied events
    StartTime=(Get-Date).AddDays(-30)
} -MaxEvents 10000 |
    Select-Object TimeCreated, Id, Message |
    Export-Csv "evidence/e8-1-applocker-blocks-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

# PowerShell blocked scripts (ScriptBlockLogging)
Get-WinEvent -FilterHashtable @{
    LogName='Microsoft-Windows-PowerShell/Operational';
    ID=4104,4103;  # Script block logging
    StartTime=(Get-Date).AddDays(-30)
} -MaxEvents 10000 |
    Where-Object { $_.Message -like "*blocked*" } |
    Export-Csv "evidence/e8-1-powershell-blocks-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

# WDAC audit events
Get-WinEvent -FilterHashtable @{
    LogName='Microsoft-Windows-CodeIntegrity/Operational';
    ID=3076,3077;  # Code integrity blocks
    StartTime=(Get-Date).AddDays(-30)
} -MaxEvents 10000 |
    Export-Csv "evidence/e8-1-wdac-blocks-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

Collection Frequency: Daily (centralized to SIEM/log aggregator) Retention: 18 months Purpose: Demonstrates application control is working + audit trail

✓ Centralized Log Collection Evidence

# If using Splunk/ELK/Azure Sentinel
# Show that AppLocker events are forwarded to central SIEM

# Example: Azure Sentinel query
# SecurityEvent
# | where EventID in (8004, 8007)  // AppLocker blocks
# | where TimeGenerated > ago(30d)
# | summarize BlockCount = count() by Computer, AccountName
# | order by BlockCount desc

# Export query results monthly
# evidence/e8-1-central-logs-summary-YYYYMM.csv

# Splunk search example
# index=windows sourcetype="WinEventLog:Microsoft-Windows-AppLocker*" EventCode=8004 OR EventCode=8007
# | stats count by host, UserName
# | outputcsv evidence/e8-1-splunk-blocks-YYYYMMDD.csv

Collection Frequency: Monthly summary report Retention: 18 months Purpose: Centralized logging (ML3 requirement)

✓ Application Control Coverage (Endpoint Inventory)

# Query all endpoints for AppLocker/WDAC status via AD
# Requires remote WinRM access

$computers = Get-ADComputer -Filter * -Properties OperatingSystem |
    Where-Object { $_.OperatingSystem -like "*Windows*" }

$results = @()
foreach ($computer in $computers) {
    try {
        $session = New-PSSession -ComputerName $computer.Name -ErrorAction Stop

        $appLockerStatus = Invoke-Command -Session $session -ScriptBlock {
            $policy = Get-AppLockerPolicy -Effective -ErrorAction SilentlyContinue
            return @{
                ComputerName = $env:COMPUTERNAME
                AppLockerEnabled = ($policy -ne $null)
                RuleCount = ($policy.RuleCollections | Measure-Object).Count
                EnforcementMode = ($policy.RuleCollections[0].EnforcementMode)
            }
        }

        $results += New-Object PSObject -Property $appLockerStatus
        Remove-PSSession -Session $session
    }
    catch {
        $results += [PSCustomObject]@{
            ComputerName = $computer.Name
            AppLockerEnabled = "ERROR: Could not connect"
        }
    }
}

$results | Export-Csv "evidence/e8-1-endpoint-coverage-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

# Calculate coverage percentage
$total = ($results | Measure-Object).Count
$enabled = ($results | Where-Object { $_.AppLockerEnabled -eq $true } | Measure-Object).Count
Write-Host "Application Control Coverage: $enabled / $total ($([math]::Round($enabled/$total*100,2))%)"

Collection Frequency: Monthly Retention: 18 months Purpose: Coverage assessment (should be 100% for ML3)

✓ Hash-Based Rules Evidence

# Verify rules use cryptographic hashes (not just path/publisher)
$policy = Get-AppLockerPolicy -Effective

$hashRules = $policy.RuleCollections | Where-Object { $_.RuleCollectionType -eq "Exe" } |
    Select-Object -ExpandProperty Rules |
    Where-Object { $_.GetType().Name -eq "FileHashRule" }

$publisherRules = $policy.RuleCollections | Where-Object { $_.RuleCollectionType -eq "Exe" } |
    Select-Object -ExpandProperty Rules |
    Where-Object { $_.GetType().Name -eq "FilePublisherRule" }

$pathRules = $policy.RuleCollections | Where-Object { $_.RuleCollectionType -eq "Exe" } |
    Select-Object -ExpandProperty Rules |
    Where-Object { $_.GetType().Name -eq "FilePathRule" }

# Export rule type breakdown
[PSCustomObject]@{
    HashRules = ($hashRules | Measure-Object).Count
    PublisherRules = ($publisherRules | Measure-Object).Count
    PathRules = ($pathRules | Measure-Object).Count
    Date = Get-Date -Format "yyyy-MM-dd"
} | Export-Csv "evidence/e8-1-rule-types-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

# For ML3: Hash rules should be >80% of total rules

Collection Frequency: Every 6 months (ML3 validation requirement) Retention: 18 months Purpose: Demonstrates cryptographic hash validation

Manual Evidence Collection

□ Semi-Annual Validation Review

  • Review application control policy effectiveness
  • Test sample of blocked applications (10-20 samples)
  • Review exception requests from last 6 months
  • Update whitelist for new approved applications
  • Document findings and improvements
  • Evidence: Validation review report (every 6 months for ML3)
  • Frequency: Every 6 months (ML3 requirement)

□ Exception Request Approvals (Sample)

  • Sample size: 25 exception requests from last 6 months
  • Required elements:
    • Business justification for exception
    • Security risk assessment
    • Approval by IT Security
    • Approval by business owner
    • Hash value added to whitelist
    • Exception expiry date (if temporary)
  • Evidence: Folder of exception tickets with approvals
  • Frequency: Every 6 months review

□ Incident Response for Blocked Applications

  • Document process for investigating blocked attempts
  • Sample of 10 blocked application incidents
  • Required elements:
    • Event details (user, application, timestamp)
    • Investigation outcome (malware? user error? legitimate need?)
    • Remediation action (educate user, add to whitelist, escalate)
  • Evidence: Incident tickets + investigation notes
  • Frequency: Every 6 months review

□ Internet-Facing Server Coverage

  • List of all internet-facing servers
  • Application control status for each server
  • For servers WITHOUT application control:
    • Justification (e.g., incompatible OS, vendor restriction)
    • Compensating controls (e.g., WAF, IDS, containment)
  • Evidence: Server inventory + application control status
  • Frequency: Every 6 months review (ML3 requirement)

□ Centralized Logging Configuration

  • Screenshots of Windows Event Forwarding (WEF) or SIEM config
  • Show AppLocker/WDAC events forwarded to central log server
  • Retention policy (18 months minimum)
  • Evidence: SIEM configuration + forwarding rules screenshots
  • Frequency: Annual review

Maturity Level Assessment Criteria

ML1 Assessment (Baseline)

✓ Application control implemented on workstations ✓ Microsoft's recommended block rules configured ✓ Policy documented

Typical Gaps:

  • No coverage on servers
  • Path-based rules instead of hash-based
  • No validation process

ML2 Assessment (Improved)

✓ ML1 + application control on internet-facing servers ✓ Microsoft's recommended driver block rules ✓ Annual validation performed ✓ Exceptions documented and approved

Typical Gaps:

  • Validation only annual (not every 6 months)
  • Centralized logging not implemented
  • Incident response process undefined

ML3 Assessment (Advanced) - ACSC Target

✓ ML2 + validation every 6 months ✓ Application control events logged centrally (SIEM) ✓ Cryptographic hash validation for >80% of rules ✓ Incident response process for blocked applications ✓ 100% coverage of in-scope systems

Evidence Required:

  • 2 validation reports per year
  • Central SIEM logs showing AppLocker/WDAC events
  • Hash-based rules evidence
  • Incident response process documentation
  • Coverage reports showing 100%

Common Assessment Findings

Critical (Likely to be rated ML0 or ML1)

❌ No application control implemented ❌ Application control in audit mode only (not enforcing) ❌ Coverage <50% of workstations ❌ No policy documentation

Moderate (Likely to be rated ML1 or ML2)

⚠️ No application control on internet-facing servers ⚠️ Path-based rules only (no hash validation) ⚠️ Validation not performed in last 12 months ⚠️ Events not centrally logged

Minor (ML2 or ML3 with improvements needed)

⚠️ Validation every 12 months (need 6 months for ML3) ⚠️ Some hash-based rules but <80% ⚠️ Centralized logging exists but retention <18 months ⚠️ Incident response process informal (not documented)

Remediation Guidance

If No Application Control Exists

  1. Phase 1 (Weeks 1-4): Planning

    • Select technology (AppLocker for Windows 10+, WDAC for Windows 11)
    • Identify all workstations and internet-facing servers
    • Create initial whitelist (scan existing approved applications)
  2. Phase 2 (Weeks 5-8): Pilot

    • Deploy AppLocker in AUDIT mode to 10% of workstations
    • Monitor audit logs for 2 weeks
    • Refine whitelist based on audit logs
    • Create exception request process
  3. Phase 3 (Weeks 9-12): Rollout

    • Deploy to 50% of workstations in AUDIT mode
    • After 2 weeks, switch to ENFORCE mode
    • Deploy to remaining 50%
    • Deploy to internet-facing servers (carefully!)
  4. Phase 4 (Weeks 13-16): Mature

    • Configure centralized logging (WEF or SIEM)
    • Migrate path rules to hash rules
    • Schedule 6-monthly validation reviews
    • Document incident response process

Timeline: 4-6 months to reach ML3

If Application Control is Audit-Only

  1. Review audit logs for last 30 days
  2. Add commonly-used applications to whitelist (if appropriate)
  3. Educate users on exception request process
  4. Schedule change window to switch to ENFORCE mode
  5. Monitor help desk tickets for 2 weeks
  6. Adjust whitelist based on legitimate exceptions

Timeline: 4-8 weeks

If No Centralized Logging

  1. Windows Event Forwarding (Free)

    • Configure WEF collector server
    • Create GPO to forward AppLocker events
    • Test with pilot group
    • Roll out to all endpoints
  2. SIEM Integration (Recommended for ML3)

    • Configure Splunk/ELK/Azure Sentinel connector
    • Ingest AppLocker event logs
    • Create dashboards and alerts
    • Set retention to 18 months

Timeline: 2-4 weeks

Cross-References

Related Essential Eight Strategies

  • #2 - Patch Applications (approved applications must be patched)
  • #3 - Configure Microsoft Office Macro Settings (AppLocker can block macros)
  • #4 - User Application Hardening (web browsers are approved applications)
  • #7 - Multi-Factor Authentication (MFA for exception approvals)

Maps to Other Frameworks

  • NIST 800-53: CM-7 (Least Functionality), SI-7 (Software Integrity)
  • ISO 27001:2022: A.8.19 (Installation of software on operational systems)
  • CMMC 2.0: CM.L2-3.4.7 (Least functionality)
  • CIS Controls v8: 2.3 (Allowlisting)

Cost Estimates

ML1 Implementation

  • Planning and policy development: 40 hours ($4,000)
  • Pilot deployment: 40 hours ($4,000)
  • Full deployment: 80 hours ($8,000)
  • Total ML1: ~$16k

ML2 Implementation (from ML1)

  • Server deployment: 40 hours ($4,000)
  • Driver block rules: 16 hours ($1,600)
  • Annual validation: 24 hours/year ($2,400/year)
  • Additional for ML2: ~$8k

ML3 Implementation (from ML2)

  • Centralized logging (SIEM): 80 hours + $10k-$50k SIEM ($18k-$58k)
  • Hash rule migration: 40 hours ($4,000)
  • Incident response process: 24 hours ($2,400)
  • Semi-annual validation: 24 hours x2/year ($4,800/year)
  • Additional for ML3: ~$29k-$69k

Total Cost (ML0 to ML3): $53k-$93k (one-time) + $7k/year (ongoing)

Evidence Package Structure

evidence/
└── essential-eight-1-application-control/
    ├── policies/
    │   ├── application-control-policy-v1.2.pdf
    │   ├── application-control-sop-v1.1.docx
    │   └── approved-application-whitelist.xlsx
    ├── automated/
    │   ├── 2024-01/
    │   │   ├── applocker-policy-20240115.xml
    │   │   ├── applocker-blocks-20240131.csv
    │   │   └── endpoint-coverage-20240131.csv
    │   └── ... (monthly)
    ├── validation/
    │   ├── 2024-H1-validation-report.pdf
    │   └── 2024-H2-validation-report.pdf (ML3: every 6 months)
    ├── exceptions/
    │   ├── exception-request-samples-2024-H1/
    │   │   ├── exception-001-adobe-acrobat.pdf
    │   │   ├── exception-002-python.pdf
    │   │   └── ... (25 samples)
    │   └── exception-register-master.xlsx
    ├── incidents/
    │   ├── blocked-app-investigation-samples/
    │   │   ├── incident-001-wannacry-block.pdf
    │   │   ├── incident-002-user-error.pdf
    │   │   └── ... (10 samples)
    │   └── incident-response-procedure.docx
    ├── central-logging/
    │   ├── siem-configuration-screenshots.pdf
    │   ├── wef-config-export.xml
    │   └── monthly-block-summaries/ (from SIEM)
    └── README.md (evidence index, 18-month retention)

Automation Script

<#
.SYNOPSIS
Essential Eight - Application Control Evidence Collection
.DESCRIPTION
Collects evidence for ACSC Essential Eight Maturity Level 3
#>

$OutputDir = "evidence/essential-eight-1-application-control/automated/$(Get-Date -Format 'yyyy-MM')"
New-Item -Path $OutputDir -ItemType Directory -Force | Out-Null

function Collect-AppLockerPolicy {
    Write-Host "Collecting AppLocker policy configuration..."

    # Export effective policy
    Get-AppLockerPolicy -Effective -Xml | Out-File "$OutputDir/applocker-policy-$(Get-Date -Format 'yyyyMMdd').xml"

    # Export rule details
    $policy = Get-AppLockerPolicy -Effective
    $policy.RuleCollections | ForEach-Object {
        $_ | Export-Csv "$OutputDir/applocker-rules-$(Get-Date -Format 'yyyyMMdd').csv" -Append -NoTypeInformation
    }

    Write-Host "✓ AppLocker policy exported"
}

function Collect-BlockedEvents {
    Write-Host "Collecting blocked application events (last 30 days)..."

    try {
        $blocks = Get-WinEvent -FilterHashtable @{
            LogName='Microsoft-Windows-AppLocker/EXE and DLL';
            ID=8004,8007;
            StartTime=(Get-Date).AddDays(-30)
        } -MaxEvents 10000 -ErrorAction Stop

        $blocks | Select-Object TimeCreated, Id, Message, MachineName, UserId |
            Export-Csv "$OutputDir/applocker-blocks-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

        Write-Host "✓ Found $($blocks.Count) blocked events"
    }
    catch {
        Write-Host "⚠️  No AppLocker block events found (normal if no blocks occurred)"
    }
}

function Test-CentralLogging {
    Write-Host "Testing centralized logging configuration..."

    # Check if Windows Event Forwarding is configured
    $wef = Get-WinEvent -ListLog "ForwardedEvents" -ErrorAction SilentlyContinue

    if ($wef) {
        [PSCustomObject]@{
            CentralLoggingConfigured = $true
            LogName = $wef.LogName
            RecordCount = $wef.RecordCount
            MaximumSizeInBytes = $wef.MaximumSizeInBytes
            RetentionDays = [math]::Round($wef.MaximumSizeInBytes / 100KB / 365, 0) # rough estimate
        } | Export-Csv "$OutputDir/central-logging-status-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

        Write-Host "✓ Centralized logging configured (WEF)"
    }
    else {
        Write-Host "⚠️  Windows Event Forwarding not detected (check SIEM instead)"
    }
}

function Measure-RuleTypes {
    Write-Host "Analyzing rule types (hash vs path vs publisher)..."

    $policy = Get-AppLockerPolicy -Effective

    $stats = @{
        HashRules = 0
        PublisherRules = 0
        PathRules = 0
    }

    foreach ($collection in $policy.RuleCollections) {
        foreach ($rule in $collection.Rules) {
            switch ($rule.GetType().Name) {
                "FileHashRule" { $stats.HashRules++ }
                "FilePublisherRule" { $stats.PublisherRules++ }
                "FilePathRule" { $stats.PathRules++ }
            }
        }
    }

    $total = $stats.HashRules + $stats.PublisherRules + $stats.PathRules
    $hashPercent = if ($total -gt 0) { [math]::Round($stats.HashRules / $total * 100, 1) } else { 0 }

    [PSCustomObject]@{
        HashRules = $stats.HashRules
        PublisherRules = $stats.PublisherRules
        PathRules = $stats.PathRules
        TotalRules = $total
        HashPercentage = $hashPercent
        ML3Compliant = ($hashPercent -ge 80)
        Date = Get-Date -Format "yyyy-MM-dd"
    } | Export-Csv "$OutputDir/rule-type-analysis-$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation

    Write-Host "✓ Rule analysis: $hashPercent% hash-based (ML3 requires ≥80%)"

    if ($hashPercent -lt 80) {
        Write-Host "⚠️  WARNING: Hash rules below 80% - not ML3 compliant"
    }
}

function Generate-MaturityReport {
    Write-Host "`nGenerating maturity level assessment..."

    # Assess current maturity
    $ml1 = $true  # If we got this far, AppLocker is configured
    $ml2 = $false # Need server coverage check
    $ml3 = $false # Need 6-month validation + central logging + hash rules

    # Read rule analysis
    $ruleAnalysis = Import-Csv "$OutputDir/rule-type-analysis-$(Get-Date -Format 'yyyyMMdd').csv"
    $hashCompliant = [bool]$ruleAnalysis.ML3Compliant

    # Read central logging status
    $centralLogging = Test-Path "$OutputDir/central-logging-status-*.csv"

    # Simple maturity assessment
    if ($hashCompliant -and $centralLogging) {
        $ml3 = $true
        $ml2 = $true
    }
    elseif ($hashCompliant -or $centralLogging) {
        $ml2 = $true
    }

    $report = @"
Essential Eight - Application Control Maturity Assessment
Generated: $(Get-Date -Format "yyyy-MM-dd HH:mm:ss")

MATURITY LEVEL ASSESSMENT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ML1 (Baseline):      $($ml1 ? '✓ ACHIEVED' : '✗ NOT ACHIEVED')
ML2 (Improved):      $($ml2 ? '✓ ACHIEVED' : '✗ NOT ACHIEVED')
ML3 (Advanced):      $($ml3 ? '✓ ACHIEVED' : '⚠️  PARTIAL (manual review required)')

EVIDENCE COLLECTED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ AppLocker policy configuration
✓ Blocked event logs (30 days)
✓ Rule type analysis (hash/publisher/path)
$(if ($centralLogging) { '✓ Centralized logging configuration' } else { '⚠️  Centralized logging NOT detected' })

MANUAL EVIDENCE REQUIRED FOR ML3
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
□ Semi-annual validation report (last 6 months)
□ Exception request samples (25 from last 6 months)
□ Incident response process documentation
□ Internet-facing server coverage assessment
□ Endpoint coverage report (should be 100%)

NEXT ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
$(if (-not $hashCompliant) { '□ Migrate path/publisher rules to hash-based rules (target: ≥80%)' })
$(if (-not $centralLogging) { '□ Configure centralized logging (WEF or SIEM)' })
□ Schedule next semi-annual validation review
□ Review exception requests from last 6 months

Evidence Location: $OutputDir
Retention: 18 months (ACSC recommendation)
"@

    $report | Out-File "$OutputDir/maturity-assessment-$(Get-Date -Format 'yyyyMMdd').txt"
    Write-Host $report
}

# Main execution
Write-Host "Essential Eight - Application Control Evidence Collection"
Write-Host "=" * 70

Collect-AppLockerPolicy
Collect-BlockedEvents
Test-CentralLogging
Measure-RuleTypes
Generate-MaturityReport

Write-Host "`n✓ Evidence collection complete"
Write-Host "Evidence saved to: $OutputDir"

ACSC Guidance: Essential Eight Maturity Model (June 2024) Target Maturity: ML3 (Advanced) - Recommended by ACSC Implementation Priority: 🔴 CRITICAL (Australian Government & Critical Infrastructure) Typical Timeline: 4-6 months (ML0 → ML3)

Maturity Level Selection

Helps determine the appropriate Essential 8 maturity level target based on organizational risk profile and requirements.

Arguments

  • $1 - Organization type (optional: government, critical-infrastructure, business, small-business)
  • $2 - Risk profile (optional: high, medium, low)

Maturity Level Decision Framework

Maturity Level 1 (Partly Aligned)

Target Organizations:

  • Small businesses with limited resources
  • Low-risk environments
  • Organizations starting cyber security journey
  • Non-critical systems

Threat Protection:

  • Basic protection against commodity malware
  • Prevents common attack techniques
  • Reduces likelihood of successful ransomware

Characteristics:

  • Entry-level security posture
  • Foundation for further maturity
  • Cost-effective baseline controls
  • Minimal operational impact

Implementation Time: 3-6 months typically


Maturity Level 2 (Mostly Aligned)

Target Organizations:

  • Medium-sized businesses
  • Organizations with moderate risk
  • State/local government agencies
  • Non-critical infrastructure
  • Most commercial entities

Threat Protection:

  • Protection against sophisticated adversaries
  • Prevents most targeted attacks
  • Reduces impact of advanced persistent threats (APTs)
  • Strong ransomware defense

Characteristics:

  • Balanced security vs usability
  • Industry-standard practices
  • Recommended for most organizations
  • Reasonable operational overhead

Implementation Time: 6-12 months typically


Maturity Level 3 (Fully Aligned)

Target Organizations:

  • Federal/state government (mandatory for many)
  • Critical infrastructure operators
  • Defense contractors
  • High-value targets
  • Organizations with sensitive data
  • Financial services, healthcare (high-risk)

Threat Protection:

  • Maximum protection against advanced adversaries
  • Nation-state actor resilience
  • Prevents zero-day exploitation
  • Comprehensive incident recovery

Characteristics:

  • Highest security posture
  • Significant operational controls
  • Substantial resources required
  • Continuous monitoring and validation

Implementation Time: 12-24 months typically


Australian Government Requirements

Mandatory Requirements

Non-corporate Commonwealth Entities (NCEs):

  • Must implement Essential Eight at Maturity Level 3
  • Annual self-assessment required
  • Report to Attorney-General's Department

Corporate Commonwealth Entities (CCEs):

  • Must implement Essential Eight (level varies)
  • Based on risk assessment
  • Report through governance processes

State/Territory Government:

  • Requirements vary by jurisdiction
  • Many mandate ML2 or ML3
  • Check specific state policies

Critical Infrastructure:

  • Security of Critical Infrastructure (SOCI) Act 2018
  • Enhanced cyber security obligations
  • Typically require ML2 or ML3

Risk-Based Selection Criteria

High-Risk Organizations (Target ML3)

  • Handle classified information
  • Critical infrastructure sectors (energy, water, healthcare, finance, transport)
  • High-profile targets (political, media)
  • Defense Industrial Base
  • Personal information at scale
  • National security implications

Medium-Risk Organizations (Target ML2)

  • Business-critical systems
  • Customer data processing
  • Regulatory compliance requirements
  • Professional services
  • Supply chain to government
  • Revenue >$100M

Low-Risk Organizations (Target ML1)

  • Non-critical business functions
  • Minimal data sensitivity
  • Small business (<50 employees)
  • Limited attack surface
  • Starting security maturity journey

Implementation Cost Considerations

Maturity Level 1

  • Tools/Technology: $10K-$50K
  • Consulting/Labor: $25K-$75K
  • Ongoing: $10K-$30K/year
  • Total Initial: $35K-$125K

Maturity Level 2

  • Tools/Technology: $50K-$150K
  • Consulting/Labor: $75K-$200K
  • Ongoing: $30K-$100K/year
  • Total Initial: $125K-$350K

Maturity Level 3

  • Tools/Technology: $150K-$500K
  • Consulting/Labor: $200K-$500K+
  • Ongoing: $100K-$300K/year
  • Total Initial: $350K-$1M+

Costs vary significantly by organization size and current maturity


Progressive Implementation Approach

Recommended Path: ML1 → ML2 → ML3

  1. Phase 1: Achieve ML1 (Months 1-6)

    • Establish baseline controls
    • Quick wins and risk reduction
    • Build security team capability
  2. Phase 2: Progress to ML2 (Months 7-12)

    • Enhance existing controls
    • Implement advanced features
    • Improve automation
  3. Phase 3: Advance to ML3 (Months 13-24)

    • Harden all controls
    • Implement phishing-resistant MFA
    • Comprehensive testing and validation

Benefits:

  • Manageable resource requirements
  • Early risk reduction
  • Staff capability development
  • Budget spreading across fiscal years

Decision Tree

Do you handle classified information or operate critical infrastructure?
├─ YES → Target ML3
└─ NO → Continue

Are you a Commonwealth government entity?
├─ YES → ML3 (NCE) or ML2+ (CCE)
└─ NO → Continue

Are you a high-profile target or handle sensitive data at scale?
├─ YES → Target ML3
└─ NO → Continue

Do you have regulatory compliance requirements or business-critical systems?
├─ YES → Target ML2
└─ NO → Continue

Are you a small business or just starting cyber security journey?
├─ YES → Start with ML1, plan progression
└─ NO → Target ML2 as baseline

Examples

# Determine level for government agency
/essential8:maturity-level government high

# Assess appropriate level for small business
/essential8:maturity-level small-business low

# Critical infrastructure guidance
/essential8:maturity-level critical-infrastructure high

# General business assessment
/essential8:maturity-level business medium

References

  • ACSC Essential Eight Maturity Model
  • Protective Security Policy Framework (PSPF)
  • Security of Critical Infrastructure (SOCI) Act 2018
  • Attorney-General's Department - Cyber Security

Essential 8 Maturity Roadmap

Creates a prioritized implementation and maturity improvement roadmap for Essential 8 mitigation strategies.

Arguments

  • $1 - Current maturity level (required: 0, 1, or 2)
  • $2 - Target maturity level (required: 1, 2, or 3)
  • $3 - Timeline (optional: aggressive, standard, conservative)

Roadmap Timeline Options

Aggressive (Fast-Track)

  • ML0 → ML1: 3-4 months
  • ML1 → ML2: 4-6 months
  • ML2 → ML3: 6-9 months
  • ML0 → ML3: 15-18 months

Characteristics:

  • Dedicated project team
  • Executive sponsorship
  • Significant budget
  • Consultant support
  • Parallel workstreams

Standard (Recommended)

  • ML0 → ML1: 6-9 months
  • ML1 → ML2: 9-12 months
  • ML2 → ML3: 12-18 months
  • ML0 → ML3: 24-36 months

Characteristics:

  • Balanced resources
  • Phased approach
  • Internal team with targeted consulting
  • Manageable change
  • Budget spread across FY

Conservative (Gradual)

  • ML0 → ML1: 9-12 months
  • ML1 → ML2: 12-18 months
  • ML2 → ML3: 18-24 months
  • ML0 → ML3: 36-48 months

Characteristics:

  • Limited resources
  • Minimal disruption
  • Internal team only
  • Incremental change
  • Budget constraints

Roadmap Structure

Each roadmap includes:

1. Assessment Phase (Weeks 1-4)

  • Current state assessment
  • Gap analysis
  • Resource requirements
  • Budget estimation
  • Stakeholder alignment

2. Planning Phase (Weeks 5-8)

  • Project charter
  • Detailed implementation plan
  • Tool selection
  • Vendor selection (if needed)
  • Communication plan

3. Implementation Phases (By Strategy)

  • Prioritized strategy implementation
  • Testing and validation
  • User training
  • Documentation
  • Rollout

4. Validation Phase

  • Independent assessment
  • Control testing
  • Remediation of findings
  • Certification (if required)

5. Continuous Improvement

  • Ongoing monitoring
  • Annual reassessment
  • Control refinement
  • Maturity progression

Implementation Priority Matrix

Priority 1 (Immediate) - Foundational Controls

Weeks 1-12:

  1. Multi-Factor Authentication (Strategy 7)

    • Highest ROI
    • Prevents majority of attacks
    • Relatively easy to implement
    • User training required
  2. Regular Backups (Strategy 8)

    • Critical for recovery
    • Protects against ransomware
    • Can be implemented quickly
    • Test restoration immediately
  3. Restrict Administrative Privileges (Strategy 5)

    • Limits lateral movement
    • Prevents privilege escalation
    • Policy-based implementation
    • Significant security improvement

Priority 2 (Quick Wins) - Risk Reduction

Weeks 13-24:

  1. User Application Hardening (Strategy 4)

    • Reduces attack surface
    • Group Policy deployment
    • Low operational impact
    • Fast implementation
  2. Configure Microsoft Office Macro Settings (Strategy 3)

    • Blocks common malware vector
    • Simple configuration
    • Minimal user disruption
    • High threat reduction

Priority 3 (Complex) - Technical Controls

Weeks 25-40:

  1. Application Control (Strategy 1)

    • Most complex to implement
    • Requires extensive testing
    • Application inventory needed
    • Potential user impact
    • Deploy in audit mode first
  2. Patch Applications (Strategy 2)

    • Ongoing process
    • Tool implementation
    • Testing procedures
    • Automation critical
  3. Patch Operating Systems (Strategy 6)

    • Similar to patch applications
    • Leverage existing WSUS/SCCM
    • Testing required
    • Scheduled maintenance windows

Maturity Level 1 Roadmap (0 → 1)

Phase 1: Quick Wins (Months 1-2)

Strategy 7: MFA

  • Deploy MFA for privileged users
  • Implement MFA for remote access
  • Deploy MFA for important data access
  • User enrollment and training

Strategy 8: Backups

  • Identify important data
  • Implement daily backup solution
  • Configure offsite/offline storage
  • Test restoration procedures

Strategy 5: Admin Privileges

  • Audit current admin accounts
  • Remove local admin from standard users
  • Create separate admin accounts
  • Implement logging

Phase 2: Configuration Controls (Months 3-4)

Strategy 4: Application Hardening

  • Standardize browser configuration
  • Block Flash, Java
  • Configure PDF security
  • Deploy via Group Policy

Strategy 3: Office Macros

  • Block macros from internet
  • Define Trusted Locations
  • Enable AMSI
  • User education

Phase 3: Patching (Months 5-6)

Strategy 2: Patch Applications

  • Application inventory
  • Vulnerability scanning
  • Patch testing process
  • Deploy critical patches

Strategy 6: Patch OS

  • Enable Windows Update/WSUS
  • Baseline current patch levels
  • Remediate critical vulnerabilities
  • Establish maintenance windows

Phase 4: Application Control (Months 7-9)

Strategy 1: Application Control

  • Application inventory
  • Baseline approved applications
  • Deploy AppLocker/WDAC in audit mode
  • Analyze audit logs
  • Transition to enforcement
  • User support processes

Phase 5: Validation (Month 9+)

  • Strategy-by-strategy testing
  • Gap remediation
  • Documentation finalization
  • Self-assessment
  • Management reporting

Maturity Level 2 Roadmap (1 → 2)

Phase 1: Enhanced MFA (Months 1-2)

Strategy 7: MFA for All Users

  • Roll out MFA to all standard users
  • Implement conditional access
  • Deploy phishing-resistant methods where possible
  • Exception management process

Phase 2: Advanced Backups (Months 2-3)

Strategy 8: Hardened Backups

  • Implement network segmentation
  • Air-gapped/immutable backups
  • Increase testing frequency
  • Backup monitoring

Phase 3: Enhanced Controls (Months 3-6)

Strategy 1: Application Control on Servers

  • Extend to all servers
  • Driver/kernel module control
  • PowerShell Constrained Language Mode
  • Script blocking

Strategy 5: Privileged Access Management

  • Implement PAM solution
  • Just-in-time administration
  • Privileged workstation hardening
  • Session monitoring

Phase 4: Accelerated Patching (Months 6-9)

Strategy 2 & 6: Two-Week Patching

  • Automated patch deployment
  • Faster testing procedures
  • Staged rollout automation
  • Compliance reporting

Phase 5: Centralization (Months 9-12)

  • Central logging (SIEM)
  • Security monitoring
  • Automated compliance checking
  • Continuous improvement

Maturity Level 3 Roadmap (2 → 3)

Phase 1: Phishing-Resistant MFA (Months 1-4)

Strategy 7: FIDO2/Smart Cards

  • Procure FIDO2 security keys
  • Deploy to all users
  • Disable non-phishing-resistant methods
  • Fallback procedures

Phase 2: Advanced Application Control (Months 4-8)

Strategy 1: Hardened Configuration

  • Independent validation
  • Penetration testing
  • Automated compliance checking
  • Continuous monitoring
  • Threat hunting

Phase 3: 48-Hour Patching (Months 8-14)

Strategy 2 & 6: Rapid Patching

  • Fully automated testing
  • Rapid deployment capabilities
  • Real-time vulnerability scanning
  • Rollback automation
  • Zero-day response process

Phase 4: Comprehensive Validation (Months 14-18)

  • Third-party assessment
  • Penetration testing
  • Red team exercises
  • Gap remediation
  • Certification (if required)

Resource Requirements

Maturity Level 1 Implementation

Team:

  • Project Manager (0.5 FTE)
  • Security Engineer (1 FTE)
  • Systems Administrator (0.5 FTE)
  • Training Coordinator (0.25 FTE)

Budget:

  • Tools/Software: $10K-$50K
  • Consulting: $25K-$75K
  • Training: $5K-$15K
  • Hardware (MFA tokens): $5K-$20K
  • Total: $45K-$160K

Maturity Level 2 Implementation

Team:

  • Project Manager (1 FTE)
  • Security Engineers (2 FTE)
  • Systems Administrator (1 FTE)
  • Training Coordinator (0.5 FTE)

Budget:

  • Tools/Software: $50K-$150K
  • Consulting: $75K-$200K
  • Training: $15K-$40K
  • Hardware: $20K-$60K
  • Total: $160K-$450K

Maturity Level 3 Implementation

Team:

  • Project Manager (1 FTE)
  • Security Engineers (3 FTE)
  • Systems Administrators (2 FTE)
  • Compliance Analyst (1 FTE)
  • Training Coordinator (0.5 FTE)

Budget:

  • Tools/Software: $150K-$500K
  • Consulting: $200K-$500K
  • Assessment/Testing: $50K-$150K
  • Training: $30K-$80K
  • Hardware: $50K-$150K
  • Total: $480K-$1.38M

Success Metrics

Technical Metrics

  • % systems with application control enabled
  • Average patch deployment time
  • % users with MFA enabled
  • % privileged accounts separated
  • Backup success rate
  • Configuration compliance score

Security Metrics

  • Reduction in malware incidents
  • Failed attack attempts blocked
  • Mean time to patch (MTTP)
  • Unauthorized access attempts
  • Successful backup restorations

Business Metrics

  • Cyber insurance premium reduction
  • Compliance posture improvement
  • Customer confidence increase
  • Audit findings reduction
  • Recovery time objective (RTO) improvement

Common Challenges and Mitigations

Challenge 1: User Resistance

Mitigation:

  • Executive communication
  • User training and awareness
  • Gradual rollout
  • Help desk support
  • Feedback mechanisms

Challenge 2: Legacy Applications

Mitigation:

  • Application inventory and assessment
  • Remediation or retirement plan
  • Compensating controls
  • Exceptions with risk acceptance

Challenge 3: Resource Constraints

Mitigation:

  • Phased approach
  • Leverage automation
  • Managed service providers
  • Open-source tools where appropriate
  • Budget across fiscal years

Challenge 4: Technical Complexity

Mitigation:

  • Consultant expertise
  • Vendor professional services
  • Pilot testing
  • Documentation
  • Knowledge transfer

Challenge 5: Operational Impact

Mitigation:

  • Change management process
  • Maintenance windows
  • Rollback procedures
  • Stakeholder communication
  • Incident response planning

Governance and Reporting

Monthly Reporting

  • Implementation progress by strategy
  • Budget vs actual
  • Issue log and risk register
  • Upcoming milestones
  • Stakeholder updates

Quarterly Reviews

  • Maturity assessment
  • Control effectiveness testing
  • Roadmap adjustments
  • Budget forecast
  • Executive briefing

Annual Assessment

  • Full Essential 8 assessment
  • Maturity level validation
  • Continuous improvement plan
  • Budget for next fiscal year
  • Compliance reporting (if required)

Examples

# Standard roadmap from nothing to ML1
/essential8:roadmap 0 1 standard

# Aggressive progression from ML1 to ML3
/essential8:roadmap 1 3 aggressive

# Conservative improvement from ML2 to ML3
/essential8:roadmap 2 3 conservative

# Default (standard) timeline from current state to ML2
/essential8:roadmap 1 2

References

  • ACSC Essential Eight Maturity Model
  • Essential Eight Assessment Process Guide
  • ACSC Implementation Guidance
  • Case Studies and Lessons Learned

Strategy Implementation Check

Provides detailed implementation guidance and verification for a specific Essential 8 mitigation strategy.

Arguments

  • $1 - Strategy number (required: 1-8) or name
  • $2 - Target maturity level (optional: 1, 2, or 3)

Strategy Selection

1. Application Control

Prevent execution of unapproved/malicious programs

2. Patch Applications

Remediate security vulnerabilities in applications

3. Configure Microsoft Office Macro Settings

Prevent malicious macros from executing

4. User Application Hardening

Reduce attack surface of internet-facing applications

5. Restrict Administrative Privileges

Prevent privilege escalation and lateral movement

6. Patch Operating Systems

Remediate security vulnerabilities in operating systems

7. Multi-Factor Authentication

Prevent unauthorized access using stolen credentials

8. Regular Backups

Recover data and system availability after incidents


Strategy 1: Application Control

Maturity Level 1

Requirements:

  • Application control implemented on all workstations
  • Allowed/blocked execution rules in place
  • Microsoft's recommended block rules applied
  • Application control events logged

Implementation Steps:

  1. Choose application control solution (AppLocker, Windows Defender Application Control)
  2. Create baseline of approved applications
  3. Configure publisher certificate rules
  4. Implement path rules for authorized locations
  5. Block execution from user-writable directories
  6. Deploy to all workstations
  7. Enable audit mode first, then enforcement
  8. Log all blocked execution attempts

Validation:

  • Test unapproved application execution (should block)
  • Verify approved applications run normally
  • Check event logs for blocked attempts

Maturity Level 2

Additional Requirements:

  • Application control on all servers
  • Drivers/kernel modules controlled
  • PowerShell, command line, scripts controlled
  • Application control events centrally logged

Implementation Steps:

  1. Extend controls to all servers
  2. Implement driver signature requirements
  3. Configure PowerShell Constrained Language Mode
  4. Block scripting languages (unless required)
  5. Central log collection (SIEM)
  6. Regular rule review and updates

Validation:

  • Test script execution blocking
  • Verify driver installation controls
  • Confirm central logging operational

Maturity Level 3

Additional Requirements:

  • Validation of application control configuration
  • Application control event analysis
  • Extremely hardened configuration
  • Annual penetration testing

Implementation Steps:

  1. Independent validation of implementation
  2. Implement automated rule compliance checking
  3. Continuous monitoring and alerting
  4. Threat hunting using control events
  5. Penetration testing of bypass techniques
  6. Annual recertification

Validation:

  • Third-party assessment of controls
  • Penetration test with bypass attempts
  • Red team exercises

Strategy 2: Patch Applications

Maturity Level 1

Requirements:

  • Security vulnerabilities in applications patched within one month of release
  • Extreme risk vulnerabilities patched within 48 hours
  • Patches applied to internet-facing applications first

Implementation Steps:

  1. Maintain inventory of all applications
  2. Subscribe to vendor security advisories
  3. Assess vulnerability severity (use CVSS)
  4. Prioritize internet-facing and critical apps
  5. Test patches in non-production environment
  6. Deploy patches according to timeline
  7. Verify successful installation
  8. Document patching activities

Extreme Risk Definition:

  • CVSS 9.0-10.0
  • Actively exploited in the wild
  • No mitigating controls available
  • Critical asset exposure

Validation:

  • Scan for unpatched vulnerabilities
  • Review patching logs
  • Verify 48-hour extreme risk compliance

Maturity Level 2

Additional Requirements:

  • Vulnerabilities patched within two weeks of release
  • Extreme risk still 48 hours
  • Automated patch deployment where possible

Implementation Steps:

  1. Implement automated patching tools
  2. Accelerate testing procedures
  3. Staged deployment approach
  4. Enhanced monitoring for patch failures
  5. Metrics tracking and reporting

Maturity Level 3

Additional Requirements:

  • All vulnerabilities patched within 48 hours
  • Automated deployment and verification
  • Comprehensive patch management process

Implementation Steps:

  1. Fully automated patch testing
  2. Rapid deployment capabilities
  3. Rollback procedures tested
  4. Continuous vulnerability scanning
  5. Real-time patch compliance dashboards

Strategy 3: Configure Microsoft Office Macro Settings

Maturity Level 1

Requirements:

  • Macros disabled for files from the internet
  • Macro antivirus scanning enabled
  • Only macros in Trusted Locations allowed to run
  • Block OLE package activation

Implementation Steps:

  1. Configure Group Policy for Office macro settings
  2. Enable "Block macros from the internet"
  3. Define Trusted Locations (limited, IT-controlled)
  4. Enable AMSI (Antimalware Scan Interface)
  5. Block embedded OLE packages
  6. Educate users on macro risks
  7. Monitor macro execution events

Validation:

  • Test internet-sourced Office files (macros should not run)
  • Verify Trusted Location macros work
  • Check Group Policy application

Maturity Level 2

Additional Requirements:

  • Only macros from Trusted Locations with validation
  • AMSI enabled for all Office applications
  • Logging of all macro execution attempts

Maturity Level 3

Additional Requirements:

  • Validated macro execution only
  • Digital signature requirements
  • Comprehensive monitoring and alerting

Strategy 4: User Application Hardening

Maturity Level 1

Requirements:

  • Web browsers: Block Flash content, block or disable ads, disable Java
  • Office: Disable add-ins except as required
  • PDF readers: Disable JavaScript, embedded content

Implementation Steps:

  1. Standardize on supported browser (Edge, Chrome)
  2. Deploy hardening settings via Group Policy/MDM
  3. Block Adobe Flash (deprecated)
  4. Install ad-blocking extensions (enterprise)
  5. Disable Java browser plugins
  6. Configure PDF reader security settings
  7. Remove unnecessary Office add-ins

Validation:

  • Test Flash content blocking
  • Verify Java disabled
  • Check PDF JavaScript execution

Maturity Level 2

Additional Requirements:

  • Block web-based Java execution
  • Disable all unnecessary features
  • Centrally managed configuration

Maturity Level 3

Additional Requirements:

  • Validated hardened configuration
  • Regular recertification
  • Advanced exploit protections enabled

Strategy 5: Restrict Administrative Privileges

Maturity Level 1

Requirements:

  • Privileged accounts separate from unprivileged accounts
  • Privileged access disabled by default
  • Standard users not local administrators
  • Privileged account usage logged

Implementation Steps:

  1. Remove local administrator rights from standard users
  2. Create separate admin accounts for IT staff
  3. Implement privileged access workstations (PAWs)
  4. Configure "Run as administrator" prompts
  5. Log all administrative actions
  6. Regular privilege review

Validation:

  • Test standard user cannot install software
  • Verify admin actions are logged
  • Audit privileged account list

Maturity Level 2

Additional Requirements:

  • Privileged accounts only for administrative tasks
  • Privileged OS hardening
  • Privileged access managed and monitored
  • Just-in-time (JIT) administration preferred

Implementation Steps:

  1. Implement Privileged Access Management (PAM) solution
  2. Time-limited admin elevation
  3. Harden privileged workstations
  4. Session recording for admin actions
  5. Multi-person authorization for critical changes

Maturity Level 3

Additional Requirements:

  • Privileged access disabled by default
  • JIT administration required
  • Comprehensive validation and monitoring

Strategy 6: Patch Operating Systems

Maturity Level 1

Requirements:

  • OS vulnerabilities patched within one month
  • Extreme risk vulnerabilities patched within 48 hours
  • Internet-facing systems prioritized

Implementation Steps:

  1. Maintain inventory of all operating systems
  2. Enable automatic Windows Update (or WSUS)
  3. Subscribe to vendor advisories (Microsoft, Linux distros)
  4. Assess vulnerability severity
  5. Test patches before deployment
  6. Deploy according to timeline
  7. Verify installation success

Validation:

  • Run vulnerability scans
  • Check Windows Update compliance
  • Review patching reports

Maturity Level 2

Additional Requirements:

  • Vulnerabilities patched within two weeks
  • Automated patching where possible

Maturity Level 3

Additional Requirements:

  • All vulnerabilities patched within 48 hours
  • Fully automated deployment and verification

Strategy 7: Multi-Factor Authentication

Maturity Level 1

Requirements:

  • MFA for access to important data repositories
  • MFA for all privileged users
  • MFA for all remote access

Implementation Steps:

  1. Identify important data repositories
  2. Deploy MFA solution (Azure AD, Duo, etc.)
  3. Enroll all privileged users
  4. Require MFA for VPN/remote access
  5. Configure conditional access policies
  6. User training on MFA

MFA Methods Accepted:

  • Authenticator apps (Microsoft Authenticator, Google Authenticator)
  • Hardware tokens (YubiKey, RSA)
  • SMS/phone call (less secure, use sparingly)

Validation:

  • Test access without MFA (should fail)
  • Verify all privileged accounts enrolled
  • Check remote access MFA enforcement

Maturity Level 2

Additional Requirements:

  • MFA for all users
  • Phishing-resistant MFA preferred
  • MFA for access to important data by all users

Implementation Steps:

  1. Roll out MFA to all standard users
  2. Implement FIDO2 security keys where possible
  3. Disable legacy authentication protocols
  4. Conditional access based on risk signals
  5. MFA exception tracking and review

Maturity Level 3

Additional Requirements:

  • Phishing-resistant MFA required for all users
  • No exceptions without compensating controls
  • Comprehensive monitoring

Phishing-Resistant MFA:

  • FIDO2 security keys (YubiKey, etc.)
  • Smart cards (PIV, CAC)
  • Windows Hello for Business
  • Certificate-based authentication

Not Phishing-Resistant:

  • SMS codes
  • Voice calls
  • Email codes
  • Push notifications (can be phishing-prone)

Implementation Steps:

  1. Deploy FIDO2 security keys to all users
  2. Disable non-phishing-resistant methods
  3. Implement fallback processes (lost key)
  4. Monitor for MFA bypass attempts

Strategy 8: Regular Backups

Maturity Level 1

Requirements:

  • Backups of important data daily (minimum weekly)
  • Retention: at least 3 months
  • Backups tested for restoration quarterly
  • Backups stored offline or offsite

Implementation Steps:

  1. Identify important data to back up
  2. Implement backup solution (Veeam, Azure Backup, etc.)
  3. Configure daily backup schedule
  4. Store backups offline or in separate environment
  5. Test restoration quarterly
  6. Document backup/recovery procedures
  7. Retain backups for 3+ months

3-2-1 Backup Rule:

  • 3 copies of data
  • 2 different media types
  • 1 copy offsite/offline

Validation:

  • Perform test restoration
  • Verify backup completion logs
  • Confirm offline/offsite storage

Maturity Level 2

Additional Requirements:

  • Backups disconnected from network (air-gapped)
  • Backup processes improved
  • More frequent testing

Implementation Steps:

  1. Implement immutable backups
  2. Network segmentation for backup infrastructure
  3. Privileged access controls for backup systems
  4. Monthly restoration testing
  5. Backup integrity monitoring

Maturity Level 3

Additional Requirements:

  • Hardened backup infrastructure
  • Comprehensive testing (full disaster recovery)
  • Automated validation

Implementation Steps:

  1. Fully hardened backup environment
  2. Automated backup verification
  3. Quarterly full disaster recovery test
  4. Backup infrastructure monitoring
  5. Incident response integration

Examples

# Check Application Control implementation at ML2
/essential8:strategy-check 1 2

# Verify MFA strategy at ML3
/essential8:strategy-check "Multi-Factor Authentication" 3

# Assess Patch Applications maturity
/essential8:strategy-check 2

# Review Regular Backups implementation
/essential8:strategy-check 8 1

Common Pitfalls

  1. Application Control: Allowing execution from user-writable locations
  2. Patching: Not treating extreme risk as truly urgent (48 hours)
  3. Office Macros: Trusting macros from email attachments
  4. Hardening: Not keeping pace with application updates
  5. Admin Privileges: Shared admin accounts, no logging
  6. OS Patching: Skipping testing, causing production issues
  7. MFA: SMS-based MFA at ML3 (not phishing-resistant)
  8. Backups: Not testing restoration, backups accessible to malware

References

  • ACSC Essential Eight Maturity Model
  • Strategies to Mitigate Cyber Security Incidents
  • ACSC Publications Library

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/essential8
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70