Onboard compliance pipeline to CFS network isolation - #8600
Open
StellaHuang95 wants to merge 1 commit into
Open
Conversation
Migrate the compliance definition to the official 1ES template, enforce the non-TCB CFSClean policy, and remove the unauthenticated global npm install. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7c06348a-a2e3-48f9-84b6-9eab3d077bd5
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
Contributor
Author
|
/azp run |
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR migrates the repository’s compliance pipeline to the official 1ES pipeline template so the run is governed by 1ES Network Isolation and CFS feed policy, reducing the chance of package restores reaching public registries.
Changes:
- Updated
azure-pipelines-compliance.ymltoextendsv1/1ES.Official.PipelineTemplate.ymland added the 1ES templatesresourcesreference. - Enabled 1ES Network Isolation (
networkIsolationPolicy: Permissive,CFSClean) and removed the globalnpm i -g npm@8step. - Switched artifact publishing to
1ES.PublishBuildArtifacts@1and explicitly resolved in-repo templates via@self.
Show a summary per file
| File | Description |
|---|---|
| azure-pipelines-compliance.yml | Moves the compliance pipeline onto the 1ES official template with Network Isolation enabled, removes global npm install, and aligns artifact publishing with 1ES tasks. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The compliance pipeline was not using the official 1ES pipeline template, so it did not run the Network Isolation start/stop tasks or enforce the CFS package-feed policy. Although the shared restore path already authenticates to Azure Artifacts feeds, the pipeline also performed a global
npminstallation that could bypass the repository.npmrcand contact the public npm registry.Changes
azure-pipelines-compliance.ymltov1/1ES.Official.PipelineTemplate.yml.Permissive,CFSClean.npm i -g npm@8step.@selfunder the external 1ES template.1ES.PublishBuildArtifacts@1for the existing compliance-log artifact.Expected result
Pipeline runs should include the 1ES Network Isolation tasks, restore dependencies through authenticated Azure Artifacts feeds, and prevent package tools from reaching public registries. Post-merge pipeline telemetry will be used to confirm clean policy enforcement and compliance lock-in.
Validation
An Azure DevOps run is required after merge to validate template expansion and Network Isolation telemetry in the hosted environment.