ContactBook a demo

Effective access

Declared is not effective.See what it can reach.

A policy says what an identity may do. Role chains, trust policies, group membership and cross-account assumption decide what it can actually do. Trustivan resolves the difference on the identity graph — per identity, per resource, with the path shown.

AvailableIdentity graph · upper bound

Book a demoExplore Access Intelligence

Part of the identity graph · effective permissions, access paths, cross-account trust

The problem

Policies describe intent. Graphs describe reality.

Every permission system composes: roles inherit, principals assume, accounts trust. Read one policy document and you learn what someone meant, not what an identity can reach.

Role chains

One role assumes another, which assumes a third — the last hop carries the privilege

Trust policies

A resource trusts a principal from another account, and nobody on either side remembers why

Dormant privileges

Permissions granted for a migration two years ago are still attached and never used

Access paths

Every path, from identity to resource.

Trustivan evaluates effective permissions by walking the graph: the identity, each credential it holds, each role it can assume, the trust relationships along the way, and the resources at the end. The result is a set of paths, not a policy document.

  • Path-level answers: which credential and which role chain grant the access.
  • Cross-account: role assumption across accounts is a first-class edge, not a footnote.
  • Upper bound, labelled: Deny statements, conditions and managed policy documents are not evaluated, so the result never understates reach.

AvailableIdentity graph · upper bound

See what a compromise would reach

How it works

Collect. Link. Evaluate. Compare.

The same identity graph that holds owners and credentials holds roles, trusts and resources — so effective access is a query, not a separate product.

  1. Collect

    Roles, groups, trust relationships and inline policy statements are read from every connected AWS account

  2. Link

    Assumption, membership and attachment become edges on the identity graph

  3. Evaluate

    Effective permissions are computed per identity as an upper bound, following every chain to its end

  4. Compare

    Effective reach is set against resource impact, so access to what matters most stands out

Explore the identity graph

What you get

Answers per identity, per resource, per path.

Built for the questions responders and reviewers actually ask: can it reach production, through what, and which grant makes that possible.

Effective permissions

Resolve what each identity can do per resource, after every chain is followed

Access paths

See the credential, roles and trust relationships that make a permission effective

Upper bound, stated

Deny statements and conditions are not evaluated, so effective access may overstate reach — never understate it

High-impact access findings

Flag identities that reach high-impact resources, with the path to each shown

Transitive reach

Follow every hop from identity to resource, not just the first grant

Cross-account trust

Inventory who can assume what across accounts and organizations — in both directions

NHI Security

Continue through the pillar

Effective access feeds risk, blast radius and governance — and depends on the inventory and ownership that come before it.

See what your identities can actually reach.

A demo walks through the access paths of one identity — declared and effective — on the demonstration estate.

Book a demo