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 technologies (PowerShell, WMI), tools (Microsoft Defender for Endpoint, formerly MDATP), and patterns (remote WMI execution, PowerShell command line). Examples and scenarios focus on Windows endpoints and do not mention or provide parity for Linux equivalents (e.g., Bash, SSH, Linux endpoint telemetry). Linux-specific attack patterns, tools, or detection methods are absent, and Windows-centric terminology is used throughout, with no corresponding Linux guidance or examples.
Recommendations
- Add scenarios and detection patterns for Linux endpoints, including common Linux attack techniques (e.g., SSH brute force, Bash script execution, Linux credential dumping tools like 'LaZagne' or 'John the Ripper').
- Provide examples of malicious activity using Linux-native tools (e.g., suspicious Bash commands, cron job abuse, systemd manipulation) alongside PowerShell and WMI examples.
- Reference Linux-compatible security solutions (e.g., Microsoft Defender for Endpoint for Linux, auditd, syslog, Linux firewall logs) in data connector sources and scenario descriptions.
- Ensure parity in threat detection coverage by describing how Fusion correlates signals from Linux systems and cloud-native Linux resources, not just Windows VMs and services.
- Explicitly mention Linux attack frameworks (e.g., Metasploit, Cobalt Strike on Linux, custom Python scripts) and how their activity would be detected.
- Balance the use of Windows-specific terminology with Linux equivalents, and avoid presenting Windows tools/patterns first or exclusively.
Create Pull Request