AZDO.1004: Additional protections when using public package registries.

Not run by Mito today

This check needs a connection to Azure DevOps, which Mito’s assessment does not set up. Mito reports it as skipped.

ID	AZDO.1004
Severity	High
Suite	Mito
Product	Azure DevOps
Feature	Security policies
Security area	Engineering systems
Resource type	Tenant
User impact of fixing	Low
Effort to fix	Low
Framework controls	nist-800-53-r5:SR-3 Supply Chain Controls and Processes
MITRE ATT&CK	T1195.001, T1204.005
Reads from	Azure DevOps
Further reading	https://devblogs.microsoft.com/devops/changes-to-azure-artifact-upstream-behavior/

What this checks and how to fix it

Externally sourced package versions should be manually approved for internal use to prevent malicious packages from a public registry being inadvertently consumed.

Rationale: Previously, Azure Artifacts feeds presented package versions from all of its upstream sources. This includes package versions that were originally pushed to an Azure Artifacts feed (internally sourced) and package versions from common public repositories like npmjs.com, NuGet.org, Maven Central, and PyPI (externally sourced).

Configure a policy for additional security for your private feeds by limiting access to externally sourced packages when internally sourced packages are already present. This change provides a new layer of protection and prevents malicious packages from a public registry being inadvertently consumed. It does not affect any package versions that are already in use or cached in your feed.

Remediation action:

Enable the policy to opt-in for additional protective behavior.

1. Sign in to your organization.
2. Choose Organization settings.
3. Select policies under the security section
4. In the security policies section, toggle on ‘Additional protections when using public package registries’

Results: The security behavior applies: when an internally sourced version is already in your feed, or when consuming a package from your feed for the first time (i.e. it is not yet in your feed), and at least one of the versions available from an upstream is internally sourced. With the new behavior, any versions from the public registry will be blocked and not made available to download. You are able to configure the upstream behavior to allow externally sourced package versions if you choose to.

Related links

• Microsoft Devblogs - Changes to Azure Artifacts Upstream Behavior

---

Mito check. Author: SebastianClaesson. Open-source licences.