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 EnglishDevelop 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.
Free. Save your status, tasks and notes.
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
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.
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).
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.
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
- 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.
- 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.
- 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/IEC 27001: 2 mappings
This control is broader than A.8.8.
Annex A 8.8 requires obtaining vulnerability information, evaluating exposure and implementing measures including secure configuration of platforms. ISM-1914 requires approved configurations for operating systems to be developed, implemented and maintained, directly reducing exposure from insecure OS settings and configuration drift. Annex A 8.8 is broader because it encompasses vulnerability identification and assessment activities and is not limited to OS configuration baselining.
This control partially meets A.8.9.
Annex A 8.9 requires secure configurations to be established and managed across IT systems. ISM-1914 aligns by requiring approved configurations for operating systems to be developed, implemented and maintained. ISM-1914 is limited to operating systems, while Annex A 8.9 spans OS, applications, hardware, services and networks and explicitly includes monitoring and review.
ASD Essential Eight: 1 mapping
This control is broader than E8-AH-ML3.2.
E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0 on Windows systems. ISM-1914 requires approved configurations for operating systems to be developed, implemented and maintained, and an approved Windows baseline would typically mandate disabling legacy components like PowerShell 2.0. ISM-1914 covers the full lifecycle of OS configuration governance, whereas E8-AH-ML3.2 is one specific configuration outcome.
ASD Essentials for enterprise IT: 3 mappings
- IT.PRO-01.2Use secure build and deployment processes to enforce security controls consistentlyPartially overlaps
This control partially overlaps IT.PRO-01.2.
IT.PRO-01.2 requires secure build and deployment processes that enforce controls consistently across systems; ISM-1914 supports this for operating systems, requiring approved configurations to be developed, implemented and maintained.
- IT.PRO-04.1Define approved hardening baselines disabling unneeded services, insecure settings and weak protocolsPartially overlaps
This control partially overlaps IT.PRO-04.1.
IT.PRO-04.1 requires approved configuration baselines that disable or remove unnecessary services, insecure settings and weak protocols; ISM-1914 requires approved operating system configurations to be developed, implemented and maintained, which goes beyond defining them.
- IT.PRO-04.2Deploy approved configuration baselines on systems, including infrastructure, operating systems and applicationsPartially overlaps
This control partially overlaps IT.PRO-04.2.
IT.PRO-04.2 requires approved configuration baselines to be deployed on infrastructure, operating systems and applications; ISM-1914 requires approved operating system configurations to be developed, implemented and maintained, covering the operating system part of it.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




