Repository navigation
Add a DFIR config and engagement kit, tested against real intrusions - #6
Merged
Merged
Conversation
- dfir/windows-ir.xml: incident-response Sysmon config designed from the 82 intrusions published by The DFIR Report. Logs every process, network connection, DNS query, driver, pipe and remote thread; covers the drop folders, file types and registry keys the intrusions used; keeps copies of tools deleted from drop folders. Exclusions are narrow and full-path only. - dfir/tests/cases.json: 71 events reconstructed from the reports (65 must be logged, 6 noise checks). check-cases.mjs runs them with the builder's rule engine; the DFIR config logs 65/65, the production config 32/65. - Validator IR profile (lint-config --ir): core events must log everything, name-only and user-writable exclusions are errors, LSASS access required. - apply-overlay.mjs merges per-client exclusions and re-validates. - Deploy/Collect/Remove PowerShell scripts: back up and restore any existing Sysmon, log sizes and audit policy; self-test; hashed evidence zip. - CI: IR lint and cases in the unit job, real Sysmon accepts the DFIR config and a merged overlay, and a new job runs the whole kit end to end on Windows PowerShell 5.1. Releases attach sysmon-dfir-kit.zip. Builder gets a DFIR preset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PS 5.1 turns redirected stderr from native programs into terminating errors when ErrorActionPreference is Stop; Sysmon writes its banner to stderr. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e folder Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ad of aborting Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rator is refused Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0xAnalyst
added a commit
that referenced
this pull request
Nov 1, 2026
Add a DFIR config and engagement kit, tested against real intrusions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of the incident-response version: the Windows config, its real-intrusion tests, and the scripts to deploy, collect and remove it during an engagement. See
dfir/README.mdfor the playbook.Config (
dfir/windows-ir.xml)The design comes from the 82 intrusions published by The DFIR Report (2020–2026):
SysmonIRArchive(about 37% of attackers deleted theirs).Real-intrusion tests
dfir/tests/cases.jsonholds 71 events reconstructed from the reports: 65 behaviors that must be logged and 6 noise checks.webapp/scripts/check-cases.mjsruns them through the builder's rule engine.dfir/windows-ir.xmlsysmonv9.xml(production)The cases also cover look-alikes of the exclusions, such as a fake
dllhost.exeunderProgramData\Microsoftand a Cobalt Strike pipe named like Chrome'smojo.*.Validation and client overlays
lint-config.mjs --irapplies an incident-response profile: core events must log everything, name-only and user-writable exclusions are errors, and LSASS access must be logged.apply-overlay.mjsmerges a client's exclusion file and re-validates it. A bad overlay (for example excludingsvchost.exeby name, orC:\Users\) is rejected.Engagement scripts (Windows PowerShell 5.1)
Deploy-SysmonIR.ps1Collect-SysmonIR.ps1: exported logs, deleted-file copies, deployment backups and host details, with a SHA256 manifest and a hashed zip.Remove-SysmonIR.ps1: restores the original Sysmon config or uninstalls Sysmon, and restores log sizes, audit policy and registry values. It refuses to run before a collection exists.CI
dfir-kitjob: on Windows, deploys twice, checks the audit and log settings, generates harmless intrusion-like activity and checks each event, collects and checks the zip and archive, then removes everything and checks the restore.Also:
sysmon-dfir-kit.zip.NOTICE.mdcredits The DFIR Report as a research reference. No report text is reproduced.🤖 Generated with Claude Code