ISM CONTROL INDEX ​

System owners obtain authorisation to operate each system from its authorising officer based on the acceptance of the security risks associated with its operation.

A cyber security strategy is developed, implemented and maintained.

Systems have a system security plan that includes a description of the system and an annex that covers both applicable controls from this document and any additional controls that have been identified.

System administration processes, and supporting system administration procedures, are developed, implemented and maintained.

Systems have an 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 which 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 Cyber Security Centre 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 located in a separate document.

Organisational-level security documentation is approved by the Chief Information Security Officer while system-specific security documentation is approved by the system’s authorising officer.

Security requirements associated with the confidentiality, integrity and availability of data are documented in contractual arrangements with service providers and reviewed on a regular and ongoing basis to ensure they remain fit for purpose.

Systems processing, storing or communicating AUSTEO or AGAO data remain at all times under the control of an Australian national working for or on behalf of the Australian Government.

Gateways undergo a security assessment by an IRAP assessor at least every 24 months.

Event logs are analysed in a timely manner to detect cyber security events.

Cyber security personnel have access to sufficient data sources and tools to ensure that systems can be monitored for key indicators of compromise.

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 of their actions
• maintaining a proper chain of custody
• following all instructions provided by relevant law enforcement agencies.

Cyber security incidents are reported to the ACSC as soon as possible after they occur or are discovered.

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.

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.

ICT equipment and media are secured when not in use.

Unauthorised people are prevented from observing systems, in particular workstation displays and keyboards, within facilities.

Cabling infrastructure is installed in accordance with relevant Australian Standards, as directed by the Australian Communications and Media Authority.

SECRET cables, when bundled together or run in conduit, are run exclusively in their own individual cable bundle or conduit.

In shared facilities, a visible smear of conduit glue is used to seal all plastic conduit joints and TOP SECRET conduits connected by threaded lock nuts.

In shared facilities, uniquely identifiable SCEC-approved tamper-evident seals are used to seal all removable covers on TOP SECRET cable reticulation systems.

When penetrating a TOP SECRET audio secure room, the Australian Security Intelligence Organisation is consulted and all directions provided are complied with.

Labels for TOP SECRET conduits are a minimum size of 2.5 cm x 1 cm, attached at five-metre intervals and marked as ‘TS RUN’.

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 verified on a regular basis.

SECRET and TOP SECRET cables are terminated on their own individual patch panels.

TOP SECRET patch panels are installed in individual TOP SECRET cabinets.

Where spatial constraints demand non-TOP SECRET patch panels be installed in the same cabinet as a TOP SECRET patch panel:

• a physical barrier in the cabinet is provided to separate patch panels
• only personnel holding a Positive Vetting security clearance have access to the cabinet
• approval from the TOP SECRET system’s authorising officer is obtained prior to installation.

If TOP SECRET fibre-optic fly leads exceeding five metres in length are used to connect wall outlet boxes to ICT equipment, they are run in a protective and easily inspected pathway that is clearly labelled at the ICT equipment end with the wall outlet box’s identifier.

Unauthorised RF and IR devices are not brought into SECRET and TOP SECRET areas.

Personnel are advised of the permitted sensitivity or classification of information that can be discussed over both 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.

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.

Paging, Multimedia Message Service, Short Message Service and messaging apps are not used to communicate sensitive or classified data.

When sending fax messages, the fax message is encrypted to an appropriate level to be communicated over unsecured telecommunications infrastructure.

A direct connection from an MFD to a digital telephone system is not enabled unless the digital telephone system is authorised to operate at the same sensitivity or classification as the network to which the MFD is connected.

An emanation security threat assessment is sought as early as possible in a system’s life cycle as implementing emanation security can have significant cost implications.

System owners deploying SECRET or TOP SECRET systems with Radio Frequency transmitters inside or co-located with their facility contact the ACSC for an emanation security threat assessment and implement any additional installation criteria derived from the threat assessment.

System owners deploying OFFICIAL or PROTECTED systems with Radio Frequency transmitters that will be co-located with SECRET or TOP SECRET systems contact the ACSC for an emanation security threat assessment and implement any additional installation criteria derived from the threat assessment.

System owners deploying systems or military platforms overseas contact the ACSC for an emanation security threat assessment and implement any additional installation criteria derived from the threat assessment.

ICT equipment meets industry and government standards relating to electromagnetic interference/electromagnetic compatibility.

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.

All web access, including that by internal servers, is conducted through web proxies.

The following details are logged for websites accessed via web proxies:

• 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.

An email usage policy is developed, implemented and maintained.

Access to non-approved webmail services is blocked.

Emails containing Australian Eyes Only, Australian Government Access Only or Releasable To data are not sent to email distribution lists unless the nationality of all members of email distribution lists can be confirmed.

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 users to select protective markings that a system has not been authorised to process, store or communicate.

If procuring an evaluated product, a product that has completed a PP-based evaluation, including against all applicable PP modules, 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.

When procuring high assurance ICT equipment, the ACSC is contacted for any equipment-specific delivery procedures.

Evaluated products are installed, configured, administered and operated in an evaluated configuration and in accordance with vendor guidance.

High assurance ICT equipment is installed, configured, administered and operated in an evaluated configuration and in accordance with ACSC guidance.

ICT equipment is classified based on the highest sensitivity or classification of data that it is approved for processing, storing or communicating.

ICT equipment, with the exception of high assurance ICT equipment, is labelled with protective markings reflecting its sensitivity or classification.

The ACSC’s approval is sought before applying labels to external surfaces of high assurance ICT equipment.

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.

Patches, updates or vendor mitigations for security vulnerabilities in high assurance ICT equipment are applied only when approved by the ACSC, and in doing so, using methods and timeframes prescribed by the ACSC.

Applications that are no longer supported by vendors are removed.

Maintenance and repairs of ICT equipment is carried out on site by an appropriately cleared technician.

If an uncleared technician is used to undertake maintenance or repairs of ICT equipment, the technician is escorted by someone who:

• is appropriately cleared and briefed
• takes due care to ensure that data is not disclosed
• takes all responsible measures to ensure the integrity of the ICT equipment
• has the authority to direct the technician
• is sufficiently familiar with the ICT equipment to understand the work being performed.

If an uncleared technician is used to undertake maintenance or repairs of ICT equipment, the ICT equipment and associated media is sanitised before maintenance or repair work is undertaken.

ICT equipment maintained or repaired off site is done so at facilities approved for handling the sensitivity or classification of the ICT equipment.

ICT equipment containing media is sanitised by removing the media from the ICT equipment or by sanitising the media in situ.

ICT equipment, including associated media, that is located overseas and has processed, stored or communicated AUSTEO or AGAO data that cannot be sanitised in situ, is returned to Australia for destruction.

ICT equipment sanitisation processes, and supporting ICT equipment sanitisation procedures, are developed, implemented and maintained.

High assurance ICT equipment is destroyed prior to its disposal.

Following sanitisation, destruction or declassification, a formal administrative decision is made to release ICT 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.

When disposing of ICT equipment that has been designed or modified to meet emanation security standards, the ACSC is contacted for requirements relating to its disposal.

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, with the exception of internally mounted fixed media within ICT equipment, is labelled with protective markings reflecting its sensitivity or classification.

An ICT equipment register is developed, implemented, maintained and verified on a regular basis.

Media is only used with systems that are authorised to process, store or communicate its sensitivity or classification.

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 device access control software or by disabling external communication interfaces.

