How we work

How it connects,

minute 0 to week 9.

Same order every time. No agents to install and nothing added to your workloads. The weeks below follow a sample Team customer.

Role
Inventory
Map
Pull requests
Short list
Every hour
Two cloud engineers at a dark wall display, one pointing at a magenta branch of a storage graph
Two cloud engineers at a dark wall display, one pointing at a magenta branch of a storage graph
§1   You stay in charge

One delete ends it.

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.

§2   Steps

Who does what,and when.

Minute 0

We send the template

A read-only role, short enough to check line by line.

You add one role

One person with access to the account adds it. That is the whole install.

Minute 12

We take inventory

Identities, grants, buckets and keys. We read settings and never copy your data.

You do nothing

Work carries on as normal. Nothing runs inside your workloads.

Minute 40

We draw the map

Every path ranked by what it reaches, not by how many settings it breaks.

You read the map

Start at the top. The first ten paths are explained in plain words.

Day 7

We open pull requests

Small Terraform changes, one root cause each, with a note on how to roll back.

You review and merge

The usual way, in your own repositories, on your own schedule.

Week 9

We work the list down

Your named engineer stays in the channel until only low-reach paths are left.

You name the owners

Each path that stays gets a person, so nothing sits unowned.

Every hour

We update the map

On the Team plan a new path shows up within the hour.

You hear about the new ones

A short note in your channel, ranked the same way as the first map.

§3   Deliverables

What you keep.

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

§4   After the first map
412

paths. 6 left, by week 9.

Sample case MAP-0412, a payments platform with 180 staff. Your own list will differ, the order will not.

Minute 40

The first map shows 412 paths. Two reach customer data in three hops.

Day 7

The first pull requests arrive. Each path gets an owner on your side.

Day 11

All Critical paths are closed.

By week 8

High next, then the Low paths you choose to take on. 37 pull requests in all.

Week 9

Six low-reach paths are left, each with a named owner.

Engineer reading a laptop in a dark room, code reflected on his face
§5   Contact

Minute 0 startswith one role.

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