What evidence do auditors commonly ask for on 24 Non-persistent virtualised sandboxed environment (Very Good)?

Sandbox reset policy and a test log showing a planted file gone after the session is closed; Architecture and configuration of the non-persistent sandbox used for web browsing and opening untrusted documents; Settings showing the sandbox resets to a clean state after each session and is isolated from corporate data; Usage records showing staff handling external attachments or risky browsing inside the sandbox.

What is the most common gap auditors find on 24?

Sandbox available but optional, so most users open untrusted files on their normal desktop

ASD Strategies to Mitigate Cyber Security Incidents · Limiting the Extent of Cyber Security Incidents

`24` Non-persistent virtualised sandboxed environment (Very Good)

Non-persistent virtualised sandboxed environment for risky activities such as processing untrusted documents and web browsing.

Source: ASD Strategies to Mitigate Cyber Security Incidents, 24. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ASD Strategies to Mitigate Cyber Security Incidents in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Cloud console / configuration management

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Sandbox reset policy and a test log showing a planted file gone after the session is closed · SIEM / log platform
Architecture and configuration of the non-persistent sandbox used for web browsing and opening untrusted documents · Cloud console / configuration management
Settings showing the sandbox resets to a clean state after each session and is isolated from corporate data · Cloud console / configuration management

periodic reviewEvidence produced at each review

Usage records showing staff handling external attachments or risky browsing inside the sandbox · Cloud console / configuration management

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Sandbox available but optional, so most users open untrusted files on their normal desktop
Virtual environment persists between sessions, letting malware survive a restart
Sandbox shares clipboard, drives or network access with the corporate environment

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

23 Protect authentication credentials (Excellent) · 25 Software firewall - inbound (Very Good)