What does ASD ISM 1657 require?

policyASD Information Security Manual (ISM)

ASD ISM 1657Restrict Application Execution to Approved Set

Official control statement

Application control restricts the execution of executables, libraries, scripts, installers, compiled HTML, HTML applications and control panel applets to an organisation-approved set.

policyASD Information Security Manual (ISM)ISM-1657

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

In plain English

Only approved software and scripts can run, enhancing system security.

ML1 ML2 ML3 NC OS PASD Information Security ManualGuidelines for system hardening

Control Stack classificationPreventative Application control

record_voice_over

What this means in practice

This control ensures that only approved software is allowed to run on your organisation's computers. It's important because if unauthorised programs are executed, they could introduce viruses or allow hackers to steal information, causing serious business disruptions.

01 - Overview

Framework

ASD Information Security Manual (ISM)

Control effect (Control Stack)

Preventative

Classifications

NC, OS, P, S, TS

ISM last updated

Sept 2025

Control Stack last updated

29 Sept 2026

E8 maturity levels

ML1, ML2, ML3

Guideline

Guidelines for system hardening

Section

Operating system hardening

Topic

Application control

priority_high

Why it matters

Without application control (approved allow list), unauthorised executables, scripts or libraries can run, enabling malware, privilege abuse and unauthorised access to systems and data.

settings

Operational notes

Maintain and review the application allow list; test and deploy updates promptly. Verify enforcement blocks unapproved executables, scripts, installers and libraries, and monitor logs for blocked attempts.

02 - Implement

build

Implementation tips

IT team: Compile a list of approved applications that are necessary for organisational tasks. Work with department heads to determine which programs are essential for daily operations and ensure these are the only ones allowed to run.
System owner: Implement application control software to manage which applications can be executed. Use the approved applications list to configure the software to block anything not listed.
Management: Communicate to all staff the importance of using only approved software for their tasks. This can be done via email or a team meeting, highlighting the risks of unauthorised software.
IT team: Regularly review and update the list of approved applications. Set a quarterly meeting with key stakeholders to ensure new software needs are considered and keep the list current.
IT team: Train staff on recognising and reporting attempts to run unauthorised software. Offer workshops or online courses explaining the steps they should take if they receive suspicious software requests.

03 - Audit

fact_check

Audit / evidence tips

AskA copy of the approved applications list: Request the list of software and scripts that are currently approved for useLook atThe contents to ensure it is up-to-date and comprehensiveGoodList will have software names, version numbers, and approval dates
AskA demonstration of the application control software: Request a live demonstration showing how the software blocks unauthorised applicationsLook atThe software's settings and logsGoodDemonstration will show blocked attempts to run unapproved applications
AskResults of the latest review of approved applications: Request documentation of the last review meeting outcomesLook atNotes detailing stakeholder input and updates madeGoodIncludes a summary of reviewed applications and any changes made
AskTo see staff training records on application control: Request evidence of completed training courses or sessionsLook atRecords showing participation and awareness. Good records will have dates, participant names, and summary of the training conducted
AskExamples of user reports on unauthorised software attemptsLook atAny incident logs or reporting records from staffGoodShows that staff are vigilant and reports are being addressed promptly

04 - Mappings

link

Cross-framework mappings

How ISM-1657 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.

ISO 27001

Control	Notes	Details
sync_altPartially overlaps(1)expand_less
Annex A 8.18	Annex A 8.18 requires restricting and tightly controlling use of utility programs that can override system and application controls, effe...

E8

Control	Notes	Details
equalEquivalent(1)expand_less

E8-AC-ML1.3	E8-AC-ML1.3 requires application control to restrict execution of executables, libraries, scripts, installers, and similar content to an ...
open_in_fullBroader than(4)expand_less

E8-AC-ML1.1	E8-AC-ML1.1 requires implementing application control on workstations to restrict what software can execute
E8-AC-ML1.2	E8-AC-ML1.2 requires application control to be applied to user profiles and temporary folders used by operating systems, browsers and ema...
E8-AC-ML2.3	E8-AC-ML2.3 requires implementing Microsoft's recommended application blocklist to block known unwanted applications
E8-AC-ML3.2	ISM-1657 requires restricting execution to an organisation-approved set for a wide range of application artefacts (executables, libraries...
sync_altPartially overlaps(3)expand_less

E8-AC-ML2.1	E8-AC-ML2.1 requires application control on internet-facing servers to ensure only approved applications run
E8-AC-ML2.2	ISM-1657 requires application control that restricts execution to an organisation-approved set of executable artefacts
E8-AC-ML3.1	E8-AC-ML3.1 requires application control on non-internet-facing servers to ensure only approved software can run
handshakeSupports(1)expand_less

E8-AC-ML2.4	ISM-1657 requires restricting application execution to an organisation-approved set, which depends on the quality and currency of the all...