External communication interfaces that allow DMA are disabled.

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.

SECRET and TOP SECRET volatile media is sanitised by overwriting it at least once in its entirety with a random pattern followed by a read back for verification.

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.

Following sanitisation, SECRET and TOP SECRET non-volatile magnetic media retains its classification.

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.

Following sanitisation, SECRET and TOP SECRET non-volatile EPROM and EEPROM media retains its classification.

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.

Following sanitisation, SECRET and TOP SECRET non-volatile flash memory media retains its classification.

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 person cleared to its sensitivity or classification.

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 personnel cleared to its sensitivity or classification.

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.

Unneeded accounts, components, services and functionality of operating systems are disabled or removed.

Unprivileged users do not have the ability to uninstall or disable approved software.

Default accounts or credentials for operating systems, including for any pre-configured accounts, are changed.

Servers maintain effective functional separation with other servers allowing them to operate independently.

Databases and their contents are classified based on the sensitivity or classification of data that they contain.

Development, testing and production environments are segregated.

Secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, and secure programming practices are used as part of application development.

Applications are comprehensively tested for security vulnerabilities, using both static application security testing and dynamic application security testing, prior to their initial release and any subsequent releases.

Requests for unprivileged access to systems, applications and data repositories are validated when first requested.

A secure record is maintained for the life of each system covering:

• all personnel authorised to access the system, and their user identification
• who provided authorisation for access
• when access was granted
• the level of access that was granted
• when access, and the level of access, was last reviewed
• when the level of access was changed, and to what extent (if applicable)
• when access was withdrawn (if applicable).

Systems have a logon banner that requires users to acknowledge and accept their security responsibilities before access is granted.

Foreign nationals, including seconded foreign nationals, do not have access to systems that process, store or communicate AUSTEO or REL data unless effective controls are in place to ensure such data is not accessible to them.

Foreign nationals, excluding seconded foreign nationals, do not have access to systems that process, store or communicate AGAO data unless effective controls are in place to ensure such data is not accessible to them.

Personnel granted access to a system and its resources are uniquely identifiable.

The use of shared user accounts is strictly controlled, and personnel using such accounts are uniquely identifiable.

When systems cannot support multi-factor authentication, single-factor authentication using passphrases is implemented instead.

Credentials are kept separate from systems they are used to authenticate to, except for when performing authentication activities.

Where a system processes, stores or communicates AUSTEO, AGAO or REL data, personnel who are foreign nationals are identified as such, including by their specific nationality.

Passphrases used for single-factor authentication are at least 4 random words with a total minimum length of 14 characters, unless more stringent requirements apply.

Passphrases used for single-factor authentication on TOP SECRET systems are at least 6 random words with a total minimum length of 20 characters.

Systems are configured with a session or screen lock that:

• activates after a maximum of 15 minutes of user inactivity, or if manually activated by users
• conceals all session content on the screen
• ensures that the screen does not enter a power saving state before the session or screen lock is activated
• requires users to authenticate to unlock the session
• denies users the ability to disable the session or screen locking mechanism.

Access to systems, applications and data repositories is removed or suspended on the same day personnel no longer have a legitimate requirement for access.

Access requirements for a system and its resources are documented in its system security plan.

Personnel undergo appropriate employment screening and, where necessary, hold an appropriate security clearance before being granted access to a system and its resources.

Personnel receive any necessary briefings before being granted access to a system and its resources.

When personnel are granted temporary access to a system, effective controls are put in place to restrict their access to only data required for them to undertake their duties.

Temporary access is not granted to systems that process, store or communicate caveated or sensitive compartmented information.

Privileged users are assigned a dedicated privileged account to be used solely for tasks requiring privileged access.

Foreign nationals, including seconded foreign nationals, do not have privileged access to systems that process, store or communicate AUSTEO or REL data.

Foreign nationals, excluding seconded foreign nationals, do not have privileged access to systems that process, store or communicate AGAO data.

Where practical, cryptographic equipment and software provides a means of data recovery to allow for circumstances where the encryption key is unavailable due to loss, damage or failure.

Cryptographic equipment or software that has completed a Common Criteria evaluation against a Protection Profile is used when encrypting media that contains OFFICIAL: Sensitive or PROTECTED data.

Full disk encryption, or partial encryption where access controls will only allow writing to the encrypted partition, is implemented when encrypting data at rest.

ASD-approved HACE is used when encrypting media that contains SECRET or TOP SECRET data.

When a user authenticates to the encryption functionality of ICT equipment or media, it is treated in accordance with its original sensitivity or classification until the user deauthenticates from the encryption functionality.

Cryptographic equipment or software that has completed a Common Criteria evaluation against a Protection Profile is used to protect OFFICIAL: Sensitive or PROTECTED data when communicated over insufficiently secure networks, outside of appropriately secure areas or via public network infrastructure.

ASD-approved HACE is used to protect SECRET and TOP SECRET data when communicated over insufficiently secure networks, outside of appropriately secure areas or via public network infrastructure.

An ASD-Approved Cryptographic Protocol (AACP) or high assurance cryptographic protocol is used to protect data when communicated over network infrastructure.

Only AACAs or high assurance cryptographic algorithms are used by cryptographic equipment and software.

When using DH for agreeing on encryption session keys, a modulus of at least 2048 bits is used, preferably 3072 bits.

When using DSA for digital signatures, a modulus of at least 2048 bits is used.

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 passing encryption session keys or similar keys, a modulus of at least 2048 bits is used, preferably 3072 bits.

When using RSA for digital signatures, and for passing encryption session keys or similar keys, a different key pair is used for digital signatures and passing encrypted session keys.

Symmetric cryptographic algorithms are not used in Electronic Codebook Mode.

Only AACPs or high assurance cryptographic protocols are used by cryptographic equipment and software.

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 login 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).

Public key-based authentication is used for SSH connections.

When using logins without a passphrase for SSH connections, the following are disabled:

• access from IP addresses that do not require access
• port forwarding
• agent credential forwarding
• X11 display remoting
• console access.

If using remote access without the use of a passphrase 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 programs are used, it is limited to workstations and servers with screen locks and key caches that are set to expire within four hours of inactivity.

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.

All communications security and equipment-specific doctrine produced by the ACSC for the management and use of ASD-approved HACE is complied with.

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.

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, maintained.

Network access controls are implemented on networks to prevent the connection of unauthorised network devices.

IPv6 functionality is disabled in dual-stack network devices unless it is being used.

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.

Unused physical ports on network devices are disabled.

Network devices managing VLANs belonging to different security domains do not share VLAN trunks.

Public wireless networks provided for general public use are segregated from all other organisation networks.

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 separated physically or logically 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.

Microphones (including headsets and USB handsets) and webcams are not used with non-SECRET workstations in SECRET areas.

Email servers are configured to block, log and report emails with inappropriate protective markings.

Email servers only relay emails destined for or originating from their domains (including subdomains).

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).

An incident management policy, and associated incident response plan, is developed, implemented and maintained.

An event logging policy is developed, implemented and maintained.

The following events are logged for operating systems:

• application and operating system crashes and error messages
• changes to security policies and system configurations
• successful user logons and logoffs, failed user logons and account lockouts
• failures, restarts and changes to important processes and services
• requests to access internet resources
• security product-related events
• system startups and shutdowns.

