A Windows security tool for real-time adversary tradecraft detection, memory scanning, and forensics via behavior-driven rules.
Fibratus is a Windows security tool that detects, protects against, and hunts advanced adversary tradecraft by analyzing system events in real-time. It uses a behavior-driven rule engine and YARA memory scanning to identify malicious activities, and supports forensic analysis through event capture. The tool helps security teams monitor, alert, and investigate threats on Windows environments.
Security professionals, incident responders, and threat hunters working on Windows systems who need real-time detection and forensic capabilities. It is also suitable for blue teams and SOC analysts focused on adversary hunting and tradecraft analysis.
Developers choose Fibratus for its integrated approach combining real-time behavior detection, memory scanning, and forensics in a single tool. Its extensibility via Python filaments and customizable rule engine allows for tailored security monitoring, making it a versatile alternative to commercial endpoint detection solutions.
Adversary tradecraft detection, protection, and hunting
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Combines real-time behavior detection, YARA memory scanning, and forensic capabilities in a single tool, as emphasized in the Fibratus mantra from the README.
Offers a behavior-driven rule engine with a catalog of rules and CLI commands for exploration and creation, enabling tailored threat detection based on system events.
Supports filaments for adding custom tools using Python, leveraging the Python ecosystem to extend functionality, as highlighted in the README.
Ships events and alerts to various outputs like Eventlog or external systems, facilitating integration with existing security infrastructure, as noted in the key features.
Exclusively designed for Windows systems, making it unsuitable for organizations with mixed or non-Windows environments, a clear restriction from the GitHub description.
Requires in-depth knowledge of system events, rule syntax, and possibly Python for filaments, with setup involving command-line tools and external documentation, which can be daunting.
Real-time event scrutiny and memory scanning with YARA may impose significant CPU and memory overhead, potentially affecting performance on resource-constrained systems.