docs(cloud-security): document the AWS iam_boundaries provider-test check - #332
Draft
maximelb wants to merge 1 commit into
Draft
docs(cloud-security): document the AWS iam_boundaries provider-test check#332maximelb wants to merge 1 commit into
maximelb wants to merge 1 commit into
Conversation
…heck The AWS provider test now probes iam:GetAccountAuthorizationDetails, the read that reports IAM permission boundaries. It is optional and covered by SecurityAudit's iam:Get*, so a role built the documented way passes; the check exists for hand-rolled least-privilege policies, where a missing boundary read silently over-reports capped principals as administrators. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y3AnxeGmcGA9scrsRZFtg9
lcbill
approved these changes
Aug 2, 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 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.
What was asked
The AWS provider test gained an optional
iam_boundariescheck (IAM permission boundary collection, parity package C2). The verify-and-coverage table on the AWS provider-setup page should list it, like every other probe.What was done
One row in
docs/cloud-security/provider-setup/aws.md, stating what is lost if the check fails: a principal whose permissions boundary caps it below its attached policies is scored on the uncapped policies, so it can be reported as an administrator when it is not.The check is optional and needs no policy change —
iam:GetAccountAuthorizationDetailsis covered byiam:Get*inSecurityAudit, which the page already tells operators to attach, so a role built the documented way passes. The row exists for operators who attach a hand-rolled least-privilege policy instead; the "WithSecurityAudit+ViewOnlyAccess, every optional surface above also passes" line below the table remains true and is unchanged.Testing
Markdown only.
Note
The
org_policiescheck (parity package C1) is also missing from this table; it belongs to that package's own docs change and is deliberately left alone here to avoid two PRs editing the same rows.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y3AnxeGmcGA9scrsRZFtg9