Governance
305
Total Pages
190
Linux-Friendly Pages
115
Pages with Bias
37.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
613 issues found
Showing 1-25 of 613 flagged pages
Governance
How to create a machine configuration assignment using Terraform
...configuration/how-to/assign-configuration/terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates machine configuration assignment using Terraform for Windows virtual machines. All code examples reference azurerm_windows_virtual_machine resources, and the built-in configuration shown is AzureWindowsBaseline, which is Windows-specific. There are no examples, references, or guidance for Linux virtual machines or Linux-specific configurations. Additionally, the 'get-started' link points to a Windows PowerShell guide, further reinforcing a Windows-centric approach.
Recommendations
- Add equivalent examples for azurerm_linux_virtual_machine, showing how to assign configurations to Linux VMs.
- Include built-in configuration examples relevant to Linux, such as CIS or Ubuntu baselines.
- Provide links to Linux/macOS Terraform setup guides alongside the Windows PowerShell guide.
- Clearly state in the introduction which OS platforms are supported and provide parity in documentation structure.
Create Pull Request
Governance
How to create a machine configuration assignment using Terraform
...configuration/how-to/assign-configuration/terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates machine configuration assignments for Windows virtual machines, referencing only Windows resources (azurerm_windows_virtual_machine) and built-in Windows configurations (AzureWindowsBaseline). There are no examples or guidance for Linux virtual machines, nor mention of Linux-specific configurations or resources. The 'get started' link points to a Windows PowerShell guide, further reinforcing the Windows-centric approach.
Recommendations
- Add equivalent examples for Linux virtual machines using azurerm_linux_virtual_machine.
- Include built-in Linux configuration assignment samples (e.g., AzureLinuxBaseline).
- Provide links to Linux/macOS Terraform setup guides, not just Windows PowerShell.
- Clarify which steps or resources are OS-specific, and offer parity where possible.
Governance
How to create custom machine configuration policy definitions
...chine-configuration/how-to/create-policy-definition.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias: all code examples use PowerShell, and all sample policy definitions specify 'Platform = Windows'. Windows-specific tools and paths (e.g., 'C:\Local\Path\To\Package') are used exclusively, with no Linux/macOS equivalents or examples. Even when Linux is mentioned (e.g., required agent versions), practical guidance and examples for Linux users are absent.
Recommendations
- Provide equivalent examples for Linux, using bash/CLI commands where possible.
- Show how to set up and use the GuestConfiguration module on Linux/macOS, including installation steps.
- Include sample policy definitions for Linux (e.g., 'Platform = Linux') and demonstrate auditing/enforcing Linux services.
- Use cross-platform file paths in examples (e.g., '/home/user/package.zip' for Linux/macOS).
- Mention Linux/macOS-specific considerations (e.g., permissions, service names, agent installation).
- Clarify which steps are OS-agnostic and which require adaptation for Linux/macOS.
Governance
Quickstart: Create a blueprint with REST API
...les/governance/blueprints/create-blueprint-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for REST API calls, recommending PowerShell as the primary tool for beginners, and omitting equivalent Linux-friendly examples (such as Bash/cURL). Windows tools and patterns are mentioned first and exclusively, with no parity for Linux or cross-platform command-line tools.
Recommendations
- Provide equivalent Bash/cURL examples for REST API calls alongside PowerShell examples.
- Mention cross-platform tools (e.g., HTTPie, curl, Postman) as alternatives to PowerShell for making REST API requests.
- Reorder sections so that cross-platform or OS-neutral tools are presented before or alongside Windows-specific tools.
- Explicitly state that instructions are applicable on both Windows and Linux, and provide guidance for authentication and REST calls in both environments.
- Include notes or links to Linux-specific setup or usage guides for Azure authentication and REST API usage.
Governance
Planning a change from Desired State Configuration extension to machine configuration
...onfiguration/whats-new/migrating-from-dsc-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It focuses almost exclusively on PowerShell DSC, Windows PowerShell versions, and Windows-specific tools and patterns. All examples, migration steps, and commands are PowerShell-centric, with no mention of Linux equivalents or cross-platform considerations. The guidance assumes the reader is working with Windows VMs and does not provide instructions or examples for Linux environments.
Recommendations
- Include explicit guidance and examples for Linux VMs, such as how to check for DSC extension presence and migrate configurations on Linux.
- Mention and provide examples for Linux-compatible configuration management tools or DSC resources, if available.
- Clarify which steps and features apply to both Windows and Linux, and note any platform-specific differences.
- Provide sample queries and commands for Linux environments (e.g., Bash, Azure CLI) alongside PowerShell examples.
- Discuss how machine configuration interacts with Linux systems, including supported versions and limitations.
Governance
How to install the machine configuration authoring module
...velop-custom-package/1-set-up-authoring-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, which is traditionally a Windows-centric tool, and all examples use PowerShell commands. Windows is listed before Ubuntu in requirements and installation tables. The instructions for installing modules and validating them are identical for both platforms, but there are no examples using native Linux tools or shell environments (e.g., Bash). The documentation assumes PowerShell is the primary interface on Linux, omitting any mention of Linux-specific workflows or alternatives.
Recommendations
- Provide equivalent examples using native Linux tools (e.g., Bash, apt, systemctl) where possible.
- Include instructions for installing and managing modules using Linux package managers or shell commands, not just PowerShell.
- Balance the order of OS mentions (alternate between Windows and Linux, or list alphabetically).
- Clarify if PowerShell is required on Linux, and discuss any limitations or alternatives for Linux users.
- Add troubleshooting or notes specific to Linux environments (e.g., permissions, file paths, service management).
Governance
Details of the Azure Policy attestation structure
...es/governance/policy/concepts/attestation-structure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references Azure Policy attestation management via ARM API, PowerShell, and Azure CLI, listing PowerShell before Azure CLI. There are no platform-specific usage examples, but the explicit mention of PowerShell (a Windows-centric tool) before Azure CLI, and the absence of Linux shell or cross-platform command examples, suggests a subtle Windows bias. No Linux-specific tools or usage patterns are discussed.
Recommendations
- Provide explicit Linux shell (bash) examples for attestation management using Azure CLI.
- List Azure CLI before PowerShell when presenting cross-platform management options, or present them together.
- Mention that Azure CLI is cross-platform and available on Linux, macOS, and Windows.
- If PowerShell is referenced, clarify that PowerShell Core is available on Linux and macOS, or provide equivalent bash examples.
- Include links or references to installing and using Azure CLI and PowerShell on Linux.
Governance
How to test machine configuration package artifacts
...ration/how-to/develop-custom-package/3-test-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation is heavily PowerShell-centric, with all examples using PowerShell commands for both Windows and Linux. Windows-specific tools (PSExec) are mentioned before Linux equivalents (sudo), and instructions often present Windows steps first. There are no native Linux shell examples (e.g., bash, sh), and the documentation assumes PowerShell is the primary interface on Linux, which is less common in typical Linux environments.
Recommendations
- Provide native Linux shell (bash/sh) examples alongside PowerShell, especially for Linux users who may not have PowerShell installed.
- Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
- Mention Linux-native tools and patterns (e.g., using root, systemd, or other common Linux practices) where appropriate, not just sudo.
- Clarify PowerShell requirements for Linux, and provide guidance for environments where PowerShell is not available.
- Consider adding troubleshooting and usage notes specific to common Linux distributions beyond Ubuntu, reflecting broader Linux usage.
Governance
How to create a machine configuration assignment using the Azure Rest API
...-configuration/how-to/assign-configuration/rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by referencing the PowerShell Get-AzAccessToken cmdlet as the only example for obtaining an Azure access token, without mentioning or providing equivalent Linux or cross-platform alternatives. There are no Linux-specific tools or commands referenced for authentication, and the only tool-specific guidance is Windows-centric.
Recommendations
- Provide equivalent examples for obtaining an Azure access token using cross-platform tools such as Azure CLI (az account get-access-token) and document how to use them in the context of the API request.
- Explicitly mention that curl and the HTTP API are cross-platform, and provide authentication examples for both Windows and Linux environments.
- Include references or links to Linux/macOS authentication workflows, such as using environment variables or OpenID Connect tokens.
- Avoid referencing only PowerShell cmdlets when cross-platform alternatives exist, or at minimum, present them alongside each other.
Governance
Protect your resource hierarchy - Azure Governance
...management-groups/how-to/protect-resource-hierarchy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides a detailed Azure PowerShell example for configuring resource hierarchy settings, but does not offer equivalent examples for Linux-native tools such as Bash, Azure CLI, or curl. The only command-line sample is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux or cross-platform alternatives. The structure also places the PowerShell example as the sole scripting method, reinforcing a Windows-centric approach.
Recommendations
- Add equivalent examples using Azure CLI and Bash/curl to demonstrate REST API calls from Linux and macOS environments.
- Explicitly mention that the REST API can be accessed from any platform and provide sample commands for non-Windows users.
- Reorganize the documentation to present cross-platform methods (e.g., REST API via curl, Azure CLI) before or alongside PowerShell examples.
- Clarify that PowerShell Core is available on Linux/macOS, but provide syntax for other common shells to ensure inclusivity.
Governance
Differences between ARG GET/LIST API and ARG Query service
...e-graph/concepts/get-list-query-service-differences.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a supported client before Azure CLI, referencing PowerShell in example links, and omitting explicit Linux or cross-platform command examples. There is no mention of Linux-specific tools or usage patterns, and examples are either generic or Windows-centric.
Recommendations
- Include explicit Azure CLI examples alongside PowerShell, especially in example links and usage scenarios.
- Mention Linux and macOS as supported platforms for Azure CLI and SDKs.
- Provide sample commands for querying ARG from Linux environments (e.g., bash scripts, curl commands).
- Avoid listing Windows tools (PowerShell) before cross-platform tools (Azure CLI) unless contextually justified.
- Add a section or note highlighting cross-platform compatibility and usage.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for interacting with Azure Resource Graph, but does not include Linux-specific shell examples (e.g., bash scripting, piping, jq usage) or mention Linux tools. Azure PowerShell, which is primarily associated with Windows environments, is given equal prominence to Azure CLI, but no Linux-centric workflows are discussed. There is no mention of Linux-specific considerations or alternative tooling, and examples do not demonstrate output manipulation typical in Linux environments.
Recommendations
- Add Linux shell examples, such as using bash with az graph query and piping results to jq for parsing.
- Include notes on cross-platform compatibility of Azure CLI and PowerShell, clarifying that both can run on Linux, macOS, and Windows.
- Demonstrate output formatting and manipulation using common Linux tools (e.g., grep, awk, jq) alongside PowerShell examples.
- Explicitly mention that Azure CLI is cross-platform and provide examples of scripting in Linux environments.
- Where PowerShell is shown, clarify that PowerShell Core is available on Linux and macOS, and provide equivalent bash examples for parity.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is the only CLI example provided for duplicating policy definitions, with no Bash, Azure CLI, or Linux-native alternatives. Windows tools and patterns (PowerShell, Visual Studio Code) are mentioned exclusively or before cross-platform options. There are references to Windows-specific policy definitions (auditing Windows machines for pending reboots) without equivalent Linux-focused examples. Linux and macOS users are not given parity in troubleshooting steps or command-line instructions.
Recommendations
- Provide equivalent Azure CLI or Bash examples alongside PowerShell scripts for all command-line instructions, especially for duplicating policy definitions.
- Mention cross-platform tools (e.g., Azure CLI, VS Code for Linux/macOS) equally or before Windows-specific tools.
- Include Linux-focused policy definition examples (e.g., auditing Linux machines for pending reboots) where Windows examples are given.
- Explicitly state that all troubleshooting steps and commands are applicable to both Windows and Linux, or provide platform-specific guidance as needed.
- Ensure that references to tools and patterns (such as VS Code extensions) clarify their availability on Linux/macOS.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently provides Azure PowerShell examples alongside Azure CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion in every example (often before or alongside CLI) may signal a Windows bias. There are no explicit Linux shell (bash, zsh, etc.) examples, nor are Linux-specific usage notes or troubleshooting tips provided. The CLI examples are cross-platform, but the lack of explicit Linux shell context or parity (e.g., scripting, environment variables, authentication differences) means Linux users may not feel fully supported.
Recommendations
- Add explicit bash/zsh shell examples for each scenario, showing how to use az CLI in Linux environments (including environment variable usage, piping, and output parsing).
- Include notes on authentication and installation differences for Linux users (e.g., az CLI installation via apt/yum, differences in credential storage).
- Where PowerShell is mentioned, clarify that it is available cross-platform, but also provide Linux-native alternatives (e.g., bash scripts, jq for JSON parsing).
- Add troubleshooting or FAQ sections for common Linux issues (e.g., permissions, path differences, dependency installation).
- Consider reordering examples to present CLI (cross-platform) first, followed by PowerShell, to emphasize platform neutrality.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a moderate Windows bias. Windows concepts (such as Windows Server patching, KB IDs, and PowerShell) are presented before or more prominently than Linux equivalents. Examples for Windows Server OS update installation are given separately and with more detail than for Linux, and Windows-specific terminology (e.g., KB IDs, update classifications like 'updateRollup', 'featurePack', 'servicePack') is used without Linux equivalents. PowerShell is featured as a primary automation tool, and there is little mention of Linux-native command-line tools or shell environments. Most queries and examples are generic, but where OS-specific details are shown, Windows is prioritized or described first. Linux-specific queries are present but less detailed and less frequent.
Recommendations
- Ensure Linux examples are given equal prominence and detail as Windows examples, especially for OS update queries.
- Provide Linux-native command-line usage patterns (e.g., bash, shell scripts) alongside PowerShell and Azure CLI.
- Clarify update classifications and terminology for Linux systems, mapping or explaining equivalents to Windows terms.
- Where OS-specific queries are shown, alternate the order or provide combined examples for both Windows and Linux.
- Include references to Linux patching tools and patterns (e.g., apt, yum, zypper) where relevant.
- Review and balance the use of Windows-centric language and concepts throughout the documentation.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There is no mention of Linux shell equivalents (e.g., Bash), nor are there examples using native Linux tools or scripting patterns. The PowerShell example is given equal prominence to the CLI, but the lack of Linux-specific guidance or examples (such as Bash scripting or usage in Linux terminals) suggests a bias toward Windows users and tooling.
Recommendations
- Add explicit Bash shell examples for running the Azure CLI command, including syntax for Linux/macOS terminals.
- Clarify that Azure CLI is cross-platform and provide instructions for installation and usage on Linux and macOS.
- Include notes or examples for using the query in Linux environments, such as piping CLI output to jq or other Linux-native tools.
- Consider adding a section on running these queries in WSL (Windows Subsystem for Linux) or native Linux environments to improve parity.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Blueprints exhibits a mild Windows bias. In the 'Next steps' section, PowerShell is listed as the only command-line example, with no mention of Bash, Azure CLI, or Linux shell equivalents. The ordering places PowerShell before REST API, and there are no Linux-specific instructions or examples. Throughout the page, there is no reference to Linux tools or cross-platform command-line usage, and the only scripting example provided is for PowerShell, which is primarily a Windows tool (although it is available cross-platform).
Recommendations
- Add Azure CLI (az) examples for blueprint creation and management, and link to them alongside PowerShell and REST API.
- Explicitly mention that PowerShell is available cross-platform, but also provide Bash or shell script equivalents for common tasks.
- Reorder the 'Next steps' section to present cross-platform tools (e.g., Portal, Azure CLI, REST API) before or alongside PowerShell.
- Include a note or section on how Linux users can interact with Azure Blueprints, especially for automation and scripting.
- Ensure that future documentation updates provide parity between Windows and Linux tooling and examples.
Governance
Understand the deployment sequence order
...les/governance/blueprints/concepts/sequencing-order.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page displays a mild Windows bias by referencing PowerShell as the primary CLI tool for creating blueprint artifacts and mentioning it before REST API alternatives. There are no Linux shell (bash, Azure CLI) examples or references, and the only command-line tool mentioned is PowerShell, which is more commonly used on Windows. JSON examples are platform-neutral, but the guidance for artifact creation is Windows-centric.
Recommendations
- Add equivalent Azure CLI (az blueprint) or bash examples for artifact creation and management.
- Mention Azure CLI and REST API as alternatives to PowerShell, and provide links to their documentation.
- Present cross-platform tools in parallel or in a neutral order, rather than listing PowerShell first.
- Clarify that blueprint artifact creation can be performed from any OS using REST API or Azure CLI, not just PowerShell.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Blueprints functions shows evidence of Windows bias, primarily through references to Azure PowerShell as a management tool and the absence of Linux-specific CLI examples or mentions. The management context is described as 'Azure PowerShell or REST API,' with no mention of Azure CLI, which is cross-platform and preferred by many Linux users. There are no examples or instructions using Linux-native tools or shell environments, and PowerShell is referenced before REST API, reinforcing a Windows-first perspective.
Recommendations
- Include Azure CLI examples alongside or instead of Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that all functions and management operations can be performed from Linux, macOS, and Windows, not just Windows environments.
- Provide sample commands or usage patterns for Linux shell environments (e.g., Bash), especially for Blueprint management tasks.
- Avoid listing PowerShell before REST API or CLI unless there is a technical reason; strive for tool parity in documentation ordering.
- Add a section or note clarifying tool compatibility and platform support for managing Azure Blueprints.
Governance
Australian Government ISM PROTECTED blueprint sample controls
...ce/blueprints/samples/ism-protected/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas. Many control mappings and audit recommendations specifically reference Windows VMs, Windows web servers, or Windows-only tools (e.g., Microsoft IaaSAntimalware extension), often without equivalent Linux examples or guidance. In several controls, only Windows audit steps are described, while Linux systems are mentioned less frequently or omitted entirely. Windows-specific terminology and tooling are used more prominently than Linux alternatives.
Recommendations
- For every control that references auditing or deploying prerequisites on Windows VMs or web servers, add equivalent instructions and examples for Linux VMs and web servers.
- Where Windows-specific tools (e.g., Microsoft IaaSAntimalware extension) are mentioned, include Linux-compatible alternatives (e.g., instructions for deploying ClamAV or other supported antimalware solutions on Linux VMs).
- Ensure that endpoint protection, vulnerability assessment, and secure communication controls provide parity between Windows and Linux, including explicit mention of supported Linux extensions and configurations.
- When referencing audit results or configuration checks (e.g., Administrators group membership, account policies), provide Linux equivalents (e.g., sudoers file, passwd/shadow file checks) and describe how to implement these audits on Linux systems.
- Review the order and prominence of Windows vs. Linux examples to avoid presenting Windows as the default or primary platform.
- Where controls are applicable to both Windows and Linux, use inclusive language and provide parallel examples for both platforms.
Governance
ISO 27001 ASE/SQL workload blueprint sample controls
...s/samples/iso27001-ase-sql-workload/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the password management and audit controls, where only Windows VM password policies are explicitly listed and audited (e.g., password complexity, age, length, reuse), while equivalent Linux password management controls (such as PAM configuration, shadow file settings, etc.) are not mentioned. Additionally, Windows VM audit results are detailed, but Linux VM examples are limited to password file permissions and accounts without passwords, omitting broader Linux security controls. Windows-specific terminology and controls are presented before or instead of Linux equivalents.
Recommendations
- Add equivalent Linux VM password management controls and audit policies, such as minimum password length, complexity, age, and reuse restrictions using PAM or shadow file settings.
- Provide Linux-specific examples and audit results for password management, not just file permissions or accounts without passwords.
- Ensure that both Windows and Linux controls are presented in parallel, with equal detail and prominence.
- Include references to Linux security tools and configuration patterns (e.g., auditd, PAM, chage, passwd) where relevant.
- Review all sections for parity in examples, terminology, and actionable guidance for both Windows and Linux environments.
Governance
Canada Federal PBMM blueprint sample
...s/governance/blueprints/samples/canada-federal-pbmm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples and parameters for both Windows and Linux VMs, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are described in detail, while equivalent Linux concepts (such as sudoers or admin groups) are not mentioned. Windows VM parameters and patterns are listed before Linux ones in the artifact parameters table, and there is no guidance or example for managing Linux VM administrative users or groups. Additionally, the documentation refers to Windows-specific groups and patterns without Linux parity.
Recommendations
- Add equivalent Linux administrative group/user management parameters and examples, such as specifying sudoers or wheel group members for Linux VMs.
- Ensure Linux VM examples and patterns are described with the same level of detail as Windows VM examples.
- Present Linux and Windows examples in parallel, rather than listing Windows first or exclusively.
- Include references to Linux tools and management patterns where Windows tools/groups are mentioned.
- Clarify any differences in artifact deployment or configuration for Linux VMs, especially for audit and administrative controls.
Governance
Deploy Australian Government ISM PROTECTED blueprint sample
.../governance/blueprints/samples/ism-protected/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific parameters (such as users included/excluded from Windows VM Administrators group and deployment of Microsoft IaaSAntimalware extension on Windows servers) are listed before or more prominently than Linux equivalents. There are several Windows-specific artifact parameters, but Linux equivalents are present for some (e.g., Log Analytics Agent deployment for both Windows and Linux VMs/VMSS). However, examples and explanations for Linux-specific settings are less detailed, and there are no explicit Linux command-line or configuration examples. The documentation does not provide parity in examples or explanations for Linux systems, and Windows terminology appears more frequently and with more detail.
Recommendations
- Ensure Linux-specific artifact parameters are described with equal detail and clarity as Windows ones.
- Provide explicit examples or guidance for Linux VM configuration, such as user/group management or security settings, similar to the Windows Administrators group examples.
- Include references to Linux tools or patterns (e.g., SSH, sudoers, Linux security extensions) where relevant.
- Balance the order of presentation so that Linux and Windows artifacts are listed together or alternately, rather than Windows first.
- Add sample commands or configuration snippets for Linux environments, not just Windows-centric settings.
Governance
ISO 27001 Shared Services blueprint sample controls
.../blueprints/samples/iso27001-shared/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. Password management and complexity controls are described and enforced only for Windows VMs, with no equivalent Linux examples or controls. Windows VM password policies are listed in detail, while Linux VM password and authentication controls are only briefly mentioned in the context of password file permissions and accounts without passwords. There are no examples or policy mappings for enforcing password complexity, aging, or reuse restrictions on Linux VMs. Windows terminology and tools (e.g., Windows VMs, password complexity settings) are used exclusively or before Linux equivalents, and Linux-specific security controls are underrepresented.
Recommendations
- Add equivalent Linux VM password complexity, aging, and reuse audit policies and examples.
- Provide parity in documentation for both Windows and Linux VM security controls, including explicit mention of Linux tools (e.g., PAM, passwd, chage) and configuration patterns.
- Where controls are OS-specific, clearly indicate this and provide guidance for both platforms.
- Ensure that examples and policy definitions are provided for Linux VMs wherever they are given for Windows VMs.
- Consider including cross-platform security recommendations and mapping tables for both Windows and Linux environments.
Governance
SWIFT CSP-CSCF v2020 blueprint sample controls
...nance/blueprints/samples/swift-2020/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Several control mappings and policy definitions reference Windows-specific features, tools, or audit scenarios (e.g., Windows VM Administrators group, password policies, antimalware extension, secure communication protocols for Windows web servers) without equivalent detail or examples for Linux systems. In some sections, Windows controls are listed before Linux ones, and some controls (e.g., password complexity, antimalware) are only described for Windows. Linux is referenced in some audit controls, but not as consistently or with the same depth as Windows.
Recommendations
- Ensure all Windows-specific audit and deployment examples have Linux equivalents, especially for password policies, domain join status, and antimalware solutions.
- Present Linux and Windows controls in parallel, rather than listing Windows controls first or exclusively.
- Include references to Linux-native tools and security patterns (e.g., auditd, fail2ban, Linux password complexity settings) where applicable.
- Expand documentation for Linux VM security controls to match the detail given for Windows (e.g., describe how to audit and enforce password complexity, minimum/maximum password age, and account management on Linux VMs).
- Where only Windows examples are given (e.g., secure communication protocols for web servers), add Linux web server equivalents (e.g., Apache, Nginx TLS configuration).
- For endpoint protection, mention and provide guidance for Linux-compatible antimalware solutions.