§1 Report sheetMAP-0371 / Sample report

roles unused for a year, removed
Client | Logistics marketplace |
Map area | Multi-cloud |
Scope | AWS, Azure and Google Cloud, 27 accounts |
Findings | 0 Critical, 8 High, 41 Low |
Result | 214 unused roles removed |
Written for the team that did the work. The client is fictional and the name is withheld.
Three teams looked after three clouds, each with its own list. Nobody could see the links between them.
One map showed the logins that crossed from one cloud to another, and that 214 roles had not been used in a year.
The team removed them in six pull requests, one for each group of unused roles, and nothing broke. Each link between clouds now has a named owner.
§3 TimelineMAP-0371 / Sample report
Sample timeline, taken from the map history. Every action has a time.
When | Step | By |
Day 1 | Read-only roles added in all three clouds | Client team |
Day 1 | First map finished across 27 accounts | Wardline |
Day 3 | Links between clouds read through together | Named engineer |
Day 8 | Usage pulled for every role, 214 unused | Wardline |
Day 15 | First three pull requests merged | Client team |
Week 6 | Last of six pull requests merged, 214 roles gone | Client team |
After the fix | ||
Week 7 | Each link between clouds given an owner | Client team |
Week 9 | Eight High paths closed | Client team |
Week 12 | One monthly report replaces three lists | Named engineer |
§4 FindingsMAP-0371 / Sample report
Severity | Finding | Closed |
High | Federated login from a test tenant into production | Week 3 |
High | Service account shared between two clouds | Week 5 |
High | Storage reader with no owner | Week 7 |
The other 46 stay in the client's copy.

§5 Client noteMAP-0371 / Sample report
We removed 214 roles and nobody noticed. That told us everything about how much we needed them.
One vocabulary across three clouds
Unused roles expire on a schedule
Every link between clouds has an owner
§6 More reportsEnd of MAP-0371