-
Notifications
You must be signed in to change notification settings - Fork 0
fix(guardrails): harden infrastructure agent permissions #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -6,9 +6,15 @@ permission: | |||||||
| "*": allow | ||||||||
| "*.env*": deny | ||||||||
| "*credentials*": deny | ||||||||
| "*.pem": deny | ||||||||
| "*.key": deny | ||||||||
| "*secret*": deny | ||||||||
| grep: | ||||||||
| "*": allow | ||||||||
| "*.env*": deny | ||||||||
|
||||||||
| "*.env*": deny | |
| "*.env*": deny | |
| "*credentials*": deny |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This agent now hard-denies docker push* / docker compose push*, but the guidance text later in the file says to never run docker push without explicit approval. Since deny means it can’t be approved at runtime, update the guidance to reflect that pushes are disallowed for this agent (or change the rule to ask if approval should be possible).
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -7,10 +7,16 @@ permission: | |||||||
| "*.env*": deny | ||||||||
| "*credentials*": deny | ||||||||
| "*.tfvars": deny | ||||||||
| "*.pem": deny | ||||||||
| "*.key": deny | ||||||||
| "*secret*": deny | ||||||||
| grep: | ||||||||
| "*": allow | ||||||||
|
||||||||
| "*": allow | |
| "*": allow | |
| "*credentials*": deny |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
greppermission rules are missing"*credentials*": deny, which is present in thesecurity-engineerbaseline. Without it, this agent can still grep for credential-related patterns and potentially expose secret material in grep output. Add the credentials deny rule to thegrepblock.