Tenant baseline
Domains, federation, defaults and administrative settings.
Cloud security
Microsoft Entra ID security review
Review workforce and workload identities, Conditional Access and privileged paths across Azure tenants. 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.
Workforce access
MFA, Conditional Access, PIM and guest lifecycle.
Workload identity
Managed identities, applications, credentials and federation.
Response
Break-glass access, sign-in evidence and risky-identity workflow.
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
- 01Tenant identity and privilege map
- 02Conditional Access findings
- 03PIM and workload-identity remediation
- 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