Siemens side-loading triage worksheet
One record per host or linked execution. Use UTC times, retain original evidence, and state unknowns.
1. Establish origin and process context
- Case and host reference, analyst, and response owner.
- Observed time or range and source timezone.
- Executable path, hash, version, signer, and signature result.
- Origin: approved deployment, download, installer, or unknown; retain an evidence reference.
- User, parent process, process ID or stable process key, and launch time.
2. Join the process to loaded DLLs
For each DLL, record path or identity reference; load time and process key; hash, signer, and evidence reference. An adjacent file is not proof it loaded.
Record module telemetry source, retention, and whether collection was enabled at the relevant time. Missing module records are a visibility gap, not an all-clear.
Do not launch a suspicious copy to update it. Preserve evidence and follow incident response.
3. Follow-on activity and search coverage
Record results, times, and evidence for startup entries and scheduled tasks; child processes and network activity; hosts and sources searched; retention, gaps, and exclusions.
4. Response and operational safety
If isolation could affect operations, agree on safe containment with the operational owner. Record access, consequence, containment decision, decision maker, and time; preserve evidence, record necessary response, and track outstanding actions.
5. Two closure records
Patch: approved source, version 4.0.9.8 or later verified, change record, and owner.
Incident: scope, execution explained, response evidence, and unresolved gaps.
Record the next action, named owner, due time, and incident status. A patched installation does not close an incident. This working record is not proof a host is clean.
Primary source: Siemens SSA-580366, v1.2; Siemens ProductCERT notice, October 19, 2026. Reviewed October 20, 2026.
