[compiler-threat-spec] docs: extend CTR-004 mapping for enclave GitHub proxy trust surface - #56521
Merged
pelikhan merged 1 commit intoAug 28, 2026
Conversation
Daily compiler threat spec optimizer review. Documents the already- implemented enclave GitHub proxy network-isolation precondition, version gating, read-only operation allowlist, and credential scoping (pkg/workflow/enclaves.go, pkg/workflow/enclave_github_proxy.go) under the existing CTR-004 Sandbox Bypass Configuration rule. No new threat class identified; mapping-only update to Section 2 and Section 7.1. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Collaborator
|
@copilot This PR has been quiet since creation. Please refresh the branch if needed, verify checks, and run the
|
Contributor
Ran the
Nothing else is actionable from the agent side — this PR needs a maintainer to approve the pending workflow runs before it can be merged. |
pelikhan
deleted the
spec/enclave-ctr004-mapping-audit-2026-08-28-841bdfcf79079378
branch
August 28, 2026 10:39
Contributor
Author
|
🎉 This pull request is included in a new release. Release: |
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.
Summary
This PR is a documentation-only update to
specs/compiler-threat-detection-spec.md, bumping the spec version from 1.0.27 to 1.0.28. It extends the CTR-004 Sandbox Bypass Configuration mapping table to document the enclave GitHub proxy trust surface (pkg/workflow/enclaves.go,pkg/workflow/enclave_github_proxy.go), which was already implemented and tested but had not previously been reflected in the Section 7.1 mapping table. No compiler behavior changes.Change Classification
Key Changes
specs/compiler-threat-detection-spec.mdv0.87.4); extended CTR-004 mapping row withenclaves.go/enclave_github_proxy.goand their tests; added 1.0.28 changelog entryImpact Assessment
.lock.ymlchanges — purely a mapping/documentation update.enclaves[].agent.github.cli: issues-read-v1proxy: AWF network-isolation precondition, AWF/MCPG minimum version gating, a fixed read-only operation allowlist (issues.comments.list,issues.get,issues.list), exclusion ofGITHUB_TOKENfrom the credential fallback chain, and repository count/sensitivity limits.CTR-*threat rule introduced; existing CTR-004/CTR-017 coverage is confirmed sufficient.Commits