Skip to content
Cyber security roles
ASD ISMISM-0027

ASD ISM 0027 Mandatory authorisation for system operation

What it says

System owners obtain an authorisation to operate for each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system from its authorising officer.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system needs an authorisation to operate: its owner must get one from its authorising officer.

System owners must obtain an authorisation to operate for each non-classified (including OFFICIAL), OFFICIAL: Sensitive, PROTECTED and SECRET system from its authorising officer. An authorisation to operate is the formal decision that a system may run, based on accepting the security risks of running it. The authorising officer is the senior executive who makes that decision, normally the CISO or their delegate. The system owner obtains the decision and cannot grant it. For TOP SECRET systems, ISM-1968 requires authorisation from Director-General ASD (or their delegate).

Why it matters

Without an authorisation to operate, a system runs with security risks nobody with the authority has accepted. Seeking one puts those risks before a senior executive, who can accept them, add limits or refuse.

How to implement

  1. Identify the system's authorising officer.

    Normally that is the organisation's CISO or their delegate; with no CISO, another senior executive. For a bought service, it is still your CISO or delegate, not the provider. For a shared system, a formal agreement can name one officer or several acting jointly. The registration under ISM-1525 should already show who it is.

  2. Prepare the authorisation package for the officer.

    Include the system security plan (ISM-0041), cyber security incident response plan (ISM-0043), change and configuration management plan (ISM-0912), continuous monitoring plan (ISM-1163), security assessment report (ISM-1563) and plan of action and milestones (ISM-1564). For a bought service, add the provider's assessment report (ISM-1570, ISM-1793).

  3. Request the decision and record it.

    Present the remaining security risks in plain terms. The officer can authorise, authorise with limits such as restricted functions or an expiry date, or refuse until remediation is done. Keep the decision, its date and any limits.

  4. Hold go-live until the authorisation is granted.

    For a system already running without one, tell the authorising officer now and ask for a decision on the evidence available, which may carry limits while the rest is completed.

Keep it running

Honour any limits, start renewal before an expiry date and report security status at least annually (ISM-1587). After major changes or a major incident, update the package so the authorising officer can keep, limit or revoke the authorisation.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The register of systems (ISM-1966), an independent list such as cloud billing records or a network discovery scan, and the authorisation to operate for each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system.

    Look at

    Whether any of these systems is operating without a current authorisation.

    Good evidence

    Every such system on the register and the independent list holds a current authorisation to operate, and none is operating without one.

  2. Check 2 of 4What an auditor asks for

    Ask for

    The authorisation to operate for a sampled system, the record of its authorising officer (ISM-1525) and its recorded boundary (ISM-1633).

    Look at

    Who granted it, and whether what it covers matches the system as it is now.

    Good evidence

    The system's authorising officer or their delegate granted it, not the system owner, and it covers the current system boundary.

  3. Check 3 of 4What an auditor asks for

    Ask for

    The authorisation date, the go-live record and the package behind the decision.

    Look at

    Whether authorisation came before the system started operating, and whether the decision rests on a security assessment report (ISM-1563) and a plan of action and milestones (ISM-1564).

    Good evidence

    The system began operating after the authorisation date or, if it was already running when authorisation was introduced, now holds an authorisation. The decision record refers to the security assessment report (ISM-1563) and the plan of action and milestones (ISM-1564) or, for a decision made on partial evidence, names which of them is outstanding.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The limits and any expiry date set in the authorisation, with the live configuration they apply to.

    Look at

    Whether each limit is in force and whether the authorisation has expired.

    Good evidence

    The authorisation is either recorded as ongoing with no limits, or has not expired and each limit it sets is in force on the live system.

Mappings

Closest match in ISO/IEC 27001: A.5.12, Classification of information, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.5.12Classification of informationPartially overlaps

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