A shop at shop.example has a small invoice site. Authentication answers 'who are you?': Ana types her password and the server now knows her requests come from Ana. Authorisation answers 'what may you do?': which invoices Ana may open, which buttons she may use, which data she may change. They are two separate questions, asked at different moments in the code.
Broken access control is what happens when the second question is skipped or answered in the wrong place. It has topped industry vulnerability lists in recent years, which hints at why: the mistakes are small, easy to write and easy to miss. This lesson shows three of them on made-up users, then the defences.
💡Good to know
Authentication is a door that opens once. Authorisation is a question asked on every request.