For each event logged, the date and time of the event, the relevant user or process, the relevant filename, the event description, and the ICT equipment involved are recorded.

A fax machine and 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.

Evaluated peripheral switches are used when sharing peripherals between systems.

When planning, designing, implementing or introducing additional connectivity to CDSs, the ACSC is consulted and any directions provided by the ACSC are complied with.

Users are trained on the secure use of CDSs before access is granted.

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.

System administrators for gateways that connect to Australian Eyes Only or Releasable To networks are Australian nationals.

Separation of duties is implemented in performing administrative activities for gateways.

Users authenticate to other networks accessed via gateways.

ICT equipment authenticates to other networks accessed via gateways.

CDSs are implemented between SECRET or TOP SECRET networks and any other networks belonging to different security domains.

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 third party.

Gateways only allow explicitly authorised data flows.

The following events are logged for gateways:

• data packets and data flows permitted through gateways
• data packets and data flows attempting to leave gateways
• real-time alerts for attempted intrusions.

CDSs implement isolated upward and downward network paths.

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.

Evaluated diodes used for controlling the data flow of unidirectional gateways between SECRET or TOP SECRET networks and public network infrastructure complete a high assurance evaluation.

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.

When manually importing data to systems, the data is scanned for malicious and active content.

Files imported or exported via gateways or CDSs undergo content filtering checks.

Data transfer logs for SECRET and TOP SECRET systems are fully verified at least monthly.

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.

Data exported from SECRET and TOP SECRET systems is reviewed and authorised by a trusted source beforehand.

Trusted sources for SECRET and TOP SECRET systems are limited to people and services that have been authorised as such by the Chief Information Security Officer.

When manually exporting data from SECRET and TOP SECRET systems, digital signatures are validated and keyword checks are performed within all textual data.

All security-relevant events generated by CDSs are logged.

Data authorised for export from SECRET and TOP SECRET systems is digitally signed by a trusted source.

Files imported or exported via gateways or CDSs that have a digital signature or cryptographic checksum are validated.

Bluetooth functionality is not enabled on SECRET and TOP SECRET mobile devices.

Mobile devices do not process, store or communicate SECRET or TOP SECRET data until approved for use by ASD.

Privately-owned mobile devices do not access SECRET and TOP SECRET systems or data.

Mobile device emergency sanitisation processes, and supporting mobile device emergency sanitisation procedures, are developed, implemented and maintained.

If a cryptographic zeroise or sanitise function is provided for cryptographic keys on a SECRET or TOP SECRET mobile device, the function is used as part of mobile device emergency sanitisation processes and procedures.

When accessing an organisation’s network via a VPN connection, split tunnelling is disabled.

A CISO is appointed to provide cyber security leadership and guidance for their organisation.

The CISO oversees the management of cyber security personnel within their organisation.

The CISO reports directly to their organisation’s senior executive or Board on cyber security matters.

The CISO develops, implements and maintains a cyber security communications 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 of key cyber security and business executives, which meets formally and on a regular basis.

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 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.

Systems are secured in facilities that meet the requirements for a security zone suitable for their sensitivity or classification.

Server rooms, communications rooms, security containers and secure rooms are not left in unsecured states.

Personnel are advised of what suspicious contact via online services is and how to report it.

Personnel are advised to not post work information to unauthorised online services and to report cases where such information is posted.

Personnel are advised of security risks associated with posting personal information to online services and are encouraged to use any available privacy settings to restrict who can view such information.

Personnel are advised not to send or receive files via unauthorised online services.

Security measures are used to detect and respond to unauthorised RF devices in SECRET and TOP SECRET areas.

Media is handled in a manner suitable for its sensitivity or classification.

Following sanitisation, TOP SECRET volatile media retains its classification if it stored static data for an extended period of time, or had data repeatedly stored on or written to the same memory location for an extended period of time.

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.

Application control is implemented on workstations.

All users (with the exception of local administrator accounts and break glass accounts) cannot disable, bypass or be exempted from application control.

On a daily basis, outside of business hours and after an appropriate period of inactivity, user sessions are terminated and workstations are restarted.

AUSTEO and AGAO data can only be accessed from systems under the sole control of the Australian Government that are located within facilities authorised by the Australian Government.

Event logs, excluding those for Domain Name System services and web proxies, are retained for at least seven years.

DKIM signing is enabled on emails originating from an organisation’s domains (including subdomains).

Mobile devices prevent personnel from installing or uninstalling non-approved applications once provisioned.

Mobile devices prevent personnel from disabling or modifying security functionality once provisioned.

Sensitive or classified data is not viewed or communicated in public locations unless care is taken to reduce the chance of the screen of a mobile device being observed.

Mobile devices encrypt their internal storage and any removable media.

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 access the internet via a VPN connection to an organisation’s internet gateway rather than via a direct connection to the internet.

Security documentation is reviewed at least annually and includes a ‘current as at [date]’ or equivalent statement.

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 software is 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.

OFFICIAL and PROTECTED cables are coloured neither salmon pink nor red.

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.

User applications are chosen from vendors that have demonstrated a commitment to secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, secure programming practices, and maintaining the security of their products.

When transferring data manually between two systems belonging to different security domains, rewritable media is sanitised after each data transfer.

Application control is implemented using cryptographic hash rules, publisher certificate rules or path rules.

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.

The OWASP Application Security Verification Standard is used in the development of web applications.

Multi-factor authentication is used to authenticate unprivileged users of systems.

Legal advice is sought on the exact wording of logon banners.

An accurate time source is established and used consistently across systems to assist with identifying connections between events.

Event logs for Domain Name System services and web proxies are retained for at least 18 months.

ECDH and ECDSA are used in preference to DH and DSA.

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.

Security measures are implemented to prevent unauthorised access to network management traffic.

The effective range of wireless communications outside an organisation’s area of control is limited by implementing RF shielding on facilities in which SECRET or TOP SECRET wireless networks are used.

Individual logins are implemented for IP phones used for SECRET or TOP SECRET conversations.

A denial of service response plan for video conferencing and IP telephony services is developed, implemented and maintained.

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 software used by external senders is configured such that it does not break the validity of the sender’s DKIM signature.

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.

A HIPS is implemented on critical servers and high-value servers.

Fax machines and MFDs are located in areas where their use can be observed.

Gateways undergo testing following configuration changes, and at regular intervals no more than six months apart, to validate they conform to expected security configurations.

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 sensitivity or classification.

LAN Manager and NT LAN Manager authentication methods are disabled.

All data stored on media is encrypted.

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.

Each system has a designated system owner.

An organisation’s systems and data are not accessed or administered by a service provider unless a contractual arrangement exists between the organisation and the service provider to do so.

Keys or equivalent access mechanisms to server rooms, communications rooms, security containers and secure rooms are appropriately controlled.

The sender of a fax message makes arrangements for the receiver to collect the fax message as soon as possible after it is sent and for the receiver to notify the sender if the fax message does not arrive in an agreed amount of time.

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 of time.

A telephone system usage policy is developed, implemented and maintained.

The ACSC’s approval is sought before undertaking any maintenance or repairs to high assurance ICT equipment.

An ASD-Approved Cryptographic Algorithm (AACA) or high assurance cryptographic algorithm is used when encrypting media.

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.

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 that are later returned
• lose mobile devices or removable media that are later found
• observe unusual behaviour of mobile devices.

Protective marking tools do not allow users replying to or forwarding emails to select protective markings lower than previously used.

