Report MAP-0412   Identity

412 paths. 6 left, by week 9.

§1 Report sheetMAP-0412 / Sample report

Engineer walking two colleagues through a magenta path on a wall graph
Sample map MAP-0412
412

paths to customer data on the first map

Report sheet

Client

Payments platform, 180 staff

Map area

Identity

Scope

14 AWS accounts, 2 Kubernetes clusters

Findings

2 Critical, 11 High, 30 Low

Result

All Critical closed in 11 days, merged as 37 pull requests

Two of them were three hops long.

Written for the team that did the work. The client is fictional and the name is withheld.

§2.1   The setup

The team connected 14 AWS accounts with the read-only role. The first map finished in 38 minutes and showed 412 paths to customer data.

§2.2   What the map showed

Two Critical paths started from a build role and reached customer records in three hops. Nobody had looked at that role in years.

§2.3   What changed

All Critical were closed in 11 days, through 37 small pull requests. By week 9 only 6 low-reach paths were left, each with a named owner.

§3 TimelineMAP-0412 / Sample report

Nine weeks, step by step.

Sample timeline, taken from the map history. Every action has a time.

When

Step

By

Minute 0

Read-only role added to the first account

Client team

Minute 38

First map finished, 412 paths ranked

Wardline

Day 1

Top ten paths read through in the shared channel

Named engineer

Day 7

First pull requests opened against the build role

Named engineer

Day 11

Both Critical paths closed

Client team

Week 9

Six low-reach paths left, each with an owner

Client team

After the fix

Week 10

Hourly map switched on for all 14 accounts

Client team

Week 12

Monthly review added to the platform team calendar

Client team

Week 13

First report exported for the audit file

Named engineer

§4 FindingsMAP-0412 / Sample report

43 findings. Four shown in full.

Severity

Finding

Closed

Critical

Build role three hops from customer records

Day 11

Critical

Deploy role trusted by a whole staging account

Day 11

High

Cluster role that could read production secrets

Week 3

High

Vendor role with no external ID

Week 4

The other 39 stay in the client's copy.

Engineer's hand on a laptop in front of a log console with two lines highlighted in magenta
Findings, sample client
2 Critical  Â·  11 High  Â·  30 Low

§5 Client noteMAP-0412 / Sample report

We had a list of findings for years. The map was the first thing that told us where to start.

Head of platform, payments platform (fictional client)
What changed

Every path to customer data has an owner

Build roles split from read roles

Fixes merged through normal review

§6 More reportsEnd of MAP-0412