Bias Analysis
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: anomaly detections and machine learning models are heavily focused on Windows Security logs (e.g., event IDs 4624 and 4625), with no equivalent coverage or examples for Linux systems. Windows-specific terminology and tools (such as Windows Security logs and PowerShell as a sub-technique) are referenced, while Linux audit logs, syslog, or other Linux-native mechanisms are absent. There are no examples or descriptions of anomaly detection for Linux account creation, logins, or brute force attempts, nor is there mention of Linux-specific event sources or patterns.
Recommendations
- Add equivalent anomaly detection rules and descriptions for Linux systems, such as monitoring /var/log/auth.log, /var/log/secure, or auditd logs for account creation, deletion, and login events.
- Include Linux-specific event IDs, syslog patterns, or audit rules alongside Windows Security log references.
- Provide examples of anomaly detection for Linux brute force attempts, privilege escalation, and code execution (e.g., monitoring sudo, su, or shell activity).
- Reference Linux tools and mechanisms (such as auditd, syslog, journald, or systemd) in parallel with Windows tools.
- Ensure that anomaly detection coverage and documentation are platform-agnostic, or clearly indicate parity between Windows and Linux where possible.
Create Pull Request