Bias Analysis
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: Windows-centric terminology (NTDomain, NetBiosName, SID, RegistryKey, RegistryValue) is used throughout, often without Linux equivalents or explanations. Windows-specific concepts (such as NTFS AlternateDataStreamName, WindowsSecurityZoneType, and registry hives) are referenced exclusively. The entity schemas and identifier examples prioritize Windows constructs, and there are no examples or explicit mentions of Linux-specific identifiers, tools, or patterns, despite the OSFamily field supporting Linux. No Linux-specific file paths, process attributes, or system concepts are provided.
Recommendations
- Add Linux-specific examples and attributes for relevant entity types (e.g., file paths using /home/user/file, Linux process attributes like UID/GID, SELinux context, etc.).
- For fields like RegistryKey and RegistryValue, clarify that these are Windows-only and provide equivalent Linux concepts (such as configuration files, systemd unit files, or dconf/gsettings for desktop environments).
- In the Host entity, provide examples of Linux hostnames, domain joining (e.g., sssd/realmd), and mention Linux-specific identifiers (such as machine-id, /etc/hostname, etc.).
- For Account entities, include Linux account identifiers (e.g., UID, /etc/passwd username, group membership) and clarify differences in domain concepts.
- Where Windows-specific fields are present (e.g., NTDomain, NetBiosName, SID), explicitly note their OS applicability and suggest Linux alternatives or state when fields are not relevant.
- Include Linux process examples (e.g., process ID, command line, parent PID, etc.) and clarify differences in process management.
- Review all entity schemas for opportunities to add Linux parity and cross-reference OS-specific documentation where appropriate.
Create Pull Request