Platform

One map.

Identities, roles, trust links and data stores on one page, joined up the way an attacker would join them.

Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk

One read-only role, no agents, and a first map today. You can remove our access with one delete.

Engineer walking two colleagues through a magenta path on a wall graph
Engineer walking two colleagues through a magenta path on a wall graph
§1   The reach map

Three hops, not 12,406 grants.

The map shows every path from an identity to your data, ranked by what it reaches. You start with the path that ends at customer records.

Sample map prod-⁠eu: 3 hops, found in 38 minutes
§2   What the map reads

Who, what, how.

412

People, service accounts and the roles they can step into, including the ones nobody has used in a year.

AWS IAM · Microsoft Entra ID · Google Cloud IAM
96

The roles your builds and deploy tokens can step into. Most short paths to production start here.

GitHub Actions · GitLab CI · Terraform
38

Buckets, databases and keys, sorted by what is inside them and who can read it. File contents stay where they are.

Amazon S3 · Azure Blob Storage · Cloud Storage
Identities, roles and data stores on sample map prod-⁠eu. Demo data.
§3   Where teams stop looking

Trust links.

The sample map holds 61 of them. They are the least reviewed part of most clouds, because no single team owns them.

a

Across clouds

Federated logins that carry a path from one provider into another.

b

Vendors

Roles an outside company can assume, including suppliers you stopped using.

c

Kubernetes

Service accounts with more reach than the workload they run.

§4   Fixes

Pull requests.

Not tickets.

Fixes arrive as small Terraform changes your team reviews and merges the usual way. Each one fixes one root cause and says how to roll it back.

Arjun Nair working at a laptop and a portable dark monitor showing a graph with one magenta path
Arjun Nair working at a laptop and a portable dark monitor showing a graph with one magenta path
§5   Where to look first

Start with your question.

You want to know

Start with

You get

Who can reach customer records?

Reach map

Paths ranked by reach

Which access keys have no owner?

Identity

Holders and last use

What can a deploy token touch?

Pipelines

Every role it can step into

Which stores hold regulated data?

Storage

Readers, counted in hops

Which vendors can still get in?

Trust links

Each outside role, by name

What will the auditor ask for?

Reports

CIS, SOC 2, ISO/IEC 27001

Every first map runs the same way.

Minute 0

Add one role

Minute 12

We take inventory

Minute 40

Read the map

Day 7

Fixes arrive

§6   Contact

Connectone account.

Free for one account. No card and no sales call. An engineer stays on hand while it runs.