Skip to content
System access
ASD ISMISM-1864

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:

  • Developed: written, then approved by the chief information security officer (ISM-0047).
  • Implemented: in force, with personnel agreeing to it before access (ISM-1865).
  • Maintained: kept current, reviewed at least once a year with a 'current as at' date (ISM-0888).

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

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

  2. Approve and publish it.

    Have the chief information security officer approve it (ISM-0047), give it a 'current as at' date (ISM-0888), publish it where all personnel can find it, and tell them of each later change (ISM-1602).

  3. Make agreement a condition of access.

    Require agreement to the current version as a step in the access request process, before access is granted (ISM-1865), and keep each person's signed agreement in their access record (ISM-0407). Include contractors and anyone else given an account.

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

Keep it running

Review the policy at least once a year (ISM-0888), and sooner when new systems, services or ways of working, such as AI tools, raise uses it does not cover. Notify personnel of each change (ISM-1602).

Evidence and audit

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

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

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

ISO/IEC 27001: 5 mappings

  • A.6.4Disciplinary processDepends on

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.