Authenticated is not the same as authorized. Most of the OWASP API Top 10 lives in that gap.
You can log in. That's not the question. The question is whether the server checks that /orders/124 belongs to you before it hands over the data — and a huge share of production APIs never make that check. Nugget starts here because it's where the real bugs are, not where the old web Top 10 trained you to look.
A session starts with Nugget sketching the request on the whiteboard: verb, path, headers, body — then asking you what the server actually verifies at each step, versus what it just assumes. From there you push on it: swap an object ID, add a field the response showed but the docs never mentioned, decode a JWT and read what's sitting in the payload. Nugget isn't handing you the finding. It's aiming the next question at whatever you skipped.
This isn't a replacement for your coursework or your bug bounty grind — it's the place where you build the reflex of asking 'can I do this to THAT object, as THIS user?' before you ever open Burp for real.
Start exploring API Security tonight — a 30-day trial, cancel anytime.
Start your 30-day trial