Transcript
November 2018. The US Postal Service website had 60 million users. Anyone who logged in could look up anyone else's email, phone and street address. The login worked perfectly. The site just never asked the second question. Every system asks two questions. Who are you? That's authentication. What are you allowed to do? That's authorization. A hotel asks both, every night. Maya walks up to the front desk. She shows her ID and her booking. The clerk checks her face against the photo. That's authentication: proving who she is, once. Then the clerk writes her a key card. On it go the rules: room 412, the gym, until Sunday at noon. That's authorization: what she may open. Upstairs, no door asks her name. She taps the card. Room 412: green. Room 415, down the hall: red. Same guest, same card, different answer. And after Sunday noon, even 412 says no. Websites work the same way. Your password, or a code from your phone, is the ID at the desk. The site then hands your browser a session token: a digital key card. Every click after that shows the token, and the server should check what that account may open. The web even has two error codes for this. 401 means: I don't know who you are. 403 means: I know you, and the answer is no. Confusingly, 401 is called "Unauthorized". It really means unauthenticated. Back to the Postal Service. The part of the site that answered data requests checked one thing: are you logged in? It never checked whose account you asked for. Some searches even took a star, meaning anything, and returned every match. A researcher had warned them more than a year earlier. It was fixed on November 20th, after a reporter asked about it. So remember it like this. Authentication asks who are you. Authorization asks what can you open. And it has to ask at every door. Want to practise access control hands-on? Try it free at seclern.com, and follow for more.