Same order every time. No agents to install and nothing added to your workloads. The weeks below follow a sample Team customer.
Our access is one read-only role in your account. You can read it line by line, and you can remove it whenever you want.
We read settings and never copy your data.
Every fix is a pull request your team reviews.
Nothing merges without your engineers.
A read-only role, short enough to check line by line.
One person with access to the account adds it. That is the whole install.
Identities, grants, buckets and keys. We read settings and never copy your data.
Work carries on as normal. Nothing runs inside your workloads.
Every path ranked by what it reaches, not by how many settings it breaks.
Start at the top. The first ten paths are explained in plain words.
Small Terraform changes, one root cause each, with a note on how to roll back.
The usual way, in your own repositories, on your own schedule.
Your named engineer stays in the channel until only low-reach paths are left.
Each path that stays gets a person, so nothing sits unowned.
On the Team plan a new path shows up within the hour.
A short note in your channel, ranked the same way as the first map.
Reports map to CIS Benchmarks, SOC 2 and ISO/IEC 27001, so the same work answers your auditor. See what is in a report
Deliverable | What is in it | Who reads it |
Read-only template | One role, every line open to check, removed with one delete | Your cloud team |
Reach map | Every path from an identity to a data store, ranked by reach | Security and platform |
Top ten paths | What each path reaches and why, in plain words | Whoever owns the fix |
Pull requests | Small Terraform changes, one root cause each, with a rollback note | Your engineers |
Dated report | Who could reach what, mapped to CIS, SOC 2 and ISO/IEC 27001 | Auditors |
Sample case MAP-0412, a payments platform with 180 staff. Your own list will differ, the order will not.
The first map shows 412 paths. Two reach customer data in three hops.
The first pull requests arrive. Each path gets an owner on your side.
All Critical paths are closed.
High next, then the Low paths you choose to take on. 37 pull requests in all.
Six low-reach paths are left, each with a named owner.

Tell us which cloud you use. An engineer sends the read-only template and stays on hand while it runs.