A key’s day

Part 3, Systems · Step 10: Analyze and notify

Which key to fix first

Sized by what the key can do, then sent to its owner. First the team checks what the key can do: take payments, issue refunds, and read customer records. Then the alert goes to Diego’s payments team, who own the key, with all five places it was copied.

Why it matters. What a key can reach sets how urgent it is. The alert has to reach someone who can replace it.

See it in the lesson Part 3 recap

This really happened: tj-actions/changed-files, 2025

Wiz found dozens of public repositories whose build logs had leaked secrets and notified the owners.

Sources

Keep going

More topics