Integrations

Your environment.
A connection plan that fits.

Start by confirming the source, required permissions and available connection method. Keep the business decision at the center of onboarding.

Source scoping

Bring your stack to the conversation.

01

Cloud identity & access

Discuss AWS identity and permission sources within the agreed estate.

02

Workforce identity

Discuss Microsoft Entra ID identities, roles and access relationships.

03

Development & machine identities

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.

Connection options

Agree the simplest supported route.

01

Scoped API access

Where supported, agree the least access needed to collect the assessment evidence.

02

Structured export

Use an agreed JSON or CSV export when direct access is unsuitable.

03

Sample environment

Explore the assessment format using synthetic data before authorizing customer access.

Before assessment

Four details worth making explicit.

01

Permissions

Which access is requested, who approves it and how it can be revoked.

02

Coverage

Which identities and relationships can be assessed from the selected source.

03

Freshness

When evidence was collected and the agreed refresh arrangements.

04

Data handling

What is accessed, retained and included in the output.

Your next move

Tell us what you want to connect.

We’ll walk through your use case, confirm the supported scope, and agree what a useful result looks like.