
ASD Essentials for enterprise IT actions
ASD Essentials for enterprise IT: 58 actions under 28 principles, applied across 8 domains, with technical domains sequenced in 3 priority phases.
Reviewed 16 October 2026 · Current to ASD Essentials for enterprise IT, October 2026 · 58 actions across 28 principles
At a glance
- Published by
- Australian Signals Directorate (ASD)
- Who it applies to
- Enterprise IT environments. ASD publishes separate chapters for cloud services and for operational technology.
- Structure
- 58 actions under 28 principles in 5 functions, applied across 8 domains.
- Where to start
- Start with the Phase 1 domains, Boundary services and Identity services. ASD's phases order the domains, not the actions.What's in each domain?
How it is structured
- 5functions
- 28principles
- 58actions
- 8domains
Actions per function
- Govern8
- Identify3
- Protect34
- Detect9
- Respond4
Actions by principle
Every action in ASD's order, grouped by function and principle. ASD recommends working through the domains phase by phase: choose a domain to see the actions that apply to it.
What's in each domain?
ASD places an asset by the role it performs, not by who owns or runs it, and an asset belongs in every domain that describes it. Include development, testing and staging environments too.
- Boundary services “Does it broker connectivity or data flows across a boundary between environments?”
- Identity services “Does it anchor decisions about who and what to trust through authentication, authorisation or identity lifecycle functions?”
- Critical processes and services “Does it directly deliver a primary organisational outcome or contribute to the health or safety of personnel or the community?”
- Privileged environments “Does it enable, broker or govern elevated control over other systems?”
- Business systems “Does it support day-to-day operations without being individually critical?”
- User devices “Does it provide the general workforce with direct access to the environment?”
- Governance and culture includes cyber security strategies, policies and procedures, awareness and training programs, security roadmaps and risk registers.
- Visibility and response includes asset registers, incident response plans and procedures, and detection and response platforms.
Quoted as published in ASD's Implementation planning guide.
Showing all 58 actions
Govern
- IT.GOV-01.1Formalise Executive and Board Accountability for Cyber Security and Risk Appetite
Defines and regularly reviews formal executive and board accountability for cyber security, including setting, monitoring and adjusting how much risk to accept.
Domains:Governance and culture
- IT.GOV-08.1Name an Executive Accountable for AI Use, Governance and Risk Management
Gives a named executive ongoing accountability for how the organisation uses, governs and manages the risks of artificial intelligence (AI).
Domains:Governance and culture
- IT.GOV-04.1Assign Sufficient Skilled Personnel to Run Security Controls and Define Role Responsibilities
Assigns enough skilled staff and resources to introduce, run, watch, maintain and retire security controls, and writes security duties into role descriptions.
Domains:Governance and culture - IT.GOV-04.2Periodically Review Cyber Security Resourcing Against Threat Trends, Incidents and Organisational Change
Checks on a set cycle that security staff, skills, tools and funding still match threat trends, lessons from incidents and organisational changes.
Domains:Governance and culture
- IT.GOV-03.1Assess and Treat Cyber Security Risks Using an Approved Methodology and Plan
Maintains an approved method and plan, and uses them to rate each cyber security risk, choose a response and carry it out.
Domains:Governance and culture
- IT.GOV-11.1Base Supplier Selection on Proportionate Cyber Supply Chain Risk Assessments
Checks each supplier's cyber security risk before taking them on, looks harder at riskier suppliers, and keeps evidence supporting the decision.
Domains:Governance and culture - IT.GOV-11.2Maintain Current Supplier Assurance and Act on Lapses or Risk Changes
Keeps up-to-date proof that suppliers still meet their security promises, and acts when that proof lapses or a supplier's risk changes.
Domains:Governance and culture
- IT.GOV-14.1Identify, Assess and Treat Legacy System Risks Until Removal or Replacement
Finds old and unsupported technology, judges its risk, and adds extra safeguards, closer monitoring and checks until it is removed or replaced.
Domains:Governance and culture
Identify
- IT.IDE-01.1Use an Approved Inventory with Automated Discovery of New and Changed Assets
Uses an approved inventory tool that automatically discovers new and changed assets, physical and non-physical, such as devices, software and cloud services.
Domains:Visibility and response - IT.IDE-01.2Keep Current Records of Infrastructure, Software, Identities, Credentials and Data
Keeps current, accurate records of infrastructure, operating systems, applications, user and system accounts, credentials (such as keys and certificates) and data.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.IDE-04.1Feed Continuously Reviewed Threat Intelligence and Weaknesses into Risk Assessments
Factors the weak spots, attacker methods and behaviours relevant to the organisation into every risk assessment, and reviews them continually.
Domains:Visibility and response
Protect
- IT.PRO-01.1Design Systems with Telemetry, Least Privilege, Data Protection and Minimal Attack Surface
Designs systems securely so they log security events by default, enforce authorised access, protect data, and keep privileges, services and features minimal.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-01.2Use Secure Build and Deployment Processes to Enforce Security Controls Consistently
Builds, deploys and changes systems through secure, controlled processes with testing and approval, so security controls are applied consistently across systems.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.PRO-16.1Verify Integrity, Authenticity and Provenance of Software, Components and Updates Before Use
Confirms software, components and updates are genuine and unchanged before use, and checks where they came from when suppliers give proof.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-16.2Monitor Vendor Advisories and Threat Intelligence to Act on Supply Chain Exposure
Watches vendor warnings and threat reports for suppliers, products or components exposed to compromise, and acts as fast as the risk requires.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments
- IT.PRO-13.1Regularly Find and Disable or Remove Default and Unused Accounts
Finds and switches off or deletes built-in and unused accounts regularly, keeping any only if documented, justified, locked down and monitored.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-13.2Store Keys, Secrets and Tokens in Approved, Access-Controlled Repositories with MFA
Keeps passwords, keys, tokens and other secrets in an approved secure store, with tight access controls and multi-factor sign-in.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems - IT.PRO-13.3Run Regular Secret Scanning and Rotate or Revoke Exposed Credentials
Scans code, settings files, shared drives and collaboration tools regularly for exposed passwords, keys and other secrets, then changes or cancels them.
Domains:Visibility and response - IT.PRO-13.4Enforce Phishing-Resistant MFA for All User Authentication, Including from Untrusted Locations
Requires users to sign in to systems with multi-factor authentication that fake sites cannot trick, including from untrusted, external or high-risk locations.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-13.5Disable Legacy Authentication Protocols and Restrict, Monitor and Decommission Exceptions
Switches off older, weaker sign-in methods, and puts limits, monitoring, extra safeguards and a removal date on any that must stay.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-13.6Enforce Unique Credentials per System and Account, Especially in High-Privilege Contexts
Gives every account its own password or key on each system, never shared or reused, especially for accounts with admin rights.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.PRO-12.1Periodically Review and Update Access Privileges to Match Current Roles and Duties
Reviews each account's access on a set cycle and updates it to match current roles, duties and business needs.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-12.2Restrict Account and Role Management and Privileged Functions to Authorised Administrative Roles
Lets only authorised admin roles create, change or delete accounts and roles, or use admin functions and applications.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments - IT.PRO-12.3Provision User, Administrative and Non-Person Accounts with Minimum Required Privileges
Gives every account, whether used by staff, admins, apps or systems, only the minimum access its defined tasks need.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments
- IT.PRO-05.1Restrict Administration to Dedicated, Hardened Environments Isolated from Unprivileged User Workloads
Restricts admin work to dedicated, locked-down computers or environments kept apart from everyday email, web browsing and other user tasks.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments - IT.PRO-05.2Require Explicit Session Establishment and Time-Bound Grants for Privileged Actions
Switches on admin access only when needed, after a fresh identity check, and switches it off automatically after a set time.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments - IT.PRO-05.3Log Every Administrative and Management Change with User, Timestamp and Target
Records every admin or management change to systems, settings and security controls, showing who made it, when and what it changed.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments
- IT.PRO-04.1Define Approved Hardening Baselines Disabling Unneeded Services, Insecure Settings and Weak Protocols
Defines approved settings per system type that switch off unneeded services, risky options and weak protocols, based on vendor and industry advice.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-04.2Deploy Approved Configuration Baselines to All Infrastructure, Operating Systems and Applications
Puts the approved secure settings on every system, including infrastructure, operating systems and applications, and confirms this with technical checks.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-04.3Detect and Remediate Configuration Drift Using Scheduled Assessments and Automated Monitoring
Finds and fixes drift from approved settings with scheduled checks and, where supported, automated monitoring, checking critical or fast-changing systems more often.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.PRO-06.1Continuously Scan and Assess Assets for Known Software and Configuration Weaknesses
Finds known software flaws and weak settings on all systems through ongoing, repeatable checks, including vulnerability scans and reviews of security advisories.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-06.2Apply Security Patches Within Risk-Based Timeframes and Automate Low-Impact Updates
Applies security patches and updates within set deadlines based on risk, or automatically where the impact on operations is low.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-06.3Remediate or Mitigate Above-Threshold Vulnerabilities Within Defined Timeframes and Verify Effectiveness
Fixes security weaknesses rated above the organisation's risk limit, or adds safeguards, by risk-based deadlines, then checks the risk really dropped.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.PRO-07.1Restrict Execution to Supported, Verified and Authorised Software with Time-Bound Exceptions
Lets only supported, checked and approved software run on systems, keeping exceptions rare, signed off, time-limited, watched and regularly reviewed.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.PRO-07.2Restrict Administrative and Management Tools to Approved Sets and Authorised Locations
Lets only approved admin and management tools run, and only from authorised places such as a dedicated admin computer or protected folder.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices)
- IT.PRO-10.1Back Up Data, Applications and Settings on Schedule to Encrypted, Resilient Storage
Backs up important data, apps and settings on a set schedule to encrypted storage that attackers cannot change or delete.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems - IT.PRO-10.2Isolate Backup Repositories from General User Environments and Production Workloads
Keeps backups separate from staff computers and live systems, so anyone who breaks into those cannot reach, change or delete them.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems - IT.PRO-10.3Regularly Test Backup and Restoration Procedures Against Defined Recovery Objectives
Tests backups and restore steps regularly to prove backups work and can meet defined targets for downtime and data loss.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems
- IT.PRO-18.1Isolate Systems in Criticality- and Trust-Based Network Zones with Approved, Monitored Pathways
Isolates systems in network zones by importance and trust, and watches traffic in and out, allowing only explicitly approved routes and services.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems - IT.PRO-18.2Restrict Lateral Movement Between and Within Segments to Approved Pathways and Services
Limits connections between and within network segments to explicitly approved routes and services matching business need and trust, stopping intruders roaming freely.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems
- IT.PRO-09.1Inspect Outbound Content on Egress Paths to Detect Unauthorised Data Transfers
Checks what leaves the organisation, by email, web upload or other routes, to spot sensitive or high-value data sent without approval.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environmentsBusiness systems - IT.PRO-09.2Block Outbound Connections to Known Malicious and Untrusted Destinations Using Threat Intelligence
Blocks systems from connecting out to websites and servers known to be dangerous or untrusted.
Domains:Boundary servicesCritical processes and services - IT.PRO-09.3Inspect All Inbound Content Channels and Block Malicious or Unsafe Content
Checks content coming in from outside or untrusted sources, and stops anything harmful before it is delivered.
Domains:Boundary servicesCritical processes and services
- IT.PRO-14.1Require Role-Tailored Cyber Security Awareness Training Before Granting Access
Gives everyone cyber security training suited to their role before they get access to the organisation's systems and data.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments - IT.PRO-14.2Regularly Update and Deliver Security Awareness Training as Threats and Operations Change
Keeps cyber security training up to date with current threats and how people work, and keeps everyone trained.
Domains:Governance and culture
Detect
- IT.DET-01.1Encrypt Event Logs and Restrict Access to Prevent Tampering and Deletion
Keeps event logs safe from being read, changed or deleted without approval, with encryption and locked-down logging systems and accounts.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.DET-01.2Forward High-Value Security Logs and Configuration Changes to Central Log Storage
Sends key security logs and setting changes from network gear, servers, computers and apps to one central store.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.DET-01.3Establish Centralised Event Log Storage Protected from Unauthorised Access and Tampering
Keeps event logs in one central store only approved staff can open and no one can tamper with.
Domains:Visibility and response
- IT.DET-04.1Continuously Monitor Software Execution to Detect Malicious Use of Legitimate Tools
Keeps watching and analysing how software runs on systems, to catch attackers misusing legitimate tools and utilities, such as built-in admin tools.
Domains:Boundary servicesIdentity servicesCritical processes and servicesPrivileged environments
- IT.DET-02.1Normalise, Time-Synchronise and Enrich Event Logs for Cross-System Correlation
Puts logs in one format and on one trusted clock, adding details like account type, so events can be matched across systems.
Domains:All six technical domains (Boundary services, Identity services, Critical processes and services, Privileged environments, Business systems, User devices) - IT.DET-02.2Deploy Detection Rules for Unauthorised Changes, Anomalous Authentication and Suspicious Software Execution
Sets rules to alert on unapproved changes, odd sign-ins and suspicious programs, and keeps them tested and tuned.
Domains:Visibility and response
- IT.DET-03.1Triage Alerts and Events Promptly Against Defined Incident Thresholds
Checks each security alert and event quickly to decide whether it meets the organisation's threshold for a cyber security incident.
Domains:Visibility and response - IT.DET-03.2Correlate Signals Across Identities, Applications, Data and Infrastructure to Identify Incidents
Spots cyber security incidents by linking clues from accounts, apps, data and systems, rather than relying on one alert alone.
Domains:Visibility and response
- IT.DET-05.1Periodically Review Detection Coverage for Gaps as Assets, Services and Architecture Change
Reviews security monitoring coverage regularly to find blind spots left by new systems, new services or changes to system design.
Domains:Visibility and response
Respond
- IT.RES-05.1Build External Reporting and Coordination Obligations into Incident Response Procedures
Builds every duty to tell or work with outside parties into the steps people follow in an incident.
Domains:Visibility and response
- IT.RES-03.1Respond to Cyber Security Incidents Using Documented, Tested and Approved Procedures
Handles incidents with written, tested and approved response procedures, rather than steps made up under pressure.
Domains:Visibility and response
- IT.RES-04.1Perform Post-Incident Reviews to Identify Security Gaps Behind Each Incident Stage
Reviews each incident that meets the organisation's severity threshold to find the security gaps that let each stage of the incident happen.
Domains:Visibility and response - IT.RES-04.2Evaluate Monitoring Coverage and Response Procedures After Incidents and Validate Improvements
Checks monitoring coverage and incident response procedures after each incident, and improves them where they fell short.
Domains:Visibility and response

