Organization access
Identity Center, accounts, SCPs and delegated administration.
Cloud security
AWS IAM security review
Review AWS identities, cross-account trust and privilege paths from Organizations to individual workloads. 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.
Role trust
Cross-account, service and federated trust policies.
Permissions
Effective access, boundaries, unused grants and escalation paths.
Workloads
Instance, task, Lambda and Kubernetes identities.
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
- 01AWS principal and trust map
- 02Privilege-path findings
- 03Policy and role remediation
- 04Access-review and break-glass procedure
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