Skip to content
Cyber security roles
ASD ISMISM-1634

ASD ISM 1634 System owners select and tailor controls in consultation with authorising officer

What it says

System owners, in consultation with each system's authorising officer, select security controls for each system and tailor them to achieve desired security and resilience objectives.

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

In plain English

Each system's owner must decide which security controls apply and tailor them to meet its desired security and resilience objectives, consulting its authorising officer.

System owners, in consultation with each system's authorising officer (the senior executive who decides whether a system may operate), must select security controls for each system and tailor them to achieve the desired security and resilience objectives. Selecting means deciding which controls apply to this system. Tailoring means adjusting each one's scope, settings or method to fit. ISM-1633 sets the objectives, and ISM-0009 covers any supplementary controls the system's unique nature requires. Implementing them is a separate step (ISM-1635).

Why it matters

Controls copied from a template can leave a system's actual objectives unmet and spend effort where it does not apply. Selecting and tailoring against this system's objectives shows which objective each control serves and exposes any objective left uncovered.

How to implement

  1. Gather the inputs for this system.

    Use its boundary and objectives (ISM-1633) and its threat and risk assessment (ISM-1203). If either is missing, complete it first, because the selection depends on both.

  2. Mark every ISM control as applicable or not.

    Compare each control's applicability marking (NC, OS, P, S or TS) with the system's classification, then check it against the system's technology and functions. Record a reason for each control left out, such as no wireless networking in this system.

  3. Tailor the selected controls to the objectives.

    Set each one's scope, settings and method, for example backup timing that meets a recovery objective. Identify any supplementary controls (ISM-0009). Note controls inherited from a platform or provider, using the shared responsibility model for a bought service (ISM-1569).

  4. Consult the authorising officer on the result.

    Walk through what was selected, left out and tailored, and why. Record the response and make any changes before implementation starts (ISM-1635).

  5. Record the selection in the system security plan annex.

    List each applicable and additional control (ISM-0041), and how you plan to implement it. The authorising officer approves this documentation (ISM-0047).

Keep it running

Revisit the selection and tailoring when the objectives, technology, threats or classification change, and when a new ISM release adds or changes controls. Record each change in the annex.

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 system security plan annex for each system.

    Look at

    Whether any system has no recorded selection of security controls.

    Good evidence

    Every system on the register and the independent list has its own recorded selection of security controls.

  2. Check 2 of 4What an auditor asks for

    Ask for

    The annex for a sampled system, with a list of the technology actually in it from a discovery scan or configuration records.

    Look at

    Whether each control left out really does not apply, and whether any technology present has its controls left out.

    Good evidence

    Every control left out has a reason that holds up against the system's actual technology, and no technology present has had its applicable controls left out.

  3. Check 3 of 4What an auditor asks for

    Ask for

    A sample of tailored controls, with the security and resilience objectives they serve.

    Look at

    How each was tailored, which objective it supports, and whether any objective has no control behind it.

    Good evidence

    Each sampled control traces to a named security or resilience objective, its tailoring is specific to this system, and no objective is left without a control.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The record of consultation with the authorising officer, the annex and the date implementation started.

    Look at

    When the officer was consulted, whether they saw what was left out as well as what was selected, and whether the annex carries their approval.

    Good evidence

    A dated record shows the authorising officer was consulted on what was selected, left out and tailored before implementation started or, for a system already running, before the selection was finalised, and the annex carries the officer's approval (ISM-0047).

Mappings

Closest match in ISO/IEC 27001: A.8.26, Application security requirements, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.8.26Application security requirementsPartially overlaps
ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

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