Limit variables that can be set at queue time
AZDO.1015 is in Maester 3.0.0-preview and not in the stable 2.3.0 release yet. It will be in the next stable release. To use it now, install the preview:
Install-Module Maester -AllowPrerelease -ForceHow to get the preview, and go backUse the preview in GitHub Actions
Part of Maester · Azure DevOps · Pipelines · All checks
Invoke-Maester -TestId AZDO.1015Overview
Section titled “Overview”User-defined variables should not be able to override system variables or variables not defined by the pipeline author.
Rationale: Only those variables explicitly marked as “Settable at queue time” can be set by user.
Remediation action
Section titled “Remediation action”Enable the policy to limit variables that can be set at queue time.
- Sign in to your organization.
- Choose Organization settings.
- Under the Pipelines section choose Settings.
- In the General section, toggle on “Limit variables that can be set at queue time”.
Results: Only those variables explicitly marked as “Settable at queue time” can be set at queue time.
Related links
Section titled “Related links”Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | AZDO.1015 |
| Severity | High |
| Suite | Maester |
| Product | Azure DevOps |
| Feature | Pipelines |
| Area | Engineering systems |
| Resource type | Tenant |
| User impact | Low |
| Implementation cost | Low |
| MITRE ATT&CK | T1677 Poisoned Pipeline Execution |
| Supports controls | nist-800-53-r5:SI-10 |
| PowerShell test | Test-AzdoOrganizationLimitVariablesAtQueueTime |
| Services | AzureDevOps |
| Learn more | https://learn.microsoft.com/azure/devops/pipelines/security/inputs?view=azure-devops#limit-variables-that-can-be-set-at-queue-time |
Source
Section titled “Source”About this check
- Severity
- High
- Effort to fix
- Low
- Impact on users
- Low
- Product
- Azure DevOps
- Feature
- Pipelines
- Area
- Engineering systems
- Suite
- Maester