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 226-250 of 380 flagged pages
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-session-management.md
...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/configuration examples are for Windows/.NET environments, with no mention of Linux, cross-platform, or open-source alternatives. There are no examples for Linux-based web servers, identity providers, or session management tools, and Windows tools and patterns are presented exclusively and first.
Recommendations
- Include equivalent examples for Linux-based web servers (e.g., Apache, Nginx) and frameworks (e.g., Node.js/Express, Django, Flask) for session and cookie management.
- Provide configuration and code samples for cross-platform identity providers (e.g., Keycloak, Auth0) and logout/session management in non-Windows environments.
- When referencing tools like PowerShell or web.config, also mention and provide examples for Linux/Unix equivalents (e.g., Bash scripts, environment variables, config files in YAML/JSON).
- Add guidance for securing cookies and sessions in non-.NET stacks (e.g., using Set-Cookie headers in Nginx/Apache, middleware in Express/Django).
- Present cross-platform or Linux-first examples alongside or before Windows-specific ones to ensure parity and inclusiveness.
Create Pull Request
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73007291.md
...rity/develop/threat-modeling-tool-releases-73007291.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide Linux installation or usage guidance. All examples and troubleshooting steps assume a Windows environment.
Recommendations
- Clearly state in the introduction if the tool is Windows-only, or provide information about cross-platform support if available.
- If Linux or macOS versions are not supported, explicitly mention this in the system requirements section.
- If any workarounds or alternatives exist for Linux users (e.g., running via Wine, using alternative tools), provide guidance.
- If future cross-platform support is planned, note this and provide a way for users to track progress or provide feedback.
- Ensure that troubleshooting and installation instructions consider non-Windows environments, or clarify their exclusivity.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73306305.md
...rity/develop/threat-modeling-tool-releases-73306305.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric: only Windows is listed as a supported OS, all installation and troubleshooting steps reference Windows-specific tools and patterns (e.g., ClickOnce, Windows Menu shortcuts), and there are no mentions of Linux or cross-platform support. No Linux installation instructions, troubleshooting, or requirements are provided.
Recommendations
- Explicitly state if the tool is Windows-only, or provide information about Linux/macOS support (or lack thereof).
- If possible, add Linux/macOS installation instructions or workarounds, or clarify that the tool is not supported on those platforms.
- Include troubleshooting steps relevant to non-Windows environments, or state their absence.
- Mention any alternative tools or approaches for Linux/macOS users if the tool is not available for those platforms.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-getting-started.md
...curity/develop/threat-modeling-tool-getting-started.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes the Microsoft Threat Modeling Tool, which is a Windows-only application, without mentioning Linux or cross-platform alternatives. All workflows, screenshots, and sharing mechanisms (e.g., OneDrive) are Windows-centric, and there is no discussion of Linux support, installation, or equivalent tools. The documentation implicitly assumes a Windows environment, omitting any guidance for Linux users.
Recommendations
- Explicitly state the platform support for the Threat Modeling Tool at the beginning of the documentation, including whether Linux or macOS are supported or not.
- If the tool is Windows-only, suggest cross-platform or Linux-native alternatives (such as OWASP Threat Dragon or other open-source threat modeling tools) for non-Windows users.
- Provide guidance on running the tool in a Linux environment if possible (e.g., via Wine or virtualization), or clarify that such options are unsupported.
- Include examples of file sharing and collaboration that are not tied to Windows-specific services like OneDrive (e.g., using generic cloud storage or Git repositories).
- Ensure that any future documentation or updates consider and address the needs of Linux and macOS users where feasible.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73007142.md
...rity/develop/threat-modeling-tool-releases-73007142.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively lists Windows 10 as the supported operating system, with no mention of Linux or macOS support or alternatives. All requirements and download instructions are Windows-centric, and there are no examples or guidance for Linux users.
Recommendations
- Clearly state whether Linux and macOS are supported or not. If not, provide reasoning or roadmap information.
- If cross-platform support is possible (e.g., via Mono, Wine, or a web version), include instructions or references for Linux users.
- Add a section addressing common questions from non-Windows users, including workarounds or alternatives.
- Ensure that future documentation includes parity in examples, requirements, and troubleshooting for all major platforms.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases.md
...cles/security/develop/threat-modeling-tool-releases.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows as the supported operating system, with no mention of Linux or macOS support or alternatives. All system requirements and download instructions are Windows-specific, and there are no examples or guidance for users on other platforms.
Recommendations
- Clearly state if the tool is Windows-only, and if so, suggest any workarounds (e.g., running via Wine or in a VM) for Linux users.
- If possible, provide information about equivalent tools or approaches for Linux users.
- Add a section addressing cross-platform availability and explicitly mention the lack of Linux/macOS support to set user expectations.
- If future support for Linux or macOS is planned, mention it in the documentation.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-configuration-management.md
...velop/threat-modeling-tool-configuration-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias throughout. Most configuration and code examples are specific to Windows technologies (e.g., ASP.NET, IIS, web.config, BitLocker, Windows Firewall, WCF), with no equivalent Linux or cross-platform instructions. Windows tools and patterns (e.g., BitLocker, Windows Firewall, web.config, IIS) are mentioned exclusively or before any alternatives. There are no Linux or open-source equivalents provided for key security practices, and the documentation assumes a Windows-centric environment.
Recommendations
- Provide equivalent Linux/Unix examples for configuration management, such as using iptables/ufw for firewalls, and SELinux/AppArmor for endpoint security.
- Include examples for configuring HTTP headers (e.g., X-Frame-Options, X-Content-Type-Options, CORS) in popular Linux web servers like Apache and Nginx, not just IIS/web.config.
- Mention and provide examples for Linux disk encryption tools (e.g., LUKS, dm-crypt) alongside BitLocker.
- Reference cross-platform or open-source frameworks (e.g., Node.js, Python Flask/Django, Java Spring) in addition to ASP.NET and WCF.
- When discussing IoT, include Linux-based IoT OSes (e.g., Raspbian, Ubuntu Core) and their security features.
- For database firewall configuration, provide Linux-based guidance (e.g., configuring firewalld, iptables, or cloud provider firewalls) in addition to Windows Firewall.
- Balance references and examples so that Linux/open-source users are not excluded or forced to translate Windows-centric instructions.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73309251.md
...rity/develop/threat-modeling-tool-releases-73309251.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide any Linux-specific guidance or alternatives. All examples and troubleshooting steps assume a Windows environment.
Recommendations
- Clarify in the introduction that the tool is Windows-only, if that is the case, to set user expectations.
- If Linux or cross-platform support is planned or possible (e.g., via Wine or .NET Core), provide explicit instructions or guidance for Linux users.
- Include troubleshooting steps or known limitations for non-Windows users, or direct them to alternative tools if the Threat Modeling Tool is not supported.
- Where possible, avoid Windows-specific terminology (like 'Windows Menu') or provide Linux/macOS equivalents or notes about their absence.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/secure-design.md
...s/blob/main/articles/security/develop/secure-design.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows and Microsoft-centric bias by referencing Windows-specific security development lifecycles, tools, and authentication mechanisms without providing Linux or cross-platform equivalents. Examples and tool recommendations are almost exclusively Microsoft/Azure-focused, and there are no Linux-specific or cross-platform command-line examples, tools, or patterns mentioned. The documentation assumes the use of Microsoft identity and security platforms, and references to PowerShell and Windows security models are implicit in the context of Azure management.
Recommendations
- Include Linux and cross-platform security tooling and patterns alongside Microsoft/Azure tools (e.g., mention open-source alternatives for threat modeling, key management, and logging).
- Provide explicit Linux command-line examples (e.g., using Bash, CLI tools) where management or configuration is discussed, especially for Azure services.
- Reference cross-platform authentication and identity solutions (such as OAuth2, SAML, or open-source identity providers) in addition to Microsoft Entra ID.
- When discussing SDKs, frameworks, and development environments, highlight popular Linux-compatible options (e.g., VS Code, JetBrains IDEs, CLI-based workflows) and not just Microsoft-centric tools.
- Balance references to Windows-specific security models (like the Security Development Lifecycle) with mentions of widely adopted, platform-agnostic security frameworks (e.g., NIST, CIS Benchmarks, OWASP SAMM).
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-auditing-and-logging.md
...y/develop/threat-modeling-tool-auditing-and-logging.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments. It references Windows-specific tools and concepts (such as Windows ACLs and WCF/.NET configuration), and provides configuration examples only for Windows-centric technologies. There are no Linux-specific examples, tools, or commands, and generic guidance does not include parity for Linux environments or mention of common Linux logging/auditing practices.
Recommendations
- For sections discussing file permissions (e.g., 'Ensure that Audit and Log Files have Restricted Access'), provide equivalent Linux/Unix guidance, such as using chmod, chown, and setfacl, with example commands.
- When referencing Windows-specific technologies (e.g., WCF, .NET Framework), include parallel examples or notes for cross-platform alternatives (such as gRPC, REST APIs, or logging frameworks like Serilog, NLog, or syslog for Linux).
- For log rotation, mention and provide examples for Linux tools like logrotate, and discuss separation of logs using Linux filesystem permissions and mount options.
- Where Windows ACLs are discussed, add a section or note on Linux file permissions and access control lists (ACLs).
- Include references to Linux-native logging/auditing tools (e.g., auditd, rsyslog, journald) and how to configure them for security auditing.
- Ensure that all code/configuration examples have Linux equivalents or at least acknowledge differences and provide links to relevant Linux documentation.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-communication-security.md
...develop/threat-modeling-tool-communication-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias: examples and recommendations are almost exclusively focused on Windows-centric technologies (e.g., ASP.NET, WCF, ADO.NET, SQL Server Management Studio, web.config, ServicePointManager, SMB 3.x for Windows clients). There are no Linux-specific examples or equivalent Linux tooling mentioned, and the only code samples are in C#/.NET. Instructions for enforcing HTTPS, certificate pinning, and secure configuration are all tailored to Windows environments, with no parity for Linux or cross-platform scenarios.
Recommendations
- Provide Linux-specific examples and instructions for each mitigation, such as using Nginx/Apache for HTTPS enforcement, OpenSSL for certificate validation, and Linux SMB clients (e.g., smbclient, mount.cifs) for Azure Files.
- Include code samples in other cross-platform languages (e.g., Python, Java, Node.js) and show how to implement security features on Linux.
- Mention Linux tools (e.g., sqlcmd for SQL Server, curl/wget for HTTP requests, systemd for service accounts) alongside or before Windows tools.
- For configuration examples (e.g., URL Rewrite), provide equivalent Nginx/Apache configuration snippets.
- When referencing service accounts and least-privilege, include Linux best practices (e.g., using dedicated system users, systemd service files).
- Update references and links to include Linux documentation and community resources.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-authentication.md
...ecurity/develop/threat-modeling-tool-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-based authentication mechanisms (e.g., Windows Authentication, Kerberos, ADFS), referencing Windows-specific tools (e.g., Windows Server certificate service, MakeCert.exe, MSMQ), and providing configuration/code examples that are either Windows-centric or lack Linux/Unix equivalents. There is a notable absence of Linux-specific authentication guidance, tools, or example configurations, especially in areas like SQL Server authentication, certificate management, and WCF/MSMQ integration.
Recommendations
- For every Windows-specific authentication mechanism or tool mentioned (e.g., Windows Authentication, Kerberos, MakeCert.exe), provide Linux/Unix alternatives (e.g., GSSAPI, OpenSSL, MIT Kerberos, Linux certificate authorities).
- Include Linux-focused examples for SQL Server authentication (e.g., using Kerberos from Linux clients, configuring SQL authentication on Linux).
- When discussing certificate management, reference cross-platform tools like OpenSSL and explain how to generate and manage certificates on Linux.
- For messaging and queueing (e.g., MSMQ), mention cross-platform alternatives (e.g., RabbitMQ, Apache Kafka) and provide authentication guidance for those.
- Balance the order of presentation: do not always list Windows-based mechanisms first; alternate or group by platform.
- Where code/configuration examples are given (e.g., WCF, MSMQ), either provide Linux/Mono equivalents or clarify platform limitations.
- Explicitly state platform support and differences for each authentication method, especially where Windows-only features are discussed.
- Reference Linux/Unix documentation and official guides alongside Microsoft/Windows references.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/secure-develop.md
.../blob/main/articles/security/develop/secure-develop.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 tools (e.g., Visual Studio, Microsoft Antimalware, Microsoft Defender Antivirus in Windows, Attack Surface Analyzer), linking to Windows-centric resources, and omitting Linux or cross-platform alternatives for several security practices. Linux tools and workflows are not mentioned, and examples or guidance are not provided for non-Windows environments.
Recommendations
- Include Linux and cross-platform alternatives for all referenced tools (e.g., suggest VS Code, JetBrains IDEs, or command-line git for code reviews; ClamAV or Sophos for antimalware; Lynis or OpenSCAP for system security scanning).
- When mentioning Windows tools, also mention equivalent Linux tools in the same context, and avoid presenting Windows tools first unless they are truly cross-platform.
- Provide examples or links for performing tasks (such as removing server headers, performing static code analysis, or running security verification tests) on Linux-based Azure environments.
- Reference documentation or blog posts that address security best practices for Linux-based Azure deployments.
- Ensure that all security recommendations are accompanied by platform-agnostic guidance or parallel instructions for both Windows and Linux environments.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-authorization.md
...security/develop/threat-modeling-tool-authorization.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows/Microsoft-centric bias by focusing on Microsoft technologies (e.g., WCF, ASP.NET, Azure, SQL Server) and referencing Windows-specific concepts (such as Windows roles/groups and configuration files like machine.config/app.config). There are no Linux/Unix-specific examples, tools, or patterns provided, and the only references to OS-level security (e.g., ACLs, user-profile directories) are generic without cross-platform command or configuration examples. The WCF and ASP.NET sections are inherently Windows/.NET focused, and the only concrete code/configuration examples are for Microsoft stacks. There is no mention of Linux equivalents (e.g., file permissions, sudoers, systemd, Linux ACLs), nor are there examples for open-source stacks or cross-platform approaches.
Recommendations
- Provide parallel examples for Linux environments, such as using chmod/chown, setfacl, or editing /etc/sudoers for least privilege.
- When discussing user-profile directories or ACLs, include both Windows (e.g., C:\Users\) and Linux (e.g., /home/username) paths and commands.
- For database access control, mention open-source databases (e.g., PostgreSQL, MySQL) and their security models alongside SQL Server.
- When referencing configuration files (e.g., machine.config, app.config), note Linux/Unix equivalents or approaches (e.g., environment variables, systemd unit files).
- Include examples for cross-platform frameworks (e.g., Node.js, Python Flask/Django) and their authorization mechanisms.
- Where possible, use neutral language and provide both Windows and Linux command-line or scripting examples (e.g., PowerShell and Bash).
- Reference open standards and tools (e.g., OAuth2, RBAC in Kubernetes, Linux PAM) in addition to Microsoft-specific solutions.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-exception-management.md
...y/develop/threat-modeling-tool-exception-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by focusing exclusively on Windows-centric technologies (WCF, ASP.NET, IIS), configuration files (web.config, machine.config), and references to Windows tools and settings. All code and configuration examples are for .NET/ASP.NET, with no mention of Linux, cross-platform .NET Core, or equivalent Linux deployment scenarios. Linux-based web servers, deployment patterns, or exception handling in non-Windows environments are not addressed.
Recommendations
- Include examples and guidance for cross-platform .NET (e.g., ASP.NET Core) that can run on Linux, not just Windows-only frameworks.
- Provide equivalent instructions for configuring error handling and deployment on Linux-based web servers (e.g., Nginx, Apache) alongside IIS.
- Mention and demonstrate how to manage configuration and exception handling in Linux environments, including file locations and permissions.
- Reference Linux-compatible deployment methods and tools, such as systemd services, Docker containers, or Azure App Service for Linux.
- Clarify which recommendations are Windows-specific and offer Linux alternatives where possible.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-cryptography.md
.../security/develop/threat-modeling-tool-cryptography.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. Windows-specific technologies, APIs, and tools (such as CNG, CAPI, Win32/64, BitLocker, SSIS, SQL Server, TPM on Windows IoT Core) are mentioned exclusively or before any cross-platform or Linux alternatives. .NET and Windows-centric cryptographic APIs are detailed, while Linux or open-source equivalents are rarely, if ever, mentioned. Example code and references are almost entirely Windows/.NET-focused, and there are no Linux command-line, OpenSSL, or cross-platform examples provided.
Recommendations
- Add Linux and cross-platform examples for cryptographic operations, such as using OpenSSL for key generation, encryption, and random number generation.
- Mention Linux equivalents for Windows tools (e.g., LUKS/dm-crypt for BitLocker, GPG for file encryption, systemd-cryptsetup for device encryption).
- Include code samples in languages and frameworks common on Linux (e.g., Python with cryptography module, Java with BouncyCastle, C/C++ with OpenSSL).
- Reference Linux/Unix APIs and tools (e.g., /dev/random, /dev/urandom, cryptsetup, openssl) alongside Windows APIs.
- Provide guidance for securing cryptographic keys on Linux-based IoT devices (e.g., using hardware security modules, TPM2.0 tools, or secure elements supported on Linux).
- Balance .NET and Windows-specific recommendations with platform-agnostic or Linux-specific best practices.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73002061.md
...rity/develop/threat-modeling-tool-releases-73002061.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows as the supported operating system, with no mention of Linux or macOS compatibility or alternatives. System requirements and download instructions are Windows-specific, and there are no examples or guidance for Linux users.
Recommendations
- Clearly state whether Linux (and macOS) are supported or not. If unsupported, explain the rationale and suggest alternatives for non-Windows users.
- If possible, provide Linux installation instructions or mention any available cross-platform versions.
- Include information about running the tool via compatibility layers (e.g., Wine) if native support is unavailable.
- Ensure future documentation includes parity in examples, requirements, and troubleshooting for all major platforms.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-71604081.md
...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 page exclusively references Windows as the supported operating system and requires the .NET Framework, which is primarily a Windows technology. There are no mentions of Linux or cross-platform support, nor are there any Linux-specific instructions or examples. All system requirements and usage patterns are Windows-centric.
Recommendations
- Explicitly state if the tool is Windows-only, or clarify any plans for Linux or cross-platform support.
- If possible, provide information about running the tool on Linux (e.g., via Wine or .NET Core/Mono) or mention alternatives for Linux users.
- Include Linux system requirements and installation instructions if/when support is available.
- Ensure that documentation examples and screenshots reflect any available cross-platform capabilities.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-71509112.md
...rity/develop/threat-modeling-tool-releases-71509112.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased towards Windows, as the Microsoft Threat Modeling Tool is described as only available for Windows 10, with no mention of Linux or macOS support. All examples, workarounds, and integrations (such as OneDrive) reference Windows-specific tools and workflows. There are no Linux equivalents, installation instructions, or troubleshooting steps provided, and the system requirements list only Windows as a supported OS.
Recommendations
- Clearly state if the tool is Windows-only, and if so, provide information about alternative tools or compatibility options for Linux users.
- If possible, develop and document cross-platform support, or provide guidance for running the tool on Linux (e.g., via Wine or virtualization).
- Include Linux (and macOS, if relevant) installation instructions, troubleshooting, and usage examples if/when support is available.
- Mention file access and integration options for non-Windows platforms, or clarify limitations.
- Consider providing a web-based version or API to enable platform-agnostic usage.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-71601261.md
...rity/develop/threat-modeling-tool-releases-71601261.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on Windows, specifying only Windows 10 as a supported operating system and referencing Windows-specific features and tools. There are no mentions of Linux or cross-platform support, nor are there any Linux-specific instructions, requirements, or troubleshooting steps.
Recommendations
- Explicitly state whether Linux or macOS are supported or unsupported platforms.
- If the tool is Windows-only, provide rationale and suggest alternatives or workarounds for Linux users.
- If cross-platform support is planned, include timelines or beta information.
- Add a section addressing installation and usage on Linux (or clarify lack thereof) to improve transparency.
- Reference any equivalent open-source or cross-platform threat modeling tools for non-Windows users.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73003161.md
...rity/develop/threat-modeling-tool-releases-73003161.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows as the supported operating system, with no mention of Linux or macOS support or equivalents. All system requirements and download instructions are Windows-specific, and there are no examples or guidance for running the tool on non-Windows platforms.
Recommendations
- Clearly state if the tool is Windows-only, and if so, provide information about alternatives or workarounds for Linux users (e.g., running via Wine, using similar open-source tools).
- If cross-platform support is planned or available, include installation and usage instructions for Linux (and macOS) alongside Windows.
- Provide parity in documentation by mentioning Linux equivalents for any Windows-specific requirements or dependencies.
- Consider adding a section addressing cross-platform compatibility or limitations to inform non-Windows users.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73209279.md
...rity/develop/threat-modeling-tool-releases-73209279.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide Linux installation or usage instructions. There are no examples or guidance for non-Windows users, indicating a strong Windows bias.
Recommendations
- Clarify in the system requirements section whether Linux or macOS are supported or not. If not, state this explicitly.
- If Linux support is possible (e.g., via Wine or alternative methods), provide installation and usage instructions for Linux users.
- If the tool is Windows-only, suggest alternative threat modeling tools for Linux users or provide guidance on how to access similar functionality on other platforms.
- Ensure that error messages and troubleshooting steps consider non-Windows environments, or clearly state their applicability.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73308291.md
...rity/develop/threat-modeling-tool-releases-73308291.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows environments, including Windows-specific installation methods (ClickOnce), error messages with Windows-style paths, and instructions to use Windows Menu shortcuts. There is no mention of Linux or cross-platform support, nor are any Linux installation or troubleshooting steps provided.
Recommendations
- Clearly state platform support at the beginning, including whether Linux or macOS are supported or not.
- If Linux is not supported, explicitly mention this to set user expectations.
- If Linux support is planned or available, provide equivalent installation, troubleshooting, and usage instructions for Linux (e.g., command-line installation, desktop integration, error handling).
- Avoid Windows-specific terminology (e.g., 'Windows Menu') without alternatives or clarifications for other platforms.
- Include file path examples in both Windows (\) and Linux (/) formats where relevant.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73211082.md
...rity/develop/threat-modeling-tool-releases-73211082.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide Linux installation or usage instructions. There are no examples or guidance for Linux users, and the system requirements only list Windows.
Recommendations
- Clarify in the introduction that the tool is Windows-only, if that is the case. If Linux support is planned or possible (e.g., via Wine or .NET Core), provide explicit instructions or caveats for Linux users.
- If the tool is not supported on Linux, suggest alternatives or workarounds for Linux users, or link to cross-platform threat modeling tools.
- Where installation patterns are discussed (e.g., ClickOnce, Windows Menu), note their Windows specificity and provide Linux equivalents or state their absence.
- Explicitly state the lack of Linux support in the system requirements section, rather than omitting Linux entirely.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73310263.md
...rity/develop/threat-modeling-tool-releases-73310263.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows operating systems, tools, and installation patterns (e.g., ClickOnce, Windows Menu shortcuts), with no mention of Linux or cross-platform support. All examples and instructions are Windows-specific, and there is no guidance for Linux users or alternatives.
Recommendations
- Clearly state if the tool is Windows-only; if cross-platform support is planned, provide timelines or alternatives.
- If possible, offer Linux installation instructions or workarounds, such as using Wine or a VM.
- Include a section addressing Linux/macOS users, even if only to clarify lack of support and suggest alternatives.
- Avoid assuming the presence of Windows-specific features (e.g., Windows Menu shortcuts) without noting platform limitations.