Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias through frequent references to Windows-specific tools (e.g., PowerShell, Windows Error and Warning Events), and scenario examples that focus on Windows malware and PowerShell-based attacks. There is a lack of Linux-specific detection scenarios, examples, or references to Linux-native tools and attack patterns. Windows-centric terminology and tools are mentioned before or instead of Linux equivalents, and no Linux/POSIX command-line or attack examples are provided.
Recommendations
- Add detection scenarios and examples involving Linux-based threats, such as SSH brute force, suspicious sudo activity, or Linux-specific malware.
- Include references to Linux logs (e.g., syslog, auth.log) and Linux-native tools (e.g., Bash, systemd, auditd) in scenario tables and examples.
- Provide parity in examples by showing how multistage attacks might manifest on Linux systems, including relevant alerts and severity levels.
- Mention Linux data connectors and how to configure them for Fusion, alongside Windows connectors.
- Ensure that documentation covers both Windows and Linux environments equally, especially in sections describing attack detection, incident generation, and analytics rule configuration.
Create Pull Request