Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Authentication verifies who you are; authorisation decides what you are allowed to do. Both are needed, they fail in different ways, and confusing them causes serious security flaws.

What Is the Difference Between Authentication and Authorisation?
Authentication answers the question “Who are you?” Authorisation answers “What are you allowed to do?” When you sign in to a finance system with a password and a code from your phone, that is authentication. When the system then lets you view invoices but not approve payments over a set limit, that is authorisation. The two always work together, authentication first, but they are built, tested, and broken in different ways.
| Authentication | Authorisation | |
|---|---|---|
| Question | Are you who you claim to be? | May you perform this action on this resource? |
| Happens | At login, and when a session is re-validated | On every request |
| Based on | Passwords, tokens, devices, biometrics | Roles, attributes, policies, ownership |
| Typical failure | Account takeover | Access to other users’ data or admin functions |
| HTTP status when it fails | 401 | 403 |
The HTTP labels are a long-standing source of confusion: status 401 is named “Unauthorized” but actually means the client has not authenticated, while 403 “Forbidden” means the server knows who you are and is refusing anyway.
Authentication relies on one or more factors: something you know (a password or PIN), something you have (a phone, hardware key, or smart card), and something you are (a fingerprint or face). Combining factors from different categories is multi-factor authentication, and it blocks the vast majority of attacks that rely on stolen passwords alone.
Not all second factors are equal. SMS codes can be intercepted through SIM swapping, and push approvals can be abused through fatigue attacks. FIDO2 security keys and passkeys are phishing-resistant because the browser will only complete the cryptographic exchange with the genuine website. The NCSC recommends MFA wherever it is available, and Cyber Essentials requires it for cloud services.
Once identity is established, the system has to decide whether each action is permitted. Common models include:
Good authorisation follows the principle of least privilege and denies by default. In larger estates, decisions are centralised in a policy decision point and enforced consistently by applications, gateways, and cloud services.
Standard protocols blur the line, so it helps to know what each one actually does:
Authentication failures lead to account takeover: weak or reused passwords exploited through credential stuffing, missing MFA on remote access, session tokens that never expire, or password reset flows that can be abused. Authorisation failures are quieter but often worse, because the attacker uses a perfectly valid account. Changing an ID in a URL to view another customer’s record, or calling an admin endpoint as a standard user, are classic examples of broken access control, the top risk in the OWASP Top 10.
If you are strengthening the authentication side first, our two-factor authentication solutions are a practical place to start.
Authentication comes first, because a system cannot decide what you may do until it knows who you are. Even anonymous access involves an authorisation decision: the system treats you as an unauthenticated user and grants only the permissions defined for that state, such as viewing public pages. Authorisation then continues on every subsequent request.
OAuth 2.0 was designed for delegated authorisation, letting an application access resources on a user’s behalf. Using raw OAuth access tokens as proof of identity has caused real vulnerabilities. For signing users in, use OpenID Connect, which builds on OAuth 2.0 and provides a verifiable ID token describing who the user is and how they authenticated.
Indirectly. MFA makes it much harder for an attacker to log in as someone else, so the permissions attached to that account are better protected. But MFA does nothing if the application itself lets any logged-in user read other users’ data. Strong authentication and correct authorisation checks are separate controls, and you need both.
AAA stands for authentication, authorisation, and accounting. Authentication establishes identity, authorisation determines permitted actions, and accounting records what each user actually did, providing an audit trail. The model is common in network access control, where protocols such as RADIUS and TACACS+ implement all three, and it remains a useful checklist for any access system.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.