Security
231
Total Pages
188
Linux-Friendly Pages
43
Pages with Bias
18.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
90 issues found
Showing 51-75 of 90 flagged pages
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 demonstrates a moderate Windows bias. It references Windows-specific concepts (e.g., Windows ACLs, WCF/.NET Framework, SQL Server Management Studio) and provides configuration examples only for Windows technologies (WCF). There are no Linux/macOS equivalents or examples for log file permissions, log rotation, or auditing, and Windows terminology is used without cross-platform context.
Recommendations
- Provide Linux/macOS equivalents for log file permission management (e.g., using chmod, chown, setfacl).
- Include examples of log rotation using Linux tools (e.g., logrotate) alongside Windows approaches.
- Offer cross-platform logging/auditing examples for web applications and APIs (e.g., using syslog, journald, or popular logging libraries).
- Reference database auditing for open-source databases (e.g., PostgreSQL, MySQL) in addition to SQL Server.
- Clarify when recommendations are Windows-specific and offer alternative steps for Linux/macOS environments.
Create Pull Request
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 exhibits 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 and MSMQ examples are Windows-centric, and certificate guidance references Windows Server certificate services and MakeCert.exe. Linux/macOS equivalents, such as Kerberos on Linux, OpenSSL, or cross-platform authentication methods, are not discussed or are mentioned only in passing. Examples and recommendations are generally Windows-first, with limited cross-platform guidance.
Recommendations
- Include Linux/macOS authentication examples for SQL Server (e.g., Kerberos setup on Linux, cross-platform ODBC authentication).
- Provide guidance on using OpenSSL and other cross-platform certificate tools, not just Windows Server certificate services or MakeCert.exe.
- Add parity for WCF/MSMQ sections by clarifying platform support and alternatives for Linux/macOS.
- Where authentication mechanisms are discussed, explicitly mention cross-platform options and provide example configurations for non-Windows environments.
- Reorder examples so that cross-platform or generic solutions are presented before Windows-specific ones.
- Reference Linux/macOS documentation and tools where relevant.
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 exhibits a notable Windows bias. Many examples and recommendations reference Windows-centric technologies (e.g., ASP.NET, WCF, SQL Server Management Studio, ServicePointManager, web.config, URL Rewrite module), and code samples are exclusively in C#/.NET. There is a lack of Linux/macOS equivalents or guidance for cross-platform scenarios. Windows tools and patterns are mentioned first or exclusively, and Linux alternatives are missing in critical sections.
Recommendations
- Provide Linux/macOS equivalents for configuration and code samples (e.g., show how to enforce HTTPS in Nginx/Apache, use OpenSSL for certificate validation, or configure HSTS headers in non-IIS environments).
- Include cross-platform code samples (e.g., Python, Node.js, Java) for certificate pinning and HTTPS enforcement.
- Reference Linux tools (e.g., psql for SQL Server, redis-cli for Redis with TLS, SMB clients on Linux) alongside Windows tools.
- Explicitly mention platform-agnostic approaches where possible, and clarify when recommendations are Windows-specific.
- Add guidance for configuring secure communication in Linux environments (e.g., systemd service accounts, SELinux/AppArmor for least privilege, Linux firewall rules).
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 largely generic and platform-neutral, but certain sections (notably WCF and ASP.NET Web API) reference Windows-centric technologies and configuration patterns (e.g., Windows Groups, machine.config, app.config, .NET Framework, WCF, ASP.NET). Examples and recommendations for authorization are given using Windows tools and concepts, with no Linux/macOS equivalents or alternative cross-platform approaches discussed. The order of presentation also places Windows-centric solutions before any mention of alternatives.
Recommendations
- For sections referencing Windows Groups or .NET configuration files, add equivalent examples for Linux/macOS environments, such as using POSIX ACLs, systemd service permissions, or cross-platform frameworks.
- Provide examples of authorization using open-source, cross-platform web frameworks (e.g., Node.js, Django, Flask) alongside ASP.NET examples.
- When discussing role-based access control, mention Linux/macOS mechanisms (e.g., sudoers, group membership, file permissions) and how they relate to the principle of least privilege.
- Clarify which recommendations are platform-specific and offer alternative approaches for non-Windows environments.
- Include links to documentation for Linux/macOS security and authorization best practices.
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 page demonstrates a notable Windows bias. Many cryptographic recommendations and examples focus on Windows-specific APIs (CNG, CAPI, Win32/64, .NET), and Microsoft technologies (SQL Server, SSIS, BitLocker, TPM on Windows IoT Core). Windows tools and patterns are mentioned first or exclusively, with limited or no Linux equivalents, especially in code samples and references. Linux/macOS alternatives are only briefly mentioned in the random number generator section, and there are no Linux-specific code examples or guidance for equivalent tasks (e.g., disk encryption, TPM usage, database encryption).
Recommendations
- Provide Linux/macOS equivalents for cryptographic APIs and tools (e.g., OpenSSL, GnuPG, dm-crypt/LUKS for disk encryption, Linux TPM tools).
- Include code samples for Linux and macOS platforms, especially for IoT device key storage, random number generation, and database encryption.
- Mention cross-platform libraries (e.g., libsodium, OpenSSL) and how to use them in .NET Core or other languages on non-Windows platforms.
- Reference Linux/macOS documentation for features like disk encryption, TPM provisioning, and secure key storage.
- Avoid listing Windows tools/APIs first; present cross-platform options or group them by OS.
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 is heavily focused on Windows-centric technologies and patterns, such as .NET, IIS, MSXML, and WCF, with code examples almost exclusively in C# and references to Windows configuration files (web.config), IIS, and Windows-specific XML libraries. There is minimal mention of Linux/macOS equivalents, and no code examples for non-Windows platforms. Even generic recommendations are illustrated using Windows tools and APIs, leaving Linux/macOS users without clear guidance or parity.
Recommendations
- Provide equivalent code examples for Linux/macOS platforms, using popular frameworks (e.g., Java/Spring, Python/Django/Flask, Node.js/Express).
- Include configuration instructions for common Linux web servers (e.g., Apache, Nginx) alongside IIS/web.config examples.
- Reference cross-platform libraries for input validation, encoding, and XML parsing (e.g., lxml for Python, Nokogiri for Ruby, libxml2 for C/C++).
- Clarify which mitigations are platform-agnostic and which are Windows-specific, and offer alternatives for non-Windows environments.
- Add links to documentation for Linux/macOS tools and libraries where relevant (e.g., mod_security for Apache, OWASP libraries for Java/Python).
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 exhibits a moderate Windows bias. Several sections reference Windows-specific technologies and tools (e.g., EFS, DPAPI, BitLocker, Windows Intune, Windows credential types in WCF) without providing equivalent Linux/macOS alternatives or examples. Windows tools and patterns (such as DPAPI, EFS, BitLocker) are mentioned exclusively or before Linux equivalents (e.g., DM-Crypt is only briefly referenced in Azure Disk Encryption). Code examples and references are predominantly .NET/C#, with little to no parity for Linux/macOS users. Powershell or Windows-centric configuration is implied in several places, and Linux alternatives are often missing or underexplained.
Recommendations
- For each Windows-specific tool or pattern (e.g., EFS, DPAPI, BitLocker), provide Linux/macOS equivalents (e.g., eCryptfs, GnuPG, LUKS, Keyring, FileVault) and usage examples.
- When discussing Azure Disk Encryption, offer equal detail and configuration examples for DM-Crypt on Linux, including command-line steps.
- Include Linux/macOS code samples and configuration snippets alongside .NET/C# and Windows-centric examples.
- Reference cross-platform libraries and tools for encryption, obfuscation, and credential management, not just Windows/.NET solutions.
- Clarify which recommendations are platform-specific and offer guidance for other platforms where applicable.
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 discusses code integrity in the context of Windows (specifically Windows Server 2016), mentioning Linux's DM-Verity only briefly and without detail or examples. All process descriptions, terminology, and workflow explanations are Windows-centric, with no Linux/macOS-specific guidance, examples, or parity in deployment or incident response sections.
Recommendations
- Provide equivalent Linux/macOS examples and workflows for code integrity enforcement, such as DM-Verity or IMA (Integrity Measurement Architecture).
- Include details on how code integrity policies are authored, deployed, and audited on Linux systems.
- Add incident response and build process sections relevant to Linux/macOS environments.
- Ensure that references to tools and terminology are balanced between Windows and Linux/macOS, or clearly indicate platform-specific differences.
Security
Security Recommendations for Azure Marketplace Images | Microsoft Docs
...cles/security/fundamentals/azure-marketplace-images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides separate sections for Linux and Windows images, but some bias is evident. In the Linux section, there is a reference to 'Windows Server roles, features, services, and networking ports' within a Linux-specific checklist, which is confusing and suggests Windows-centric language. The Windows section mentions BitLocker and auto-update, but the Linux section does not mention equivalent Linux disk encryption (e.g., LUKS) or auto-update mechanisms (e.g., unattended-upgrades). Some configuration examples (e.g., for SSH and waagent) are given for Linux, but overall, Windows tools and terminology are more prominent, and some Linux best practices are omitted.
Recommendations
- Remove references to Windows Server roles/features from the Linux checklist.
- Add Linux equivalents for disk encryption (e.g., recommend LUKS or dm-crypt for OS/data disks).
- Include guidance for enabling automatic security updates on Linux (e.g., using unattended-upgrades or dnf-automatic).
- Ensure Linux-specific terminology and examples are used in the Linux section, and avoid Windows-centric language.
- Provide parity in recommendations, such as mentioning removal of sensitive files (e.g., /etc/hosts for Linux, not just HOSTS for Windows).
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 Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the frequent mention of PowerShell for administration and bulk operations, and the use of Windows-centric terminology (e.g., Microsoft 365 Apps, Office, Exchange, SharePoint) without explicit Linux/macOS alternatives or parity. PowerShell is referenced as the main administrative interface, and there are no examples or guidance for equivalent Linux/macOS command-line tools or workflows. Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, and Linux-specific instructions are only briefly referenced in the context of IoT device builders.
Recommendations
- Provide equivalent CLI examples for Linux/macOS users, such as Azure CLI or REST API usage, alongside PowerShell instructions.
- Explicitly mention cross-platform administration options where available, and clarify any limitations for non-Windows environments.
- Include Linux/macOS-specific guidance for on-premises scenarios, especially for scanner deployment and management.
- Ensure that SDK and automation sections highlight language and platform support for Linux/macOS.
- Add parity in examples and troubleshooting for Linux-based environments, especially in sections related to agent installation, file classification, and security management.
Security
Isolation in the Azure Public Cloud | Microsoft Docs
...in/articles/security/fundamentals/isolation-choices.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It frequently references Windows-specific technologies (e.g., Windows Firewall, BitLocker, Active Directory Federation Services), and often mentions Windows tools and patterns before their Linux equivalents. Some sections, such as disk encryption and domain services, provide more detail for Windows solutions or mention Windows features first. There are references to PowerShell and Windows-centric management patterns, while Linux alternatives (e.g., dm-crypt, mdadm) are mentioned but not explained in equal depth or with parity in examples. No explicit Linux command-line examples or Linux-first guidance is provided.
Recommendations
- Provide Linux-specific examples and command-line instructions (e.g., using Azure CLI on Linux, Linux firewall configuration).
- Ensure equal coverage and explanation for Linux technologies (e.g., dm-crypt, mdadm, LVM) as for Windows technologies like BitLocker and Storage Spaces.
- Mention Linux tools and patterns alongside Windows equivalents, and avoid presenting Windows solutions first unless contextually necessary.
- Include references to Linux authentication and identity management patterns (e.g., integration with LDAP, Kerberos) where relevant.
- Add explicit Linux/macOS usage notes for Azure management tools and APIs.
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
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates moderate Windows bias. Several examples and tool references (e.g., PowerShell cmdlets like Add-AzKeyVaultKey and Set-AzVMDiskEncryptionExtension, Windows Defender, WSUS, and Windows Update) are Windows-centric, with Linux equivalents either missing or mentioned secondarily. Some instructions (e.g., disk encryption, backup, and update management) provide detailed steps or links for Windows but lack parity for Linux, or use Windows-specific terminology and tools first. Linux support is acknowledged in some sections, but examples and actionable guidance are less complete for Linux users.
Recommendations
- Provide Linux-specific command-line examples (e.g., az CLI, bash scripts) alongside PowerShell cmdlets.
- Mention Linux tools (e.g., ClamAV, Linux-native endpoint protection) and update mechanisms (e.g., apt, yum, unattended-upgrades) with equal detail as Windows tools.
- Ensure links to Linux documentation are as prominent and detailed as those for Windows.
- Where backup and snapshot procedures are described, include Linux-specific steps and references.
- When discussing monitoring and diagnostics, highlight Linux agent configuration and troubleshooting as much as Windows.
- Avoid listing Windows tools or examples first unless there is a technical reason; alternate ordering or present both together.
Security
Azure identity & access security best practices | Microsoft Docs
...ity/fundamentals/identity-management-best-practices.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. It frequently references Windows-specific tools and patterns (Active Directory, Windows Server agents, Windows Hello for Business, Privileged Access Workstations), and PowerShell is mentioned as a primary automation method. Linux/macOS equivalents or cross-platform alternatives are rarely mentioned, and examples or guidance are generally Windows-first or Windows-only. There are no explicit Linux/macOS command-line examples, and guidance for admin workstations and password protection is focused on Windows environments.
Recommendations
- Include Linux/macOS equivalents for all Windows-specific tools and patterns (e.g., guidance for integrating Linux PAM with Entra ID, or using Azure CLI on Linux/macOS for automation).
- Provide cross-platform examples for automation (e.g., Bash, Azure CLI, Python SDK) alongside PowerShell.
- Mention and link to documentation for managing Entra ID and Azure resources from Linux/macOS systems.
- Clarify which features and recommendations are platform-agnostic and which are Windows-specific.
- Add guidance for securing privileged access from Linux/macOS admin workstations (e.g., using FIDO2 keys, SSH certificates, or other cross-platform MFA methods).
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (e.g., Windows Event Log, Azure Diagnostics) are mentioned before their Linux equivalents (Syslog), and Windows-specific logging is described in more detail. Linux logging (Syslog) is referenced only briefly, with no concrete examples or instructions. There are no Linux/macOS-specific integration steps or troubleshooting guidance, and most examples and integrations focus on Windows or generic Azure tools.
Recommendations
- Provide equivalent Linux examples and instructions for collecting and integrating Syslog and other Linux-specific logs.
- Ensure that Linux logging tools and patterns are described with equal detail and prominence as Windows tools.
- Add troubleshooting steps and integration guidance for Linux-based systems, including common log locations and collection agents.
- Where possible, present Windows and Linux options side-by-side, or alternate which platform is described first.
Security
Enhance remote management security in Azure | Microsoft Docs
...blob/main/articles/security/fundamentals/management.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific tools (AppLocker, Hyper-V, Group Policy, BitLocker, Windows Firewall, MMC, Windows Intune) are referenced exclusively or before any Linux/macOS equivalents. Examples and recommendations focus on Windows technologies and management patterns, such as PowerShell for Azure management, with no mention of Linux/macOS alternatives (e.g., SSH, iptables, SELinux, Linux-based hardening, or Azure CLI on Linux/macOS). The guidance for workstation hardening, firewall configuration, and virtualization is Windows-centric, and there are no examples or instructions for non-Windows platforms.
Recommendations
- Include Linux/macOS equivalents for all Windows-specific tools and patterns (e.g., AppArmor/SELinux for AppLocker, iptables/firewalld for Windows Firewall, SSH for RDP, Linux VMs for Hyper-V, Azure CLI for PowerShell).
- Provide examples and step-by-step instructions for hardening Linux/macOS workstations for Azure management, including patching, user privilege management, and firewall configuration.
- Mention cross-platform management tools (e.g., Azure CLI, Terraform, Ansible) and how they can be securely used from Linux/macOS.
- Clarify which recommendations are platform-agnostic and which are Windows-specific, and provide parity guidance for other operating systems.
- Add references to Linux/macOS security best practices and relevant documentation.
Security
Azure Operational Security | Microsoft Docs
...articles/security/fundamentals/operational-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology (e.g., 'Windows Azure', 'Windows Server', 'Windows event logs') is frequently used, sometimes as the default or first example. Several sections reference Windows-specific tools and logs (such as Windows event logs, IIS logs, System Center Data Protection Manager) without equivalent Linux examples or explicit parity. While Linux is mentioned as supported (e.g., 'Linux containers', 'agent for Windows and Linux'), concrete examples, instructions, or references for Linux are sparse or absent, especially in sections about diagnostics and backup.
Recommendations
- Provide explicit Linux examples and instructions alongside Windows ones, especially for diagnostics, logging, and backup.
- Use platform-neutral terminology (e.g., 'Azure' instead of 'Windows Azure') where appropriate.
- Mention Linux equivalents for tools and logs (e.g., syslog for Linux, alternatives to IIS logs).
- Clarify support for Linux in all agent, backup, and monitoring scenarios, with links to relevant documentation.
- Ensure that any references to PowerShell, Windows event logs, or Windows-specific tools are balanced with Linux CLI, shell, or syslog examples.
Security
Securing PaaS web & mobile applications
...y/fundamentals/paas-applications-using-app-services.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page shows mild Windows bias in the section on restricting incoming source IP addresses. It specifically mentions configuring web.config for dynamic IP security on App Service for Windows, referencing IIS documentation, but does not provide equivalent guidance or examples for Linux-based App Service environments. No Linux or cross-platform alternatives are discussed, and Windows-specific tooling is referenced first and exclusively.
Recommendations
- Add equivalent instructions or references for restricting IP addresses dynamically on App Service for Linux, such as using .htaccess for Apache, nginx configuration, or App Service access restrictions.
- Clearly indicate which features or configuration options are Windows-only and provide Linux/macOS alternatives where possible.
- Present platform-specific guidance in parallel, rather than focusing on Windows first or exclusively.
- Include cross-platform examples or note differences in implementation between Windows and Linux App Service environments.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates moderate Windows bias. Windows terminology, features, and tools (e.g., PowerShell, IIS, Windows-specific features in Microsoft Entra ID) are mentioned first or exclusively in several sections. Examples and instructions (such as enabling SQL VM TDE with PowerShell) are Windows-centric, with Linux equivalents either missing or referenced after Windows. Some features (e.g., Microsoft Entra join, BitLocker recovery) are described as Windows-only, and diagnostic tooling (IIS trace logs) is discussed without Linux alternatives. While Linux is acknowledged (e.g., Azure supports Linux VMs, disk encryption), practical guidance and examples for Linux users are less prominent.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for tasks like VM encryption, backup, and key management.
- Include Linux equivalents for diagnostic and troubleshooting tools (e.g., reference Linux logging and tracing utilities in addition to IIS).
- When mentioning PowerShell or Windows tools, also mention Bash/CLI or Linux-native tools and provide parity in step-by-step guides.
- Clarify which features are cross-platform and which are Windows-only, and offer alternative solutions for Linux/macOS users where possible.
- Reorder examples so that Linux and Windows are presented equally, or alternate which is shown first.
Security
Best practices for secure PaaS deployments - Microsoft Azure
...ain/articles/security/fundamentals/paas-deployments.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools and interfaces (e.g., remote PowerShell, Microsoft Defender for Cloud, Microsoft Entra ID) and omits explicit Linux/macOS equivalents or examples. The mention of 'portal/remote PowerShell' as a management interface for Azure is Windows-specific, and there are no CLI, Bash, or Linux-native tool examples. The documentation assumes familiarity with Microsoft-centric technologies and patterns, which may create friction for Linux/macOS users.
Recommendations
- Include Azure CLI and Bash examples alongside or before PowerShell examples for management tasks.
- Explicitly mention cross-platform management interfaces (e.g., Azure CLI, REST API, Terraform) where relevant.
- Add notes or sections highlighting how Linux/macOS users can perform equivalent actions, especially for authentication, monitoring, and security configuration.
- Reference Linux-native tools (e.g., OpenSSL for certificate management, Linux firewalls) when discussing security best practices.
- Clarify that Azure services and security features are accessible from non-Windows platforms and provide links to platform-agnostic documentation.
Security
Best practices for protecting secrets
...ticles/security/fundamentals/secrets-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Azure and Microsoft-centric tools and workflows, with no mention of Linux or macOS equivalents. Examples and guidance focus on Azure Key Vault, Azure Managed HSM, and related Microsoft services, omitting cross-platform secret management tools or patterns. Service-specific best practices reference Windows-centric technologies (e.g., Azure PowerShell, SQL Server on Azure VMs with a 'windows' path), and do not provide Linux/macOS-specific examples or alternatives. No Linux command-line tools (such as Bash, OpenSSL, HashiCorp Vault, or GnuPG) are mentioned, and there is no guidance for non-Windows environments.
Recommendations
- Include examples and references for Linux/macOS secret management tools, such as HashiCorp Vault, GnuPG, or native OS keyrings.
- Provide CLI examples using Bash, Azure CLI, and cross-platform scripting, not just Azure PowerShell.
- Add guidance for integrating secret management in Linux-based CI/CD pipelines (e.g., GitHub Actions runners on Linux, Jenkins, etc.).
- Reference open-source secret scanning tools (e.g., TruffleHog, Gitleaks) alongside Microsoft tools.
- Ensure service-specific best practices include Linux/macOS deployment scenarios and examples.
- Explicitly mention that Azure services and tools are cross-platform where applicable, and clarify any Windows-only limitations.
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 demonstrates a Windows bias by referencing Windows-specific tools (e.g., Security Event log, PowerShell Operational logs, Defender for Endpoint) and patterns without mentioning Linux equivalents or providing Linux/macOS-specific guidance. Examples and recommendations are centered around Windows environments, with no explicit instructions for Linux-based Azure VMs or their logging/response mechanisms.
Recommendations
- Include examples and guidance for detecting ransomware on Linux-based Azure VMs, such as monitoring syslog, auditd, and Linux-specific security logs.
- Mention Linux/macOS equivalents for tools like Defender for Endpoint, or clarify cross-platform support and usage.
- Provide containment and mitigation steps relevant to Linux environments (e.g., disabling compromised Linux accounts, isolating Linux VMs, updating Linux anti-malware solutions).
- Ensure that event log clearing and security tool disabling detection covers Linux audit logs and common Linux security controls.
- Present examples for both Windows and Linux environments, or clarify when guidance is Windows-specific.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (PowerShell, Windows Server certificate service, Active Directory) are mentioned exclusively or before any Linux alternatives. Examples and instructions reference Windows clusters and PowerShell modules, with no equivalent Linux or cross-platform guidance. There is a lack of explicit Linux/macOS examples for cluster creation, certificate management, and security configuration, making it harder for non-Windows users to follow best practices.
Recommendations
- Add explicit Linux/macOS examples for cluster creation, certificate management, and security configuration.
- Mention and provide guidance for Linux tools (e.g., Azure CLI, OpenSSL, Linux certificate authorities) alongside or before Windows tools.
- Clarify which instructions are cross-platform and which are Windows-only; provide parity where possible.
- Include links to Linux/macOS-specific documentation or sections.
- Avoid assuming PowerShell is the default scripting environment; provide Bash/CLI alternatives.
Security
Secure your Microsoft Entra identity infrastructure
...rticles/security/fundamentals/steps-secure-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a moderate Windows bias, primarily through references to Windows-centric technologies (e.g., AD FS, Windows Server Active Directory, password protection for Windows Server, Windows Hello for Business) and the absence of Linux/macOS-specific examples or guidance. The document assumes familiarity with Windows-based identity infrastructure and does not provide parity for Linux or macOS environments, especially in hybrid scenarios and authentication technologies.
Recommendations
- Include equivalent Linux/macOS guidance or examples for hybrid identity scenarios, such as integrating non-Windows directory services with Microsoft Entra ID.
- Mention and provide links to cross-platform authentication methods (e.g., FIDO2 security keys, platform-agnostic passwordless solutions) before or alongside Windows-specific solutions.
- Clarify which features and recommendations are applicable regardless of OS, and explicitly note any Windows-only limitations.
- Provide examples or references for monitoring and securing identity infrastructure on Linux/macOS servers (e.g., using SIEM tools, log forwarding from non-Windows systems).
- Where AD FS or Windows Server Active Directory is referenced, offer alternatives or note the lack of equivalent Linux/macOS solutions.
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, primarily through exclusive use of PowerShell scripts and tools for critical tasks such as identifying dangling DNS entries. The only provided automation example is a PowerShell script, with no mention of Linux/macOS alternatives (e.g., Bash, Azure CLI, or cross-platform scripting). Additionally, the 'Quickstart' link for Resource Graph queries directs users to a PowerShell-based tutorial, and Windows-centric terminology and tooling are presented first and exclusively in sections where cross-platform options could be relevant.
Recommendations
- Provide equivalent Bash or Azure CLI examples/scripts for identifying dangling DNS entries and running Resource Graph queries.
- Explicitly state cross-platform compatibility of the PowerShell script (if applicable), or offer installation guidance for PowerShell Core on Linux/macOS.
- Include links to Azure CLI documentation and tutorials for relevant tasks.
- Add notes or sections clarifying how Linux/macOS users can perform the same operations, including prerequisites and environment setup.
- Consider reordering examples so that cross-platform or OS-neutral approaches are presented first, or in parallel with Windows-specific ones.
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias, particularly in the section on SMB encryption, which exclusively references Windows versions and tools. There are no explicit Linux or macOS examples or mentions for SMB access, nor are cross-platform command-line examples provided for encryption tasks. The order of presentation also tends to mention Windows technologies first when discussing SMB and VPN protocols.
Recommendations
- Include references to Linux and macOS clients for SMB access, such as using smbclient or mounting Azure Files via CIFS on Linux.
- Provide cross-platform examples for encryption-related tasks, including command-line snippets for Linux (e.g., using OpenSSL, curl, or Azure CLI on bash).
- Mention Linux support for VPN protocols (IPsec, SSTP, OpenVPN) and provide links to relevant Azure documentation for non-Windows platforms.
- When listing supported platforms or tools, present them in a neutral or alphabetical order, and avoid Windows-first phrasing.
- Add notes or links to platform-specific guides for macOS and Linux users where relevant.