Document Details
Threat Modeling Tool Cryptography
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
powershell_heavy
⚠️
missing_linux_example
Summary:
The documentation demonstrates a strong Windows bias throughout. Windows-specific technologies, APIs, and tools (such as CNG, CAPI, Win32/64, BitLocker, SSIS, SQL Server, TPM on Windows IoT Core) are mentioned exclusively or before any cross-platform or Linux alternatives. .NET and Windows-centric cryptographic APIs are detailed, while Linux or open-source equivalents are rarely, if ever, mentioned. Example code and references are almost entirely Windows/.NET-focused, and there are no Linux command-line, OpenSSL, or cross-platform examples provided.
Recommendations:
- Add Linux and cross-platform examples for cryptographic operations, such as using OpenSSL for key generation, encryption, and random number generation.
- Mention Linux equivalents for Windows tools (e.g., LUKS/dm-crypt for BitLocker, GPG for file encryption, systemd-cryptsetup for device encryption).
- Include code samples in languages and frameworks common on Linux (e.g., Python with cryptography module, Java with BouncyCastle, C/C++ with OpenSSL).
- Reference Linux/Unix APIs and tools (e.g., /dev/random, /dev/urandom, cryptsetup, openssl) alongside Windows APIs.
- Provide guidance for securing cryptographic keys on Linux-based IoT devices (e.g., using hardware security modules, TPM2.0 tools, or secure elements supported on Linux).
- Balance .NET and Windows-specific recommendations with platform-agnostic or Linux-specific best practices.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |