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 26-50 of 380 flagged pages
Security
Microsoft Threat Modeling Tool release 4/9/2019
...rity/develop/threat-modeling-tool-releases-71604081.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for the Microsoft Threat Modeling Tool is exclusively focused on Windows, listing only Windows 10 as a supported operating system and requiring .NET Framework (Windows-only). There are no mentions of Linux or macOS support, nor any examples or instructions for non-Windows platforms. All tooling and requirements are Windows-centric.
Recommendations
- Explicitly state platform support, including whether Linux or macOS are supported or not.
- If Linux/macOS support is possible, provide installation and usage instructions for those platforms.
- If the tool is Windows-only, suggest alternative threat modeling tools for Linux/macOS users or provide rationale for the limitation.
- Consider developing cross-platform support in future releases to improve accessibility and parity.
Create Pull Request
Security
Microsoft Threat Modeling Tool release 10/16/2019 - Azure
...rity/develop/threat-modeling-tool-releases-71610151.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for the Microsoft Threat Modeling Tool is heavily Windows-centric. Only Windows operating systems are listed as supported, with no mention of Linux or macOS compatibility. All system requirements reference Windows-specific technologies (.NET Framework, Windows 10), and there are no examples or instructions for Linux users. The download and usage instructions assume a Windows environment, and no cross-platform alternatives or parity are provided.
Recommendations
- Clearly state platform limitations and, if possible, provide information about Linux/macOS support or alternatives.
- If the tool is Windows-only, suggest open-source or cross-platform threat modeling tools for Linux users.
- Include a section addressing installation and usage on non-Windows platforms, or explicitly mention lack of support.
- If future support is planned, note this in the documentation to inform non-Windows users.
- Ensure that any referenced tools or frameworks (such as .NET) include cross-platform installation instructions if applicable.
Security
Sensitive Data - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...ecurity/develop/threat-modeling-tool-sensitive-data.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several areas: Windows-specific technologies (EFS, DPAPI, BitLocker, Intune) are mentioned exclusively or before Linux equivalents, and examples are primarily for Windows environments (.NET, C#, ASP.NET, WCF). Linux alternatives (e.g., LUKS/dm-crypt for disk encryption) are only briefly referenced or omitted, and there are no Linux-specific code samples or configuration examples. The documentation also references Windows-centric tools and patterns (CryptoObfuscator, Intune, DPAPI) without providing parity for Linux or cross-platform scenarios.
Recommendations
- Provide Linux-specific examples and references for file system encryption (e.g., LUKS, eCryptfs, GnuPG, OpenSSL).
- When mentioning Windows tools (EFS, DPAPI, BitLocker), also mention and explain Linux equivalents (dm-crypt, LUKS, GnuPG) in parallel.
- Include code samples for Linux environments (e.g., bash scripts, Python, configuration for nginx/apache) alongside .NET/C# examples.
- Reference cross-platform or Linux-friendly obfuscation tools (e.g., ProGuard for Java, pyarmor for Python) when discussing binary obfuscation.
- For mobile device management, mention Android Enterprise, Apple MDM, and Linux-based solutions in addition to Intune.
- Balance references to Microsoft-centric technologies (Azure Key Vault, Intune, DPAPI) with open-source or cross-platform alternatives (HashiCorp Vault, GnuPG, OpenSSL).
- Explicitly state platform applicability in each section and provide guidance for both Windows and Linux deployments.
Security
Microsoft Antimalware code samples for Azure | Microsoft Docs
...cles/security/fundamentals/antimalware-code-samples.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell code samples and references to Windows-centric tools and file paths (e.g., C:\), with no mention of Linux equivalents or cross-platform approaches. All configuration and deployment instructions assume a Windows environment, omitting any guidance for Linux VMs or non-Windows management tools. This creates a strong Windows bias and leaves Linux users without actionable instructions.
Recommendations
- Provide equivalent Bash/CLI/ARM template examples for Linux VMs, or explicitly state if Microsoft Antimalware is not supported on Linux.
- Clarify platform support (Windows-only or cross-platform) at the start of the documentation.
- Include instructions or links for configuring antimalware or endpoint protection on Linux Azure VMs, such as using Microsoft Defender for Endpoint on Linux.
- Avoid using Windows-specific file paths (e.g., C:\) in generic configuration examples, or provide Linux path equivalents.
- Mention and demonstrate use of Azure CLI (az) where possible, as it is cross-platform.
Security
Session Management - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
...ity/develop/threat-modeling-tool-session-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows-centric technologies and patterns, such as ASP.NET, ADFS, web.config, and PowerShell commands. All code samples and configuration examples use Windows-specific frameworks (ASP.NET MVC, Web Forms, web.config XML, C#), and there are no Linux or cross-platform equivalents provided. Windows tools (e.g., PowerShell for ADFS configuration) are mentioned exclusively, and Linux alternatives (such as bash scripts, nginx/apache config, or cross-platform frameworks) are missing. The documentation assumes a Windows/IIS environment throughout and does not address Linux-hosted web applications or APIs.
Recommendations
- Add equivalent examples for Linux-based web frameworks (e.g., Django, Flask, Node.js/Express, Ruby on Rails) for session management, CSRF protection, and secure cookie settings.
- Include configuration samples for popular Linux web servers (nginx, Apache) showing how to enforce secure and HttpOnly cookies.
- Provide cross-platform code samples (e.g., using Python, JavaScript, or Java) for session timeout and logout logic.
- Mention Linux command-line tools and scripts (e.g., bash, systemd, cron) for managing session lifetimes and authentication tokens.
- Reference open-source identity providers and SSO solutions (e.g., Keycloak, Auth0, OAuth2-proxy) and show how to configure logout and session management on Linux.
- When describing PowerShell commands, offer bash or CLI alternatives for Linux environments where possible.
- Clarify which mitigations and patterns are Windows-specific and which are applicable cross-platform, and structure documentation so that Linux options are presented alongside Windows ones.
Security
Security Recommendations for Azure Marketplace Images | Microsoft Docs
...cles/security/fundamentals/azure-marketplace-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page presents recommendations for both Linux and Windows images, but several signs of Windows bias are evident. In the Linux section, Windows terminology (e.g., 'Windows Server roles') appears, and some checks reference Windows-specific concepts. The Windows section includes recommendations for BitLocker and auto-update, but Linux equivalents (e.g., LUKS encryption, unattended-upgrades) are not mentioned. Additionally, Windows tools and patterns (BitLocker, HOSTS file) are referenced without Linux counterparts, and some recommendations are more detailed for Windows than Linux.
Recommendations
- Remove or clarify Windows-specific terminology in the Linux section (e.g., 'Windows Server roles').
- Add Linux equivalents for Windows-specific recommendations, such as mentioning LUKS for disk encryption and 'unattended-upgrades' for automatic security updates.
- Ensure that examples and recommendations for sensitive file removal reference Linux-specific files (e.g., /etc/hosts, .bash_history) alongside Windows files.
- Balance the level of detail between Windows and Linux sections, providing parity in actionable steps and tool references.
- Consider listing Linux recommendations before Windows recommendations or interleaving them to avoid implicit prioritization.
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, notably in the SMB encryption section, which references only Windows versions and tools (Windows Server, Windows 8/10) without mentioning Linux or cross-platform SMB clients. There are no PowerShell-heavy examples, but Windows tools and terminology are used exclusively or before Linux equivalents in some areas. No explicit Linux examples or parity notes are provided for encryption features that are relevant to both platforms.
Recommendations
- Add examples or references for using SMB encryption with Linux clients (e.g., smbclient, mount.cifs with encryption options).
- Where Windows tools or protocols are mentioned (e.g., SMB, SSTP), clarify cross-platform support and provide Linux/macOS equivalents or links to relevant documentation.
- Include notes or examples for configuring Azure encryption features from Linux environments, such as using Azure CLI or REST APIs from Linux shells.
- Ensure that protocol and tool descriptions (e.g., VPN, SMB, TLS) mention support and usage on non-Windows platforms where applicable.
Security
Microsoft Antimalware for Azure | Microsoft Docs
...lob/main/articles/security/fundamentals/antimalware.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All examples, deployment instructions, and supported platforms focus exclusively on Windows Server and Windows-based Azure services. There is no guidance or parity for Linux VMs or Linux-based services, and all configuration and management steps rely on Windows-centric tools such as PowerShell, Visual Studio, and Windows event logs. Linux is explicitly stated as unsupported, and no alternative antimalware solutions or deployment patterns for Linux are mentioned.
Recommendations
- Clearly state Linux support status at the beginning of the document and provide links to recommended antimalware solutions for Linux VMs in Azure.
- If Microsoft Antimalware is not available for Linux, suggest equivalent Azure-supported antimalware extensions (e.g., Trend Micro, Symantec, etc.) and provide deployment instructions for those.
- Include Linux-focused examples for monitoring, event collection, and extension deployment using Bash/CLI, ARM templates, or other cross-platform tools.
- Mention Linux equivalents for event logging and diagnostics (e.g., syslog, journald) and how to collect and monitor antimalware events on Linux.
- Balance PowerShell-heavy sections with Azure CLI or REST API examples that work on both Windows and Linux platforms.
- Add a comparison table of antimalware solutions available for Windows and Linux in Azure, including supported features and deployment methods.
Security
Data security and encryption best practices - Microsoft Azure
...ecurity/fundamentals/data-encryption-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Privileged Access Workstation, Microsoft 365, Entra ID, Azure RMS) without mentioning Linux equivalents or alternatives. Endpoint and workstation security guidance is framed around Windows concepts, and there are no examples or recommendations for Linux-based management workstations or open-source alternatives. The documentation assumes a Windows-centric environment, omitting Linux-specific best practices and tools for secure access, endpoint protection, and data encryption.
Recommendations
- Include examples and guidance for securing Linux-based management workstations, such as using hardened Linux distributions (e.g., Ubuntu LTS, CentOS Stream) and open-source endpoint protection solutions.
- Mention Linux-compatible key management and encryption tools, such as integration with Azure Key Vault via CLI, REST API, or SDKs available for Linux.
- Provide parity in endpoint protection recommendations, referencing Linux security frameworks (e.g., SELinux, AppArmor), and open-source antivirus solutions.
- Add examples for VPN and secure access setup using Linux clients (e.g., strongSwan, OpenVPN) alongside Windows examples.
- Reference cross-platform Azure management tools (e.g., Azure CLI, Terraform) and provide usage examples on Linux.
- Ensure documentation language and examples address both Windows and Linux environments equally, avoiding implicit Windows-first assumptions.
Security
Cloud feature availability for commercial and US Government customers
...articles/security/fundamentals/feature-availability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing PowerShell for administration and automation tasks, and by focusing on Microsoft Office and related Windows-centric tools. There are no Linux or cross-platform command-line examples, nor are Linux-native tools or patterns mentioned for feature administration or automation. The only explicit Linux reference is for the Defender for IoT micro agent, which is not a general administrative or automation example. This creates a perception that Windows is the primary or only supported platform for many administrative scenarios.
Recommendations
- Provide equivalent Linux/bash CLI examples alongside PowerShell examples for all administrative and automation tasks.
- Reference and document usage of Azure CLI and REST API for feature management, which are cross-platform.
- Highlight Linux support for relevant features, especially in sections about scanners, SDKs, and automation.
- Include links to Linux-specific documentation or troubleshooting guides where appropriate.
- Clarify platform requirements and parity for all features, especially where only Windows tools are mentioned.
Security
Azure identity & access security best practices | Microsoft Docs
...ity/fundamentals/identity-management-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as Active Directory, Windows Server agents, Windows Hello for Business, and Privileged Access Workstations (PAWs), without providing equivalent Linux examples or alternatives. Windows-centric terminology and solutions are presented exclusively or before any mention of cross-platform or Linux-compatible options. There is a lack of guidance for organizations using Linux-based infrastructure, especially for password protection, privileged access workstations, and authentication methods.
Recommendations
- Include Linux equivalents or alternatives for all Windows-specific tools and features (e.g., mention Linux PAM modules for password protection, Linux-based privileged access workstation strategies, and Linux-compatible MFA solutions).
- Provide cross-platform examples for identity integration, authentication, and automation (e.g., Azure CLI usage on Linux, non-Windows SSO and passwordless authentication methods).
- Explicitly state when features are Windows-only and offer guidance for Linux environments where possible.
- Add documentation links or references to Azure identity and access management best practices for Linux and other non-Windows platforms.
- Ensure parity in examples and recommendations for both Windows and Linux administrators throughout the document.
Security
Azure identity management security overview
.../security/fundamentals/identity-management-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric concepts and tools (Active Directory, AD DS, AD FS, Windows Hello for Business) without mentioning Linux equivalents or providing Linux-specific examples. The documentation assumes familiarity with Windows environments and omits guidance for organizations using Linux-based identity management, authentication, or device registration solutions.
Recommendations
- Include examples and guidance for integrating Microsoft Entra ID with Linux-based identity management systems (e.g., LDAP, FreeIPA).
- Mention Linux-compatible authentication methods and device registration options, such as FIDO2 keys and certificate-based authentication on Linux endpoints.
- Provide parity in hybrid identity management by describing how Linux servers and workstations can participate in identity synchronization and SSO scenarios.
- Reference cross-platform tools and patterns (e.g., SSSD, Kerberos, PAM modules) alongside Windows tools.
- Add links to documentation or tutorials for configuring Microsoft Entra ID features on Linux systems.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific components (e.g., Windows Fabric platform, Windows administrator accounts) and tools (Endpoint Protection anti-virus) without mentioning Linux equivalents or providing Linux-focused examples. The narrative and terminology consistently prioritize Windows environments and patterns, with no discussion of Linux guest OS scenarios, Linux-based security tools, or cross-platform considerations.
Recommendations
- Include explicit references to Linux guest OS scenarios and describe how infrastructure integrity is maintained for Linux-based VMs.
- Mention and provide examples of anti-virus or endpoint protection tools commonly used in Linux environments (e.g., ClamAV, Sophos, etc.) and clarify whether similar scanning procedures apply.
- Discuss account management and default security practices for Linux VMs (e.g., disabling root, use of sudo, SSH key management).
- Describe how ACLs and firewalls are configured and managed for Linux nodes, and whether there are platform-specific differences.
- Ensure that monitoring agent descriptions include Linux compatibility and deployment patterns.
- Balance references to Windows-specific technologies (such as Windows Fabric) with Linux equivalents or clarify cross-platform support.
Security
Azure security logging and auditing | Microsoft Docs
.../blob/main/articles/security/fundamentals/log-audit.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows event logs and tools before Linux equivalents, providing more detail about Windows logging mechanisms (e.g., Windows Event Log service) and referencing Windows-specific integration patterns (Azure Diagnostics for Windows). Linux logging (Syslog) is mentioned only as an aside, with no examples or further explanation. There are no Linux-specific integration or usage examples, and Windows tools/patterns are referenced more prominently.
Recommendations
- Provide equal coverage and examples for Linux logging, such as detailed instructions for collecting and integrating Syslog data from Linux VMs.
- Include Linux-specific tools and integration patterns (e.g., using the Azure Monitor agent on Linux, configuring rsyslog or journald for Azure integration).
- Present Windows and Linux logging options side-by-side in tables and explanations, rather than listing Windows first or in greater detail.
- Add practical Linux command-line examples for log collection, forwarding, and integration with Azure Monitor or SIEM systems.
- Reference Linux documentation and best practices for security logging and auditing in Azure environments.
Security
Security best practices for IaaS workloads in Azure | Microsoft Docs
...-docs/blob/main/articles/security/fundamentals/iaas.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (e.g., PowerShell cmdlets like Add-AzKeyVaultKey and Set-AzVMDiskEncryptionExtension) are referenced without Linux CLI equivalents. Windows terminology and update patterns (WSUS, Windows Update) are mentioned before or more prominently than Linux alternatives. Examples and guidance for Linux users are sparse or missing, especially for operational tasks like disk encryption, backup, and diagnostics. Some sections mention Linux, but practical instructions or command-line examples are focused on Windows.
Recommendations
- Provide Linux CLI (bash/az CLI) equivalents for all PowerShell cmdlet examples, especially for key management and disk encryption.
- Include Linux-specific operational guidance for tasks such as backup, diagnostics, and VM monitoring (e.g., using Azure Diagnostics extension on Linux, snapshotting Linux disks).
- Balance the order of presentation so that Linux and Windows are treated equally, mentioning both platforms in parallel where possible.
- Reference Linux-native tools and update mechanisms (e.g., apt/yum/dnf for updates, cron for scheduling) alongside Windows tools.
- Add explicit Linux examples for integrating with Azure services (e.g., using Entra authentication, Defender for Cloud, Azure Monitor) with step-by-step instructions.
- Clarify when recommendations apply to both platforms and highlight any differences in implementation.
Security
Azure information system components and boundaries
...les/security/fundamentals/infrastructure-components.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows Server as the host operating system for Azure VMs, mentioning Windows Firewall as the default security tool, and omitting any discussion of Linux-based host or guest operating systems. There are no examples or references to Linux tools, patterns, or equivalents, and Windows technologies are presented as the default or only option.
Recommendations
- Explicitly mention support for Linux-based host and guest operating systems in Azure, if applicable.
- Include examples or descriptions of security tools and configurations for Linux VMs (e.g., iptables, firewalld) alongside Windows Firewall.
- Clarify whether the Azure hypervisor and fabric controller support Linux hosts or guests, and describe any differences in management or security practices.
- Provide parity in documentation by listing both Windows and Linux options for VM images, management, and configuration.
- Avoid language that implies Windows is the only or default platform; use neutral phrasing and highlight cross-platform capabilities.
Security
Isolation in the Azure Public Cloud | Microsoft Docs
...in/articles/security/fundamentals/isolation-choices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by frequently referencing Windows-specific technologies (e.g., Windows Firewall, BitLocker, Active Directory Federation Services), mentioning Windows tools and patterns before their Linux equivalents, and providing more detail for Windows scenarios. Linux equivalents are sometimes mentioned but often lack parity in explanation or are referenced after Windows options. There are no explicit Linux command-line or tool examples, and PowerShell/Windows-centric terminology dominates, with little attention to Linux-native workflows.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, such as using Azure CLI/bash commands for access control and diagnostics.
- Mention Linux technologies (e.g., iptables, SELinux, dm-crypt) with equal detail and priority as Windows tools like Windows Firewall and BitLocker.
- Ensure that references to management tools (e.g., Azure CLI, SSH) are presented before or alongside Windows tools (e.g., PowerShell, RDP).
- Include explicit Linux scenarios and troubleshooting steps, not just generic references.
- Balance explanations of identity and access management to include Linux-based integration patterns (e.g., LDAP, PAM) where relevant.
- Review and update diagrams and examples to show both Windows and Linux VM contexts.
Security
Azure security management and monitoring overview
...ecurity/fundamentals/management-monitoring-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias. Azure Automation highlights PowerShell before Python for runbooks, and features like hotpatching in Azure Update Manager are described as Windows Server-specific. There is a general tendency to mention Windows-centric tools and features (e.g., PowerShell, Windows Server hotpatching) without equal emphasis on Linux equivalents or examples. No explicit Linux command-line or automation examples are provided, and Windows features are sometimes described first or exclusively.
Recommendations
- Include Linux-specific examples and automation scenarios alongside Windows/PowerShell, such as Bash or Python scripts for Azure Automation.
- Clarify which features (e.g., hotpatching) are Windows-only and highlight equivalent or alternative Linux update management strategies.
- Provide parity in documentation for both Windows and Linux, ensuring that Linux tools, commands, and workflows are described with equal prominence.
- Add explicit examples or references for managing Linux VMs, such as using Azure Automation with Python or Bash, and update management for Linux distributions.
- Where PowerShell is mentioned, also mention Bash or other Linux-native scripting options, especially in automation sections.
Security
Azure operational security checklist| Microsoft Docs
...rticles/security/fundamentals/operational-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing Windows-specific protocols (SMB 3.0) and tools without providing equivalent Linux examples or alternatives. Windows technologies are mentioned first or exclusively, such as SMB for Azure File Shares, and there is a lack of Linux-specific operational security guidance or examples throughout the checklist.
Recommendations
- Include Linux-specific examples and tools where relevant, such as mentioning NFS or other Linux-compatible protocols for Azure File Shares alongside SMB.
- Provide parity in operational security recommendations for both Windows and Linux environments, such as referencing Azure Disk Encryption for Linux VMs with equal prominence as Windows VMs.
- Add examples or guidance for Linux command-line tools and security practices (e.g., using Bash, SSH, or Linux-native monitoring solutions) in addition to or alongside Windows/Powershell examples.
- Ensure that documentation does not assume a Windows-first approach and explicitly addresses cross-platform scenarios, including hybrid and Linux-only deployments.
Security
Introduction to Azure security | Microsoft Docs
...s/blob/main/articles/security/fundamentals/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows and Windows-specific tools (such as PowerShell, IIS, and Windows 10 features) are mentioned before or in greater detail than their Linux equivalents. Examples and instructions often reference Windows or PowerShell without providing equivalent Linux commands or guidance. Some features and integrations (e.g., Microsoft Entra join, BitLocker recovery, IIS diagnostics) are described only for Windows, with little or no mention of Linux alternatives. In several places, antimalware and backup solutions are described with a Windows-first perspective, and Linux-specific security practices or tools are underrepresented or omitted.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows/PowerShell examples, especially for VM management, backup, encryption, and diagnostics.
- Mention Linux tools and patterns (e.g., SELinux, auditd, iptables, systemd, journald) where relevant, and describe how Azure integrates with or supports these.
- Ensure parity in feature descriptions, such as disk encryption, backup, and monitoring, by explicitly stating Linux support and linking to Linux documentation.
- Include guidance for Linux-based identity and access management scenarios, such as integration with PAM, SSH key management, and Linux authentication modules.
- Balance references to Windows-specific features (e.g., BitLocker, IIS, PowerShell) with Linux equivalents (e.g., LUKS, Apache/Nginx, Bash/CLI).
- Add troubleshooting and diagnostic instructions for Linux environments, including log collection, performance monitoring, and security auditing.
- Highlight Azure security services and integrations that are platform-agnostic or provide clear Linux support.
Security
Best practices for protecting secrets
...ticles/security/fundamentals/secrets-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure and Microsoft-centric tools and patterns, with examples and links focused on Windows environments (e.g., Azure Key Vault, Azure Managed HSM, Azure role-based access control, Azure DevOps Credential Scanner). There are no Linux-specific examples, tools, or patterns mentioned, nor is there guidance for non-Windows platforms. Service-specific best practices reference Windows-centric technologies (such as Azure PowerShell and SQL Server on Azure VMs), and Linux alternatives or parity are not addressed.
Recommendations
- Include examples and guidance for Linux environments, such as using environment variables, secret management tools (e.g., HashiCorp Vault, GnuPG, sops), and Linux command-line utilities.
- Provide parity for secret scanning tools by mentioning open-source or Linux-native options (e.g., truffleHog, git-secrets) alongside Azure DevOps Credential Scanner.
- Reference cross-platform automation and scripting options (e.g., Bash, Python scripts) in addition to or instead of Azure PowerShell.
- Add documentation links and examples for managing secrets in Linux-based Azure services (e.g., Azure Database for PostgreSQL, AKS) using Linux tools and workflows.
- Explicitly state platform-agnostic best practices and clarify where recommendations apply to both Windows and Linux, or provide separate guidance for each.
Security
Azure Operational Security | Microsoft Docs
...articles/security/fundamentals/operational-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows terminology (e.g., 'Windows Azure') is used throughout, and Windows Server is mentioned before Linux in backup scenarios. Diagnostic log examples focus on Windows event logs, with Linux equivalents (e.g., syslog) mentioned only in passing. Tooling references (PowerShell, System Center Data Protection Manager) are Windows-centric, and instructions or examples for Linux management (such as enabling diagnostics or using CLI tools) are missing or less prominent.
Recommendations
- Ensure Linux is mentioned alongside Windows in all relevant scenarios, such as backup, monitoring, and diagnostics.
- Provide explicit Linux examples (e.g., syslog configuration, Linux agent installation, CLI commands) wherever Windows examples are given.
- Avoid using Windows-centric terminology (e.g., 'Windows Azure') when referring to the broader Azure platform.
- Highlight cross-platform tools (e.g., Azure CLI, REST API) and provide parity in instructions for both Windows and Linux environments.
- Include references to Linux-native management solutions and logs (e.g., journald, auditd) where appropriate.
Security
Securing PaaS web & mobile applications
...y/fundamentals/paas-applications-using-app-services.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing a specific example for restricting IP addresses using web.config, which is only applicable to App Service on Windows. There are no equivalent examples or guidance for Linux-based App Service environments, and Windows-specific tooling (web.config, IIS Dynamic IP Security) is mentioned without Linux parity.
Recommendations
- Add examples and instructions for restricting IP addresses on App Service for Linux, such as using iptables, nginx configuration, or Azure App Service access restrictions.
- Mention Linux equivalents alongside Windows-specific tools (e.g., web.config) to ensure parity and inclusivity.
- Where platform-specific features are discussed, clearly indicate alternatives or limitations for both Windows and Linux environments.
- Review the documentation for other sections where Windows-first language or examples may be present and update to include Linux scenarios.
Security
Best practices for secure PaaS deployments - Microsoft Azure
...ain/articles/security/fundamentals/paas-deployments.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and interfaces (such as PowerShell and Microsoft Defender), focusing exclusively on Microsoft authentication and identity solutions, and omitting Linux-specific examples or tools. There are no Linux command-line or configuration examples, nor are Linux-native security tools or patterns mentioned. Where remote management is referenced, only PowerShell is named, and general security practices are described solely in terms of Microsoft/Azure technologies, which are most familiar to Windows users.
Recommendations
- Include Linux-specific examples for common security tasks, such as using Azure CLI or Bash scripts for identity and key management.
- Mention Linux-native tools and patterns (e.g., SSH, iptables, SELinux/AppArmor, Linux-based monitoring agents) alongside Windows equivalents.
- When referencing remote management, include both PowerShell and Azure CLI/Bash options, and provide parity in instructions.
- Highlight how Azure security features integrate with Linux-based workloads and provide best practices for securing Linux PaaS deployments.
- Add sample configurations or code snippets for Linux environments, especially for authentication, monitoring, and secure deployment.
- Ensure that documentation does not assume a Windows-first audience by balancing terminology and examples for both platforms.
Security
Detect and respond to ransomware attacks
...les/security/fundamentals/ransomware-detect-respond.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. It references Windows-specific tools and concepts (such as PowerShell Operational logs, Security Event logs, Defender for Endpoint, and RDP) without mentioning Linux equivalents or providing Linux-specific guidance. Examples and recommendations are tailored to Windows environments, with no parity for Linux systems running on Azure. The documentation assumes familiarity with Windows-centric incident response workflows and omits details on how to detect and respond to ransomware on Linux VMs or services.
Recommendations
- Add explicit guidance and examples for Linux-based Azure VMs, including how to detect ransomware using Linux audit logs, syslog, and other native tools.
- Mention Linux equivalents for Windows concepts, such as monitoring /var/log/auth.log, /var/log/syslog, and bash history instead of PowerShell logs.
- Include instructions for isolating Linux VMs using Defender for Endpoint or other Azure-native controls, and clarify any differences in containment procedures.
- Reference Linux-specific ransomware detection and response tools (e.g., ClamAV, Linux EDR solutions) alongside Windows tools.
- Ensure that incident response workflows and recommendations are platform-neutral or provide parallel steps for both Windows and Linux environments.