Report MAP-0356   Pipelines

A deploy token printed in a build log, revoked in nine minutes.

§1 Report sheetMAP-0356 / Sample report

Minh Tran, build log lines reflected in his glasses in low magenta light
Sample map MAP-0356
9 min

from the alert to a revoked token

Report sheet

Client

Consumer lending app

Map area

Pipelines

Scope

GitHub Actions, 6 AWS accounts

Findings

1 Critical, 3 High, 12 Low

Result

Token revoked in 9 minutes

One debug line, readable by everyone.

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

§2.1   The setup

The team connected GitHub Actions and six AWS accounts so the map could read which roles their builds can step into. It reads settings, never logs.

§2.2   What the map showed

A debug step printed a deploy token into a build log that the whole engineering team could read. GitHub secret scanning raised the alert, the team passed it on, and the map showed that the token reached production.

§2.3   What changed

It was revoked nine minutes after the alert. Deploys now use a short-lived token per job, and logs are checked for secrets.

§3 TimelineMAP-0356 / Sample report

Nine minutes, then two weeks.

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

When

Step

By

10:02

GitHub secret scanning alert passed to the shared channel

Client team

10:03

Named engineer posts what the token can reach, from the map

Named engineer

10:05

Token owner confirmed

Client team

10:08

Build log removed

Client team

10:11

Token revoked, path gone from the map

Client team

After the fix

Day 2

No use of the token found in the team's own provider logs

Client team

Day 6

Deploys moved to a short-lived token per job

Client team

Day 14

Log check added to every pipeline

Client team

§4 FindingsMAP-0356 / Sample report

16 findings. Three shown in full.

Severity

Finding

Closed

Critical

Exposed deploy token with a path to production

9 min

High

Token valid for all six accounts

Day 6

High

Fork builds could read repository secrets

Day 9

The other 13 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  Â·  3 High  Â·  12 Low

§5 Client noteMAP-0356 / Sample report

It was nine minutes, and most of that was finding the person who owned it. Now every token has a name on it.

Engineering manager, consumer lending app (fictional client)
What changed

Short-lived tokens per job

Logs checked for secrets

Fork builds hold no secrets

§6 More reportsEnd of MAP-0356