Repository navigation
feat(security): enforce the privileged RBAC policy with exact-identity exclusions - #3791
Conversation
…y exclusions Switch audit-privileged-rbac to Enforce on its rule, so a Role or ClusterRole granting wildcard administration, bind/escalate or impersonation is refused at admission, including grants a chart renders in-cluster. The reviewed objects that need such grants are excluded by exact identity: ClusterRoles by name, Roles by namespace and name. Drop the scored=false annotation so rejections report as fail. The gate pins the exclusion list and forbids selectors or userInfo exemptions, and new fixtures prove an excluded name does not exempt a lookalike name, another namespace, or another kind. Part of #3486. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
What was exercised at
|
The gate only rejected the exclusion keys it named, so single-field edits weakened Enforce and still passed: an exclusion with empty names (any Role in a namespace), failureActionOverrides back to Audit, admission disabled, CREATE-only matching, or a label precondition. Check the exact key set of the spec, rule, match, validate and CEL levels instead, and require literal names and exactly one namespace per Role exclusion. Also document where the excluded names come from and what a refused chart role does to its Flux Kustomization, list kube-node-lease among the filtered namespaces, and note that the apply census, not the skip rows, proves exclusion. Part of #3486. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai review |
|
|
|
Warning Review limit reachedNext included review available in 10 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
CodeRabbit refused this round at |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Swish! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Readiness at
|
Why
Nothing stopped an installed Helm chart from granting itself cluster-admin-equivalent permissions. The privileged-RBAC policy only reported such grants, and CI cannot see what a chart renders in-cluster. Now that reporting coverage is complete and every current holder has been reviewed, the policy can block new grants.
What
Part of #3486
🤖 Generated with Claude Code