Skip to content
System hardening
ASD ISMISM-1914

ASD ISM 1914 Ensure operating systems have approved configurations

What it says

Approved configurations for operating systems are developed, implemented and maintained.

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

What it means

In plain English

Develop an approved configuration for each operating system in use, apply it to the machines running that system and keep it current; a signed-off document alone does not meet this.

Approved configurations for operating systems on workstations and servers, meaning required settings that have been formally signed off, must be:

  • Developed: required settings are worked out for each operating system in use, drawing on the guidance ISM-1409 requires.
  • Implemented: machines actually run those settings, so a document alone does not count.
  • Maintained: settings stay current as the operating system and its hardening guidance change. The statement sets no interval, so the organisation sets one. ISM-0888 separately sets how often the written configuration is reviewed.

Why it matters

An operating system left in its default state, or set up with settings nobody approved, can give malicious actors an initial foothold on the network. An approved configuration that machines actually run replaces those defaults with settings someone checked and signed off.

How to implement

  1. List each operating system and version in use.

    Take them from your asset inventory and a network discovery scan, covering workstations and servers, and note roles that need different settings, such as domain controllers or internet-facing servers.

  2. Develop a configuration for each one.

    Start from the ASD and vendor hardening guidance ISM-1409 requires, then add settings the ISM names separately, such as exploit protection (ISM-1492) and boot protections (ISM-1745). Record each setting, its required value and the reason.

  3. Get each configuration approved and dated.

    ISM-0047 sets the approver: the chief information security officer for organisational-level documents, the system's authorising officer for system-specific ones. Add a 'current as at' date and review the document at least annually (ISM-0888). Run later changes through your change and configuration management plan (ISM-0912).

  4. Apply it through central management.

    Push settings by central policy or an endpoint management tool, and build them into your standard operating environments (ISM-1406), so new machines start compliant. For a provider-run server or vendor appliance, agree the settings in writing and get a settings export, because your tools may not reach it.

  5. Check for drift and keep the configuration current.

    Run a configuration compliance scan that compares live settings with approved values, at an interval you set, and fix differences. Revise and re-approve the configuration when the operating system or hardening guidance changes.

Keep it running

Compare live settings with the approved values at an interval the organisation sets, because the statement sets none, and fix any machine that differs. A new operating system release or new hardening guidance should trigger a revision and fresh approval.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The approved configurations with their approval records, and a network discovery scan listing the operating systems on workstations and servers.

    Look at

    Whether every operating system and version found has a configuration, who approved each one, and its 'current as at' date.

    Good evidence

    Every operating system on the scan has a configuration approved as ISM-0047 requires, with a 'current as at' date no more than 12 months old (ISM-0888).

  2. Check 2 of 3What an auditor asks for

    Ask for

    Live settings exported from workstations and servers sampled from that scan, including machines outside central management.

    Look at

    Every difference between live settings and approved values.

    Good evidence

    Every setting on every sampled machine matches its approved value. A difference fails even when an exception is recorded for it.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The change history of a sampled configuration, with the release dates of the operating system versions and hardening guidance it covers.

    Look at

    Whether each release was assessed, and whether resulting changes reached live machines.

    Good evidence

    Each release since the configuration was first approved was assessed, any changed setting was re-approved, and the new values appear on the sampled machines.

Mappings

Closest match in ISO/IEC 27001: A.8.8, Management of technical vulnerabilities, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 2 mappings

  • A.8.9Configuration managementPartially meets
Essential Eight

ASD Essential Eight: 1 mapping

ASD Essentials

ASD Essentials for enterprise IT: 3 mappings

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