Keying material is changed when compromised or suspected of being compromised.

Separate fax machines or MFDs are used for sending sensitive or classified fax messages and all other fax messages.

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.

SECRET cables are terminated in an individual cabinet; or for small systems, a cabinet with a division plate between any SECRET cables and non-SECRET cables.

TOP SECRET cables are terminated in an individual TOP SECRET cabinet.

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.

SECRET and TOP SECRET wall outlet boxes contain exclusively SECRET or TOP SECRET cables.

OFFICIAL 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 are inspectable at a minimum of five-metre intervals.

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.

A visible gap exists between TOP SECRET cabinets and non-TOP SECRET cabinets.

Cables in TOP SECRET areas are fully inspectable for their entire length.

Where wall penetrations exit a TOP SECRET area into a lower classified area, TOP SECRET cables are encased in conduit with all gaps between the TOP SECRET conduit and the wall filled with an appropriate sealing compound.

A power distribution board with a feed from an Uninterruptible Power Supply is used to power all TOP SECRET ICT equipment.

In shared facilities, cables are run in an enclosed cable reticulation system.

In shared facilities, TOP SECRET cables are not run in party walls.

System owners deploying SECRET or TOP SECRET systems in shared facilities contact the ACSC for an emanation security threat assessment and implement any additional installation criteria derived from the threat assessment.

Only the latest version of TLS is used for TLS connections.

Patch management processes, and supporting patch management procedures, are developed, implemented and maintained.

Privacy filters are applied to the screens of SECRET and TOP SECRET mobile devices.

Personnel are advised to maintain separate work and personal accounts for online services.

SPF is used to verify the authenticity of incoming emails.

Evaluated diodes are used for controlling the data flow of unidirectional gateways between networks.

Evaluated diodes used for controlling the data flow of unidirectional gateways between SECRET or TOP SECRET networks and any other networks complete a high assurance evaluation.

If using degaussers to destroy media, degaussers evaluated by the United States’ National Security Agency are used.

Systems have a continuous monitoring plan that includes:

• conducting vulnerability scans for systems at least fortnightly
• conducting vulnerability assessments and penetration tests for systems prior to deployment, including prior to deployment of significant changes, and at least annually thereafter
• analysing identified security vulnerabilities to determine their potential impact
• implementing mitigations based on risk, effectiveness and cost.

In shared facilities, conduits or the front covers of ducts, cable trays in floors and ceilings, and associated fittings are clear plastic.

Attempts to access websites through their IP addresses instead of their domain names are blocked by web content filters.

Multi-factor authentication is used to authenticate privileged users of systems.

Privileged user accounts are prevented from accessing the internet, email and web services.

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 network traffic within and between network segments to only those required for business purposes.

A hard fail SPF record is used when specifying authorised email servers (or lack thereof) for an organisation’s domains (including subdomains).

IPv6 capable network security appliances are used on IPv6 and dual-stack networks.

When manually exporting data from systems, the data is checked for unsuitable protective markings.

Gateways inspect and filter data flows at the transport and above network layers.

A Mobile Device Management solution is used to ensure mobile device management policy is applied to all mobile devices.

OFFICIAL and PROTECTED mobile devices are configured to remain undiscoverable to other Bluetooth devices except during Bluetooth pairing.

Bluetooth pairing for OFFICIAL and PROTECTED mobile devices is performed in a manner such that connections are only made between intended Bluetooth devices.

Bluetooth pairings for OFFICIAL and PROTECTED mobile devices are removed when there is no longer a requirement for their use.

Bluetooth pairing for OFFICIAL and PROTECTED mobile devices is performed using Secure Connections, preferably with Numeric Comparison if supported.

System administrators document requirements for administrative activities, consider potential security impacts, obtain any necessary approvals, notify users of any disruptions or outages, and maintain system and security documentation.

Following intrusion remediation activities, full network traffic is captured for at least seven days and analysed to determine whether the adversary has been successfully removed from the system.

SECRET and TOP SECRET cables with non-conformant cable colouring are both banded with the appropriate colour and labelled at inspection points.

Labels and markings indicating the owner, sensitivity, classification or any other marking that can associate ICT equipment with its prior use are removed prior to its disposal.

ICT equipment, including associated media, that is located overseas and has processed, stored or communicated AUSTEO or AGAO data, is sanitised in situ.

MFD print drums and image transfer rollers are inspected and destroyed if there is remnant toner which 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.

The paper tray of the fax machine is removed, and a fax message with a minimum length of four pages is transmitted, before the paper tray is re-installed to allow a fax summary page to be printed.

Fax machines are checked to ensure no pages are trapped in the paper path due to a paper jam.

Credentials set for user accounts are randomly generated.

Cyber security events are analysed in a timely manner to identify cyber security incidents.

IKE version 2 is used for key exchange when establishing IPsec connections.

Email content filtering is implemented to filter potentially harmful content in email bodies and attachments.

Add-ons, extensions and plug-ins for office productivity suites, web browsers, email clients, PDF software and security products are restricted to an organisation-approved set.

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.

Threat modelling is used in support of application development.

Robust web application frameworks are used in the development of web applications.

Validation or sanitisation is performed on all input handled by web applications.

Output encoding is performed on all output produced by web applications.

A database register is developed, implemented, maintained and verified on a regular basis.

All temporary installation files and logs created during server application installation processes are removed after server applications have been installed.

ACSC and vendor hardening guidance for server applications is implemented.

Unneeded accounts, components, services and functionality of server applications are disabled or removed.

Server applications are configured to run as a separate account with the minimum privileges needed to perform their functions.

The accounts under which server applications run have limited access to their underlying server’s file system.

Database users’ ability to access, insert, modify and remove database contents is restricted based on their work duties.

File-based access controls are applied to database files.

Default accounts or credentials for server applications, including for any pre-configured accounts, are changed.

Unique privileged accounts are used for administering individual server applications.

The need-to-know principle is enforced for database contents through the application of minimum privileges, database views and database roles.

Database servers and web servers are functionally separated.

Database servers are placed on a different network segment to user workstations.

Network access controls are implemented to restrict database server communications to strictly defined network resources, such as web servers, application servers and storage area networks.

If only local access to a database is required, networking functionality of database management system software is disabled or directed to listen solely to the localhost interface.

Development and testing environments do not use the same database servers as production environments.

Database contents from production environments are not used in development or testing environments unless the environment is secured to the same level as the production environment.

All queries to databases from web applications are filtered for legitimate content and correct syntax.

Parameterised queries or stored procedures, instead of dynamically generated queries, are used for database interactions.

Data communicated between database servers and web servers is encrypted.

Web applications are designed or configured to provide as little error information as possible about the structure of databases.

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 in order 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 in order to undergo content filtering checks.

Data transfer logs for systems are partially verified at least monthly.

Physical security is implemented to protect network devices in public areas from physical damage or unauthorised access.

Legal advice is sought prior to allowing privately-owned mobile devices to access systems or data.

Personnel are advised of privacy and security risks when travelling overseas with mobile devices.

Personnel take the following precautions when travelling overseas with mobile devices:

