Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a noticeable Windows bias. Many examples and hunting queries focus on Windows-specific tools (e.g., PowerShell, rundll32.exe, certutil, Exchange PowerShell Snapin), and several analytic rules and queries are tailored to Windows process activity and registry manipulation. There is a lack of Linux-specific examples, tools, or patterns, and the content prioritizes Windows-centric threats and detection methods. Linux equivalents or cross-platform considerations are missing throughout the document.
Recommendations
- Add Linux-specific analytic rules and hunting queries, such as detection of suspicious bash scripts, cron job persistence, or common Linux malware behaviors.
- Include examples of Linux process activity (e.g., suspicious use of bash, sh, systemd, or common Linux binaries like curl, wget, netcat) alongside Windows examples.
- Provide parity for registry activity by mentioning Linux equivalents (e.g., manipulation of configuration files like /etc/passwd, /etc/shadow, or systemd service files).
- Balance PowerShell-heavy examples with Linux shell script or command-line examples (e.g., detection of malicious shell scripts, use of sudo, or abuse of system utilities).
- Explicitly note cross-platform applicability of ASIM where relevant, and clarify which rules or queries are Windows-only versus platform-agnostic.
- Where possible, reference Linux security tools (e.g., auditd, syslog, journald, SELinux) and how their logs can be normalized and analyzed within ASIM.
Create Pull Request