2.3 KiB
2.3 KiB
Windows EVTX Export for Hayabusa
This document defines the Windows-side export path for Hayabusa DFIR enrichment.
Purpose
Windows hosts do not analyze EVTX locally for this contour.
They export selected event logs into a bounded forensic staging area, and the server-side Hayabusa workflow on 10.10.10.13 analyzes those artifacts later.
Export script
- script:
windows/export-evtx-for-hayabusa.ps1 - deployed path on Windows host:
<StateRoot>\export-evtx-for-hayabusa.ps1
Default config path:
C:\ProgramData\AWatch-rus\deployment-config.json
Default export root
<StateRoot>\forensics\evtx-exports- Ansible override variable:
aw_windows_forensics_root - retention override variable:
aw_windows_evtx_retention_days - channel override variable:
aw_windows_evtx_channels
Example:
C:\ProgramData\AWatch-rus\forensics\evtx-exports
Each run creates:
<forensics-root>\<HOST>-<YYYYMMDD-HHMMSS>\evtx\*.evtx<forensics-root>\<HOST>-<YYYYMMDD-HHMMSS>\manifest.json- optional zip:
<forensics-root>\<HOST>-<YYYYMMDD-HHMMSS>.zip
Default channel set
SecuritySystemApplicationMicrosoft-Windows-PowerShell/OperationalMicrosoft-Windows-TerminalServices-LocalSessionManager/OperationalMicrosoft-Windows-TerminalServices-RemoteConnectionManager/Operational
Notes:
Sysmonis intentionally not assumed by default.- If
Sysmonexists in the environment, it should be added later as an explicit extension. - the channel list is now carried through deployment config and validation, not left as an implicit script default.
Retention
- default retention:
14days - cleanup is local to the forensic export root
- old export directories and zip packages are removed after the retention cutoff
- retention is now exposed as
aw_windows_evtx_retention_daysin Ansible vars
Example run
powershell.exe -ExecutionPolicy Bypass -File C:\ProgramData\AWatch-rus\export-evtx-for-hayabusa.ps1
Example with custom window:
powershell.exe -ExecutionPolicy Bypass -File C:\ProgramData\AWatch-rus\export-evtx-for-hayabusa.ps1 -DaysBack 1
Boundaries
- output stays outside standard AW buckets
- output stays outside normal DLP screenshot artifacts
- this phase only defines and validates Windows export
- transfer to
10.10.10.13and Hayabusa execution belong to later phases