Overview
Cloud permissions tend to grow and never shrink: short-term production rights nobody remembered to revoke, or a deployment role given full admin because the right policy felt like too much effort. Using access analysis and audit logs, we compare what every identity is allowed to do with what it actually did over 90 days. We then write tighter policies to replace the overly broad ones. Nothing is cut blindly; we suggest every change, review it with you and only apply what is safe. Your team also gets a repeatable quarterly review.
What you receive
- A full list of users, roles, service accounts and access keys
- Each identity's permissions compared against 90 days of real activity
- Tighter least-privilege policies written and ready to deploy
- Unused accounts and stale keys identified, with a removal plan
- A check of multi-factor sign-in and top-level account settings
- Cross-account trust and outside access reviewed for risk
- A written quarterly review routine for your own staff
How it runs
-
Step - 01
Inventory
We gather every identity and its activity logs, then analyse how each is used.
-
Step - 02
Comparison
Allowed permissions are measured against actual use for each identity over 90 days.
-
Step - 03
Proposal
We write narrower policies and go through them with the teams that own them.
-
Step - 04
Rollout
Approved changes go out in small batches with a rollback plan ready.
Timeline: 10 working days, counted from the day we receive what we need from you.
Is it a fit?
A good match for
- Cloud accounts where access has piled up for years without review
- Businesses where ex-employees could still log in
- Teams facing an upcoming audit that will probe least privilege
What we need from you
- Read-only access for auditing every in-scope cloud account
- Confirmation of who owns each service account today
- A scheduled change window to roll out the approved policies
Why it helps
- A leaked key can reach much less than it can today
- Idle credentials and leftover ex-employee access get cleared out
- A quarterly routine your people can repeat without outside help
Questions
That risk is why we base changes on 90 days of actual activity and apply them in small batches. Anything unclear is flagged for your decision rather than guessed.
Yes, using each provider's own identity and access tools. Let us know which provider you use when you place the order.
Only after you approve each batch in writing. We never remove access on our own, and a rollback plan is ready before every change.