Report MAP-0398   Storage

A staging key that could read production backups, gone in an afternoon.

§1 Report sheetMAP-0398 / Sample report

Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk
Sample map MAP-0398
1

unused key between staging and every backup

Report sheet

Client

Health records software

Map area

Storage

Scope

9 AWS accounts, 31 data stores

Findings

1 Critical, 6 High, 19 Low

Result

Critical closed the same afternoon

A restore key nobody had retired.

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

§2.1   The setup

The team connected nine accounts to see which roles could reach the stores tagged as patient records.

§2.2   What the map showed

A key made for a staging restore could still read the production backup store. It had not run in eleven months, and nobody could name its owner.

§2.3   What changed

The key was deleted that afternoon. Restores now use a short-lived role that exists only while the job runs.

§3 TimelineMAP-0398 / Sample report

One afternoon, step by step.

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

When

Step

By

12:10

Read-only role added to nine accounts

Client team

12:51

First map finished, backup store flagged

Wardline

13:05

Path read through in the shared channel

Named engineer

13:40

Last use of the key confirmed as eleven months ago

Client team

14:20

Pull request opened to remove the key

Named engineer

15:02

Key deleted, path gone from the map

Client team

After the fix

Day 2

Restore job moved to a short-lived role

Client team

Day 7

Six High paths raised as pull requests

Named engineer

Day 30

All High paths closed

Client team

§4 FindingsMAP-0398 / Sample report

26 findings. Four shown in full.

Severity

Finding

Closed

Critical

Staging key could read production backups

Same day

High

Backup store readable by nine build roles

Day 12

High

Log store readable by a build role

Day 19

High

Old analytics role with read on all stores

Day 30

The other 22 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
1 Critical  Â·  6 High  Â·  19 Low

§5 Client noteMAP-0398 / Sample report

I asked who could read our backups and had the answer before lunch. The fix was merged before the end of the day.

VP Engineering, health records software (fictional client)
What changed

No long-lived keys near backups

Restores use a short-lived role

Backup readers reviewed every month

§6 More reportsEnd of MAP-0398