• never leaving mobile devices or removable media unattended for any period of time, including by placing them in checked-in luggage or leaving them in hotel safes
• never storing credentials with mobile devices that they grant access to, such as in laptop bags
• never lending mobile devices or removable media to untrusted people, even if briefly
• never allowing untrusted people to connect their mobile devices or removable media, including for charging
• never using designated charging stations, wall outlet charging ports or chargers supplied by untrusted people
• avoiding connecting mobile devices to open or untrusted Wi-Fi networks
• using a VPN connection to encrypt all mobile device communications
• using encrypted messaging apps for communications instead of using foreign telecommunication networks
• disabling any communications capabilities of mobile devices when not in use, such as cellular data, wireless, Bluetooth and Near Field Communication
• avoiding reuse of removable media once used with other parties’ systems or mobile devices
• ensuring any removable media used for data transfers are thoroughly checked for malicious code beforehand
• never using any gifted mobile devices, especially removable media, when travelling or upon returning from travelling.

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.

Default accounts or credentials for network devices including for any pre-configured accounts, are changed.

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.

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 authentication with EAP-TLS, using X.509 certificates, is used for mutual authentication; with all other EAP methods disabled on supplications and authentication servers.

Evaluated supplicants, authenticators, wireless access points and authentication servers are used in wireless networks.

Certificates are required for both devices and users accessing wireless networks.

Certificates are generated using an evaluated certificate authority or hardware security module.

Certificates are protected by encryption, user authentication, and both logical and physical access controls.

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.

A HIPS is implemented on workstations.

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.

Network devices managing VLANs terminate VLANs belonging to different security domains on separate physical network interfaces.

Security updates are applied to mobile devices as soon as they become available.

AES-GCM is used for encryption of TLS connections.

Only server-initiated secure renegotiation is used for TLS connections.

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.

Privileged users use separate privileged and unprivileged operating environments.

Only privileged operating environments can communicate with jump servers.

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.

Only jump servers can communicate with assets requiring administrative activities to be performed.

Executable files imported via gateways or CDSs are automatically executed in a sandbox to detect any suspicious behaviour.

When implementing application control using path rules, only approved users can modify approved files and write to approved folders.

Service providers, including any subcontractors, provide an appropriate level of protection for any data entrusted to them or their services.

Personnel accessing OFFICIAL and PROTECTED systems or data using a privately-owned mobile device use an ASD-approved platform, a security configuration in accordance with ACSC guidance, and have enforced separation of work and personal data.

Multi-factor authentication uses either: something users have and something users know, or something users have that is unlocked by something users know or are.

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.

Accounts, except for break glass accounts, are locked out after a maximum of five failed logon attempts.

Unprivileged access to systems and applications is automatically disabled after 45 days of inactivity.

A centralised event logging facility is implemented and event logs are sent to the facility as soon as possible after they occur.

SOEs are used for workstations and servers.

The latest release, or the previous release, of operating systems are used.

Where supported, 64-bit versions of operating systems are used.

ACSC and vendor hardening guidance for operating systems is implemented.

ACSC or vendor hardening guidance for web browsers is implemented.

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.

Antivirus software 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 on at least a daily basis
• regular scanning configured for all fixed disks and removable media.

If there is no business requirement for reading from removable media and devices, such functionality is disabled via the use of device access control software or by disabling external communication interfaces.

Development and modification of software only takes place in development environments.

Data from production environments is not used in a development or testing environment unless the environment is secured to the same level as the production environment.

Unauthorised access to the authoritative source for software is prevented.

Web applications implement Content-Security-Policy, HSTS and X-Frame-Options via security policy in response headers.

Gateways perform ingress traffic filtering to detect and prevent IP source address spoofing.

Unless explicitly required, IPv6 tunnelling is disabled on all network devices.

IPv6 tunnelling is blocked by network security appliances at externally-connected network boundaries.

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.

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.

When using elliptic curve cryptography, a curve from FIPS 186-4 is used.

When using DH or ECDH for key establishment of TLS connections, the ephemeral variant is used.

SSH private keys are protected with a passphrase or a key encryption key.

Microphones (including headsets and USB handsets) and webcams are not used with non-TOP SECRET workstations in TOP SECRET areas.

Types of data and its ownership is documented in contractual arrangements with service providers.

A supply chain risk assessment is performed for suppliers of applications, ICT equipment and services in order to assess the impact to a system’s security risk profile.

Perfect Forward Secrecy (PFS) is used for TLS connections.

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.

Evaluated peripheral switches used for sharing peripherals between SECRET and TOP SECRET systems, or between SECRET or TOP SECRET systems belonging to different security domains, preferably complete a high assurance evaluation.

When using a software-based isolation mechanism to share a physical server’s hardware, the isolation mechanism is from a vendor that has demonstrated a commitment to secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, secure programming practices, and maintaining the security of their products.

When using a software-based isolation mechanism to share a physical server’s hardware for SECRET or TOP SECRET computing environments, the physical server and all computing environments are of the same classification and belong to the same security domain.

The latest release of office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are used.

Unneeded components, services and functionality of office productivity suites, web browsers, email clients, PDF software and security products are disabled or removed.

When implementing application control using publisher certificate rules, both publisher names and product names are used.

The CISO oversees their organisation’s cyber security program and ensures their organisation’s compliance with cyber security policy, standards, regulations and legislation.

Servers minimise communications with other servers at both the network and file system level.

Evaluated peripheral switches used for sharing peripherals between SECRET or TOP SECRET systems and any non-SECRET or TOP SECRET systems complete a high assurance evaluation.

Personnel accessing systems or data using an organisation-owned mobile device use an ASD-approved platform, a security configuration in accordance with ACSC guidance, and have enforced separation of work and personal data.

The latest release of internet-facing server applications are used.

Web browsers do not process web advertisements from the internet.

Web browsers do not process Java from the internet.

Only privileged users responsible for validating 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 users.

Application control is implemented on internet-facing servers.

Unprivileged 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.

Software registers for workstations, servers, network devices and other ICT equipment are developed, implemented, maintained and verified on a regular basis.

Operating systems that are no longer supported by vendors are replaced.

Emails arriving via an external connection where the email source address uses an internal domain, or internal subdomain, are blocked at the email gateway.

Multi-factor authentication is used by an organisation’s users if they authenticate to their organisation’s internet-facing services.

Multi-factor authentication is used to authenticate users accessing important data repositories.

The use of SSH version 1 is disabled for SSH connections.

Requests for privileged access to systems and applications are validated when first requested.

Privileged access to systems and applications is limited to only what is required for users and services to undertake their duties.

Privileged access events are logged.

A digital preservation policy is developed, implemented and maintained.

Backups of important data, software and configuration settings are performed and retained with a frequency and retention timeframe in accordance with business continuity requirements.

Restoration of important data, software and configuration settings from backups to a common point of time is tested as part of disaster recovery exercises.

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.

System administrators for gateways undergo appropriate employment screening and, where necessary, hold an appropriate security clearance based on the sensitivity or classification of gateways.

CDSs implement protocol breaks at each network layer.

CDSs implement independent security-enforcing functions for upward and downward network paths.

A sample of security-relevant events relating to data transfer policies are taken at least every three months and assessed against security policies for CDSs to identify any operational failures.

Content filters used by CDSs undergo rigorous security testing to ensure they perform as expected and cannot be bypassed.

System owners register each system with its authorising officer.

System owners monitor each system, and associated cyber threats, security risks and controls, on an ongoing basis.

Evaluated firewalls are used between an organisation’s networks and public network infrastructure.

Only community or private clouds are used for outsourced SECRET and TOP SECRET cloud services.

Servers, network devices and cryptographic equipment are secured in security containers or secure rooms suitable for their sensitivity or classification taking into account the combination of security zones they reside in.

