A Cloud Sandbox detonation shows a document beaconing through obfuscated scripts and spawning child processes...

The observed beaconing, script obfuscation, child-process creation, and calls to newly registered domains justify preventive enforcement. In a ZIA Sandbox rule, Quarantine holds an unknown file while analysis is performed, as documented in Configuring the Sandbox Policy. A more specific rule for the affected document type and required users, locations, or destinations should be placed above a broader existing rule so it is evaluated first. Applicable web and SaaS delivery paths should be included to avoid a channel gap. If analysis determines the file is safe, the configured workflow can release it; a malicious verdict prevents delivery and supports follow-up investigation. Out-of-band-only scanning occurs after storage and does not provide equivalent inline prevention. Manual review delays containment, and lowering sensitivity reduces protection despite strong malicious behavior. Option A therefore prevents another patient-zero download while retaining controlled analysis.