Photo: Kedibone Isaac Makhumisane / Unsplash
The numbers were confidential. The address wasn't.
A team built a dashboard to keep an eye on its key figures. Anyone who knew the address could see it.
How it came about.
The goal was sensible: all the important numbers in one place. The key figures from day-to-day business, plus the objectives and key results – KPIs and OKRs.
The dashboard was built locally and then moved to a server on the network. It ran. But there was no access control.
So everything was openly visible as soon as someone found out the address.
What we found.
What we did.
The goal was for the numbers to stay where they belong – with the people they are meant for.
- Checked reachability: Where can the dashboard be reached from, and what can you see without signing in? Only this picture shows how big the gap is.
- Closed access: The dashboard is now only reachable for authorized people. Anyone who wants to see the numbers has to identify themselves.
- Verified the effect: Without authorization, nothing is visible anymore – not even if you know the address.
Now only the people they are meant for can see the numbers.
Same application. Clear state.
What others can learn from it.
An address is not a password. What is reachable on the internet isn't protected just because nobody is supposed to know the link – addresses get passed on, guessed or found.
Before an internal tool moves to a server, one question belongs on the table: Who is allowed to see this – and how do we make sure only those people see it?
Next file → 002Building it isn't running it.
We review first, before we take on responsibility.
Request an Operations Check ↗