Security
116
Total Pages
38
Linux-Friendly Pages
78
Pages with Bias
67.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
380 issues found
Showing 301-325 of 380 flagged pages
Security
Microsoft Antimalware code samples for Azure | Microsoft Docs
...cles/security/fundamentals/antimalware-code-samples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively provides PowerShell code samples and references Windows-centric tools and configuration patterns (e.g., .exe processes, C:\ paths, XML config with Windows-style exclusions). There are no Bash, CLI, or Linux/macOS examples, nor any mention of Linux-specific Antimalware extension support or configuration. This creates friction for Linux users seeking parity or guidance.
Recommendations
- Clarify in the introduction whether Microsoft Antimalware is Windows-only, or explicitly state platform limitations.
- If Linux support exists, provide equivalent Bash/CLI examples for deploying and configuring the Antimalware extension on Linux VMs or Arc-enabled Linux servers.
- Reference Linux-specific configuration patterns (e.g., Linux file paths, process names) in sample exclusion lists.
- If Antimalware is not supported on Linux, add a clear note to inform users and direct them to Linux security solutions (e.g., Microsoft Defender for Endpoint on Linux).
Create Pull Request
Security
Cloud feature availability for commercial and US Government customers
...articles/security/fundamentals/feature-availability.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides feature availability for Azure and Azure Government clouds, focusing on security and compliance. While most content is platform-neutral, there are notable instances of Windows/PowerShell bias, particularly in administrative examples and feature tables. PowerShell is referenced as the primary method for service administration (e.g., Azure Information Protection, Azure Attestation), with no mention of Linux/macOS CLI alternatives. In feature tables, Windows-centric tools (PowerShell) are listed first or exclusively, and Linux equivalents (such as Azure CLI or REST API) are not referenced. However, most features themselves are not inherently Windows-only, and some Linux support is mentioned for IoT device builders.
Recommendations
- Include Azure CLI and REST API examples alongside PowerShell for administrative tasks, especially for Azure Information Protection and Azure Attestation.
- Explicitly mention cross-platform support for management tools where available.
- Add footnotes or links to Linux/macOS documentation for equivalent operations.
- Where PowerShell is listed as the only method, clarify if Linux users can use PowerShell Core or provide alternative instructions.
Security
Azure identity & access security best practices | Microsoft Docs
...ity/fundamentals/identity-management-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page presents Azure identity and access security best practices in a platform-neutral manner overall, but there are several instances of Windows bias. Windows-specific tools (e.g., Windows Hello for Business, Privileged Access Workstations, Microsoft Entra password protection for Windows Server Active Directory) are mentioned without Linux/macOS equivalents or alternatives. Examples and recommendations for admin workstations and password protection focus on Windows, and there are no Linux/macOS-specific guidance or examples for equivalent scenarios. This may create friction for organizations with non-Windows infrastructure.
Recommendations
- When mentioning Windows-specific tools (e.g., Windows Hello for Business, Privileged Access Workstations, Entra password protection for Windows Server), add notes or links to Linux/macOS alternatives or clarify if no equivalent exists.
- Provide examples or guidance for securing admin workstations on Linux/macOS (e.g., using hardened Linux desktops, macOS security best practices, or referencing CIS benchmarks).
- When discussing password protection, clarify whether Entra password protection is available for Linux/macOS, or suggest alternative approaches for those platforms.
- Include cross-platform CLI examples (e.g., Azure CLI usage on Linux/macOS) alongside PowerShell references, especially in sections about automation and workload identities.
- Explicitly state when a feature or recommendation is Windows-only to help non-Windows users understand applicability.
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform and avoids Windows-centric bias in most sections. However, the SMB encryption section exclusively references Windows versions and tools (Windows Server, Windows 8/10), and mentions SMB 3.0 encryption only in the context of Windows clients. This may create friction for Linux/macOS users who use SMB/CIFS to access Azure Files. Additionally, Windows tools are mentioned before any Linux equivalents, and no Linux/macOS SMB encryption guidance is provided.
Recommendations
- Add information about SMB encryption support for Linux and macOS clients, including references to relevant tools (e.g., smbclient, mount.cifs) and configuration steps.
- Clarify whether SMB encryption is available and supported for non-Windows clients accessing Azure Files, and link to official documentation for those platforms.
- When mentioning protocols or tools (like SMB), present cross-platform options or note platform-specific limitations.
- Consider including examples or references for Linux/macOS users in sections where Windows tools are mentioned.
Security
Security best practices for IaaS workloads in Azure | Microsoft Docs
...-docs/blob/main/articles/security/fundamentals/iaas.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides security best practices for Azure IaaS workloads and is intended for both Windows and Linux VMs. However, there is a notable Windows bias in several areas: PowerShell cmdlets (e.g., Add-AzKeyVaultKey, Set-AzVMDiskEncryptionExtension) are referenced without equivalent Linux CLI or Bash examples; Windows tools and concepts (e.g., WSUS, Windows Update, BitLocker) are mentioned before or more prominently than Linux equivalents; and some example links (e.g., snapshot-copy-managed-disk) point to Windows-specific documentation first. While Linux is acknowledged and supported in most features, Linux users may need to infer or search for equivalent commands and workflows.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell cmdlets for key management and disk encryption tasks.
- When referencing tools like BitLocker, also mention and link to DM-Crypt documentation for Linux.
- Ensure that links to snapshot and backup documentation include both Windows and Linux VM scenarios.
- When listing update management tools, clarify Linux equivalents (e.g., apt, yum, zypper) and how they integrate with Azure Update Management.
- Balance the order of presentation so that Linux and Windows examples/tools are given equal prominence.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page references Windows-specific concepts and tools (such as 'Windows administrator accounts', 'Windows Fabric platform-management endpoint', and Endpoint Protection anti-virus) before or exclusively, without mentioning Linux equivalents or providing Linux-focused examples. The use of Windows terminology in infrastructure descriptions and security controls creates a subtle Windows-first bias, though the content is largely platform-neutral.
Recommendations
- Where possible, clarify whether features (such as administrator account disabling, platform-management endpoints, and virus scanning tools) apply to Linux-based infrastructure as well, or provide Linux-specific details/examples.
- Mention Linux equivalents for anti-virus scanning (e.g., ClamAV, Microsoft Defender for Linux) if applicable in Azure infrastructure.
- If the infrastructure includes Linux nodes or guest OSes, describe how integrity and access controls are managed for those platforms.
- Use more platform-neutral terminology (e.g., 'administrator accounts' instead of 'Windows administrator accounts') when describing general infrastructure controls.
Security
Azure information system components and boundaries
...les/security/fundamentals/infrastructure-components.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page describes Azure's architecture and management, with notable references to Windows-centric components such as Windows Firewall and Windows Server as the host operating system. These elements are mentioned without equivalent references to Linux-based alternatives, and Windows technologies are presented as the default or only example in several sections, despite Azure's support for Linux VMs and workloads.
Recommendations
- Where discussing VM security (e.g., firewall configuration), mention that Linux VMs use different firewall solutions (such as iptables, firewalld, or ufw) and provide a brief note or link to relevant Linux documentation.
- Clarify that while Azure host infrastructure is based on Windows Server, guest VMs can run Linux or Windows, and link to documentation about Linux VM images and management.
- When describing service definition files and port configuration, note any differences or equivalents for Linux-based deployments.
- Ensure that references to administrative workstations (SAWs) and privileged access controls include guidance or links for Linux/macOS users where applicable.
Security
Azure security logging and auditing | Microsoft Docs
.../blob/main/articles/security/fundamentals/log-audit.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references both Windows and Linux logging mechanisms, but Windows examples and terminology (e.g., Windows Event Log) are mentioned first and more prominently. There is a lack of concrete Linux-specific examples (such as Syslog configuration or log retrieval commands), and integration steps or tooling for Linux are not described in detail. Windows-centric tools and patterns (e.g., Azure Diagnostics extension for Windows Event Log) are referenced before Linux equivalents.
Recommendations
- Provide explicit Linux logging examples, such as how to configure and collect Syslog data from Linux VMs in Azure.
- Include Linux-specific integration steps for Azure Monitor and SIEM systems, with sample commands or configuration files.
- Balance the order of presentation so that Linux and Windows logging mechanisms are described with equal prominence.
- Reference Linux-native tools (e.g., rsyslog, journald) alongside Windows Event Log, and provide links to relevant Azure documentation for Linux logging.
Security
Introduction to Azure security | Microsoft Docs
...s/blob/main/articles/security/fundamentals/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is generally cross-platform and acknowledges Azure's support for Linux and open-source technologies. However, several sections show Windows bias: Windows/PowerShell examples or terminology are presented first or exclusively (e.g., SQL VM TDE mentions Azure PowerShell cmdlets for Windows VMs, IIS diagnostics, and Windows 10-specific features in identity tables). Some features/tools (e.g., Microsoft Antimalware, App Service diagnostics with IIS, BitLocker recovery, and Windows 10 device join) are described with Windows-centric language or examples, while Linux equivalents are not mentioned or are referenced only briefly. In places where both Windows and Linux are supported (e.g., VM backup, disk encryption), Windows is often listed first or described in more detail.
Recommendations
- Ensure that examples and instructions are provided for both Windows and Linux platforms where applicable, especially for VM management, disk encryption, and backup.
- When describing features or tools (e.g., antimalware, diagnostics, identity management), explicitly mention Linux-compatible alternatives or workflows.
- Avoid listing Windows/PowerShell examples or terminology before Linux/Bash unless the feature is truly Windows-only.
- Add parity in diagnostic and troubleshooting sections (e.g., mention Linux logging/diagnostics tools alongside IIS/App Service diagnostics).
- In identity and device management tables, clarify which features are Windows-only and highlight Linux/macOS options where available.
Security
Securing PaaS web & mobile applications
...y/fundamentals/paas-applications-using-app-services.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally presents platform-neutral Azure security best practices, but in the 'Restrict incoming source IP addresses' section, it specifically calls out a Windows-only method (web.config for Dynamic IP Security) and links to IIS documentation, without mentioning Linux equivalents or alternatives. This may create friction for Linux App Service users seeking similar functionality.
Recommendations
- Add guidance or links for restricting IP addresses on Linux-based App Service (e.g., using app settings, Azure portal, or web server configuration like nginx or Apache).
- Clarify that the web.config/IIS method is Windows-only and suggest Linux alternatives where possible.
- Ensure examples and tooling recommendations are provided for both Windows and Linux App Service environments.
Security
Detect and respond to ransomware attacks
...les/security/fundamentals/ransomware-detect-respond.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily through references to Windows-specific logging (Security Event log and PowerShell Operational logs) and containment guidance that implicitly assumes Windows endpoints (e.g., Defender for Endpoint isolation links to Windows documentation). There are no explicit Linux or macOS examples, nor are Linux-specific tools or logs mentioned. While the page is Azure-focused and not strictly Windows-only, it overlooks Linux VM scenarios and cross-platform detection/response patterns.
Recommendations
- Include examples or references for detecting ransomware on Linux-based Azure VMs, such as monitoring syslog, auditd, or Linux-specific security logs.
- Mention Linux-compatible security tools (e.g., Defender for Endpoint for Linux, Azure Security Center for Linux VMs) and provide links to relevant documentation.
- Balance references to Windows-specific logs (e.g., Security Event log, PowerShell logs) with Linux equivalents (e.g., /var/log/auth.log, /var/log/audit/audit.log).
- Add containment and isolation guidance for Linux VMs, including command-line examples (e.g., using Azure CLI or SSH to isolate a Linux VM).
Security
Best practices for Azure Service Fabric security
...security/fundamentals/service-fabric-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Service Fabric security best practices demonstrates a moderate Windows bias. It frequently references Windows-specific tools (such as PowerShell modules and Windows Server certificate services), and examples or instructions are given primarily for Windows environments. There is little to no mention of Linux equivalents, and Linux-specific guidance is missing for key tasks such as cluster creation, certificate management, and automation. The use of Windows terminology and tools is prevalent, and Linux users may need to infer or research alternative approaches.
Recommendations
- Include Linux-specific instructions and examples for cluster creation, certificate management, and automation (e.g., using Azure CLI, Bash scripts, or Linux-based certificate tools).
- Mention cross-platform tools where available, such as Azure CLI, and clarify which steps are applicable to both Windows and Linux clusters.
- Provide guidance or links to documentation for managing Service Fabric clusters on Linux, including security best practices and automation workflows.
- When referencing PowerShell or Windows Server tools, add equivalent Linux commands or note differences in workflow for Linux clusters.
Security
Prevent subdomain takeovers with Azure DNS alias records and Azure App Service's custom domain verification
...n/articles/security/fundamentals/subdomain-takeover.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its guidance for identifying dangling DNS entries. The only tool recommended for discovery is a PowerShell script ('Get-DanglingDnsRecords.ps1'), with no mention of equivalent Linux/macOS-compatible options or cross-platform alternatives. All scripting and automation examples are PowerShell-centric, and links to further automation (such as Resource Graph queries) direct users to PowerShell-based tutorials, with no reference to Azure CLI, Bash, or other non-Windows tooling. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
- Provide equivalent instructions and examples using Azure CLI and/or Bash scripts for identifying dangling DNS entries.
- Explicitly mention that PowerShell Core is cross-platform, and provide installation guidance for Linux/macOS users if PowerShell is required.
- Include links to Resource Graph query tutorials for Azure CLI and REST API, not just PowerShell.
- Offer sample scripts or workflows for DNS record management using Linux-native tools (e.g., dig, nslookup) where appropriate.
Security
Secure your Microsoft Entra identity infrastructure
...rticles/security/fundamentals/steps-secure-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page 'Secure your Microsoft Entra identity infrastructure' demonstrates a moderate Windows bias. Several sections reference Windows-centric tools (e.g., AD FS, Windows Hello for Business, password protection for Windows Server Active Directory) and patterns, often without mentioning Linux/macOS equivalents or alternatives. Examples and recommendations for credential protection, authentication, and monitoring are generally described in a platform-neutral way, but where platform-specific details are provided, Windows tools and features are referenced first or exclusively. There are no explicit Linux/macOS command-line examples, nor are Linux-specific identity integration scenarios discussed.
Recommendations
- Where Windows-specific features (e.g., AD FS, Windows Hello for Business) are mentioned, clarify their platform scope and, where possible, provide links or notes about Linux/macOS alternatives (e.g., SSSD, PAM, FIDO2 support on Linux, or third-party federation solutions).
- Include examples or guidance for integrating Linux/macOS systems with Microsoft Entra ID, such as using SAML, OAuth, or OpenID Connect for Single Sign-On, or leveraging cross-platform passwordless authentication methods.
- When discussing password protection, monitoring, and provisioning, note any platform limitations and provide parity guidance for non-Windows environments.
- Add references to open standards and cross-platform tools where relevant (e.g., FIDO2 keys, Authenticator apps available on all platforms).
- Consider adding a section or appendix for Linux/macOS administrators outlining best practices for securing Entra-integrated identities on those platforms.
Security
Cryptography - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
.../security/develop/threat-modeling-tool-cryptography.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias, with frequent references to Windows-specific cryptographic APIs (CNG, CAPI, Win32/64 functions), .NET classes, and features like BitLocker and TPM on Windows IoT Core. Examples and recommendations are centered on Windows technologies, with Linux and macOS alternatives rarely mentioned or relegated to secondary status. There are no Linux command-line or code examples, and critical sections (e.g., IoT device key storage, database encryption) focus exclusively on Microsoft/Windows solutions.
Recommendations
- Add equivalent Linux and macOS cryptographic API references (e.g., OpenSSL, /dev/urandom, GnuPG, dm-crypt, LUKS, cryptsetup).
- Provide Linux/macOS code samples for key generation, encryption, and secure storage (e.g., using Python's cryptography library, OpenSSL CLI, or C/C++ APIs).
- Mention Linux alternatives to BitLocker (e.g., LUKS/dm-crypt) and TPM usage (e.g., tpm2-tools, Linux kernel TPM support).
- Ensure that generic recommendations are truly cross-platform, and avoid listing Windows APIs first unless they are the only supported option.
- Include references to cross-platform libraries and tools (e.g., OpenSSL, libsodium, PKCS#11).
Security
Authorization - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...security/develop/threat-modeling-tool-authorization.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral, focusing on concepts and Azure-specific features. However, there is a notable Windows bias in the WCF sections, which reference Windows-specific technologies (WCF, .NET Framework, Windows Groups) and provide configuration/code examples that are only applicable to Windows environments. The authorization example for WCF uses Windows roles and groups first and does not mention Linux/macOS equivalents or cross-platform alternatives. Other sections (e.g., ACLs, user-profile directories) are generic and do not specify Windows or Linux, but lack explicit Linux/macOS guidance or examples.
Recommendations
- For WCF and .NET authorization examples, add notes or examples for cross-platform alternatives (e.g., .NET Core, ASP.NET Core, or other frameworks that run on Linux/macOS).
- When discussing role-based authorization, mention non-Windows approaches (e.g., POSIX groups, Linux ACLs, OAuth, OpenID Connect) and provide relevant examples.
- Where file system concepts are discussed (ACLs, user-profile directories), clarify how these map to Linux/macOS (e.g., use of chmod, chown, /home/user directories).
- Explicitly state platform applicability in each section, and provide parity in examples for Linux/macOS where possible.
Security
Detect and respond to ransomware attacks
...les/security/fundamentals/ransomware-detect-respond.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools and concepts (e.g., Security Event log, PowerShell Operational logs, Defender for Endpoint isolation instructions linked to Windows documentation) without mentioning Linux equivalents or providing Linux/macOS-specific guidance. Examples and recommendations are implicitly Windows-centric, and there are no explicit Linux or macOS instructions for detection, containment, or recovery steps.
Recommendations
- Include explicit guidance for Linux and macOS systems, such as monitoring Linux audit logs, syslog, and relevant security logs.
- Provide examples of containment and mitigation steps for Linux VMs (e.g., using iptables, fail2ban, or Linux-native endpoint protection tools).
- Reference cross-platform Defender for Endpoint documentation, highlighting Linux/macOS capabilities and isolation procedures.
- Add parity in incident response recommendations, such as how to disable compromised accounts or block ransomware communications on Linux/macOS.
- Ensure that detection and response steps mention both Windows and Linux event sources and tools where applicable.
Security
Securing PaaS web & mobile applications
...y/fundamentals/paas-applications-using-app-services.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific configuration (web.config) and IIS Dynamic IP Security for restricting IP addresses, without mentioning equivalent approaches for Linux-based App Service environments. Windows tools and patterns are presented exclusively, and Linux alternatives are omitted.
Recommendations
- Include instructions or references for restricting IP addresses on Linux-based App Service environments, such as using iptables, App Service access restrictions, or other supported mechanisms.
- Mention configuration files and security controls relevant to Linux (e.g., .htaccess for Apache, nginx.conf for Nginx) alongside web.config for Windows.
- Clearly indicate which features or examples apply only to Windows and provide parity for Linux users where possible.
- Add a comparison table or section outlining platform-specific security configuration steps.
Security
Design secure applications on Microsoft Azure
...s/blob/main/articles/security/develop/secure-design.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias, primarily through its references to Microsoft-centric tools, services, and patterns. The Security Development Lifecycle (SDL) is linked to Windows documentation, and management interfaces like 'Azure portal/remote PowerShell' are mentioned without Linux CLI equivalents. Examples and links for security controls and mitigations often reference .NET, Visual Studio, and Windows-based technologies first or exclusively. There is little mention of Linux/macOS-specific tools, workflows, or parity in examples.
Recommendations
- Include Linux/macOS equivalents for management interfaces (e.g., Azure CLI, Bash scripts) alongside PowerShell references.
- Provide examples and links for security controls using cross-platform frameworks and languages (e.g., Python, Java, Node.js) in addition to .NET.
- Reference Linux/macOS documentation for SDL and other security practices where available.
- Mention open-source, cross-platform tools for threat modeling and attack surface analysis, not just Microsoft-provided ones.
- Ensure that links and examples for logging, error handling, and authentication cover non-Windows environments and editors (e.g., VS Code, JetBrains IDEs).
Security
Auditing and Logging - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...y/develop/threat-modeling-tool-auditing-and-logging.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several sections reference Windows-specific technologies (e.g., Windows ACLs, WCF/.NET Framework, SQL Server) and provide examples or instructions that are only applicable to Windows environments. There are no equivalent Linux/macOS examples or references for log file permissions, logging frameworks, or database auditing. Windows terminology and tools are mentioned exclusively or before any cross-platform alternatives.
Recommendations
- Add Linux/macOS equivalents for log file access control (e.g., using chmod, chown, and POSIX ACLs).
- Include examples for configuring log rotation on Linux (e.g., logrotate) alongside Windows instructions.
- Provide guidance for auditing and logging in cross-platform web frameworks (e.g., Node.js, Python, Java) and databases (e.g., PostgreSQL, MySQL).
- Reference Linux/macOS tools and patterns for centralized logging (e.g., syslog, journald, rsyslog, ELK stack).
- Ensure that examples and terminology are presented in a platform-neutral way, or provide parallel instructions for each major OS.
Security
Authentication - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...ecurity/develop/threat-modeling-tool-authentication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, especially in sections related to SQL Server authentication, WCF/MSMQ, and certificate management. Windows Authentication is recommended as the default for SQL Server, with little mention of Linux alternatives. WCF/MSMQ examples and configuration are inherently Windows-centric, and certificate guidance refers to Windows Server certificate services and MakeCert.exe. There is a lack of Linux/macOS-specific examples or guidance, and Windows-based tools and patterns are mentioned before cross-platform or open-source equivalents.
Recommendations
- Include equivalent Linux/macOS authentication patterns and examples, such as Kerberos integration for SQL Server on Linux.
- Provide guidance for certificate management using cross-platform tools like OpenSSL, especially in sections currently referencing Windows Server certificate services or MakeCert.exe.
- Add examples for securing services using Linux-native mechanisms (e.g., PAM, SELinux, systemd) where appropriate.
- For WCF/MSMQ, clarify platform limitations and suggest alternatives for cross-platform messaging and authentication (e.g., RabbitMQ, gRPC, or other open standards).
- Ensure that examples and recommendations are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux/macOS.
Security
Communication security for the Microsoft Threat Modeling Tool
...develop/threat-modeling-tool-communication-security.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of Windows-centric technologies, tools, and code samples (e.g., ASP.NET, WCF, ADO.NET, web.config, ServicePointManager, SQL Server Management Studio). Examples and recommendations are tailored to Windows environments, with no equivalent Linux/macOS instructions or code samples provided. Linux and macOS users are left without guidance for implementing the described security mitigations in their environments.
Recommendations
- Provide equivalent Linux/macOS examples for each mitigation, such as using NGINX/Apache for HTTPS enforcement, OpenSSL for certificate validation, and Linux-based tools for SQL connectivity.
- Include cross-platform code samples (e.g., Python, Java, Node.js) alongside C#/.NET examples.
- Reference Linux/macOS tools (e.g., psql, mysql, openssl, curl) where applicable.
- When describing configuration steps (e.g., enforcing HTTPS), include both Windows (IIS/web.config) and Linux (NGINX/Apache) approaches.
- Explicitly state platform applicability for each mitigation and provide links to relevant cross-platform documentation.
Security
Input Validation - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...urity/develop/threat-modeling-tool-input-validation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. Most code examples are in C#/.NET, and configuration instructions reference Windows-specific technologies (IIS, web.config, MSXML, http.sys, WCF). There is little to no mention of Linux or cross-platform equivalents, and alternative approaches for non-Windows environments are largely absent or relegated to references. This bias may hinder Linux/macOS users from applying the guidance directly.
Recommendations
- Add equivalent examples for Linux-based web servers (e.g., Apache, Nginx) and configuration files (e.g., .htaccess, nginx.conf) for headers like X-Content-Type-Options.
- Provide code samples in other popular languages/frameworks (e.g., Python/Flask, Node.js/Express, Java/Spring) alongside .NET.
- Include instructions for disabling XSLT scripting and XML entity resolution in cross-platform libraries (e.g., lxml, xml.etree in Python, libxml2 in C/C++).
- Reference Linux/macOS tools and patterns for file upload validation, regular expression timeouts, and web application security.
- Clearly indicate which mitigations are Windows-specific and offer alternatives for other platforms.
Security
Sensitive Data - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...ecurity/develop/threat-modeling-tool-sensitive-data.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific technologies and tools (EFS, DPAPI, BitLocker, Intune, CryptoObfuscator) are mentioned exclusively or before Linux equivalents. Examples and references are often .NET/Windows-centric, with limited or no Linux/macOS alternatives or code samples. Linux technologies (e.g., DM-Crypt) are mentioned only briefly and without practical guidance or examples.
Recommendations
- For each Windows-specific tool or technology (EFS, DPAPI, BitLocker, Intune), provide Linux/macOS equivalents (e.g., eCryptfs, LUKS, Gnome Keyring, FileVault) and practical usage examples.
- Include Linux/macOS code samples and configuration snippets alongside Windows/.NET examples, especially for file system encryption, configuration protection, and mobile device management.
- Reference cross-platform or open-source tools where possible (e.g., VeraCrypt, KeePassXC) and clarify platform applicability.
- Reorder sections or examples so that platform coverage is balanced, not Windows-first.
- Explicitly state platform limitations or alternatives when a feature is Windows-only.
Security
Platform code integrity - Azure Security
.../main/articles/security/fundamentals/code-integrity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes code integrity in the context of Windows (specifically Windows Server 2016), with only a brief mention of the Linux equivalent (DM-Verity) and no further details or examples for Linux. All technical explanations, policy descriptions, and process details are Windows-centric, leaving Linux users with minimal guidance.
Recommendations
- Expand the section on DM-Verity to describe how code integrity is implemented and managed on Linux systems, including configuration steps and policy enforcement.
- Provide Linux-specific examples and workflows for code integrity, similar to the Windows explanations.
- Include references to other Linux code integrity tools (e.g., IMA, AppArmor, SELinux) and how they relate to the Azure security model.
- Ensure parity in describing audit modes, deployment safety, and incident response for Linux environments.