Document Details
Threat Modeling Tool Sensitive Data
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
Detected Bias Types
windows_tools
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. Windows-specific technologies (EFS, DPAPI, BitLocker, Windows Intune, WCF with Windows credentials) are mentioned exclusively or before Linux equivalents. In several cases, only Windows solutions or .NET/C# code samples are provided, with little or no mention of Linux alternatives (e.g., LUKS/dm-crypt for file encryption, Gnome Keyring/KWallet for keystore, Linux-based obfuscation tools). Examples and references are heavily oriented towards Microsoft/Windows technologies, and Linux-specific guidance is generally missing.
Recommendations
- For every Windows-specific tool or technology (e.g., EFS, DPAPI, BitLocker), provide Linux equivalents (e.g., LUKS/dm-crypt, GnuPG, eCryptfs) and describe how to implement similar protections on Linux systems.
- Include code samples for both Windows (.NET/C#) and Linux (e.g., Python, Bash, OpenSSL) where applicable, especially for file encryption, configuration protection, and key management.
- When discussing Azure Disk Encryption, give equal detail to Linux disk encryption (dm-crypt) as is given to BitLocker for Windows.
- Mention cross-platform or Linux-native obfuscation tools (e.g., ProGuard for Java, pyarmor for Python) alongside CryptoObfuscator.
- Add references to Linux documentation and community resources for sensitive data protection, encryption, and secure configuration.
- Ensure that recommendations and examples for mobile clients include Android and iOS native approaches, not just Windows Intune or .NET for iOS.
- Where WCF or Windows authentication is referenced, clarify alternatives for Linux-based services (e.g., TLS client certificates, OAuth2, JWT).
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|