IAM & access-policy verification
"Parses fine, production disagrees" is the everyday IAM experience, wildcard escalations and privilege widening are rule-shaped.
Access policies are the purest example of “parses fine, production disagrees”: a wildcard in the wrong place is valid JSON and a full-account escalation. Planned: rules over IAM and access-policy documents for privilege widening, wildcard actions and resources, and trust-policy changes, held to the same fixtures-both-directions bar as everything else.
Want this built sooner?
What gets built next bends toward what connected teams actually need, tell us.