Report WL-2229   Cloud

One build role that could read every customer's storage.

§1 Report sheetWL-2229 / Sample report

Tester seated in a dark room, studying a magenta attack path on a wide screen
Sample engagement WL-2229
1

role from a migration, with read access to all storage

Report sheet

Client

Software vendor

Test type

Cloud

Scope

Identity paths and pipelines across two clouds, six days.

Findings

1 Critical, 6 High, 12 Low

Result

Storage read

A role that outlived its migration.

Written for the client's board. The client is fictional and the name is withheld.

§2.1   The test

We followed identity paths and build pipelines across two clouds for six days.

§2.2   How it worked

A role left over from a migration still held read access across all storage. Any build job could use it.

§2.3   What changed

The role was split and given an end date. Unused permissions fell sharply at the retest.

§3 TimelineWL-2229 / Sample report

Thirty-eight days, step by step.

Sample timeline, taken from the test log. Every action has a time.

When

Step

By

Day 0

Scope, test windows and stop contact signed

Lead

Day 1

Roles and pipelines listed across both clouds

Tester

Day 2

Old migration role found on the build system

Tester

Day 3

Test build job reads a sample file with that role

Tester

Day 3

Named contact phoned with the proof and a fix

Tester

Day 6

Remaining paths tested, testing ends

Tester

After the test

Day 8

Report read through with the client on a call

Lead

Day 16

Role split and given an end date

Client IT

Day 38

Retest: every Critical and High closed

Tester

§4 FindingsWL-2229 / Sample report

Nineteen findings. Four shown in full.

Severity

Finding

Closed

Critical

Build jobs could read all customer storage

Day 38

High

Migration role with no end date

Day 38

High

Roles shared across two clouds

Day 38

High

Build logs kept long-lived keys

Day 38

The other 15 stay in the client's copy.

Tester's hands at a keyboard, a dark log console and a hardware key on the desk
Findings, sample client
1 Critical  Â·  6 High  Â·  12 Low

§5 Client noteWL-2229 / Sample report

Nobody had decided to give the build that access. It just never went away after the migration.

Head of engineering, software vendor (fictional client)
What changed

Build roles split by job

Every role has an end date

Short-lived keys in the pipeline

§6 More reportsEnd of WL-2229