Slide 18 of 28
Part 4 · PreventionSlide 18
PART 4
Prevention
Slides 18–28 · 7 mitigations, the matrix, quiz, done
Slide 18 · Prevention Overview
The fix sounds simple. The hard part is discipline.
Fixing BOLA doesn't require new technology — it requires remembering to ask one question.
The core fix — one sentence

Every time an API receives an object ID from a client, it must verify that the requesting user is authorized to access that specific object. Every time. Every endpoint. No exceptions.

Why it's hard in practice

Scale. A large API can have hundreds of endpoints. Every single one that accepts an ID needs this check. Miss one and that endpoint is exposed.

Assumption. Many developers assume "if they have the ID, they're allowed." IDs are treated as secrets — but they're not. Sequential integers are trivially guessable.

Testing gaps. Standard unit tests don't catch BOLA because they test your data with your credentials. BOLA only appears when you test someone else's data with your credentials.

Seven mitigations coming up

The next 7 slides cover each prevention strategy. They layer on top of each other — no single one is enough on its own. Real security comes from applying several together.

← Back Let's start → Mitigation 1 →