VLANs are not used to separate network traffic between an organisation’s networks and public network infrastructure.

A mobile device management policy is developed, implemented and maintained.

Printer ribbons in printers and MFDs are removed and destroyed.

Processes, and supporting procedures, are developed, implemented and maintained to prevent AUSTEO, AGAO and REL data in both textual and non-textual formats from being exported to unsuitable foreign systems.

The following events are logged for web applications: attempted access that is denied, crashes and error messages, and search queries initiated by users.

The following events are logged for databases:

• 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.

DMARC records are configured for an organisation’s domains (including subdomains) such that emails are rejected if they do not pass DMARC checks.

Microsoft Office is configured to prevent activation of Object Linking and Embedding packages.

An authorised RF and IR device register for SECRET and TOP SECRET areas is developed, implemented, maintained and verified on a regular basis.

Microsoft’s ‘recommended block rules’ are implemented.

Users are authenticated before they are granted access to a system and its resources.

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.

A media management policy is developed, implemented and maintained.

ICT equipment disposal processes, and supporting ICT equipment disposal procedures, are developed, implemented and maintained.

An ICT equipment management policy is developed, implemented and maintained.

All web application content is offered exclusively using HTTPS.

TLS compression is disabled for TLS connections.

If travelling overseas with mobile devices to high or extreme risk countries, personnel are:

• issued with newly provisioned 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.

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 accounts, applications and data
• apply security configuration settings, such as lock screens
• configure remote locate and wipe functionality
• enable encryption, including for any removable media
• backup all important data and configuration 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 accounts for any indicators of compromise, such as failed logon attempts.

Passphrases used for single-factor authentication on SECRET systems are at least 5 random words with a total minimum length of 17 characters.

Passphrases used for single-factor authentication are not a list of categorised words; do not form a real sentence in a natural language; and are not constructed from song lyrics, movies, literature or any other publicly available material.

Memorised secrets used for multi-factor authentication are a minimum of 6 characters, unless more stringent requirements apply.

Memorised secrets used for multi-factor authentication on SECRET systems are a minimum of 8 characters.

Memorised secrets used for multi-factor authentication on TOP SECRET systems are a minimum of 10 characters.

Video conferencing and IP telephony infrastructure is hardened.

At the conclusion of a security assessment for a system, a security assessment report is produced by the assessor and covers:

• the scope of the security assessment
• the system’s strengths and weaknesses
• security risks associated with the operation of the system
• the effectiveness of the implementation of controls
• any recommended remediation actions.

At the conclusion of a security assessment for a system, a plan of action and milestones is produced by the system owner.

Tailored privileged user training is undertaken annually by all privileged users.

Use of unprivileged access is logged.

Suppliers identified as high risk by a cyber supply chain risk assessment are not used.

Applications, ICT equipment and services are chosen 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 in order to articulate the security responsibilities of each party.

Outsourced cloud service providers and their cloud services undergo a security assessment by an IRAP assessor 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 allows for 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 or data are accessed or administered by a service provider in an unauthorised manner, the organisation is immediately notified.

An organisation’s networks are segregated from their service providers’ networks.

Cloud service providers’ ability to dynamically scale resources in response to a genuine spike 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.

Application control rulesets are validated on an annual or more frequent basis.

Personnel who are contractors are identified as such.

Unprivileged users are prevented from bypassing, disabling or modifying security functionality of operating systems.

Web browser security settings cannot be changed by users.

Data transfer logs are used to record all data imports and exports from systems.

System owners report the security status of each system to its authorising officer at least annually.

SOEs are reviewed and updated at least annually.

MTA-STS is enabled to prevent the unencrypted transfer of emails between complying servers.

Credentials are changed if:

• they are compromised
• they are suspected of being compromised
• they are discovered stored on networks in the clear
• they are discovered being transferred across networks in the clear
• membership of a shared account changes
• they have not been changed in the past 12 months.

Access to systems, applications and data repositories is removed or suspended as soon as practicable when personnel are detected undertaking malicious activities.

Unprivileged users do not have the ability to install unapproved software.

Users provide sufficient evidence to verify their identity when requesting new credentials.

Credentials are provided to users via a secure communications channel or, if not possible, split into two parts with one part provided to users and the other part provided to supervisors.

Credentials provided to users are changed on first use.

Credentials, in the form of memorised secrets, are not reused by users across different systems.

Credentials are obscured as they are entered into systems.

Following maintenance or repair activities for ICT equipment, the ICT equipment is inspected to confirm it retains its approved software configuration and that no unauthorised modifications have taken place.

ICT equipment is handled in a manner suitable for its sensitivity or classification.

Media is sanitised before it is used for the first time.

Microsoft’s Attack Surface Reduction rules are implemented.

Security documentation, including notification of subsequent changes, is communicated to all stakeholders.

Authentication methods susceptible to replay attacks are disabled.

When using a software-based isolation mechanism to share a physical server’s hardware, 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 to share a physical server’s hardware, the underlying operating system is hardened.

When using a software-based isolation mechanism to share a physical server’s hardware, patches, updates or vendor mitigations for security vulnerabilities are applied to the isolation mechanism and underlying operating system in a timely manner.

When using a software-based isolation mechanism to share a physical server’s hardware, integrity and log monitoring are performed for the isolation mechanism and underlying operating system in a timely manner.

SOEs provided by third parties are scanned for malicious code and configurations.

System owners are consulted before allowing intrusion activity to continue on a system for the purpose of collecting further data or evidence.

A method of emergency access to systems 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 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.

A vulnerability disclosure program is implemented to assist with the secure development and maintenance of products and services.

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.

Service accounts are created as group Managed Service Accounts.

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 is configured to use module logging, script block logging and transcription functionality.

PowerShell script block logs are protected by Protected Event Logging functionality.

A trusted insider program is developed, implemented and maintained.

Legal advice is sought regarding the development and implementation of a trusted insider program.

Inbound network connections from anonymity networks to internet-facing services are blocked.

Outbound network connections to anonymity networks are blocked.

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 DSA for digital signatures, a modulus and associated parameters are generated according to FIPS 186-4.

Suppliers of applications, ICT equipment and services associated with systems are identified.

Applications, ICT equipment and services are chosen from suppliers that have a strong track record of transparency and maintaining the security of their own systems and cyber supply chains.

System owners determine the type, value and security objectives for each system based on an assessment of the impact if it were to be compromised.

System owners select controls for each system and tailor them to achieve desired security objectives.

System owners implement controls for each system and its operating environment.

System owners ensure controls for each system and its operating environment are assessed to determine if they have been implemented correctly and are operating as intended.

An outsourced cloud service register is developed, implemented, maintained and verified on a regular basis.

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 assessment of the cloud service
• contractual arrangements for the cloud service
• point of contact for users of the cloud service
• 24/7 contact details for the cloud service provider.

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.

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.

Software registers contain versions and patch histories of applications, drivers, operating systems and firmware.

Sensitive or classified phone calls are not conducted in public locations unless care is taken to reduce the chance of conversations being overheard.

Floor plan diagrams are developed, implemented, maintained and verified on a regular basis.

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.

Privileged access to systems and applications is automatically disabled after 12 months unless revalidated.

Privileged access to systems and applications is automatically disabled after 45 days of inactivity.

Just-in-time administration is used for administering systems and applications.

Privileged account and group management events are logged.

