These are the questions teams ask before they add the role. If yours is missing, an engineer will answer it.
A scanner lists settings that break a rule. A map shows what each one connects to, so you start with the path that ends at real data.
The one closest to your customer data. If you are not sure, pick your busiest production account. One account is enough for a useful first map.
One of our engineers, in a shared channel, on working hours. The person who reads your first map stays with you afterwards.
No. The role only lists and describes settings. Nothing is installed and nothing runs inside your workloads.
One person with access to the account adds the role. Most teams show the template to their cloud lead first, and it is short enough to check line by line.
Today. Add the role at minute 0 and read the map at minute 40.
It can list and describe settings. It cannot change anything, and it cannot open files or read records.
No. We read names, tags, roles and policies. File contents and customer records stay where they are.
AWS, Microsoft Azure and Google Cloud, along with GitHub Actions, GitLab CI, Terraform and the Kubernetes clusters tied to them.
No. There are no agents and nothing is added to your workloads. You add one role.
Delete the role. Our access ends at that moment, and you need nobody's permission.

Per cloud account. Team is a sample $480 per cloud account, per month, however many people read the map.
One AWS account, one Azure subscription or one Google Cloud project. Pipelines and Kubernetes clusters tied to it are included.
Yes, before the first call if you want. Our own outside review summary is shared under NDA too.
A real vendor should show you one. Wardline is a fictional business, so its Type II report is a demo sample and nothing here has been audited.
The first pull requests arrive on the Team plan. Each one fixes one root cause.
Six sections: a summary for your board, accounts and settings read, paths ranked by reach, who could reach what by date, fixes merged, and exceptions with their owners. Reports come with Team and Company.
By what they reach, not by how many settings they break. A dull setting three hops from customer records goes first.
CIS Benchmarks, SOC 2 and ISO/IEC 27001. Each has a set place in the report, so your auditor can find it without asking.
On the Team plan, as small Terraform pull requests, one root cause each, with a note on how to roll back.
Your engineers, the usual way, in your own repositories. Nothing merges without them.
Each one gets a named owner on your side and stays in the report as an exception.
