Identity map
People, groups, roles, service identities and trust relationships.
Cloud security
Identity and access management consulting
Design and repair human and workload access across cloud accounts, delivery systems and production services. Reduce cloud attack paths without making routine engineering depend on a security ticket.
01 / Scope
Work on the system, not around it.
The engagement starts with the architecture and working constraints already in place. We agree the risky paths, make the changes visible and leave ownership with the team running the system.
Privilege paths
Standing access, escalation routes, unused permissions and emergency access.
Lifecycle
Joiner, mover, leaver, rotation and periodic review workflows.
Implementation
Federation, short-lived credentials, guardrails and policy-as-code.
02 / Method
Reduce cloud attack paths without making routine engineering depend on a security ticket.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Map the boundary
Start with evidence, owners and the constraints that shape the safe solution.
Validate the risky paths
Prioritise by practical impact and implement with the people who operate the system.
Implement and verify
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01Current-state identity and privilege map
- 02Prioritised access findings with affected principals
- 03Implemented role and federation changes
- 04Review and emergency-access runbooks
Related work
Continue with the adjacent problem.
04 / Talk to Gritt
What is happening in the system?
Send the cloud, workload or deadline. An engineer will reply and tell you whether this is the right scope.
email