Privileged access event logs are stored centrally.

Privileged account and group management event logs are stored centrally.

Privileged service accounts are prevented from accessing the internet, email and web services.

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, software 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 ‘recommended driver block rules’ are implemented.

Allowed and blocked execution events on workstations are logged.

Allowed and blocked execution events on internet-facing servers are logged.

Allowed and blocked execution events on non-internet-facing servers are logged.

Application control event logs are stored centrally.

Blocked PowerShell script execution events are logged.

PowerShell event logs are stored centrally.

Internet Explorer 11 does not process content from the internet.

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 software is blocked from creating child processes.

Microsoft Office macros are disabled for 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 on an annual or more frequent basis.

Allowed and blocked Microsoft Office macro execution events are logged.

Microsoft Office macro event logs are stored centrally.

Multi-factor authentication is used by an organisation’s users if they authenticate to third-party internet-facing services that process, store or communicate their organisation’s sensitive data.

Multi-factor authentication (where available) is used by an organisation’s users if they authenticate to third-party internet-facing services that process, store or communicate their organisation’s non-sensitive data.

Multi-factor authentication is enabled by default for an organisation’s non-organisational users (but users can choose to opt out) if they authenticate to the organisation’s internet-facing services.

Multi-factor authentication is phishing-resistant.

Successful and unsuccessful multi-factor authentication events are logged.

Multi-factor authentication event logs are stored centrally.

Credentials for break glass accounts, local administrator accounts and service accounts are long, unique, unpredictable and managed.

Windows Defender Credential Guard and Windows Defender Remote Credential Guard are enabled.

Privileged operating environments are not virtualised within unprivileged operating environments.

Unprivileged accounts cannot logon to privileged operating environments.

Privileged accounts (excluding local administrator accounts) cannot logon to unprivileged operating environments.

Patches, updates or vendor mitigations for security vulnerabilities in internet-facing services are applied within two weeks of release, or within 48 hours if an exploit exists.

Patches, updates or vendor mitigations for security vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within two weeks of release.

Patches, updates or vendor mitigations for security vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within 48 hours if an exploit exists.

Patches, updates or vendor mitigations for security vulnerabilities in applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, and security products are applied within one month of release.

Patches, updates or vendor mitigations for security vulnerabilities in operating systems of internet-facing services are applied within two weeks of release, or within 48 hours if an exploit exists.

Patches, updates or vendor mitigations for security vulnerabilities in operating systems of workstations, servers and network devices are applied within two weeks of release.

Patches, updates or vendor mitigations for security vulnerabilities in operating systems of workstations, servers and network devices are applied within 48 hours if an exploit exists.

Patches, updates or vendor mitigations for security vulnerabilities in drivers and firmware are applied within two weeks of release, or within 48 hours if an exploit exists.

A vulnerability scanner is used at least daily to identify missing patches or updates for security vulnerabilities in internet-facing services.

A vulnerability scanner is used at least weekly to identify missing patches or updates for security vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF software, and security products.

A vulnerability scanner is used at least fortnightly to identify missing patches or updates for security vulnerabilities in applications other than office productivity suites, web browsers and their extensions, email clients, PDF software, and security products.

A vulnerability scanner is used at least daily to identify missing patches or updates for security vulnerabilities in operating systems of internet-facing services.

A vulnerability scanner is used at least weekly to identify missing patches or updates for security vulnerabilities in operating systems of workstations, servers and network devices.

A vulnerability scanner is used at least weekly to identify missing patches or updates for security vulnerabilities in drivers and firmware.

Internet-facing services, office productivity suites, web browsers and their extensions, email clients, PDF software, Adobe Flash Player, and security products that are no longer supported by vendors are removed.

Privileged accounts (excluding backup administrator accounts) cannot access backups belonging to other accounts.

Privileged accounts (excluding backup administrator accounts) cannot access their own backups.

Privileged accounts (excluding backup administrator accounts) are prevented from modifying and deleting backups.

Privileged accounts (including backup administrator accounts) are prevented from modifying and deleting backups during their retention period.

Configuration 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.

A removable media register is developed, implemented, maintained and verified on a regular basis.

Unprivileged access event logs are stored centrally.

Break glass event logs are stored centrally.

Access to data repositories is automatically disabled after 45 days of inactivity.

A ‘security.txt’ file is hosted for all internet-facing organisational domains to assist in the responsible disclosure of security vulnerabilities in an organisation’s products and services.

SECRET cables are coloured salmon pink.

TOP SECRET cables are coloured red.

SECRET wall outlet boxes are coloured salmon pink.

TOP SECRET wall outlet boxes are coloured red.

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.

The resulting media waste particles from the destruction of SECRET media is stored and handled as OFFICIAL if less than or equal to 3 mm, PROTECTED if greater than 3 mm and less than or equal to 6 mm, or SECRET if greater than 6 mm and less than or equal to 9 mm.

The resulting media waste particles from the destruction of TOP SECRET media is stored and handled as OFFICIAL if less than or equal to 3 mm, or SECRET if greater than 3 mm and less than or equal to 9 mm.

A software bill of materials is produced and made available to consumers of software.

Planning and coordination of intrusion remediation activities are conducted on a separate system to that which has been compromised.

To the extent possible, all intrusion remediation activities are conducted in a coordinated manner during the same planned outage.

Requests for privileged access to data repositories are validated when first requested.

Privileged access to data repositories is automatically disabled after 12 months unless revalidated.

Faulty or damaged media that cannot be successfully sanitised is destroyed prior to its disposal.

A managed service register is developed, implemented, maintained and verified on a regular basis.

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 assessment of the managed service
• contractual arrangements for the managed service
• point of contact for users of 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 exercised on a regular and ongoing basis.

A system’s security architecture is approved prior to the development of the system.

Personnel dealing with banking details and payment requests are advised of what business email compromise is, how to manage such situations and how to report it.

ICT equipment destruction processes, and supporting ICT equipment destruction procedures, are developed, implemented and maintained.

ICT equipment that cannot be sanitised is destroyed.

Operating systems are chosen from vendors that have demonstrated a commitment to secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, secure programming practices, and maintaining the security of their products.

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.

Operating system event logs are stored centrally.

Email client security settings cannot be changed by users.

Cached credentials are limited to one previous logon.

Administrative infrastructure for critical servers, high-value servers and regular servers is segregated from each other.

Patches, updates or vendor mitigations for security vulnerabilities in operating systems of ICT equipment other than workstations, servers and network devices are applied within two weeks of release, or within 48 hours if an exploit exists.

A vulnerability scanner is used at least weekly to identify missing patches or updates for security vulnerabilities in operating systems of ICT equipment other than workstations, servers and network devices.

Network devices and other ICT equipment that are no longer supported by vendors are replaced.

Security vulnerabilities identified in applications are resolved by software developers 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.

Web application event logs are stored centrally.

Database event logs are stored centrally.

When using DH for agreeing on encryption session keys, a modulus of at least 3072 bits is used, preferably 3072 bits.

DSA is not used for digital signatures.

When using ECDH for agreeing on encryption session keys, NIST P-256, P-384 or P-521 curves are used, preferably the NIST P-384 curve.

When using ECDH for agreeing on encryption session keys, NIST P-384 or P-521 curves are used, preferably the NIST P-384 curve.

When using ECDSA for digital signatures, NIST P-256, P-384 or P-521 curves are used, preferably the NIST P-384 curve.

