§1 Report sheetMAP-0342 / Sample report

add-on with read on every secret
Client | Online learning platform |
Map area | Kubernetes |
Scope | 3 Kubernetes clusters, 8 Google Cloud projects |
Findings | 0 Critical, 5 High, 17 Low |
Result | Cluster-wide read removed |
Written for the team that did the work. The client is fictional and the name is withheld.
The team connected three clusters and eight projects before a busy enrolment period.
A monitoring add-on had asked for cluster-wide read on install, so it could read every secret in every namespace.
The add-on now reads only what it reports on, and the rule is held in Terraform so it cannot drift back.
§3 TimelineMAP-0342 / Sample report
Sample timeline, taken from the map history. Every action has a time.
When | Step | By |
Day 1 | Read-only role added to all eight projects | Client team |
Day 1 | First map finished, service account flagged | Wardline |
Day 2 | Add-on permissions read through together | Named engineer |
Day 5 | Reduced role tested on one cluster | Client team |
Day 9 | Pull request merged for all three clusters | Client team |
After the fix | ||
Day 12 | Rule moved into Terraform | Named engineer |
Day 18 | Five High paths closed | Client team |
Day 21 | Add-on install check added to the release list | Client team |
§4 FindingsMAP-0342 / Sample report
Severity | Finding | Closed |
High | Service account could read every namespace | Day 9 |
High | Node role could reach storage in two projects | Day 14 |
High | Default service accounts mounted in all pods | Day 18 |
The other 19 stay in the client's copy.

§5 Client noteMAP-0342 / Sample report
The add-on worked perfectly with a tenth of the access. Nobody had ever asked it to.
Add-ons get only what they report on
Cluster roles held in Terraform
Install check before every add-on
§6 More reportsEnd of MAP-0342