Cloud identity & access
Discuss AWS identity and permission sources within the agreed estate.
Start by confirming the source, required permissions and available connection method. Keep the business decision at the center of onboarding.
Discuss AWS identity and permission sources within the agreed estate.
Discuss Microsoft Entra ID identities, roles and access relationships.
Discuss repository evidence, service accounts and AI-agent access paths.
These are source-scoping categories, not a list of universally available native connectors. We confirm current support, permissions and readiness for each source before an engagement.
Where supported, agree the least access needed to collect the assessment evidence.
Use an agreed JSON or CSV export when direct access is unsuitable.
Explore the assessment format using synthetic data before authorizing customer access.
Which access is requested, who approves it and how it can be revoked.
Which identities and relationships can be assessed from the selected source.
When evidence was collected and the agreed refresh arrangements.
What is accessed, retained and included in the output.
We’ll walk through your use case, confirm the supported scope, and agree what a useful result looks like.