When using ECDSA for digital signatures, NIST P-384 or P-521 curves are used, preferably the NIST P-384 curve.

When using RSA for digital signatures, and passing encryption session keys or similar keys, a modulus of at least 3072 bits is used, preferably 3072 bits.

When using SHA-2 for hashing, an output size of at least 224 bits is used, preferably SHA-384.

When using SHA-2 for hashing, an output size of at least 256 bits is used, preferably SHA-384.

When using SHA-2 for hashing, an output size of at least 384 bits is used, preferably SHA-384.

When using AES for encryption, AES-128, AES-192 or AES-256 is used, preferably AES-256.

When using AES for encryption, 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.

System administrators for gateways that connect to Australian Government Access Only networks are Australian nationals or seconded foreign nationals.

Gateways are managed via a secure path isolated from all connected networks.

Gateway event logs are stored centrally.

CDS event logs are stored centrally.

Web proxy event logs are stored centrally.

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.

SecDevOps practices are used for application development.

All data communicated over network infrastructure is encrypted.

A protective DNS service is used to block access to known malicious domain names.

Public IP addresses controlled by, or used by, an organisation are signed by valid ROA records.

The incident management policy, including the associated incident response plan, is exercised at least annually.

A supplier relationship management policy is developed, implemented and maintained.

An approved supplier list is developed, implemented and maintained.

Applications, ICT equipment and services are sourced from approved suppliers.

Multiple potential suppliers are identified for sourcing critical applications, ICT equipment and services.

Sufficient spares of critical ICT equipment are sourced and kept in reserve.

Applications, ICT equipment and services are delivered in a manner that maintains their integrity.

The integrity of applications, ICT equipment and services are assessed as part of acceptance of products and services.

The authenticity of applications, ICT equipment and services are assessed as part of acceptance of products and services.

Managed service providers and their managed services undergo a security assessment by an IRAP assessor 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.

Credentials for break glass accounts, local administrator accounts and service accounts are a minimum of 30 characters.

Files containing executable content are digitally signed as part of application development.

Installers, patches and updates are digitally signed or provided with cryptographic checksums as part of application development.

Secure configuration guidance is produced as part of application development.

Incoming emails are rejected if they do not pass DMARC checks.

Network devices are flashed with trusted firmware before they are used for the first time.

Network devices are restarted on at least a monthly basis.

HACE does not process, store or communicate SECRET or TOP SECRET data until approved for use by ASD.

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.

Break clauses associated with failure to meet security requirements are documented in contractual arrangements with service providers.

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.

Default accounts or credentials for user applications, including for any pre-configured accounts, are changed.

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.

When applications, operating systems, network devices or other ICT equipment that are no longer supported by vendors cannot be immediately removed or replaced, compensating controls are implemented until such time that they can be removed or replaced.

Backups of important data, software and configuration settings are synchronised to enable restoration to a common point in time.

Backups of important data, software and configuration settings are retained in a secure and resilient manner.

Unprivileged accounts cannot access backups belonging to other accounts.

Unprivileged accounts cannot access their own backups.

Unprivileged accounts are prevented from modifying and deleting backups.

Event logs stored within a centralised event logging facility are protected from unauthorised modification and deletion.

Unauthorised modification of the authoritative source for software is prevented.

Authentication and authorisation of clients is performed when clients call web APIs that facilitate access to data not authorised for release into the public domain.

Authentication and authorisation of clients is performed when clients call web APIs that facilitate modification of data.

Following the identification of a cyber security incident, an organisation’s incident response plan is enacted.

Cables for individual systems use a consistent colour.

TOP SECRET cables, when bundled together or run in conduit, are run exclusively in their own individual cable bundle or conduit.

Wall outlet boxes for individual systems use a consistent colour.

Office productivity suite security settings cannot be changed by users.

PDF software security settings cannot be changed by users.

Security product security settings cannot be changed by users.

Server applications are chosen from vendors that have demonstrated a commitment to secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, secure programming practices, and maintaining the security of their products.

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 and cpasswords are not used in Group Policy Preferences.

Security-related events for Microsoft AD DS are logged.

Microsoft AD DS event logs are stored centrally.

Only service accounts and computer accounts are configured with Service Principal Names (SPNs).

Service accounts are provisioned with the minimum privileges required and are not members of the domain administrators group or similar highly privileged groups.

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.

User accounts are not configured with password never expires or password not required.

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 service accounts are used to add machines to the domain.

User accounts with unconstrained delegation are reviewed at least annually, and those without an associated Kerberos 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.

Credentials for the Kerberos Key Distribution Center’s service account (KRBTGT) are changed twice, allowing for replication to all Microsoft Active Directory Domain Services domain controllers in-between each change, if:

• the domain has been directly compromised
• the domain is suspected of being compromised
• they have not been changed in the past 12 months.

When using a software-based isolation mechanism to share a physical server’s hardware, the isolation mechanism or underlying operating system is replaced when it is no longer supported by a vendor.

The OWASP Top Ten 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.

Unprivileged access to systems, applications and data repositories is limited to only what is required for users and services to undertake their duties.

Privileged access to data repositories is limited to only what is required for users and services to undertake their duties.

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 logged.

MFD event logs are stored centrally.

ICT equipment is chosen from vendors that have demonstrated a commitment to secure-by-design and secure-by-default principles, use of memory-safe programming languages where possible, secure programming practices, and maintaining the security of their products.

ACSC and vendor hardening guidance for ICT equipment is implemented.

ACSC or vendor hardening guidance for office productivity suites is implemented.

ACSC or vendor hardening guidance for PDF software is implemented.

Protective Process Light for LSASS is enabled with a UEFI lock.

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.

Networked management interfaces for ICT equipment are not directly exposed to the internet.

Event logs are collected and analysed in a timely manner to detect cyber security events.

Cyber security events are analysed in a timely manner to identify cyber security incidents.

A Chief Information Security Officer provides leadership and oversight of cyber security.

The identity and value of systems, applications and data is determined and documented.

The confidentiality, integrity and availability requirements for systems, applications and data are determined and documented.

Security risk management processes are embedded into organisational risk management frameworks.

Security risks are identified, documented, managed and accepted both before systems and applications are authorised for use, and continuously throughout their operational life.

Only trusted and vetted personnel are granted access to systems, applications and data repositories.

Personnel are granted the minimum access to systems, applications and data repositories required for their duties.

Multiple methods are used to identify and authenticate personnel to systems, applications and data repositories.

Personnel are provided with ongoing cyber security awareness training.

Physical access to systems, supporting infrastructure and facilities is restricted to authorised personnel.

Systems and applications are designed, deployed, maintained and decommissioned according to their value and their confidentiality, integrity and availability requirements.

Systems and applications are delivered and supported by trusted suppliers.

Systems and applications are designed and configured to reduce their attack surface.

Systems and applications are administered in a secure and accountable manner.

Security vulnerabilities in systems and applications are identified and mitigated in a timely manner.

Only trusted and supported operating systems, applications and computer code can execute on systems.

Data is encrypted at rest and in transit between different systems.

Data communicated between different systems is controlled and inspectable.

Data, applications and configuration settings are backed up in a secure and proven manner on a regular basis.

Cyber security incidents are reported both internally and externally to relevant bodies in a timely manner.

Cyber security incidents are contained, eradicated and recovered from in a timely manner.

Business continuity and disaster recovery plans are enacted when required.