Prepared for
Security coverage report: what your licences already cover
ISM controls in our count reachable from the tiers you selected. ISM release 2026.09.4.
Of the ISM's 1143 controls (release 2026.09.4) we count the 1031 applicable to non-classified, OFFICIAL: Sensitive and PROTECTED systems; SECRET and TOP SECRET-only controls are excluded.
Maturity-level rows derive from ASD's own Essential Eight markings on ISM controls; each level counts the ISM controls ASD marks for it.
Maturity-level rows derive from ASD's own Essential Eight markings on ISM controls; each level counts the ISM controls ASD marks for it.
Maturity-level rows derive from ASD's own Essential Eight markings on ISM controls; each level counts the ISM controls ASD marks for it.
| Principle group | Controls covered |
| Govern | 1 / 88 |
| Identify | 8 / 81 |
| Protect | 161 / 745 |
| Detect | 1 / 36 |
| Respond | 1 / 21 |
| Recover | 36 / 60 |
ASD's cyber security principles are published without a mapping to individual controls, so this roll-up assigns each ISM chapter to the principle group it chiefly serves (our reading, not ASD's).
Every ISM control we count, with ASD's own wording, grouped by chapter: the ones your selection reaches and the ones it does not.
Looking up one control? Every control below is linked by its identifier, in ASD's wording for release 2026.09.4, for example #ISM-1685. "Reached" and "not reached" describe this sample stack, not yours.
See which of your own licences reach it: free, about 3 minutes →
Latest ISM release: ISM September 2026: What Changed and What to Check →
Not reached from your selection
Cabling infrastructure is installed in accordance with relevant Australian Standards, as directed by the Australian Communications and Media Authority.
Cable labelling processes, and supporting cable labelling procedures, are developed, implemented and maintained.
A cable register contains the following for each cable:
- cable identifier
- cable colour
- sensitivity/classification
- source
- destination
- location
- seal numbers (if applicable).
A cable register is developed, implemented, maintained and regularly verified.
IT equipment meets industry and government standards relating to electromagnetic interference/electromagnetic compatibility.
Non-classified, OFFICIAL: Sensitive and PROTECTED cables are coloured neither salmon pink nor red.
Wall outlet boxes denote the systems, cable identifiers and wall outlet box identifier.
Cables are labelled at each end with sufficient source and destination details to enable the physical identification and inspection of the cable.
In TOP SECRET areas, cable reticulation systems leading into cabinets in server rooms or communications rooms are terminated as close as possible to the cabinet.
Cable reticulation systems leading into cabinets are terminated as close as possible to the cabinet.
In TOP SECRET areas, cable reticulation systems leading into cabinets not in server rooms or communications rooms are terminated at the boundary of the cabinet.
Non-classified, OFFICIAL: Sensitive and PROTECTED wall outlet boxes are coloured neither salmon pink nor red.
Wall outlet box covers are clear plastic.
Fibre-optic cables are used for cabling infrastructure instead of copper cables.
Cables in non-TOP SECRET areas are inspectable every five metres or less.
Cable bundles or conduits sharing a common cable reticulation system have a dividing partition or visible gap between each cable bundle and conduit.
Cables from cable trays to wall outlet boxes are run in flexible or plastic conduit.
Cables in TOP SECRET areas are fully inspectable for their entire length.
In shared facilities, cables are run in an enclosed cable reticulation system.
In shared facilities, conduits or the front covers of ducts, cable trays in floors and ceilings, and associated fittings are clear plastic.
Building management cables are labelled with their purpose in black writing on a yellow background, with a minimum size of 2.5 cm x 1 cm, and attached at five-metre intervals.
Cables for foreign systems installed in Australian facilities are labelled at inspection points.
Floor plan diagrams are developed, implemented, maintained and regularly verified.
Floor plan diagrams contain the following:
- cable paths (including ingress and egress points between floors)
- cable reticulation system and conduit paths
- floor concentration boxes
- wall outlet boxes
- network cabinets.
Cables for individual systems use a consistent colour.
Wall outlet boxes for individual systems use a consistent colour.
Emanation security doctrine produced by ASD for the management of emanation security matters is complied with.
Reached from your selection
Microphones (including headsets and USB handsets) and webcams are not used with non-SECRET workstations in SECRET areas.
Microphones (including headsets and USB handsets) and webcams are not used with non-TOP SECRET workstations in TOP SECRET areas.
Video conferencing and IP telephony infrastructure is hardened.
Not reached from your selection
Personnel are advised of the permitted sensitivity or classification of information that can be discussed over internal and external telephone systems.
Personnel are advised of security risks posed by non-secure telephone systems in areas where sensitive or classified conversations can occur.
When using cryptographic equipment to permit different levels of conversation for different kinds of connections, telephone systems give a visual indication of what kind of connection has been made.
Telephone systems used for sensitive or classified conversations encrypt all traffic that passes over external systems.
Cordless telephone handsets and headsets are not used for sensitive or classified conversations unless all communications are encrypted using ASD-approved cryptography.
Speakerphones are not used on telephone systems in TOP SECRET areas unless the telephone system is located in an audio secure room, the room is audio secure during conversations and only personnel involved in conversations are present in the room.
Off-hook audio protection features are used on telephone systems in areas where background conversations may exceed the sensitivity or classification that the telephone system is authorised for communicating.
MFDs are not connected to digital telephone systems.
When video conferencing or IP telephony traffic passes through a gateway containing a firewall or proxy, a video-aware or voice-aware firewall or proxy is used.
Video conferencing and IP telephony calls are conducted using a secure real-time transport protocol.
Video conferencing and IP telephony calls are established using a secure session initiation protocol.
Video conferencing and IP telephony traffic is physically or logically separated from other data traffic.
IP telephony is configured such that:
- IP phones authenticate themselves to the call controller upon registration
- auto-registration is disabled and only authorised devices are allowed to access the network
- unauthorised devices are blocked by default
- all unused and prohibited functionality is disabled.
Authentication and authorisation is used for all actions on a video conferencing network, including call setup and changing settings.
An encrypted and non-replayable two-way authentication scheme is used for call authentication and authorisation.
Authentication and authorisation is used for all actions on an IP telephony network, including registering a new IP phone, changing phone users, changing settings and accessing voicemail.
Workstations are not connected to video conferencing units or IP phones unless the workstation or the device uses virtual local area networks or similar mechanisms to maintain separation between video conferencing, IP telephony and other data traffic.
IP phones used in public areas do not have the ability to access data networks, voicemail and directory services.
An MFD usage policy is developed, implemented and maintained.
MFDs are not used to scan or copy documents above the sensitivity or classification of networks they are connected to.
Authentication measures for MFDs are the same strength as those used for workstations on networks they are connected to.
In SECRET and TOP SECRET areas, push-to-talk handsets or push-to-talk headsets are used to meet any off-hook audio protection requirements.
A denial of service response plan for video conferencing and IP telephony services is developed, implemented and maintained.
MFDs are placed in areas where their use can be observed.
A telephone system usage policy is developed, implemented and maintained.
A denial of service response plan for video conferencing and IP telephony services contains the following:
- how to identify signs of a denial-of-service attack
- how to identify the source of a denial-of-service attack
- how capabilities can be maintained during a denial-of-service attack
- what actions can be taken to respond to a denial-of-service attack.
Human users authenticate to MFDs before they can print, scan or copy documents.
Use of MFDs for printing, scanning and copying purposes, including the capture of shadow copies of documents, are centrally logged.
Fax machines, and online fax services, are not used for sending or receiving fax messages.
Reached from your selection
The SSH daemon is configured to:
- only listen on the required interfaces (ListenAddress xxx.xxx.xxx.xxx)
- have a suitable login banner (Banner x)
- have a login authentication timeout of no more than 60 seconds (LoginGraceTime 60)
- disable host-based authentication (HostbasedAuthentication no)
- disable rhosts-based authentication (IgnoreRhosts yes)
- disable the ability to log in directly as root (PermitRootLogin no)
- disable empty passwords (PermitEmptyPasswords no)
- disable connection forwarding (AllowTCPForwarding no)
- disable gateway ports (GatewayPorts no)
- disable X11 forwarding (X11Forwarding no).
When using logins without a password for SSH connections, the following are disabled:
- access from IP addresses that do not require access
- port forwarding
- agent credential forwarding
- X11 forwarding
- console access.
If using remote access without the use of a password for SSH connections, the ‘forced command’ option is used to specify what command is executed and parameter checking is enabled.
When SSH-agent or similar key caching applications are used, cached private keys have a maximum lifetime of four hours and, where applicable, screen locks are used on workstations and servers.
Not reached from your selection
The compromise or suspected compromise of cryptographic equipment or associated keying material is reported to the chief information security officer, or one of their delegates, as soon as possible after it occurs.
Where practical, cryptographic equipment, applications and libraries provide a means of data recovery to allow for circumstances where the encryption key is unavailable due to loss, damage or failure.
Cryptographic equipment, applications or libraries that have completed a Common Criteria evaluation against an ASD-endorsed Protection Profile are used when encrypting media that contains OFFICIAL: Sensitive or PROTECTED data.
When a user authenticates to the encryption functionality of IT equipment or media, it is treated in accordance with its original sensitivity or classification until the user deauthenticates from the encryption functionality.
Cryptographic equipment, applications or libraries that have completed a Common Criteria evaluation against an ASD-endorsed Protection Profile are used to protect OFFICIAL: Sensitive or PROTECTED data when communicated over insufficiently secure networks, outside of appropriately secure areas or via public network infrastructure.
An AACP or high assurance cryptographic protocol is used when encrypting data in transit.
Only AACAs or high assurance cryptographic algorithms are used by cryptographic equipment, applications and libraries.
When using DH for agreeing on encryption session keys, a modulus of at least 2048 bits is used, preferably 3072 bits.
When using ECDH for agreeing on encryption session keys, a base point order and key size of at least 224 bits is used, preferably the NIST P-384 curve.
When using ECDSA for digital signatures, a base point order and key size of at least 224 bits is used, preferably the P-384 curve.
When using RSA for digital signatures, and transporting encryption session keys (and similar keys), a modulus of at least 2048 bits is used, preferably 3072 bits.
When using RSA for digital signatures, and for transporting encryption session keys (and similar keys), a different key pair is used for digital signatures and transporting encryption session keys.
Symmetric cryptographic algorithms are not used in Electronic Codebook Mode.
Only AACPs or high assurance cryptographic protocols are used by cryptographic equipment, applications and libraries.
Public key-based authentication is used for SSH connections.
Versions of S/MIME earlier than S/MIME version 3.0 are not used for S/MIME connections.
Tunnel mode is used for IPsec connections; however, if using transport mode, an IP tunnel is used.
The ESP protocol is used for authentication and encryption of IPsec connections.
A security association lifetime of less than four hours (14400 seconds) is used for IPsec connections.
Keyed cryptographic equipment is transported based on the sensitivity or classification of its keying material.
Cryptographic key management processes, and supporting cryptographic key management procedures, are developed, implemented and maintained.
ECDH is used in preference to DH.
AUTH_HMAC_SHA2_256_128, AUTH_HMAC_SHA2_384_192, AUTH_HMAC_SHA2_512_256 or NONE (only with AES-GCM) is used for authenticating IPsec connections, preferably NONE.
DH or ECDH is used for key establishment of IPsec connections, preferably 384-bit random ECP group, 3072-bit MODP Group or 4096-bit MODP Group.
PFS is used for IPsec connections.
An AACA or high assurance cryptographic algorithm is used when encrypting data at rest.
Keying material is changed when compromised or suspected of being compromised.
Only the latest version of TLS is used for TLS connections.
IKE version 2 is used for key exchange when establishing IPsec connections.
AES-GCM is used for encryption of TLS connections.
Only server-initiated secure renegotiation is used for TLS connections.
The ephemeral variant of DH or ECDH is used for key establishment of TLS connections.
Anonymous DH is not used for TLS connections.
SHA-2-based certificates are used for TLS connections.
SHA-2 is used for the Hash-based Message Authentication Code (HMAC) and pseudorandom function (PRF) for TLS connections.
When using elliptic curve cryptography, a suitable curve from NIST SP 800-186 is used.
SSH private keys are protected with a password or a key encryption key.
Perfect Forward Secrecy (PFS) is used for TLS connections.
The use of SSH version 1 is disabled for SSH connections.
TLS compression is disabled for TLS connections.
When using DH for agreeing on encryption session keys, a modulus and associated parameters are selected according to NIST SP 800-56A Rev. 3.
When using SHA-2 for hashing, an output size of at least 224 bits is used, preferably SHA-384 or SHA-512.
When using AES for encryption, AES-128, AES-192 or AES-256 is used, preferably AES-256.
AES is used for encrypting IPsec connections, preferably ENCR_AES_GCM_16.
PRF_HMAC_SHA2_256, PRF_HMAC_SHA2_384 or PRF_HMAC_SHA2_512 is used for IPsec connections, preferably PRF_HMAC_SHA2_512.
The development and procurement of new cryptographic equipment, applications and libraries ensures support for the use of ML-DSA-87, ML-KEM-1024, SHA-384, SHA-512 and AES-256 by no later than 2030.
When using ML-DSA and ML-KEM, as per FIPS 204 and FIPS 203 respectively, adherence to pre-requisite FIPS 140-3 validation is preferred.
When using ML-DSA for digital signatures, ML-DSA-65 or ML-DSA-87 is used, preferably ML-DSA-87.
When using ML-DSA for digital signatures, the hedged variant is used whenever possible.
Pre-hashed variants of ML-DSA-65 and ML-DSA-87 are only used when the performance of default variants is unacceptable.
When the pre-hashed variants of ML-DSA-65 and ML-DSA-87 are used, at least SHA-384 and SHA-512 respectively are used for pre-hashing.
When using ML-KEM for encapsulating encryption session keys (and similar keys), ML-KEM-768 or ML-KEM-1024 is used, preferably ML-KEM-1024.
When a post-quantum traditional hybrid scheme is used, either the post-quantum cryptographic algorithm, the traditional cryptographic algorithm or both are AACAs.
A post-quantum cryptography transition plan is developed, implemented and maintained.
Reached from your selection
Systems have a change and configuration management plan that includes:
- the establishment and maintenance of authorised baseline configurations for systems
- what constitutes routine and urgent changes to the configuration of systems
- how changes to the configuration of systems will be requested, tracked and documented
- who needs to be consulted prior to routine and urgent changes to the configuration of systems
- who needs to approve routine and urgent changes to the configuration of systems
- who needs to be notified of routine and urgent changes to the configuration of systems
- what additional change management and configuration management processes and procedures need to be followed before, during and after routine and urgent changes to the configuration of systems.
Not reached from your selection
A cyber security strategy is developed, implemented and maintained.
Systems have a system security plan that includes an overview of the system (covering the system’s purpose, the system boundary and how the system is managed) as well as an annex that covers applicable security controls from this document and any additional security controls that have been identified and implemented.
Systems have a cyber security incident response plan that covers the following:
- guidelines on what constitutes a cyber security incident
- the types of cyber security incidents likely to be encountered and the expected response to each type
- how to report cyber security incidents, internally to an organisation and externally to relevant authorities
- other parties that need to be informed in the event of a cyber security incident
- the authority, or authorities, responsible for investigating and responding to cyber security incidents
- the criteria by which an investigation of a cyber security incident would be requested from a law enforcement agency, the Australian Signals Directorate or other relevant authority
- the steps necessary to ensure the integrity of evidence relating to a cyber security incident
- system contingency measures or a reference to such details if they are in a separate document.
Organisational-level cyber security documentation is approved by the chief information security officer while system-specific cyber security documentation is approved by the system’s authorising officer.
Cyber security documentation is reviewed at least annually and includes a ‘current as at \[date\]’ or equivalent statement.
Systems have a continuous monitoring plan that includes:
- conducting security assessment activities to identify vulnerabilities
- analysing identified vulnerabilities to determine their potential impact
- implementing mitigations based on risk, effectiveness and cost.
At the conclusion of a security control assessment for a system, a security assessment report is produced by the assessor and covers:
- the scope of the security control assessment
- the system’s strengths and weaknesses
- security risks associated with the operation of the system
- the effectiveness of the implementation of security controls
- any recommended remediation actions.
At the conclusion of a security control assessment for a system, a plan of action and milestones is produced by the system owner.
Cyber security documentation, including notification of subsequent changes, is communicated to all stakeholders.
A system’s security architecture is approved prior to the development of the system.
Reached from your selection
When malicious code is detected, the following steps are taken to handle the infection:
- the infected systems are isolated
- all previously connected media used in the period leading up to the infection are scanned for signs of infection and isolated if necessary
- antivirus applications are used to remove the infection from infected systems and media
- if the infection cannot be reliably removed, systems are restored from a known good backup or rebuilt.
Not reached from your selection
Cyber security incidents are reported to the chief information security officer, or one of their delegates, as soon as possible after they occur or are discovered.
A cyber security incident register is developed, implemented and maintained.
When a data spill occurs, data owners are advised and access to the data is restricted.
Legal advice is sought before allowing intrusion activity to continue on a system for the purpose of collecting further data or evidence.
The integrity of evidence gathered during an investigation is maintained by investigators:
- recording all their actions
- maintaining a proper chain of custody
- following all instructions provided by relevant law enforcement agencies.
Cyber security incidents are reported to ASD as soon as possible after they occur or are discovered.
A cyber security incident management policy, and associated cyber security incident response plan, is developed, implemented and maintained.
Following intrusion remediation activities, enhanced monitoring is conducted until there is sufficient evidence-based confidence that malicious actors have been eradicated from a system and have not re-established access.
System owners are consulted before allowing intrusion activity to continue on a system for the purpose of collecting further data or evidence.
An insider threat mitigation program is developed, implemented and maintained.
Legal advice is sought regarding the development and implementation of an insider threat mitigation program.
Planning and coordination of intrusion remediation activities are conducted using trusted systems separate from a compromised system.
Intrusion remediation activities are coordinated and sequenced to minimise opportunities for re-compromise of a system while balancing operational risk and business continuity requirements.
The cyber security incident management policy, including the associated cyber security incident response plan, is exercised at least annually.
A cyber security incident register contains the following for each cyber security incident:
- the date the cyber security incident occurred
- the date the cyber security incident was discovered
- a description of the cyber security incident
- any actions taken in response to the cyber security incident
- to whom the cyber security incident was reported.
Following the identification of a cyber security incident, the cyber security incident response plan is enacted.
Cyber security incidents that involve customer data are reported to customers and the public in a timely manner after they occur or are discovered.
Cyber security incidents that do not involve customer data are reported to customers and the public in a timely manner after they occur or are discovered.
Malicious code, when stored or communicated, is treated beforehand to prevent accidental execution.
Malicious code processing for cyber security incident response or research purposes is conducted in a dedicated analysis environment segregated from other systems.
Not reached from your selection
System owners, in consultation with each system’s authorising officer, identify any supplementary security controls required based upon the unique nature of each system, its operating environment and the organisation’s risk tolerances.
System owners obtain an authorisation to operate for each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system from its authorising officer.
A CISO is appointed to provide cyber security leadership and guidance for their organisation (covering IT and OT).
The CISO oversees the management of cyber security personnel within their organisation.
The CISO regularly reports directly to their organisation’s board of directors or executive committee on cyber security matters.
The CISO oversees the development, implementation and maintenance of a cyber security communications strategy to assist in communicating the cyber security vision and strategy for their organisation.
The CISO implements cyber security measurement metrics and key performance indicators for their organisation.
The CISO coordinates cyber security and business alignment through a cyber security steering committee or advisory board, comprising key cyber security and business executives, which meets formally and regularly.
The CISO coordinates security risk management activities between cyber security and business teams.
The CISO oversees cyber supply chain risk management activities for their organisation.
The CISO receives and manages a dedicated cyber security budget for their organisation.
The CISO is fully aware of all cyber security incidents within their organisation.
The CISO contributes to the development, implementation and maintenance of business continuity and disaster recovery plans for their organisation to ensure that business-critical services are supported appropriately in the event of a disaster.
The CISO oversees the development, implementation and maintenance of their organisation’s cyber security awareness training program.
Each system has a designated system owner.
System owners, in consultation with each system’s authorising officer, conduct a threat and risk assessment for each system.
The CISO oversees their organisation’s cyber security program and ensures their organisation’s compliance with cyber security policy, standards, regulations and legislation.
System owners register each system with its authorising officer.
System owners continuously monitor the security of each system, and manage associated cyber threats, security risks and security controls.
System owners report the security status of each system to its authorising officer at least annually.
The CISO regularly reviews and updates their organisation’s cyber security program to ensure its relevance in addressing cyber threats and harnessing business and cyber security opportunities.
The CISO oversees their organisation’s response to cyber security incidents.
System owners, in consultation with each system’s authorising officer, determine the system boundary, business criticality, and security and resilience objectives for each system based on an assessment of the impact if it were to be compromised or attacked.
System owners, in consultation with each system’s authorising officer, select security controls for each system and tailor them to achieve desired security and resilience objectives.
System owners implement security controls for each system and its operating environment.
System owners, in consultation with each system’s authorising officer, ensure security controls for each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system and its operating environment undergo a security control assessment by their organisation’s own assessors or Infosec Registered Assessor Program (IRAP) assessors to determine if they have been implemented correctly and are operating as intended.
The CISO regularly reports directly to their organisation’s audit, risk and compliance committee (or equivalent) on cyber security matters.
The CISO develops, implements, maintains and regularly verifies a register of systems used by their organisation.
The board of directors or executive committee defines clear roles and responsibilities for cyber security both within the board of directors or executive committee and broadly within their organisation.
The board of directors or executive committee ensures that cyber security is integrated throughout all business functions within their organisation.
The board of directors or executive committee ensures the cyber security strategy for their organisation is aligned with the overarching strategic direction and business strategy for their organisation.
The board of directors or executive committee seeks regular briefings or reporting on the cyber security posture of their organisation, as well as the threat environment in which they operate, from internal and external subject matter experts.
The board of directors or executive committee champions a positive cyber security culture within their organisation, including through leading by example.
The board of directors or executive committee maintains a sufficient level of cyber security literacy to fulfil both their fiduciary duties and any legislative or regulatory obligations.
The board of directors or executive committee maintains awareness of key cyber security recruitment activities, retention rates for cyber security personnel, and cyber security skills and experience gaps within their organisation.
The board of directors or executive committee supports the development of cyber security skills and experience for all personnel via internal and external cyber security awareness raising and training opportunities.
The board of directors or executive committee understands the business criticality of their organisation’s systems, including at least a basic understanding of what systems exist, their value, where they reside, who has access, who might seek access, how they are protected, and how that protection is verified.
The board of directors or executive committee plans for major cyber security incidents, including by participating in exercises, and understands their duties in relation to such cyber security incidents.
The CISO ensures sufficient cyber security personnel, with the right skills and experience, are acquired to support cyber security activities within their organisation.
System owners implement and maintain data minimisation practices for each of their systems.
Not reached from your selection
When manually importing data to systems, the data is scanned for malicious and active content.
Human users transferring data to and from systems are held accountable for data transfers they perform.
Data transfer processes, and supporting data transfer procedures, are developed, implemented and maintained.
When manually exporting data from systems, the data is checked for unsuitable protective markings.
Data transfer logs for systems are partially verified at least monthly.
Data transfer logs are used to record all data imports and exports from systems.
When manually importing data to systems, all data that fails security checks is quarantined until reviewed and subsequently approved or not approved for release.
When manually exporting data from systems, all data that fails security checks is quarantined until reviewed and subsequently approved or not approved for release.
Reached from your selection
Not reached from your selection
Databases and their contents are classified based on the sensitivity or classification of data that they contain.
A database register is developed, implemented, maintained and regularly verified.
Database users’ ability to access, insert, modify and remove database contents is restricted based on their duties or functions.
File-based access controls are applied to database files.
The need-to-know principle is enforced for database contents through the application of minimum privileges, database views, database roles and data tokenisation.
Database servers are placed on a different network segment to workstations.
Network access controls are implemented to restrict database server communications to strictly defined network resources that require access to the database server.
Database servers for development, testing, staging and production environments are segregated.
Database contents from production environments are not used in non-production environments unless the non-production environment is secured to at least the same level as the production environment.
Data communicated between database servers and web servers is encrypted using Australian Signals Directorate-approved cryptography.
Security-relevant events for databases are centrally logged, including:
- access or modification of particularly important content
- addition of new users, especially privileged users
- changes to user roles or privileges
- attempts to elevate user privileges
- queries containing comments
- queries containing multiple embedded queries
- database and query alerts or failures
- database structure changes
- database administrator actions
- use of executable commands
- database logons and logoffs.
Reached from your selection
Email servers only relay emails destined for or originating from their domains (including subdomains).
Not reached from your selection
An email usage policy is developed, implemented and maintained.
Access to non-approved webmail services is blocked.
Protective markings are applied to emails and reflect the highest sensitivity or classification of the subject, body and attachments.
Protective marking tools do not automatically insert protective markings into emails.
Protective marking tools do not allow the selection of protective markings that a system has not been authorised to process, store or communicate.
Email servers are configured to block, log and report emails with inappropriate protective markings.
Emails are routed via centralised email gateways.
Where backup or alternative email gateways are in place, they are maintained at the same standard as the primary email gateway.
When users send or receive emails, an authenticated and encrypted channel is used to route emails via their organisation’s centralised email gateways.
Opportunistic TLS encryption is enabled on email servers that make incoming or outgoing email connections over public network infrastructure.
SPF is used to specify authorised email servers (or lack thereof) for an organisation’s domains (including subdomains).
DKIM signing is enabled on emails originating from an organisation’s domains (including subdomains).
The intended recipients of blocked inbound emails, and the senders of blocked outbound emails, are notified.
Notifications of undeliverable emails are only sent to senders that can be verified via SPF or other trusted means.
DKIM signatures on incoming emails are verified.
Email distribution list applications used by external senders is configured such that it does not break the validity of the sender’s DKIM signature.
When replying to or forwarding emails, protective marking tools do not allow the selection of protective markings lower than previously used.
SPF is used to verify the authenticity of incoming emails.
A hard fail SPF record is used when specifying authorised email servers (or lack thereof) for an organisation’s domains (including subdomains).
Email content filtering is implemented to filter potentially harmful content in email bodies and attachments.
Emails arriving via an external connection where the email source address uses an internal domain, or internal subdomain, are blocked at the email gateway.
DMARC records are configured for an organisation’s domains (including subdomains) such that emails are rejected if they do not pass DMARC checks.
MTA-STS is enabled to prevent the unencrypted transfer of emails between email servers.
Incoming emails are rejected if they do not pass DMARC checks.
Reached from your selection
Mobile device emergency sanitisation processes, and supporting mobile device emergency sanitisation procedures, are developed, implemented and maintained.
Mobile devices prevent personnel from installing non-approved applications once provisioned.
Mobile devices prevent personnel from disabling or modifying security functionality once provisioned.
Mobile devices encrypt their internal storage and any removable media using ASD-approved cryptography.
Mobile Device Management solutions that have completed a Common Criteria evaluation against the Protection Profile for Mobile Device Management, version 4.0 or later, are used to enforce mobile device management policy.
Non-classified, OFFICIAL: Sensitive and PROTECTED mobile devices are configured to remain undiscoverable to other Bluetooth devices except during Bluetooth pairing.
Bluetooth pairing for non-classified, OFFICIAL: Sensitive and PROTECTED mobile devices is performed in a manner such that connections are only made between intended Bluetooth devices.
Bluetooth pairings for non-classified, OFFICIAL: Sensitive and PROTECTED mobile devices are removed when there is no longer a requirement for their use.
Bluetooth pairing for non-classified, OFFICIAL: Sensitive and PROTECTED mobile devices is performed using Secure Connections, preferably with Numeric Comparison if supported.
Security updates are applied to mobile devices as soon as they become available.
Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data have enforced separation of classified data and personal data.
Personnel using organisation-owned mobile devices or desktop computers to access classified systems or data have enforced separation of classified data and personal data.
A mobile device management policy is developed, implemented and maintained.
If travelling overseas with mobile devices to high or extreme risk countries, personnel are:
- issued with newly provisioned user accounts, mobile devices and removable media from a pool of dedicated travel devices which are used solely for work-related activities
- advised on how to apply and inspect tamper seals to key areas of mobile devices
- advised to avoid taking any personal mobile devices, especially if rooted or jailbroken.
Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data are prevented from storing classified data on their privately owned mobile devices and desktop computers.
Mobile devices are configured to operate in a supervised (or equivalent) mode.
Mobile devices are configured with remote locate and wipe functionality.
Mobile devices are configured with secure password-based lock screens.
Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data are disallowed from granting access to unapproved artificial intelligence agents.
Mobile devices are configured to enforce separation between organisational and personal mobile applications and data.
Mobile devices are configured to prevent data transfers over Universal Serial Bus connections.
Mobile devices are not connected to the infotainment systems of connected vehicles.
Not reached from your selection
Paging, Multimedia Message Service, Short Message Service and messaging apps are not used to communicate sensitive or classified data.
When accessing an organisation’s network via a VPN connection, split tunnelling is disabled.
Sensitive or classified data is not viewed on mobile devices in public locations unless care is taken to reduce the chance of the screen of a mobile device being observed.
Mobile devices are carried or stored in a secured state when not being actively used.
Mobile devices are kept under continual direct supervision when being actively used.
Mobile devices and desktop computers access the internet via an organisation’s internet gateway rather than via a direct connection to the internet.
A mobile device usage policy is developed, implemented and maintained.
Personnel are advised of the sensitivity or classification permitted for voice and data communications when using mobile devices.
If unable to carry or store mobile devices in a secured state, they are physically transferred in a security briefcase or an approved multi-use satchel, pouch or transit bag.
Mobile devices encrypt all sensitive or classified data communicated over public network infrastructure using ASD-approved cryptography.
Personnel report the potential compromise of mobile devices, removable media or credentials to their organisation as soon as possible, especially if they:
- provide credentials to foreign government officials
- decrypt mobile devices for foreign government officials
- have mobile devices taken out of sight by foreign government officials
- have mobile devices or removable media stolen, including if later returned
- lose mobile devices or removable media, including if later found
- observe unusual behaviour of mobile devices.
Legal advice is sought prior to allowing privately owned mobile devices and desktop computers to access systems or data.
Personnel are advised of privacy and security risks when travelling overseas with mobile devices.
Personnel are advised to take the following precautions when using mobile devices:
- never leave mobile devices or removable media unattended, including by placing them in checked-in luggage or leaving them in hotel safes
- never store credentials with mobile devices that they grant access to, such as in laptop computer bags
- never lend mobile devices or removable media to untrusted people, even if briefly
- never allow untrusted people to connect their mobile devices or removable media to your mobile devices, including for charging
- never connect mobile devices to designated charging stations or wall outlet charging ports
- never use gifted or unauthorised peripherals, chargers or removable media with mobile devices
- never use removable media for data transfers or backups that have not been checked for malicious code beforehand
- avoid reuse of removable media once used with other parties’ systems or mobile devices
- avoid connecting mobile devices to open or untrusted Wi-Fi networks
- consider disabling any communications capabilities of mobile devices when not in use, such as Wi-Fi, Bluetooth, Near Field Communication and ultra-wideband
- consider periodically rebooting mobile devices
- consider using a VPN connection to encrypt all cellular and wireless communications
- consider using encrypted email or messaging apps for all communications.
Upon returning from travelling overseas with mobile devices, personnel take the following actions:
- sanitise and reset mobile devices, including all removable media
- decommission any credentials that left their possession during their travel
- report if significant doubt exists as to the integrity of any mobile devices or removable media.
Before travelling overseas with mobile devices, personnel take the following actions:
- record all details of the mobile devices being taken, such as product types, serial numbers and International Mobile Equipment Identity numbers
- update all operating systems and applications
- remove all non-essential data, applications and user accounts
- backup all remaining data, applications and settings.
If returning from travelling overseas with mobile devices to high or extreme risk countries, personnel take the following additional actions:
- reset credentials used with mobile devices, including those used for remote access to their organisation’s systems
- monitor user accounts for any indicators of compromise, such as failed logon attempts.
Sensitive or classified phone calls and conversations are not conducted in public locations unless care is taken to reduce the chance of conversations being overheard.
Mobile devices that access OFFICIAL: Sensitive or PROTECTED systems or data use mobile platforms that have completed a Common Criteria evaluation against the Protection Profile for Mobile Device Fundamentals, version 3.3 or later, and are operated in accordance with the latest version of their associated ASD security configuration guide.
Mobile devices are configured with always on VPN functionality.
Sensitive or classified data is not viewed on mobile devices within or near connected vehicles.
Sensitive or classified phone calls and conversations are not conducted within or near connected vehicles.
Mobile applications encrypt all sensitive or classified data communicated over public network infrastructure using ASD-approved cryptography.
Reached from your selection
Evaluated products are installed, configured, administered and operated in an evaluated configuration and in accordance with vendor guidance.
Not reached from your selection
If procuring an evaluated product, a product that has completed a PP-based evaluation, including against all applicable PP modules (as well as a software bill of materials assessment if applicable), is selected in preference to one that has completed an EAL-based evaluation.
Evaluated products are delivered in a manner consistent with any delivery procedures defined in associated evaluation documentation.
Not reached from your selection
Non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET gateways undergo an IRAP assessment, using the latest release of the ISM available prior to the beginning of the IRAP assessment (or a subsequent release), at least every 24 months.
All web access, including that by internal servers, is conducted through web proxies.
The following details are centrally logged for websites accessed via web proxies:
- web address
- date and time
- user
- amount of data uploaded and downloaded
- internal and external IP addresses.
TLS traffic communicated through gateways is decrypted and inspected.
Evaluated peripheral switches are used when sharing peripherals between systems.
System administrators for gateways are assigned the minimum privileges required to perform their duties.
System administrators for gateways are formally trained on the operation and management of gateways.
Separation of duties is implemented in performing administrative activities for gateways.
Users authenticate to other networks accessed via gateways.
IT equipment authenticates to other networks accessed via gateways.
Gateways are implemented between networks belonging to different security domains.
For gateways between networks belonging to different security domains, any shared components are managed by system administrators for the higher security domain or by system administrators from a mutually agreed upon third party.
Gateways only allow explicitly authorised data flows.
Security-relevant events for gateways are centrally logged, including:
- data packets and data flows permitted through gateways
- data packets and data flows attempting to leave gateways
- real-time alerts for attempted intrusions.
Gateways implement a demilitarised zone if external parties require access to an organisation’s services.
Evaluated firewalls are used between networks belonging to different security domains.
Evaluated diodes are used for controlling the data flow of unidirectional gateways between an organisation’s networks and public network infrastructure.
Files imported or exported via gateways or CDSs are filtered for allowed file types.
Files identified by content filtering checks as malicious, or that cannot be inspected, are blocked.
Files identified by content filtering checks as suspicious are quarantined until reviewed and subsequently approved or not approved for release.
Files imported or exported via gateways or CDSs undergo content filtering checks.
Files imported or exported via gateways or CDSs that have a digital signature or cryptographic checksum are validated.
An organisation-approved list of domain names, or list of website categories, is implemented for all Hypertext Transfer Protocol and Hypertext Transfer Protocol Secure traffic communicated through gateways.
Client-side active content is restricted by web content filters to an organisation-approved list of domain names.
Web content filtering is implemented to filter potentially harmful web-based content.
Gateways undergo testing following configuration changes, and at regular intervals no more than six months apart, to validate that they conform to expected security configurations.
Evaluated diodes are used for controlling the data flow of unidirectional gateways between networks.
Attempts to access websites through their IP addresses instead of their domain names are blocked by web content filters.
Gateways inspect and filter data flows at the transport and above network layers.
Malicious domain names, dynamic domain names and domain names that can be registered anonymously for free are blocked by web content filters.
Web content filtering is applied to outbound web traffic where appropriate.
Files imported or exported via gateways or CDSs undergo content validation.
Files imported or exported via gateways or CDSs undergo content conversion.
Files imported or exported via gateways or CDSs undergo content sanitisation.
Files imported or exported via gateways or CDSs undergo antivirus scanning using multiple different scanning engines.
Archive files imported or exported via gateways or CDSs are unpacked to undergo content filtering checks.
Archive files are unpacked in a controlled manner to ensure content filter performance or availability is not adversely affected.
Encrypted files imported or exported via gateways or CDSs are decrypted to undergo content filtering checks.
Executable files imported via gateways or CDSs are automatically executed in a sandbox to detect any suspicious behaviour.
Gateways perform ingress traffic filtering to detect and prevent IP source address spoofing.
System administrators for gateways undergo appropriate employment screening, and where necessary hold an appropriate security clearance, based on the sensitivity or classification of gateways.
Evaluated firewalls are used between an organisation’s networks and public network infrastructure.
Gateways are managed via a secure path isolated from all connected networks.
Public IP addresses controlled by, or used by, an organisation are signed by valid ROA records.
If using a WAF, disclosing the IP addresses of web servers under an organisation’s control (referred to as origin servers) is avoided and access to the origin servers is restricted to the WAF and authorised management networks.
Files imported or exported via gateways or CDSs undergo content checking.
Routes for RPKI-registered IP addresses that are advertised from invalid Autonomous Systems, or that are longer than allowed, are rejected or deprioritised by routers that exchange routes via BGP.
Reached from your selection
Following maintenance or repairs to IT equipment, it is inspected to confirm that it retains its approved configuration and that no unauthorised modifications have been made.
IT equipment is hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
Approved configurations for IT equipment are developed, implemented and maintained.
Not reached from your selection
IT equipment is classified based on the highest sensitivity or classification of data that it is approved for processing, storing or communicating.
IT equipment, except for high assurance IT equipment, is labelled with protective markings reflecting its sensitivity or classification.
Maintenance or repairs of IT equipment are carried out on site by an appropriately cleared technician.
If an appropriately cleared technician is not used to undertake maintenance or repairs to IT equipment, the technician is escorted by someone who:
- has the authority to direct the technician
- is appropriately cleared and briefed
- is sufficiently familiar with the IT equipment to understand the work being undertaken
- takes all responsible measures to ensure the integrity of the IT equipment
- takes due care to ensure that data is not disclosed.
If an appropriately cleared technician is not used to undertake maintenance or repairs to IT equipment, the IT equipment and associated media are sanitised before maintenance or repairs.
IT equipment maintained or repaired off site is handled at facilities approved for handling the sensitivity or classification of the IT equipment.
IT equipment containing media is sanitised by removing the media from the IT equipment or by sanitising the media in situ.
IT equipment sanitisation processes, and supporting IT equipment sanitisation procedures, are developed, implemented and maintained.
Following sanitisation, destruction or declassification, a formal administrative decision is made to release IT equipment, or its waste, into the public domain.
At least three pages of random text with no blank areas are printed on each colour printer cartridge or MFD print drum.
When unable to sanitise printer cartridges or MFD print drums, they are destroyed as per electrostatic memory devices.
A networked IT equipment register is developed, implemented, maintained and regularly verified.
Televisions and computer monitors with minor burn-in or image persistence are sanitised by displaying a solid white image on the screen for an extended period.
Labels and markings indicating the owner, sensitivity, classification or any other marking that can associate IT equipment with its prior use are removed prior to its disposal.
MFD print drums and image transfer rollers are inspected and destroyed if there is remnant toner that cannot be removed or a print is visible on the image transfer roller.
Printer and MFD platens are inspected and destroyed if any text or images are retained on the platen.
Printers and MFDs are checked to ensure no pages are trapped in the paper path due to a paper jam.
Televisions and computer monitors that cannot be sanitised are destroyed.
Memory in network devices is sanitised using the following processes, in order of preference:
- following device-specific guidance provided in evaluation documentation
- following vendor sanitisation guidance
- loading a dummy configuration file, performing a factory reset and then reinstalling firmware.
Printer ribbons in printers and MFDs are removed and destroyed.
IT equipment disposal processes, and supporting IT equipment disposal procedures, are developed, implemented and maintained.
An IT equipment management policy is developed, implemented and maintained.
IT equipment is handled in a manner suitable for its sensitivity or classification.
IT equipment destruction processes, and supporting IT equipment destruction procedures, are developed, implemented and maintained.
IT equipment that cannot be sanitised is destroyed.
A non-networked IT equipment register is developed, implemented, maintained and regularly verified.
Reached from your selection
Full disk encryption, or partial encryption where access controls only allow writing to encrypted partitions or volumes, is implemented when encrypting media.
All data stored on media is encrypted using ASD-approved cryptography.
A removable media register is developed, implemented, maintained and regularly verified.
Pre-boot authentication using passwords, or managed network-based key release, is implemented for media containing encrypted system volumes.
Not reached from your selection
Media is classified to the highest sensitivity or classification of data it stores, unless the media has been classified to a higher sensitivity or classification.
Any media connected to a system with a higher sensitivity or classification than the media is reclassified to the higher sensitivity or classification, unless the media is read-only or the system has a mechanism through which read-only access can be ensured.
Before reclassifying media to a lower sensitivity or classification, the media is sanitised or destroyed, and a formal administrative decision is made to reclassify it.
Media, except for internally mounted fixed media within information technology equipment, is labelled with protective markings reflecting its sensitivity or classification.
Media is only used with systems that are authorised to process, store or communicate its sensitivity or classification.
When transferring data manually between two systems belonging to different security domains, write-once media is used unless the destination system has a mechanism through which read-only access can be ensured.
Media sanitisation processes, and supporting media sanitisation procedures, are developed, implemented and maintained.
The following media types are destroyed prior to their disposal:
- microfiche and microfilm
- optical discs
- programmable read-only memory
- read-only memory
- other types of media that cannot be sanitised.
Volatile media is sanitised by removing its power for at least 10 minutes.
Non-volatile magnetic media is sanitised by overwriting it at least once (or three times if pre-2001 or under 15 GB) in its entirety with a random pattern followed by a read back for verification.
Non-volatile EPROM media is sanitised by applying three times the manufacturer’s specified ultraviolet erasure time and then overwriting it at least once in its entirety with a random pattern followed by a read back for verification.
Non-volatile flash memory media is sanitised by overwriting it at least twice in its entirety with a random pattern followed by a read back for verification.
Magnetic media is destroyed using a degausser with a suitable magnetic field strength and magnetic orientation.
Product-specific directions provided by degausser manufacturers are followed.
Media destruction processes, and supporting media destruction procedures, are developed, implemented and maintained.
Media destroyed using a hammer mill, disintegrator, grinder/sander or by cutting results in media waste particles no larger than 9 mm.
The destruction of media is performed under the supervision of at least one cleared person.
Personnel supervising the destruction of media supervise its handling to the point of destruction and ensure that the destruction is completed successfully.
The destruction of media storing accountable material is performed under the supervision of at least two cleared personnel.
Personnel supervising the destruction of media storing accountable material supervise its handling to the point of destruction, ensure that the destruction is completed successfully and sign a destruction certificate afterwards.
Media disposal processes, and supporting media disposal procedures, are developed, implemented and maintained.
Following sanitisation, destruction or declassification, a formal administrative decision is made to release media, or its waste, into the public domain.
Labels and markings indicating the owner, sensitivity, classification or any other marking that can associate media with its prior use are removed prior to its disposal.
Media is handled in a manner suitable for its sensitivity or classification.
Non-volatile EEPROM media is sanitised by overwriting it at least once in its entirety with a random pattern followed by a read back for verification.
The destruction of media storing accountable material is not outsourced.
When outsourcing the destruction of media storing non-accountable material, a National Association for Information Destruction AAA certified destruction service with endorsements, as specified in ASIO’s Protective Security Circular-167, is used.
When transferring data manually between two systems belonging to different security domains, rewritable media is sanitised after each data transfer.
The host-protected area and device configuration overlay table are reset prior to the sanitisation of non-volatile magnetic hard drives.
The ATA secure erase command is used, in addition to block overwriting software, to ensure the growth defects table of non-volatile magnetic hard drives is overwritten.
If using degaussers to destroy media, degaussers evaluated by the United States’ National Security Agency are used.
A removable media usage policy is developed, implemented and maintained.
Security Construction and Equipment Committee-approved equipment or ASIO-approved equipment is used when destroying media.
Equipment that is capable of reducing microform to a fine powder, with resultant particles not showing more than five consecutive characters per particle upon microscopic inspection, is used to destroy microfiche and microfilm.
A media management policy is developed, implemented and maintained.
Media is sanitised before it is used for the first time.
Following the use of a degausser, magnetic media is physically damaged by deforming any internal platters.
Media is sanitised before it is reused in a different security domain.
Electrostatic memory devices are destroyed using a furnace/incinerator, hammer mill, disintegrator or grinder/sander.
Magnetic floppy disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, degausser or by cutting.
Magnetic hard disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, grinder/sander or degausser.
Magnetic tapes are destroyed using a furnace/incinerator, hammer mill, disintegrator, degausser or by cutting.
Optical disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, grinder/sander or by cutting.
Semiconductor memory is destroyed using a furnace/incinerator, hammer mill or disintegrator.
Media that cannot be successfully sanitised is destroyed prior to its disposal.
Reached from your selection
Servers maintain effective functional separation from each other.
Unused physical ports on network devices are disabled.
Default user accounts or credentials for network devices, including for any pre-configured user accounts, are changed, disabled or removed during initial setup.
SNMP version 1 and SNMP version 2 are not used on networks.
All default SNMP community strings on network devices are changed and write access is disabled.
Unless explicitly required, IPv6 tunnelling is disabled on all network devices.
Dynamically assigned IPv6 addresses are configured with Dynamic Host Configuration Protocol version 6 in a stateful manner with lease data stored in a centralised event logging facility.
Servers minimise communications with other servers at the network and file system level.
Network devices are flashed with trusted firmware before they are used for the first time.
Network devices are restarted at least monthly.
Network documentation includes device settings for all critical servers, high-value servers, network devices and network security appliances.
SMB version 1 is not used on networks.
The integrity of network device firmware and running configurations is verified against an approved known-good baseline following patching, on detection of anomalous behaviour and at least monthly.
Unneeded components, services and functionality of network devices are disabled or removed.
Not reached from your selection
Network documentation includes high-level network diagrams showing all connections into networks and logical network diagrams showing all critical servers, high-value servers, network devices and network security appliances.
Network documentation is developed, implemented and maintained.
Network access controls are implemented on networks to prevent the connection of unauthorised network devices and networked IT equipment.
VLANs are not used to separate network traffic between networks belonging to different security domains.
Network devices managing VLANs are administered from the most trusted security domain.
Network devices managing VLANs belonging to different security domains do not share VLAN trunks.
Public wireless networks provided for public use are segregated from all other organisation networks.
Security measures are implemented to prevent unauthorised access to network management traffic.
A NIDS or NIPS is deployed in gateways between an organisation’s networks and other networks they do not manage.
A NIDS or NIPS is located immediately inside the outermost firewall for gateways and configured to generate event logs and alerts for network traffic that contravenes any rule in a firewall ruleset.
Network documentation provided to a third party, or published in public tender documentation, only contains details necessary for other parties to undertake contractual services.
Networks are segregated into multiple network zones according to the criticality of servers, services and data.
Network access controls are implemented to limit the flow of network traffic within and between network segments to only that required for business purposes.
IPv6 capable network security appliances are used on IPv6 and dual-stack networks.
All wireless devices are Wi-Fi Alliance certified.
The administrative interface on wireless access points is disabled for wireless network connections.
Default SSIDs of wireless access points are changed.
SSIDs of non-public wireless networks are not readily associated with an organisation, the location of their premises or the functionality of wireless networks.
SSID broadcasting is not disabled on wireless access points.
Static addressing is not used for assigning IP addresses on wireless networks.
MAC address filtering is not used to restrict which devices can connect to wireless networks.
802.1X with EAP-TLS is used for mutual authentication and key exchange; with all other EAP methods disabled on supplicants and authentication servers.
Evaluated supplicants, authenticators and authentication servers are used for 802.1X authentication implementations.
X.509 certificates are required for devices and human users authenticating to networks using 802.1X.
X.509 certificates are generated using an evaluated certificate authority or hardware security module.
X.509 certificates are protected by logical and physical access controls and encryption, with those issued to human users requiring authentication before use.
The PMK caching period is not set to greater than 1440 minutes (24 hours).
WPA3-Enterprise 192-bit mode is used to protect the confidentiality and integrity of all wireless network traffic.
Wireless networks implement sufficient frequency separation from other wireless networks.
Wireless access points enable the use of the 802.11w amendment to protect management frames.
Instead of deploying a small number of wireless access points that broadcast on high power, a greater number of wireless access points that use less broadcast power are deployed to achieve the desired footprint for wireless networks.
Network devices managing VLANs terminate VLANs belonging to different security domains on separate physical network interfaces.
IPv6 tunnelling is blocked by network security appliances at externally connected network boundaries.
Denial-of-service attack mitigation strategies are discussed with cloud service providers, specifically:
- their capacity to withstand denial-of-service attacks
- costs likely to be incurred as a result of denial-of-service attacks
- availability monitoring and thresholds for notification of denial-of-service attacks
- thresholds for turning off any online services or functionality during denial-of-service attacks
- pre-approved actions that can be undertaken during denial-of-service attacks
- any arrangements with upstream service providers to block malicious network traffic as far upstream as possible.
Domain names for online services are protected via registrar locking and confirming that domain registration details are correct.
Critical online services are segregated from other online services that are more likely to be targeted as part of denial-of-service attacks.
Cloud service providers are used for hosting online services.
Where a high availability requirement exists for website hosting, CDNs that cache websites are used.
If using CDNs, disclosing the IP addresses of web servers under an organisation’s control (referred to as origin servers) is avoided and access to the origin servers is restricted to the CDNs and authorised management networks.
Communications between authenticators and a RADIUS server are encapsulated with an additional layer of encryption using RADIUS over Internet Protocol Security or RADIUS over Transport Layer Security.
VLANs are not used to separate network traffic between an organisation’s networks and public network infrastructure.
An organisation’s networks are segregated from their service providers’ networks.
Cloud service providers’ ability to scale resources dynamically in response to genuine spikes in demand is discussed and verified as part of capacity and availability planning for online services.
Where a high availability requirement exists for online services, the services are architected to automatically transition between availability zones.
Continuous real-time monitoring of the capacity and availability of online services is performed.
Inbound network connections from anonymity networks are blocked.
Outbound network connections to anonymity networks are blocked.
Settings for wireless access points are hardened.
User identity confidentiality is used if available with EAP-TLS implementations.
The use of FT (802.11r) is disabled unless authenticator-to-authenticator communications are secured by an ASD-Approved Cryptographic Protocol.
All data communicated over network infrastructure is encrypted using ASD-approved cryptography.
A protective DNS service is used to block access to known malicious domain names.
Networked management interfaces for IT equipment are not directly exposed to the internet.
Security-relevant events for internet-facing network devices are centrally logged.
Security-relevant events for non-internet-facing network devices are centrally logged.
DNS traffic is encrypted by clients and servers using ASD-approved cryptography.
Internet connectivity for networked devices is strictly limited to those that require access.
Networked management interfaces for IT equipment are only accessible from a dedicated management network that is segregated from the wider network and the internet.
When using MACsec, confidentiality protection mode is enabled using GCM-AES-128, GCM-AES-256, GCM-AES-XPN-128 or GCM-AES-XPN-256, preferably GCM-AES-256 or GCM-AES-XPN-256.
A connectivity association lifetime of less than 24 hours (86400 seconds) is used for MACsec connections.
When using EAP-TLS, each device performs a fresh EAP-TLS authentication each time a new Connectivity Association Key is required.
A secure association lifetime of less than four hours (14400 seconds) is used for MACsec connections.
The use of a Pre-Shared Key as a fallback authentication method for MACsec is disabled.
Not reached from your selection
Cyber security awareness training is undertaken annually by all personnel and covers:
- the purpose of the cyber security awareness training
- security appointments and contacts
- authorised use of systems and their resources
- protection of systems and their resources
- reporting of cyber security incidents and suspected compromises of systems and their resources.
A web usage policy is developed, implemented and maintained.
Personnel are advised of what suspicious contact via online services is and how to report it.
Personnel are advised not to post work-related information on unauthorised online services, and to report cases where such information is posted.
Personnel are advised of security risks associated with posting personal information on online services.
Personnel are advised not to send or receive files via unauthorised online services.
Personnel are advised to maintain separate personal user accounts from any work user accounts they use for online services.
Tailored privileged user training is undertaken annually by all personnel with privileged access to systems and their resources.
Personnel dealing with banking details and payment requests are advised of what business email compromise is and how to manage and report it.
A cyber security awareness training register is developed, implemented and maintained.
Personnel dealing with user account details are advised of what social engineering attacks are, how to manage such situations and how to report them.
A general-purpose AI usage policy is developed, implemented and maintained.
Personnel are advised not to post information about their security clearance and briefings on unauthorised online services, and to report cases where such information is posted.
Personnel are advised to limit posting information about their work-related duties on unauthorised online services, and to report cases where such information is posted.
Personnel are advised to limit posting information about their work-related skills and experience on unauthorised online services, and to report cases where such information is posted.
Personnel are encouraged to use any available privacy settings to restrict who can view personal information they post on online services.
Personnel positively identify requestors using a pre-established authentication method or independent trusted communication channel before actioning requests to modify user account details, modify banking details or conduct financial transactions.
Not reached from your selection
IT equipment and media are secured when not in use.
Unauthorised people are prevented from observing systems, in particular workstation displays and keyboards, within facilities.
Classified systems are secured in facilities that meet the requirements for a security zone suitable for their classification.
Server rooms, communications rooms and security containers are not left in unsecured states.
Classified servers, network devices and cryptographic equipment are secured in server rooms or communications rooms that meet the requirements for a security zone suitable for their classification.
Keys or equivalent access mechanisms to server rooms, communications rooms and security containers are appropriately controlled.
Physical security is implemented to protect network devices in public areas from physical damage or unauthorised access.
Classified servers, network devices and cryptographic equipment are secured in security containers suitable for their classification taking into account the combination of security zones they reside in.
Non-classified systems are secured in suitably secure facilities.
Non-classified servers, network devices and cryptographic equipment are secured in suitably secure server rooms or communications rooms.
Non-classified servers, network devices and cryptographic equipment are secured in suitably secure security containers.
Not reached from your selection
Security requirements associated with the confidentiality, integrity and availability of data are documented in contractual arrangements with service providers and regularly reviewed to ensure they remain fit for purpose.
The requirement for service providers to report cyber security incidents to a designated point of contact as soon as possible after they occur or are discovered is documented in contractual arrangements with service providers.
An organisation’s systems are not accessed or administered by a service provider unless a contractual arrangement exists between the organisation and the service provider to do so.
Service providers, including any subcontractors, provide an appropriate level of protection for any data entrusted to them or their services.
Types of data and its ownership is documented in contractual arrangements with service providers.
A supply chain risk assessment is performed for suppliers of operating systems, applications, IT equipment, OT equipment and services to assess the impact to a system’s security risk profile.
Suppliers identified as high risk by a cyber supply chain risk assessment are not used.
Operating systems, applications, IT equipment, OT equipment and services are procured from suppliers that have demonstrated a commitment to the security of their products and services.
A shared responsibility model is created, documented and shared between suppliers and their customers to articulate the security responsibilities of each party.
Outsourced cloud service providers and their non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET cloud services undergo an IRAP assessment, using the latest release of the ISM available prior to the beginning of the IRAP assessment (or a subsequent release), at least every 24 months.
The right to verify compliance with security requirements is documented in contractual arrangements with service providers.
The regions or availability zones where data will be processed, stored and communicated, as well as a minimum notification period for any configuration changes, is documented in contractual arrangements with service providers.
Access to all logs relating to an organisation’s data and services is documented in contractual arrangements with service providers.
The storage of data in a portable manner that enables backups, service migration and service decommissioning without any loss of data is documented in contractual arrangements with service providers.
A minimum notification period of one month for the cessation of any services by a service provider is documented in contractual arrangements with service providers.
If an organisation’s systems are accessed or administered by a service provider in an unauthorised manner, it is treated as a cyber security incident and the organisation is immediately notified.
Suppliers of operating systems, applications, IT equipment, OT equipment and services associated with systems are identified.
Operating systems, applications, IT equipment, OT equipment and services are procured from suppliers that have a strong track record of maintaining the security of their own systems.
An outsourced cloud service register is developed, implemented, maintained and regularly verified.
An outsourced cloud service register contains the following for each outsourced cloud service:
- cloud service provider’s name
- cloud service’s name
- purpose for using the cloud service
- sensitivity or classification of data involved
- due date for the next security control assessment of the cloud service
- contractual arrangements for the cloud service
- organisational point of contact for the cloud service
- 24/7 contact details for the cloud service provider.
A managed service register is developed, implemented, maintained and regularly verified.
A managed service register contains the following for each managed service:
- managed service provider’s name
- managed service’s name
- purpose for using the managed service
- sensitivity or classification of data involved
- due date for the next security control assessment of the managed service
- contractual arrangements for the managed service
- organisational point of contact for the managed service
- 24/7 contact details for the managed service provider.
The right to verify compliance with security requirements documented in contractual arrangements with service providers is regularly exercised.
A supplier relationship management policy is developed, implemented and maintained.
An approved supplier list is developed, implemented and maintained.
Operating systems, applications, IT equipment, OT equipment and services are sourced from approved suppliers.
Multiple potential suppliers are identified for sourcing critical operating systems, applications, IT equipment, OT equipment and services.
Sufficient spares of critical IT equipment and OT equipment are sourced and kept in reserve.
Operating systems, applications, IT equipment, OT equipment and services are delivered in a manner that maintains their integrity.
The integrity of operating systems, applications, IT equipment, OT equipment and services are assessed as part of acceptance of products and services.
The authenticity of operating systems, applications, IT equipment, OT equipment and services are assessed as part of acceptance of products and services.
Managed service providers and their non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET managed services undergo an Infosec Registered Assessor Program (IRAP) assessment, using the latest release of the ISM available prior to the beginning of the IRAP assessment (or a subsequent release), at least every 24 months.
A minimum notification period of one month by service providers for significant changes to their own service provider arrangements is documented in contractual arrangements with service providers.
Break clauses associated with failure to meet security requirements are documented in contractual arrangements with service providers.
Operating systems, applications, IT equipment, OT equipment and services are procured from suppliers that have demonstrated a commitment to transparency for their products and services.
Access by a service provider to an organisation’s systems is restricted to remote management tools, source network addresses and time windows explicitly approved by the organisation.
All access to an organisation’s systems by a service provider is independently logged by the organisation in a manner that the service provider cannot modify or delete, and analysed in a timely manner to detect any anomalous, unexpected or unauthorised activity.
Reached from your selection
An accurate and consistent time source is used for event logging.
Not reached from your selection
Event logs from workstations are analysed in a timely manner to detect cyber security events.
Cyber security personnel have access to sufficient tools to facilitate the detection of cyber security events and the identification of cyber security incidents.
A security monitoring policy is developed, implemented and maintained.
For each event logged, the date and time of the event, the relevant user or process, the relevant filename, the event description, and the information technology equipment involved are captured.
Cyber security events are analysed in a timely manner to identify cyber security incidents.
A centralised event logging facility is implemented.
A vulnerability scanner is used at least daily to identify missing patches or updates for vulnerabilities in online services.
A vulnerability scanner is used at least weekly to identify missing patches or updates for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products.
A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in applications other than office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products.
A vulnerability scanner is used at least daily to identify missing patches or updates for vulnerabilities in operating systems of internet-facing servers and internet-facing network devices.
A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices.
A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in drivers.
A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in operating systems of IT equipment other than workstations, servers and network devices.
An automated method of asset discovery is used at least fortnightly to support the detection of assets for subsequent vulnerability scanning activities.
A vulnerability scanner with an up-to-date vulnerability database is used for vulnerability scanning activities.
Event logs are protected from unauthorised modification and deletion.
A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in firmware.
Event logs from internet-facing servers are analysed in a timely manner to detect cyber security events.
Event logs from non-internet-facing servers are analysed in a timely manner to detect cyber security events.
The likelihood of system compromise is frequently assessed when working exploits exist for unmitigated vulnerabilities.
To the extent possible, event logs are captured and stored in a consistent and structured format.
Event logs from internet-facing network devices are analysed in a timely manner to detect cyber security events.
Event logs from non-internet-facing network devices are analysed in a timely manner to detect cyber security events.
Event logs sent to a centralised event logging facility are sent as soon as possible after they occur.
Event logs sent to a centralised event logging facility are encrypted in transit using Australian Signals Directorate (ASD)-approved cryptography.
Event logs are protected from unauthorised access.
Event logs from critical servers are analysed in a timely manner to detect cyber security events.
Event logs from security products are analysed in a timely manner to detect cyber security events.
Event logs are retained in a searchable manner for at least 12 months.
Event logs are retained as per minimum retention requirements for various classes of records as set out by the National Archives of Australia’s Administrative Functions Disposal Authority Express (AFDA Express) Version 2 publication.
Cyber threat intelligence services are used to support the detection of cyber security events and the identification of cyber security incidents.
Suitable AI models are used to augment the detection of cyber security events and the identification of cyber security incidents.
Vulnerability assessments and penetration tests are conducted for systems prior to their deployment, including prior to the deployment of significant changes, and at least every six months thereafter.
Suitable AI models are used to augment vulnerability assessments and penetration tests.
Threat hunting activities, informed by current strategic and sector-specific cyber threat intelligence, are conducted at least every three months.
Reached from your selection
Web applications that support Single Sign On equally support Single Logout.
Not reached from your selection
Development, testing, staging and production environments are segregated.
Secure by Design principles and practices are followed throughout the software development life cycle.
Software is comprehensively tested for vulnerabilities using SAST, DAST and SCA prior to its initial release, any subsequent release, and periodically to help identify any previously unidentified vulnerabilities.
The OWASP Application Security Verification Standard is used in the development of web applications.
Threat modelling is used in support of the software development life cycle.
Robust web application frameworks are used in the development of web applications.
Validation and sanitisation are performed on all input received over the internet by software.
Output encoding is performed on all output produced by web applications.
All queries to databases from software are filtered for legitimate content and correct syntax.
Parameterised queries or stored procedures, instead of dynamically generated queries, are used by software for database interactions.
Software is designed or configured to provide as little error information as possible about the structure of databases.
Development and modification of software only take place in development environments.
Data from production environments is not used in non-production environments unless the non-production environment is secured to at least the same level as the production environment.
Unauthorised access to the authoritative source for software is prevented.
Content-Security-Policy, Hypertext Transfer Protocol Strict Transport Security and X-Frame-Options are specified by web server software via security policy in response headers.
All queries to databases from software, and any resulting crash or error messages, are centrally logged.
All web application content is offered exclusively using HTTPS.
A vulnerability disclosure program is implemented to assist with the secure development and maintenance of products and services.
A ‘security.txt’ file is hosted for each of an organisation’s internet-facing website domains to assist in the responsible disclosure of vulnerabilities in the organisation’s products and services.
A software bill of materials is produced and made available to consumers of software.
Vulnerabilities identified in software are resolved in a timely manner.
A vulnerability disclosure policy is developed, implemented and maintained.
Vulnerability disclosure processes, and supporting vulnerability disclosure procedures, are developed, implemented and maintained.
SecDevOps practices are used for software development.
Files containing executable content are digitally signed by a certificate with a verifiable chain of trust as part of software development.
Installers, patches and updates are digitally signed or provided with cryptographic checksums as part of software development.
Secure configuration guidance, in the form of a hardening guide or loosening guide, is produced and made available to consumers as part of software development.
Unauthorised modification of the authoritative source for software is prevented.
Authentication and authorisation of clients is performed when clients call network APIs that facilitate access to data not authorised for release into the public domain and are accessible over the internet.
Authentication and authorisation of clients is performed when clients call network APIs that facilitate modification of data and are accessible over the internet.
The OWASP Top 10 Proactive Controls are used in the development of web applications.
The OWASP Top 10 are mitigated in the development of web applications.
The OWASP API Security Top 10 are mitigated in the development of web APIs.
Vulnerabilities identified in software are publicly disclosed in a responsible and timely manner, including with Common Weakness Enumeration and Common Platform Enumeration information.
In resolving vulnerabilities, root cause analysis is performed and, to the greatest extent possible, entire vulnerability classes are remediated.
Network API calls that facilitate modification of data, or access to data not authorised for release into the public domain, and are accessible over the internet, are centrally logged.
Security-relevant usage, error messages and crashes for software are centrally logged.
The OWASP Mobile Application Security Verification Standard is used in the development of mobile applications.
Generative AI applications evaluate user prompts to detect and mitigate adversarial inputs or suffixes designed to elicit unintended behaviour or assist in the generation of sensitive or harmful content.
Authentication and authorisation of clients is performed when clients call network APIs that facilitate modification of data but are not accessible over the internet.
Authentication and authorisation of clients is performed when clients call network APIs that facilitate access to data not authorised for release into the public domain but are not accessible over the internet.
Network API calls that facilitate modification of data, or access to data not authorised for release into the public domain, but are not accessible over the internet, are centrally logged.
Validation and sanitisation are performed on all input received over a local network by software.
An authoritative source for software is established and maintained.
The authoritative source for software is used for all software development activities.
An issue tracking solution is used to link software development tasks to security issues and decisions, change or feature requests, programming issues, or bug fixes.
All software artefacts are scanned for malicious content before being imported into the authoritative source for software.
All software artefacts are verified by a digital signature, or a secure hash provided over a secure channel, before being imported into the authoritative source for software.
All software artefacts are tested to detect known weaknesses using static application security testing (SAST), dynamic application security testing (DAST) or software composition analysis (SCA), depending on the software artefact type, before being imported into the authoritative source for software.
The authoritative source for software restricts the use and import of third-party libraries and software components to trustworthy sources.
Scanning is used during commits to identify plain text or encoded credentials, keys and secrets, which are then blocked from being stored in the authoritative source for software.
Compilers, interpreters and build tools (including pipelines) that provide security features to improve executable file security are implemented and such security features are used.
The build solution ensures that all automated testing is completed without warnings, alerts or errors before building software artefacts.
All software security requirements are documented, stored securely and maintained throughout the software development life cycle.
Security design decisions are documented and reviewed throughout the software development cycle.
Security roles, responsibilities and knowledge required to support the software development life cycle are identified and documented.
Security responsibilities for software developers are identified and documented.
Software developers that lack sufficient cyber security knowledge and skills required for their projects or tasks undertake suitable training or upskilling on secure software development and programming practices.
A software developer cyber security knowledge and skills register is developed, implemented and maintained.
The software threat model is reviewed throughout the software development life cycle to ensure it reflects the as-built software and any changes to the threat environment.
Secure programming practices for the chosen programming language are used for software development.
Memory-safe programming languages, or less preferably memory-safe programming practices, are used for software development.
Secure by Default principles and practices are followed throughout the software development life cycle, including by ensuring that all built-in security measures are included and enabled in the base product at no extra cost to consumers.
Software is architected and structured to support readability and maintainability.
Software has no default credentials; however, if credentials are required, they are created on first install by the installing organisation.
Application backwards compatibility does not compromise any security measures or features.
Where software allows user impersonation, sensitive data is not logged and appropriate permissions are set.
Where software allows an authentication factor to be reset for a human user, the human user is notified of the reset through a secondary channel.
Where software supports multiple user roles, non-administrative users are prevented from altering their profile permissions or privileges.
When user permissions or credentials are changed, software forces all impacted users to re-authenticate.
When digital signatures are processed by software, they are validated against a certificate trust chain and checked for revocation using a Certificate Revocation List or with the Online Certificate Status Protocol.
Software generates sufficient event logs to support the detection of cyber security events.
Event logs produced by software ensure that any sensitive data is protected.
End of life procedures for software, including procedures for software removal and the archival or destruction of user accounts and data, are produced and made available to consumers.
If a software bill of materials is available for imported third-party software components, it is used during software development to ensure such software components have no known vulnerabilities.
If a software build provenance is available for imported third-party software components, it is used during software development to ensure such software components are built to an appropriate standard.
A software build provenance is produced and made available to consumers of software.
All input validation rules are documented, implemented in code, and tested using both positive and negative unit tests and integration tests.
Data sources and serialised data inputs are validated before being deserialised.
File uploads or input are restricted to specific file types, with malicious content scanning occurring prior to file access, file execution or file storage.
Code reviews are utilised to ensure software components meets Secure by Design principles and practices as well as secure programming practices.
Peer reviews are conducted on all critical and security-related software components.
Unit testing and integration testing, covering both positive and negative use cases, are used for software components to ensure code quality and correctness.
If supported, web application session cookies set the HttpOnly flag, Secure flag and the SameSite flag by default.
Web application session cookies contain only digitally signed opaque bearer tokens.
Web application session cookies using opaque bearer tokens that are not digitally signed use non-sequential random identifiers with a minimum of 128 bits of entropy, preferably 256 bits of entropy.
Web application sessions are centrally managed server side.
AI models are stored in a non-executable file format that does not allow arbitrary code execution.
If a cryptographic bill of materials is available for imported third-party software components, it is used during software development to ensure such software components provide support for standardised implementations of ASD-Approved Cryptographic Algorithms.
A cryptographic bill of materials is produced and made available to consumers of software.
AI-specific documentation, including AI model cards and AI system cards (or equivalent artefacts), is used to document AI model characteristics, system architectures, use cases and security risks.
The exposure of exact AI model confidence scores in API outputs or user interfaces is prevented.
The source and integrity of AI models, structures and weights are verified.
The source and integrity of training data for AI models is verified.
Data validation and verification techniques are used to ensure the reliability and accuracy of training data used by AI models.
AI model performance metrics are monitored and anomalies are investigated.
Rate limiting is applied to inference queries for AI models.
Resource limits are enforced for AI models.
Access control policies are implemented to enforce fine-grained permissions for AI applications.
Role-based access controls are implemented for AI applications to restrict access to sensitive data.
Content filtering is implemented by AI applications to detect and block sensitive data exposure and improper output.
Existing software artefacts in the authoritative source for software are periodically tested to detect known weaknesses using SAST, DAST or SCA, depending on the software artefact type, throughout the software development life cycle.
Organisational data generated, collected or processed by AI applications is not used for training, fine-tuning or improving AI models unless informed and explicit consent has been obtained from data owners in advance.
A secure software development policy is developed, implemented and maintained.
Software developers that lack sufficient cyber security knowledge and skills required for their projects or tasks are not used.
Suitable AI models are used to augment software security testing.
All prompts and outputs associated with chat sessions are securely deleted when chat sessions are removed from AI applications.
Software artefact dependencies are pinned to approved versions in source code.
Software is built using reproducible build practices that enable independent verification that release artefacts were produced from the stated source code.
Agentic AI applications are restricted to the minimum set of tools, functions and permissions required for their intended purpose.
Tools invoked by agentic AI applications are subject to both the access controls of the invoking user and agent-specific, task-scoped authorisation, with effective permissions limited to the minimum permitted by both.
External content retrieved by agentic AI applications is treated as untrusted data throughout processing, is clearly delimited from system instructions, is subject to validation and sanitisation measures applied to other untrusted input, remains untrusted following such processing, and is prevented from modifying or overriding system instructions, security policies, access controls, tool permissions or human approval requirements.
All tool invocations, external requests and outputs generated by agentic AI applications are centrally logged with sufficient detail to support cyber security incident investigations.
Reached from your selection
Systems have a logon banner that reminds personnel of their security responsibilities when accessing the system and its resources.
When systems cannot support multi-factor authentication, single-factor authentication using passwords is implemented instead.
Passwords used for single-factor authentication on non-classified, OFFICIAL: Sensitive and PROTECTED systems are a minimum of 15 characters.
Services are configured with a session lock that:
- activates after a maximum of 15 minutes of human user inactivity, a maximum of 12 hours of overall session time or when manually activated
- blocks access to all session content
- requires re-authentication by human users using all authentication factors to unlock the session
- denies human users the ability to disable the session locking mechanism.
Interactive user sessions are terminated and workstations are restarted at least daily.
Multi-factor authentication is used to authenticate unprivileged human users of systems.
LAN Manager and NT LAN Manager authentication methods are disabled.
Multi-factor authentication is used to authenticate privileged human users of systems.
Credentials set for user accounts are randomly generated.
Multi-factor authentication uses either: something people have and something people know, or something people have that is unlocked by something people know or are.
User accounts, except for break glass accounts, are protected by fixed or risk-based lockout mechanisms aligned to a maximum of five failed logon attempts, with either indefinite or automated lockout durations.
Multi-factor authentication is used to authenticate human users to their organisation’s online services that process, store or communicate their organisation’s sensitive data.
Multi-factor authentication is used to authenticate human users of data repositories.
Users are authenticated before they are granted access to a system and its resources.
Passwords using a sequence of words for single-factor authentication are not constructed using:
- a list of categorised words
- a real sentence in a natural language
- song lyrics, movie or television show quotes, literature, or any other publicly available material
- less than 4 random words for non-classified, OFFICIAL: Sensitive and PROTECTED systems; 5 random words for SECRET systems; or 6 random words for TOP SECRET systems.
Passwords used for multi-factor authentication on non-classified, OFFICIAL: Sensitive and PROTECTED systems are a minimum of 6 characters.
Credentials for user accounts are changed if:
- they are compromised or suspected of being compromised
- they are discovered stored on systems in the clear
- they are discovered being transferred across networks in the clear
- membership of a shared user account changes.
Human users provide sufficient evidence to verify their identity when first requesting credentials, when requesting the reset of any credentials, when requesting the temporary disabling of any credentials, and when requesting the enrolment or re-enrolment of any credentials.
Credentials for human users are provided via a secure communications channel or, if not possible, split into two parts with one part provided to the human user and the other part provided to their supervisor.
Credentials provided to human users are changed on first use.
Credentials are not reused by users across different systems.
Credentials are obscured as they are entered into systems.
Authentication methods susceptible to replay attacks are disabled.
A method of emergency access to systems and their resources is documented and tested at least once when initially implemented and each time fundamental information technology infrastructure changes occur.
Break glass accounts are only used when normal authentication processes cannot be used.
Break glass accounts are only used for specific authorised activities.
Use of break glass accounts is centrally logged.
Break glass account credentials are changed by the account custodian after they are accessed by any other party.
Break glass accounts are tested after credentials are changed.
Multi-factor authentication is used to authenticate human users to third-party online services that process, store or communicate their organisation’s sensitive data.
Multi-factor authentication (where available) is used to authenticate human users to third-party online services that process, store or communicate their organisation’s non-sensitive data.
Multi-factor authentication is used to authenticate customers to online customer services that process, store or communicate sensitive customer data.
Multi-factor authentication used for authenticating human users of systems is phishing-resistant.
Credentials for break glass accounts, local administrator accounts and service accounts are long, unique, unpredictable and managed.
Credential Guard functionality is enabled.
Cached credentials are limited to one previous logon.
Credentials for built-in Administrator accounts, break glass accounts, local administrator accounts and service accounts are a minimum of 30 characters.
Local Security Authority protection functionality is enabled.
Multi-factor authentication used for authenticating human users of online services is phishing-resistant.
Multi-factor authentication used for authenticating customers of online customer services provides a phishing-resistant option.
Multi-factor authentication used for authenticating customers of online customer services is phishing-resistant.
Multi-factor authentication is used to authenticate human users to their organisation’s online customer services that process, store or communicate their organisation’s sensitive customer data.
Multi-factor authentication is used to authenticate human users to third-party online customer services that process, store or communicate their organisation’s sensitive customer data.
Multi-factor authentication used for authenticating human users of data repositories is phishing-resistant.
Remote Credential Guard functionality is enabled.
When multi-factor authentication is used to authenticate human users or customers to online services or online customer services, all other authentication protocols that do not support multi-factor authentication are disabled.
When multi-factor authentication is used to authenticate human users to online services, online customer services, systems or data repositories – that process, store or communicate their organisation’s sensitive data or sensitive customer data – human users are prevented from self-enrolling into multi-factor authentication from untrustworthy devices.
Credentials for built-in Administrator accounts, break glass accounts, local administrator accounts and service accounts are randomly generated.
Credential hint functionality is not used for systems.
When phishing-resistant multi-factor authentication is used by human users, other non-phishing-resistant multi-factor authentication options are disabled for their user accounts.
Systems are configured with a screen lock that:
- activates after a maximum of 15 minutes of human user inactivity, or when manually activated
- conceals all content on the screen
- ensures that the screen does not enter a power saving state before the screen lock is activated
- requires re-authentication by human users using all authentication factors to unlock the system
- denies human users the ability to disable the screen locking mechanism.
Security questions are not used for authentication purposes.
Email is not used for out-of-band authentication purposes.
Passwords appearing in lists of commonly used passwords or lists of compromised passwords are not used.
Maximum length limits for passwords are not less than 64 characters.
Password complexity requirements are not imposed for passwords.
All ASCII printable characters are supported for passwords.
Risk-based access decisions, informed by contextual signals, are enforced for access to systems and their resources.
The OAuth device code authentication flow is disabled unless required, and where required, is restricted to authorised user accounts and managed devices.
Authentication tokens, session cookies and refresh tokens are cryptographically bound to the device on which they were issued.
Active sessions, refresh tokens and other authentication artefacts are revoked when credentials are reset or re-enrolled, when credentials are compromised or suspected of being compromised, when a device no longer meets compliance requirements, or when high-risk sign-in activity is detected.
Not reached from your selection
Requests for unprivileged access to systems and their resources are validated when first requested.
A secure record is maintained for the life of systems and their resources that covers the following for each human user:
- their unique identifier
- their signed agreement to abide by system usage policies
- who authorised their access
- when their access was granted
- the level of access they were granted
- when their access, and their level of access, was last reviewed
- when their level of access was changed, and to what extent (if applicable)
- when their access was withdrawn (if applicable).
Users granted access to systems and their resources are uniquely identifiable.
The use of shared user accounts is strictly controlled, and users of such accounts are uniquely identifiable.
Physical credentials are kept separate from systems they are used to authenticate to, except for when performing authentication activities.
Access to systems and their resources are removed or suspended the same day users no longer have a legitimate requirement for access.
Access requirements for systems and their resources are documented in their system security plan.
Personnel undergo appropriate employment screening and, where necessary, hold an appropriate security clearance before being granted access to systems and their resources.
Personnel receive any necessary briefings before being granted access to systems and their resources.
When personnel are granted temporary access to systems and their resources, effective security controls are put in place to restrict their access to only data required for them to undertake their duties or functions.
Privileged human users are assigned a dedicated privileged user account to be used solely for duties requiring privileged access.
Privileged user accounts (excluding those explicitly authorised to access online services) are prevented from accessing the internet, email and web services.
Unique privileged user accounts are used for administering individual server applications.
Credentials stored on systems are protected by a password manager; a hardware security module; or by salting, hashing and stretching them before storage within a database.
Unprivileged access to systems and their resources are disabled after 45 days of inactivity.
Requests for privileged access to systems and their resources are validated when first requested.
Privileged access to systems and their resources is limited to only what is required for users to undertake their duties or functions.
Privileged access events are centrally logged.
Use of unprivileged access is centrally logged.
Personnel who are contractors are identified as such.
Access to systems and their resources are removed or suspended as soon as practicable when users are detected undertaking malicious activities.
Service accounts are created as group Managed Service Accounts.
Privileged access to systems and their resources are disabled after 12 months unless revalidated.
Privileged access to systems and their resources are disabled after 45 days of inactivity.
Just-in-time administration is used for the administration of systems and their resources.
Privileged user account and security group management events are centrally logged.
Successful and unsuccessful multi-factor authentication events are centrally logged.
Credentials for the Kerberos Key Distribution Center’s service account (KRBTGT) are changed twice, allowing for replication to all Microsoft AD DS domain controllers in-between each change, if the domain has been directly compromised, the domain is suspected of being compromised or they have not been changed in the past six months.
Unprivileged access to systems and their resources is limited to only what is required for users to undertake their duties or functions.
A system usage policy is developed, implemented and maintained.
Personnel agree to abide by system usage policies before being granted access to systems and their resources.
Systems are scanned at least monthly to identify any credentials that are being stored in the clear.
Privileged user accounts explicitly authorised to access online services are strictly limited to only what is required for users to undertake their duties or functions.
Successful and unsuccessful single-factor authentication events are centrally logged.
Credentials for the built-in Administrator account in each domain are long, unique, unpredictable and managed.
Credentials for computer accounts are changed if they are compromised, they are suspected of being compromised or they have not been changed in the past 30 days.
Microsoft AD FS token-signing and encryption certificates are changed twice in quick succession if they are compromised, they are suspected of being compromised or they have not been changed in the past 12 months.
Private keys for Microsoft AD CS certification authority servers are protected by a hardware security module.
Each AI agent is assigned a unique identity that is distinct from the user accounts of personnel and the identities of other AI agents.
An AI agent register is developed, implemented, maintained and regularly verified.
An AI agent register contains the following for each AI agent:
- its unique identifier
- its owner and business purpose
- the identities assigned to it
- any user accounts and credentials it uses
- the tools, permissions and data repositories it can access.
Human users are prevented from granting consent to third-party OAuth applications, with such consent granted only by an authorised administrator.
OAuth application consents, including their granted permissions, are reviewed at least every six months, with unused applications and excessive permissions revoked.
Consent grants, token issuance and token use for third-party OAuth applications are centrally logged.
Applications and workloads use short-lived dynamically issued credentials in preference to long-lived static credentials.
Static credentials used by applications and workloads are centrally managed using a credential or secrets management solution.
Applications and workloads use unique credentials that are not shared with other applications or workloads, or across development, testing, staging and production environments.
Static credentials used by applications and workloads are changed if:
- they are compromised or suspected of being compromised
- they are discovered stored on systems in the clear
- they are discovered being transferred across networks in the clear.
Credentials for user accounts are revoked when they are no longer required.
Static credentials used by applications and workloads are revoked when they are no longer required.
Reached from your selection
Automatic execution features for removable media are disabled.
If there is no business requirement for writing to removable media and devices, such functionality is disabled via the use of a device access control application or by disabling external communication interfaces.
External communication interfaces that allow DMA are disabled.
Unneeded user accounts, components, services and functionality of operating systems are disabled or removed.
Default user accounts or credentials for operating systems, including for any pre-configured user accounts, are changed, disabled or removed during initial setup.
Application control is implemented on workstations.
Users cannot disable or bypass application control, and are not exempted from application control, except when using local administrator accounts or break glass accounts.
Application control is implemented using cryptographic hash rules, publisher certificate rules or path rules.
All temporary installation files created during server application installation processes are removed after server applications have been installed.
Server applications are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
Unneeded user accounts, components, services and functionality of server applications are disabled or removed.
Server applications are configured to run as a separate user account with the minimum privileges needed to perform their functions.
The user accounts under which server applications run have limited access to their underlying server’s file system.
Default user accounts or credentials for server applications, including for any pre-configured user accounts, are changed, disabled or removed during initial setup.
When implementing application control using path rules, only approved users can modify approved files and write to approved folders.
SOEs are used for workstations and servers.
The latest release, or the previous release, of operating systems are used.
64-bit versions of operating systems are used.
Operating systems are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
A software firewall is implemented on workstations and servers to restrict inbound and outbound network connections to an organisation-approved set of applications and services.
If there is no business requirement for reading from removable media and devices, such functionality is disabled via the use of a device access control application or by disabling external communication interfaces.
When implementing application control using publisher certificate rules, publisher names and product names are used.
Application control is implemented on internet-facing servers.
Microsoft’s recommended application blocklist is implemented.
Application control rulesets are validated at least annually.
SOEs are reviewed and updated at least annually.
Unprivileged human users do not have the ability to install unapproved applications.
When using a software-based isolation mechanism that consumes shared physical computing resources, the configuration of the isolation mechanism is hardened by removing unneeded functionality and restricting access to the administrative interface used to manage the isolation mechanism.
When using a software-based isolation mechanism that consumes shared physical computing resources, the underlying operating system is hardened.
When using a software-based isolation mechanism that consumes shared physical computing resources, patches, updates or vendor mitigations for vulnerabilities are applied to the isolation mechanism and underlying operating system in a timely manner.
SOEs provided by third parties are scanned for malicious code and configurations.
Internet Explorer 11 is disabled or removed.
.NET Framework 3.5 (includes .NET 2.0 and 3.0) is disabled or removed.
Application control is implemented on non-internet-facing servers.
Application control restricts the execution of executables, libraries, scripts, installers, compiled HTML, HTML applications and control panel applets to an organisation-approved set.
Application control restricts the execution of drivers to an organisation-approved set.
Microsoft’s vulnerable driver blocklist is implemented.
Early Launch Antimalware, Secure Boot, Trusted Boot and Measured Boot functionality is enabled.
When implementing application control using path rules, only approved users can change file system permissions for approved files and folders.
When using a software-based isolation mechanism that consumes shared physical computing resources, the isolation mechanism or underlying operating system is replaced when it is no longer supported by a vendor.
Application control is applied to user profiles and temporary folders used by operating systems, web browsers and email clients.
Application control is applied to all locations other than user profiles and temporary folders used by operating systems, web browsers and email clients.
Memory integrity functionality is enabled.
Approved configurations for operating systems are developed, implemented and maintained.
Approved configurations for server applications are developed, implemented and maintained.
Microsoft AD DS domain controllers, Microsoft AD CS servers, Microsoft AD FS servers and Microsoft Entra Connect servers are only used for their designed role and no other applications or services are installed, unless they are security related.
Backups of Microsoft AD DS domain controllers, Microsoft AD CS servers, Microsoft AD FS servers and Microsoft Entra Connect servers are encrypted using ASD-approved cryptography, stored securely and only accessible to backup administrator accounts.
Soft matching between Microsoft AD DS and Microsoft Entra ID is disabled following initial synchronisation activities.
Hard match takeover is disabled for Microsoft Entra Connect servers.
Privileged user accounts are not synchronised between Microsoft AD DS and Microsoft Entra ID.
Extensions for server applications are restricted to an organisation-approved set.
Digital signature verification functionality for drivers is enforced before they are loaded.
The ability to install, load or modify kernel-mode code, including drivers, kernel modules and extensions, is limited to privileged users who require such abilities as part of their duties or functions.
Not reached from your selection
Unprivileged human users do not have the ability to uninstall or disable approved applications.
Security-relevant events for Microsoft Windows operating systems are centrally logged.
Vendors that have demonstrated a commitment to Secure by Design and Secure by Default principles and practices, including secure programming practices and either memory-safe programming languages or less preferably memory-safe programming practices, are used for user applications.
A HIPS or EDR solution is implemented on critical servers and high-value servers.
Extensions for user applications are restricted to an organisation-approved set.
A HIPS or EDR solution is implemented on workstations.
Web browsers are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
An antivirus application is implemented on workstations and servers with:
- signature-based detection functionality enabled and set to a high level
- heuristic-based detection functionality enabled and set to a high level
- reputation rating functionality enabled
- ransomware protection functionality enabled
- detection signatures configured to update at least daily
- regular scanning configured for all fixed disks and removable media.
When using a software-based isolation mechanism that consumes shared physical computing resources, the isolation mechanism is from a vendor that has demonstrated a commitment to Secure by Design and Secure by Default principles and practices, including secure programming practices and either memory-safe programming languages or less preferably memory-safe programming practices.
The latest release of email clients, office productivity suites, PDF applications, security products and web browsers, including their extensions, are used.
Unneeded user accounts, components, services and functionality of user applications are disabled or removed.
The latest release of internet-facing server applications is used.
Web browsers do not process web advertisements from the internet.
Web browsers do not process Java from the internet.
Only privileged human users responsible for checking that Microsoft Office macros are free of malicious code can write to and modify content within Trusted Locations.
Microsoft Office macros in files originating from the internet are blocked.
Microsoft Office macro security settings cannot be changed by human users.
Unprivileged human users are prevented from running script execution engines, including:
- Windows Script Host (cscript.exe and wscript.exe)
- PowerShell (powershell.exe, powershell_ise.exe and pwsh.exe)
- Command Prompt (cmd.exe)
- Windows Management Instrumentation (wmic.exe)
- Microsoft Hypertext Markup Language (HTML) Application Host (mshta.exe).
Operating system exploit protection functionality is enabled.
Microsoft Office is configured to prevent activation of Object Linking and Embedding packages.
Unprivileged users are prevented from bypassing, disabling or modifying security functionality of operating systems.
Web browser security settings cannot be changed by human users.
Microsoft’s attack surface reduction rules are implemented.
When using a software-based isolation mechanism that consumes shared physical resources, integrity monitoring and centralised event logging is performed for the isolation mechanism and underlying operating system.
Privileged user accounts are members of the Protected Users security group.
Windows PowerShell 2.0 is disabled or removed.
PowerShell is configured to use Constrained Language Mode.
PowerShell module logging, script block logging and transcription events are centrally logged.
PowerShell script block logs are protected by Protected Event Logging functionality.
Allowed and blocked application control events are centrally logged.
Microsoft Office is blocked from creating child processes.
Microsoft Office is blocked from creating executable content.
Microsoft Office is blocked from injecting code into other processes.
PDF applications are blocked from creating child processes.
Microsoft Office macros are disabled for human users that do not have a demonstrated business requirement.
Microsoft Office macro antivirus scanning is enabled.
Microsoft Office macros are blocked from making Win32 API calls.
Only Microsoft Office macros running from within a sandboxed environment, a Trusted Location or that are digitally signed by a trusted publisher are allowed to execute.
Microsoft Office macros digitally signed by an untrusted publisher cannot be enabled via the Message Bar or Backstage View.
Microsoft Office’s list of trusted publishers is validated at least annually.
Vendors that have demonstrated a commitment to Secure by Design and Secure by Default principles and practices, including secure programming practices and either memory-safe programming languages or less preferably memory-safe programming practices, are used for operating systems.
Email client security settings cannot be changed by human users.
Default user accounts or credentials for user applications, including for any pre-configured user accounts, are changed, disabled or removed during initial setup.
Office productivity suite security settings cannot be changed by human users.
PDF application security settings cannot be changed by human users.
Security product security settings cannot be changed by human users.
Vendors that have demonstrated a commitment to Secure by Design and Secure by Default principles and practices, including secure programming practices and either memory-safe programming languages or less preferably memory-safe programming practices, are used for server applications.
Microsoft AD DS domain controllers are administered using dedicated domain administrator user accounts that are not used to administer other systems.
The Print Spooler service is disabled on Microsoft AD DS domain controllers.
Passwords are not stored in Group Policy Preferences.
Security-relevant events for Microsoft AD DS domain controllers, Microsoft AD CS servers, Microsoft AD FS servers and Microsoft Entra Connect servers are centrally logged.
Only service accounts and computer accounts are configured with Service Principal Names (SPNs).
User accounts are provisioned with the minimum privileges required.
Duplicate SPNs do not exist within the domain.
Privileged user accounts are configured as sensitive and cannot be delegated.
User accounts require Kerberos pre-authentication.
The UserPassword attribute for user accounts is not used.
Account properties accessible by unprivileged users are not used to store passwords.
User account passwords do not use reversible encryption.
Unprivileged user accounts cannot add machines to the domain.
Dedicated privileged service accounts are used to add machines to the domain.
User accounts with unconstrained delegation are reviewed at least annually, and those without an SPN or demonstrated business requirement are removed.
Computer accounts that are not Microsoft AD DS domain controllers are not trusted for delegation to services.
When a user account is disabled, it is removed from all security group memberships.
The Pre-Windows 2000 Compatible Access security group does not contain user accounts.
Office productivity suites are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
PDF applications are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
Command line process creation events are centrally logged.
Microsoft Office macros are checked to ensure they are free of malicious code before being digitally signed or placed within Trusted Locations.
Microsoft Office macros digitally signed by signatures other than V3 signatures cannot be enabled via the Message Bar or Backstage View.
Approved configurations for user applications are developed, implemented and maintained.
Access to Microsoft AD DS domain controllers, Microsoft AD CS servers, Microsoft AD FS servers and Microsoft Entra Connect servers is limited to privileged users that require access.
Lightweight Directory Access Protocol signing is enabled on Microsoft AD DS domain controllers.
Passwords are prevented from being stored in Group Policy Preferences.
SID Filtering is enabled for domain and forest trusts.
The number of service accounts configured with an SPN is minimised.
Service accounts configured with an SPN do not have DCSync permissions.
User accounts with DCSync permissions are reviewed at least every six months, and those without an ongoing requirement for the permissions have them removed.
Computer accounts are not configured for unconstrained delegation.
The sIDHistory attribute for user accounts is not used.
User accounts are checked at least weekly for the presence of the sIDHistory attribute.
The Domain Computers security group does not have write or modify permissions to any Microsoft Active Directory objects.
The number of user accounts that are members of the Domain Admins, Enterprise Admins or other highly privileged security groups is minimised.
Service accounts are not members of the Domain Admins, Enterprise Admins or other highly privileged security groups.
Computer accounts are not members of the Domain Admins, Enterprise Admins or other highly privileged security groups.
The Domain Computers security group is not a member of any privileged or highly privileged security groups.
Strong mapping between certificates and users is enforced.
The EDITF_ATTRIBUTESUBJECTALTNAME2 flag is removed from Microsoft AD CS certification authority configurations.
The CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT flag is removed from certificate templates.
Unprivileged user accounts do not have write access to certificate templates.
Extended Key Usages that enable user authentication are removed.
Certificate manager approval is required for certificate templates that allow a Subject Alternative Name to be supplied.
Microsoft AD FS servers are administered using a dedicated service account that is not used to administer other systems.
Security-relevant events for Apple macOS operating systems are centrally logged.
Security-relevant events for Linux operating systems are centrally logged.
Security-relevant events for server applications on internet-facing servers are centrally logged.
Security-relevant events for server applications on non-internet-facing servers are centrally logged.
Service accounts configured with an SPN use the Advanced Encryption Standard for encryption.
User applications are hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur.
All temporary installation files created during user application installation processes are removed after user applications have been installed.
AI applications that process classified data have their ability to directly access external public data sources disabled.
AI applications are configured to require human approval before executing sensitive or high-impact actions.
Baselines of expected behaviour and performance for AI applications are established and monitored for unexpected deviations.
WMI activity, including the creation of permanent event subscriptions, is centrally logged.
Web-based enrolment interfaces for Microsoft AD CS servers are disabled unless required, and where enabled, are configured to require HTTPS and Extended Protection for Authentication.
Certificate templates are reviewed at least every three months to identify and remediate misconfigurations that could enable privilege escalation or unauthorised certificate enrolment.
Certificate enrolment events, including successful and unsuccessful requests and changes to certificate templates or Microsoft AD CS configurations, are centrally logged.
Reached from your selection
A centralised and managed approach that maintains the integrity of patches or updates, and confirms that they have been applied successfully, is used to patch or update applications, operating systems, drivers and firmware.
Patch management processes, and supporting patch management procedures, are developed, implemented and maintained.
Privileged human users use separate privileged and unprivileged operating environments.
Operating systems that are no longer supported by vendors are replaced.
Backups of data, applications and settings are performed and retained in accordance with business criticality and business continuity requirements.
Data backup processes, and supporting data backup procedures, are developed, implemented and maintained.
Data restoration processes, and supporting data restoration procedures, are developed, implemented and maintained.
Privileged operating environments are not virtualised within unprivileged operating environments.
Unprivileged user accounts cannot be used to log on to privileged operating environments.
Privileged user accounts (excluding local administrator accounts) cannot be used to log on to unprivileged operating environments.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of internet-facing servers and internet-facing network devices are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within one month of release.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in drivers are applied within one month of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Privileged user accounts (excluding backup administrator accounts) cannot access backups belonging to other user accounts.
Privileged user accounts (excluding backup administrator accounts) cannot access their own backups.
Privileged user accounts (excluding backup administrator accounts) are prevented from modifying and deleting backups.
Backup administrator accounts are prevented from modifying and deleting backups during their retention period.
Administrative infrastructure for critical servers, high-value servers and regular servers is segregated from each other.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of IT equipment other than workstations, servers and network devices are applied within one month of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Backups of data, applications and settings are synchronised to enable restoration to a common point in time.
Backups of data, applications and settings are retained in a secure and resilient manner.
Unprivileged user accounts cannot access backups belonging to other user accounts.
Unprivileged user accounts cannot access their own backups.
Unprivileged user accounts are prevented from modifying and deleting backups.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of internet-facing servers and internet-facing network devices are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of IT equipment other than workstations, servers and network devices are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in drivers are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Secure Admin Workstations are used in the performance of administrative activities.
Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within one month of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in firmware are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in firmware are applied within one month of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
User accounts with DCSync permissions cannot be used to log on to unprivileged operating environments.
A list of authorised RMM tools and remote access tools is developed, enforced and maintained.
Backups are stored using a technically enforced immutability mechanism that prevents their modification or deletion for the duration of their retention period.
Backup infrastructure, including backup servers, repositories and management consoles, is segregated from production environments and uses a separate authentication mechanism for administrative access.
Not reached from your selection
System administration processes, and supporting system administration procedures, are developed, implemented and maintained.
Applications other than office productivity suites, web browsers and their extensions, email clients, PDF applications, Adobe Flash Player, and security products that are no longer supported by vendors are removed.
System administration activities are performed in accordance with the system’s change and configuration management plan.
Administrative infrastructure is segregated from the wider network and the internet.
Network management traffic can only originate from administrative infrastructure.
Administrative activities are conducted through jump servers.
Software registers for workstations, servers, network devices and networked IT equipment are developed, implemented, maintained and regularly verified.
A digital preservation policy is developed, implemented and maintained.
Restoration of data, applications and settings from backups to a common point in time is tested as part of disaster recovery exercises.
Software registers contain versions and patch histories of applications, drivers, operating systems and firmware.
Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within two weeks of release.
Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Patches, updates or other vendor mitigations for vulnerabilities in applications other than office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within one month of release.
Office productivity suites, web browsers and their extensions, email clients, PDF applications, Adobe Flash Player, and security products that are no longer supported by vendors are removed.
Internet-facing network devices that are no longer supported by vendors are replaced.
When applications, operating systems, network devices or networked IT equipment that are no longer supported by vendors cannot be immediately removed or replaced, compensating security controls are implemented until such time that they can be removed or replaced.
Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within 48 hours of release when vulnerabilities are assessed as critical by vendors or when working exploits exist.
Network devices that do not belong to administrative infrastructure cannot initiate connections with administrative infrastructure.
Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within two weeks of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.
Online services that are no longer supported by vendors are removed.
Non-internet-facing network devices that are no longer supported by vendors are replaced.
Networked IT equipment that is no longer supported by vendors is replaced.
Network connections for unauthorised RMM tools and remote access tools are blocked at gateways.
Your licences include these, and you told us they are not in use. Turning them on costs nothing further.
Backups (NinjaOne Backup Device Backup)
Your NinjaOne Backup Device Backup licence entitles you to this, and you told us it is not switched on. Turning it on costs nothing further.
https://www.ninjaone.com/docs/backup/image-backup-and-restore/image-backup-plans/ · checked 2026-09-05
Your licences include these and you were not sure they are in use. Check before buying anything that would duplicate them.
Operating system patching (Microsoft Intune Plan 1)
Your Microsoft Intune Plan 1 licence entitles you to this. You were not sure whether it is in use. It is worth confirming before buying anything that would duplicate it.
https://learn.microsoft.com/en-us/intune/device-updates/windows/ · checked 2026-09-05
These are switched on, but your answers suggest nobody runs them or would notice them failing. Usually fixed with a process, not a purchase.
Application control (Microsoft Intune Plan 1)
You have this running through Microsoft Intune Plan 1, but you were not sure anyone acts on what it finds. A control nobody watches protects you right up until the day it matters. This is usually fixed with a process, not a purchase.
https://learn.microsoft.com/en-us/intune/device-configuration/endpoint-security/manage-app-control · checked 2026-09-05
You are paying more than once for this evidence. Overlap is not automatically waste, but it should be a decision rather than an accident.
Conditional access (Microsoft Intune Plan 1 and Microsoft Entra ID P1)
Both Microsoft Intune Plan 1 and Microsoft Entra ID P1 provide this. Overlap is not automatically waste (a second independent source raises confidence), but it is worth knowing you are paying for it twice.
https://learn.microsoft.com/en-us/intune/fundamentals/what-is-intune · checked 2026-09-05
https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mfa-licensing · checked 2026-09-03
For the products you selected: ISM controls in our count that our catalogue does not reach.
Australian ISM (2026.09.4)
For the products you selected, our mapping does not reach 823 of the 1031 Australian ISM (2026.09.4) controls we count. Not every gap is a purchase: we class 149 of those as closed by a written policy or plan rather than by anything you can buy, and 31 as needing a named owner rather than a product. The remaining 643 are the kind a tool can close. Our catalogue already reaches some of them through products outside your selection.
523of these requirements are reachable today with capabilities already mapped in our catalogue, provided by products outside your selection. Which products, whether they fit your environment, and the technical requirements we have not yet mapped are what we work through with you in a consultation.
This count reflects our catalogue as it stands today. We research and map products and capabilities continuously, so it will change as that work progresses.
See where your own products stand: free, about 3 minutes.
Check your coverage →