Before you start
- Use a disposable resource in a test project, subscription or namespace. Keep a separate administrator who can restore the test assignment.
- Record the exact identity, resource and action. Use a read action with a predictable result, such as listing resources in a known test project.
Data and access
Google Cloud
In Policy Troubleshooter, enter the principal, resource and IAM permission for the test action. Check where the role is granted and whether a conditional or inherited policy applies. For a removal check, remove only the disposable grant at the level that owns it. Direct policy edits typically propagate in about two minutes and can take seven minutes or longer. Group membership changes can take longer.
Check. The troubleshooter shows the identity and permission you entered and where any matching allow or deny comes from.
Microsoft Azure
On the resource, open Access control (IAM), then Check access. Select the test identity and review assignments at the resource and any inherited scope. If you remove the disposable assignment, repeat the check and get a fresh session for the test identity. Microsoft lists up to ten minutes for typical role assignment changes.
Check. Check access identifies direct and inherited assignments for the same identity and resource. After removal, compare with a fresh request after propagation.
Kubernetes
Confirm the cluster context, identity and namespace. From the test identity's context, run the authorization check with your test namespace. Inspect its RoleBindings and any ClusterRoleBindings that apply. Remove only the disposable RoleBinding, then repeat the same authorization check.
kubectl auth can-i get configmaps --namespace access-rehearsalCheck. Record the API authorization answer for the same verb, resource and namespace before and after removing the test RoleBinding.
OpenStack
Use openstack role assignment list with the test user, project and the effective option to see effective assignments. Check direct, group and inherited assignments before touching a role. If an administrator removes a disposable assignment, get a fresh project-scoped session and repeat the same read action. A different role may still grant it under that service's policy.
Check. The assignment output identifies the user and project. Check the result of the same service read with a fresh project-scoped session.
Hetzner Cloud
Open the test project, then Security and API tokens. Choose Read for a disposable token and use it to list servers in that project. Read tokens allow GET requests. Record the project and permission level and keep the token itself private. Console membership and API token permissions are separate checks.
Check. The test request lists servers for the selected project, and the token details show Read.
Record the result
Keep the allowed result and the grant or token scope that explains it. If you removed a test assignment, repeat the same action once the change has propagated and record the resulting denial or the remaining grant. Confirm that the separate administrator can still reach the test resource.
Check. Keep the actual allow or deny result, the role or scope that explains it, and the separate administrator’s access check.
Check your result
The test identity, resource and operation are the same in each result. Record the actual response and any remaining path that grants access.
If you get stuck
The test identity still has access
Check that the request used the intended identity and resource. Look for another assignment through a group, parent scope or cluster role. Check the provider's propagation guidance and use a fresh test session before reporting that removal failed.