A collection of 200 Windows EVTX event log samples mapped to MITRE ATT&CK techniques for detection testing and threat hunting.
EVTX-ATTACK-SAMPLES is a collection of Windows EVTX event log files that simulate real attack techniques mapped to the MITRE ATT&CK framework. It provides security professionals with realistic log data to test detection capabilities, train in digital forensics, and understand adversary behaviors without needing to generate attacks themselves.
Cybersecurity professionals, including threat hunters, DFIR analysts, detection engineers, and red team members who work with Windows event logs and need realistic attack data for testing and training.
This project offers a unique, curated dataset of attack-specific EVTX samples directly mapped to ATT&CK techniques, saving security teams time in creating test data and providing standardized examples for detection development and training scenarios.
Windows Events Attack Samples
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Each EVTX sample is directly mapped to specific ATT&CK techniques, as highlighted in the README, providing clear context for detection development and threat hunting.
Enables testing of SIEM rules and detection scripts with realistic attack logs, saving time in creating test data for cybersecurity teams.
Serves as a hands-on dataset for digital forensics and incident response training, offering curated examples to practice threat hunting, as stated in the key features.
Includes a PowerShell script to parse and replay EVTX files into tools like Elastic Stack, facilitating easy log analysis and replay, as detailed in the README section.
The repository is exclusively for Windows EVTX logs, making it ineffective for security analysis in mixed or non-Windows environments.
While realistic, the samples are curated simulations that may not fully replicate the noise, variability, or edge cases of real-world attack logs.
Effective use, especially with the Winlogbeat script, depends on external tools like Elastic Stack and PowerShell, adding setup complexity and dependency overhead.
As admitted in the README, mapping is to ATT&CK techniques, not detailed procedures, which could limit granularity for advanced analysis or specific attack variations.