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 and technologies such as PowerShell and Windows Management Instrumentation (WMI), with no mention of equivalent Linux tools or scenarios. Examples and detection scenarios focus on Windows-centric attack patterns and do not provide parity for Linux environments. The documentation also references Microsoft Defender for Endpoint (which is historically Windows-focused, though now cross-platform) and does not mention Linux-specific security tools, logs, or attack techniques. This results in limited guidance for organizations with significant Linux infrastructure.
Recommendations
- Add detection scenarios that cover Linux-specific attack vectors, such as suspicious Bash or Python script execution, use of cron jobs for persistence, or exploitation of Linux services (e.g., SSH, sudo).
- Include examples of credential theft tools and techniques relevant to Linux (e.g., use of 'John the Ripper', 'Hydra', or 'ssh-agent' abuse), alongside Windows tools like Mimikatz.
- Reference Linux equivalents for Windows technologies mentioned (e.g., instead of only PowerShell, also discuss Bash, Python, Perl, etc.; for WMI, discuss D-Bus, systemd, or other Linux management interfaces).
- Highlight cross-platform capabilities of Microsoft Defender for Endpoint and Sentinel, and provide guidance on configuring and ingesting Linux logs (e.g., syslog, auditd, journald) into Sentinel.
- Ensure that examples and scenarios do not always begin with Windows-centric technologies, but alternate or balance with Linux-focused content.
- Mention Linux-specific MITRE ATT&CK techniques and tactics where relevant, such as Linux privilege escalation, lateral movement via SSH, or Linux ransomware behaviors.
Create Pull Request