No action in that domain yet
No published action applies in that domain yet.
Guides and tools
Frequently asked questions
What is ASD Essentials for enterprise IT?
It is the enterprise IT chapter of the ASD Essentials series, which the Australian Signals Directorate published on 15 October 2026 and describes as an evolution of the Essential Eight. It sets out 58 actions that achieve 28 cyber security principles, grouped in five functions: Govern, Identify, Protect, Detect and Respond. Control Stack explains each action in plain English, with implementation tips, audit tips and mappings.
What are domains and priority phases?
Each action applies in one or more of eight domains. The six technical domains are sequenced in three priority phases: Boundary services and Identity services first, then Critical processes and services and Privileged environments, then Business systems and User devices. ASD calls the phases "a sequencing mechanism, not a rating". The two capability domains, Governance and culture and Visibility and response, apply in every phase. Because the phases order domains rather than actions, an action that applies in several domains comes up in each of their phases.
Does it cover cloud services?
This is ASD's enterprise IT chapter. ASD publishes a separate cloud chapter for environments delivered through software-as-a-service (SaaS) and platform-as-a-service (PaaS), and a chapter for operational technology (OT), and expects most organisations to need both the enterprise IT and cloud chapters over time. Control Stack covers the enterprise IT chapter.
Why do the principles have ISM identifiers?
The principles come from ASD's Information Security Manual and keep their ISM identifiers, such as GOV-01, for traceability. The numbers are not an order of work.





