Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a clear Windows bias by prioritizing Windows technologies, APIs, and tools (e.g., CNG, CAPI, Win32/64, .NET, BitLocker, TPM on Windows IoT Core, SQL Server features) throughout the cryptography guidance. Windows-specific solutions are described in detail, often with code examples, while Linux or cross-platform equivalents are rarely mentioned or omitted entirely. Where alternatives are listed (e.g., random number generators), Windows APIs are listed first and with more detail. There are no Linux command-line or open-source tool examples, and Linux-specific cryptographic practices (e.g., use of OpenSSL, dm-crypt, LUKS, GnuPG, Linux TPM stack) are missing.
Recommendations
- Include Linux-specific examples and references for cryptographic operations, such as OpenSSL, GnuPG, dm-crypt/LUKS for disk encryption, and Linux TPM tools.
- Provide parity in code samples, showing both Windows (.NET, CNG, PowerShell) and Linux (Python, C, Bash/OpenSSL) implementations for key generation, encryption, and random number generation.
- Mention and link to Linux equivalents for features like BitLocker (e.g., LUKS/dm-crypt), TPM support (Linux tpm2-tools), and database encryption (PostgreSQL TDE, MySQL encryption).
- List cross-platform APIs and libraries (e.g., OpenSSL, libsodium, BouncyCastle) alongside Windows-specific ones.
- Avoid listing Windows APIs/tools first by default; alternate or group by platform.
- Add guidance for Linux/Unix administrators and developers, including relevant security policies and configuration steps.
Create Pull Request