ASD ISM 1624 Protect PowerShell script block logs
What it says
PowerShell script block logs are protected by Protected Event Logging functionality.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Encrypt PowerShell script block logs with Protected Event Logging, so their contents, which can include credentials, can be read only with the private key.
PowerShell script block logs must be protected by Protected Event Logging, a feature that encrypts sensitive event log content with a public key, so only the matching private key can decrypt it. Script block logging (ISM-1623) records the code PowerShell processes, which can include credentials. The control names this feature, so access permissions on the logs (ISM-1985) do not replace it. It covers script block logs only, not module logs or transcripts.
Free. Save your status, tasks and notes.
Why it matters
Script block logs can capture credentials and other sensitive data that scripts use, so on a compromised device readable logs could give a malicious actor what they need to reach further. Encrypted entries hide the script text from anyone without the private key.
How to implement
Issue a certificate for encrypting the logs.
It needs the Document Encryption enhanced key usage and either the Data Encipherment or Key Encipherment key usage. Create it with your certificate authority or a certificate tool, then separate the public certificate from the private key.
Keep the private key off the devices that log.
Hold it only where logs are decrypted, such as a secured central log collector, and restrict who can use it. Back it up, because losing it makes the protected logs unreadable.
Set up and test decryption on a pilot group before deploying Protected Event Logging widely.
The script text in encrypted events cannot be searched or alerted on until decrypted. Decrypt at the collector, for example with Unprotect-CmsMessage on event ID 4104, before your analysis tool reads them, and protect the decrypted copies from unauthorised access (ISM-1985).
Deploy the policy to every workstation and server.
In Group Policy, under Administrative Templates, Windows Components, Event Logging, turn on the policy named Enable Protected Event Logging and supply the public certificate by thumbprint, path or encoded content. Devices outside Group Policy need the same setting through your device management tool or powershell.config.json.
Close gaps you cannot configure directly.
Ask a provider that runs a server to apply this setting. A Windows version without the feature needs upgrading (ISM-1407 requires the latest or previous release). Until then, record a known shortfall for the authorising officer.
Keep it running
Keep each private key for as long as logs encrypted with it are retained (ISM-1988). Replacing the certificate, rebuilding the log collector or changing the analysis tool should trigger a fresh test from device to decryption.
Evidence and audit
- Check 1 of 3What an auditor asks for
Look at
Whether the event holds readable script text or an encrypted message in Cryptographic Message Syntax, and whether searching the device's script block events finds the marker word.
Good evidence
On every sampled device the event holds an encrypted message, and the marker word cannot be found in the device's script block events.
- Check 2 of 3What an auditor asks for
Ask for
A decryption of those events at the collector, and the location of the private key.
Look at
Whether the marker word can be read after decryption, and whether any sampled logging device holds the private key.
Good evidence
The marker word appears after decryption at the collector, and no sampled logging device holds the private key.
- Check 3 of 3What an auditor asks for
Ask for
The Protected Event Logging policy state for all Windows workstations and servers from your management tool, with the IT equipment registers and a discovery scan to compare it with.
Look at
Devices on those lists missing from the report, or without the policy or the current certificate.
Good evidence
Every Windows workstation and server on those lists has the policy on with the current certificate. A recorded gap is a shortfall, not a pass.
Mappings
Closest match in ASD Essential Eight: E8-AH-ML2.13, Protect event logs from unauthorised changes or deletion, which this control covers in full and more.
ASD Essential Eight: 5 mappings
This control is broader than E8-AH-ML2.13.
ISM-1624 requires PowerShell script block logs to be protected using Protected Event Logging functionality. E8-AH-ML2.13 requires protection of event logs from unauthorised modification and deletion at a general level, which includes PowerShell event logs. ISM-1624 is a more specific requirement focused on a particular Windows logging feature and log source, while E8-AH-ML2.13 is broader and does not prescribe a specific mechanism.
This control partially meets E8-AC-ML2.6.
ISM-1624 requires PowerShell script block logs to be protected using Protected Event Logging functionality. E8-AC-ML2.6 requires event logs generally to be protected from unauthorised modification and deletion, which includes PowerShell-related event logs in scope. ISM-1624 is a specific technical instantiation for one high-value log source (PowerShell script blocks), whereas E8-AC-ML2.6 applies broadly to event logs across systems.
This control partially meets E8-RA-ML2.8.
ISM-1624 requires PowerShell script block logs to be protected using Protected Event Logging functionality. E8-RA-ML2.8 requires event logs to be protected from unauthorised modification and deletion across the environment, which would encompass PowerShell logs as a subset. ISM-1624 is narrower because it specifies one log type and a particular protection approach rather than a general requirement for all event logs.
- E8-AH-ML2.11Centrally log PowerShell module, script block, and transcription eventsPartially overlaps
This control partially overlaps E8-AH-ML2.11.
ISM-1624 requires PowerShell script block logs to be protected using Protected Event Logging to prevent tampering and unauthorised disclosure. E8-AH-ML2.11 relates by requiring PowerShell module, script block and transcription logging to be centrally logged, which is a common way to improve integrity and retention of these logs. ISM-1624 focuses on the protection mechanism for script block logs specifically, while E8-AH-ML2.11 focuses on central collection across multiple PowerShell log types rather than the specific protection method.
This control partially overlaps E8-MF-ML2.7.
E8-MF-ML2.7 requires event logs to be protected from unauthorised modification and deletion. ISM-1624 strengthens this outcome for a specific log source by requiring PowerShell script block logs to be protected using Protected Event Logging, reducing opportunities for attackers to tamper with that telemetry. ISM-1624 is narrower (PowerShell-specific) and does not, by itself, address protection of all event logs across the environment.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




