Lesson 3.3 Category: Module 3 · Security foundations

Authentication Versus Authorization

Authentication checks who you are; authorization decides what you are allowed to do. They sound alike, but mixing them up causes real security problems.

What you’ll understand

  • What authentication means, and the main ways to prove who you are.
  • What authorization means, and why it is a separate step.
  • How these ideas show up on shared devices and websites.

At a public library, you show your library card at the desk. The librarian checks it and confirms you are a member. That is one step.

Then you ask to borrow a rare book from the reference room. The librarian says, “Sorry, members can read that here but not take it home.” That is a different step. You were recognized, but recognition didn’t mean you could do everything.

Computers make exactly the same two decisions, and they have two very similar-sounding names for them.

Authentication: who are you?

Authentication is proving that you are who you claim to be. Signing in to an account is authentication.

There are three broad kinds of proof, often called factors:

  • Something you know: a password, passphrase, or PIN.
  • Something you have: your phone, a security key, or an authenticator app on a device you carry.
  • Something you are: a fingerprint or face, often used to unlock a device.

Using two or more different kinds together is called multi-factor authentication (MFA). It is covered in the lesson on passwords and MFA.

Authorization: what may you do?

Authorization is deciding what an authenticated person is allowed to do. It happens after authentication, and it is often checked again and again while you use a service.

On a school website, a student and a teacher both sign in. Both are authenticated. But only the teacher is authorized to change marks. The website must check that difference every single time someone tries to edit a mark, not just once at the front door.

Authentication

“Who are you?”

  • Happens when you sign in
  • Uses passwords, codes, devices, fingerprints
  • Result: the system knows which account you are

Authorization

“What are you allowed to do?”

  • Happens after you are identified, and keeps happening
  • Uses permissions, roles, and rules
  • Result: you may view, edit, or do nothing
Two questions, in this order. A good system answers both, every time it matters.

A concrete example: the shared family computer

A family laptop has two accounts:

  • A parent’s account, which is an administrator. It can install software and change system settings.
  • A child’s account, which is a standard user. It can use apps and save files but can’t install new software.

When the child signs in with their password, that is authentication. When the child tries to install a game and the laptop asks for an administrator’s password, that is authorization at work: the child is recognized but not permitted to make that change alone.

This setup also limits damage. If the child accidentally opens a harmful download, it has fewer permissions to cause trouble. Giving each person only the access they need is a principle called least privilege, and it has its own planned lesson.

Why the difference matters

Both steps can fail, and they fail in different ways.

If authentication fails, someone gets into an account that isn’t theirs, often with a stolen or guessed password. The fix involves stronger passwords, MFA, and spotting scams.

If authorization fails, a genuine user can do something they shouldn’t. Imagine an online shop that checks you are signed in, but forgets to check whether the order you are viewing is actually yours. Every customer is properly authenticated, and yet they could see each other’s addresses. Problems like this are among the most common security flaws in websites, and they are the website owner’s job to prevent.

A common mix-up

“I’m signed in, so I’m allowed” mixes up the two ideas. Signing in only proves identity. What you can do after that depends on authorization rules. The reverse confusion happens too: a website that shows you an “Edit” button might still refuse the change, because the real authorization check happens on the server. (Testing whether a real website checks properly is something only its owners, or people with their explicit permission, should do.)

Try it safely

On a computer you own, open the user accounts section of Settings. Check whether your everyday account is an administrator or a standard user. Many people use an administrator account for everything. You don’t need to change it today. Just notice which kind you use, and that the device treats the two kinds differently.

Check your understanding

You type your password and a code from your phone to sign in to email. Is that authentication or authorization?

Answer: Authentication. You are proving who you are, using two different factors.

A signed-in employee can see the payroll file even though their job has nothing to do with payroll. Which step has failed?

Answer: Authorization. The employee was correctly identified, but the system allowed access they shouldn’t have.

Why might a parent give a child a standard account instead of an administrator account?

Answer: A standard account limits what can be changed or installed, which reduces the damage from mistakes or harmful downloads.

The key idea

Authentication answers “Who are you?” Authorization answers “What are you allowed to do?” A system needs both, and being recognized is never the same as being allowed.

Further reading