ASD ISM 1864 Develop and enforce a system usage policy
What it says
A system usage policy is developed, implemented and maintained.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Write, put into effect and keep current a system usage policy: the organisation's rules for how personnel may use its systems and their resources.
A system usage policy must be developed, implemented and maintained. It sets the rules for how personnel may use systems and their resources, so people can be held accountable for their actions. The control lists no contents, so the organisation decides them. Each verb is a duty:
Free. Save your status, tasks and notes.
Why it matters
Without written rules for using systems, the organisation cannot show a person knew an action was not allowed, so misuse is hard to act on. A current policy personnel have agreed to lets it hold them accountable for their actions on its systems.
How to implement
Decide what the policy covers.
Base it on the behaviour you need to hold people to, such as permitted and prohibited uses, personal use, sharing accounts or passwords, handling data by classification, installing software, monitoring of use, reporting suspected incidents and what follows a breach. Point to the separate web, email and mobile device usage policies.
Apply the policy when it is breached.
When monitoring or a report shows a breach, deal with it as the policy sets out and record the outcome, so the rules carry weight.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The current system usage policy with its approval record, 'current as at' date and review history, and the register of systems (ISM-1966).
Look at
Who approved it, when it was last reviewed, and whether it covers every system on the register.
Good evidence
The chief information security officer approved the current version, it was reviewed within the last 12 months and carries a 'current as at' date, and no system on the register falls outside it.
- Check 2 of 3What an auditor asks for
Ask for
Access records for a sample of people drawn from the identity platform, including recent joiners and contractors.
Look at
Whether each person agreed to the policy before their access was granted.
Good evidence
Every sampled person agreed to the system usage policy before their access began, and the signed agreement is in their access record.
- Check 3 of 3What an auditor asks for
Ask for
Records that test two or three rules the auditor picks from the policy, such as logons to shared accounts or software installs.
Look at
Whether practice matches the rules, and what happened to each breach found.
Good evidence
The records show the chosen rules being applied, and every breach in them was dealt with as the policy sets out, with the outcome recorded.
Mappings
Closest match in ISO/IEC 27001: A.5.10, Acceptable use of information and other associated assets, which asks for the same thing.
ISO/IEC 27001: 5 mappings
This control is equivalent to A.5.10.
ISM-1864 requires the organisation to develop, implement, and maintain a system usage policy governing how systems are used. Annex A 5.10 similarly requires documented and implemented rules for acceptable use and handling of information and associated assets. Both controls are centred on establishing and enforcing acceptable-use expectations for users, with only minor differences in phrasing ('system usage' versus 'information and assets').
This control partially meets A.5.1.
ISM-1864 requires a specific topic-level policy for system usage to be developed, implemented, and maintained. Annex A 5.1 is broader, requiring an overarching information security policy framework and topic-specific policies to be defined, approved, communicated, acknowledged, and reviewed. ISM-1864 fits as one such topic-specific policy within the wider governance requirements of Annex A 5.1.
This control supports A.5.4.
ISM-1864 requires the organisation to establish and maintain a system usage policy. Annex A 5.4 supports this by placing responsibility on management to require personnel to apply information security in accordance with established policies and procedures, which is necessary to enforce ISM-1864 in practice. Annex A 5.4 is about managerial enforcement/accountability rather than defining the content of the usage policy itself.
This control depends on A.6.3.
ISM-1864 requires a system usage policy to be created and maintained to define expected system use. Annex A 6.3 supports this by requiring awareness, education, and training so personnel receive updates and understand relevant policies and procedures, including acceptable use expectations. ISM-1864 is primarily about the policy artefact and its enforcement, while Annex A 6.3 is about ensuring people know and can apply it.
This control depends on A.6.4.
Annex A 6.4 requires a formalised and communicated disciplinary process for handling information security policy violations. ISM-1864 establishes and enforces a system usage policy, which defines expected behaviour and creates the basis for determining when a violation has occurred and when Annex A 6.4 should be invoked. ISM-1864 does not require disciplinary actions or procedures, while Annex A 6.4 focuses on consequences and process once a breach is identified.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




