Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page exhibits a Windows bias in several ways: many analytic rules and hunting queries focus on Windows-specific tools (e.g., rundll32.exe, PowerShell, certutil, Exchange PowerShell Snapin), and there is a notable absence of Linux-specific examples or references to Linux tools and patterns. The majority of process activity examples are Windows-centric, and PowerShell usage is highlighted repeatedly without mention of Linux shell equivalents. No Linux-specific threats, commands, or detection patterns are provided, and Windows terminology (e.g., registry, UAC bypass) is used exclusively or first.
Recommendations
- Add Linux-specific analytic rules and hunting queries, such as detection of suspicious bash, python, or perl scripts, or Linux persistence techniques (e.g., cron jobs, systemd services).
- Include examples of Linux command-line tools (e.g., grep, awk, systemctl) and detection of common Linux attack patterns (e.g., SSH brute force, sudo abuse, rootkit installation).
- Balance the coverage of Windows and Linux by providing parity in threat detection scenarios, such as both Windows and Linux privilege escalation, process monitoring, and file activity.
- Explicitly mention Linux equivalents when referencing Windows tools (e.g., PowerShell vs. bash/zsh, certutil vs. openssl), and provide hunting queries for both platforms.
- Highlight cross-platform threats and detection strategies, ensuring that examples and documentation do not assume a Windows-only environment.
Create Pull Request