Repository navigation
entitlement-problems: three access designs that leak a privilege through composition - #4
Merged
1 commit merged intoOct 3, 2026
Merged
1 commit merged into
1 commit merged into
Conversation
…ugh composition separation-of-duties: a toxic-combination table checked by group name, and a role added later that approves; two grants, neither listed, make a conflict. scp-escalation: moving prod into an OU built from the sandbox template; compare reports the CloudTrail guardrail and the security team's audit read LOST. joiner-mover-leaver: group-based offboarding and the direct permission set it cannot see; a trap, not a delay. Writing it, writ found a second bug in the first draft of the safe plan (approve, leave, provision) and the README keeps it. Each failing property names a (show …) query, and each .rules file prints the privilege path. Cross-check 31 -> 41 properties (never: 3 -> 7); 257 checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 3, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Adds
entitlement-problems/: three access-control designs, each a safe model and a shortcut asked the same.claims. This is the IAM prototype the recommendations ask for first.separation-of-duties/alice-joins-requesters,alice-also-joins-finance-leads;a = alice;derive conflictgives the two groupsscp-escalation/compare:dev-can-deploypreserved,dev-never-edits-cloudtrailLOST,sec-can-always-auditLOST;derive escalationgivesdev power prod-acct workloadsjoiner-mover-leaver/prod-admin(assigned directly) after 4 steps, and nothing left in the plan can remove itEach failing property names a
(show …)query, so the verdict says who is affected. Each.rulesfile prints the privilege path as a table.While I was writing joiner-mover-leaver, writ found a bug in the first draft of the safe plan: approve → leave → provision. The README for that problem tells the story, and both files carry the fix.
Notes
comparereports properties LOST for all three pairs. The plan assumed otherwise. It also reports a violated equation aspreserved, because laws are compared by declaration;entitlement-problems/README.mdsays so.never3 → 7). It only runs the safe models. I randeriveagainst each shortcut by hand and the counts matchedwrit check, but no test asserts that../run-tests.sh all: 257 checks, 0 failed (222 before). The new tests and the cross-check also come out green in Docker (writ:latest, built from the v0.3.0 tag commit).🤖 Generated with Claude Code