authorization
Deciding whether an already identified caller may perform a particular action on a particular resource.
In more detail
It follows authentication and is checked by the service that owns the resource, even if a gateway already verified the token. A known caller without permission gets 403 Forbidden. Field selection, filters and embedded data must all respect it, and it should deny by default when facts are missing.
Examples
In AWS: Deciding what an already identified caller is allowed to do.sudo: bob : user NOT in sudoers ; TTY=pts/1 ; PWD=/home/bob ; USER=root ; COMMAND=/usr/bin/cat /etc/shadow09:15:10 bob authz refused as root: /usr/bin/cat /etc/shadowIt comes after authentication: once a system knows who you are, file modes, sudo rules or an application's own checks decide what you may do. A valid TLS certificate or accepted SSH host key proves an identity but grants nothing by itself. Server-side authorization, such as an authorized_keys entry, is what actually admits a user.The course calls it a design problem, fixed by putting the ownership check inside the data lookup and taking the caller's rights from the server, never from the request.Related terms
- authentication — Establishing who a request represents, for example by checking a password, a session cookie or a signed token.
- 403 Forbidden — The HTTP status meaning the server knows who the caller is but that identity is not allowed to do this.
- role-based access control — An authorization model where permissions are grouped into named roles, such as reader or editor, and people or services are given roles.
- attribute-based access control — An authorization model that decides each request from attributes of the subject, the resource and the environment, such as owner, department or time of day.
- broken access control — A flaw where the server lets a caller act on data or operations it should not, for example by trusting a user name the caller supplied or skipping an ownership check.
- policy evaluation logic — The fixed order AWS uses to decide a request: an explicit deny wins, otherwise any allow wins, otherwise the answer is deny.
- IAM policy — A JSON document that lists which actions are allowed or denied on which resources, and under which conditions.
- --authorization-mode — The kube-apiserver flag, and matching kubelet setting, that lists which authorizers decide requests, such as Node,RBAC.
- IAAA — The four steps of every access decision: identification, authentication, authorisation and accountability.
- sudo — A command that runs another command with administrator (root) rights after checking you are allowed to.
- root user — The all-powerful administrator account on Linux, with user ID 0, which can read or change anything.
- policy-based authorization — Protecting endpoints with named policies that bundle requirements, such as a scope claim and a role.
- role — A coarse label on a user, such as editor or administrator, that authorization can check.
- broken object level authorization — An API flaw where changing an identifier in a request, such as /tasks/2 instead of /tasks/1, lets a caller reach an object that belongs to someone else.
- file permissions — Rules on each file saying which user and group own it and who may read, write or run it.
- sudoers file — The configuration file, /etc/sudoers plus files in /etc/sudoers.d, that says who may run which commands as which user through sudo.
- authorized_keys — The file in a user's ~/.ssh directory listing the public keys allowed to log in to that account over SSH.
- Server Action security — Treating every Server Action as a public HTTP endpoint that anyone can call with any arguments.
- ownership check — Confirming that the object a caller asked for actually belongs to that caller before returning or changing it.
- signed URL — A link to a stored object that carries a cryptographic signature and expiry time, granting temporary access.
Taught in
- Cookies And CORS — Modern API Architecture: REST, GraphQL & gRPC
- Basic Auth, Tokens And Sessions — Modern API Architecture: REST, GraphQL & gRPC
- RBAC Contrasted With ABAC — Modern API Architecture: REST, GraphQL & gRPC
- API Gateways And Proxies — Modern API Architecture: REST, GraphQL & gRPC
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC
- Ten Findings, Six Pillars — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Twelve Alerts, Ten Services — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Policy Evaluation: Deny Wins, And Both Accounts Must Agree — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- KMS And Envelope Encryption: Who Can Still Decrypt? — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Serverless And Container Patterns: Where The Limits Bite — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Authentication, Authorisation And Admission — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Mock Exam: Sixteen Tasks Against The Clock — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Six Seconds, Every Secret — Certified Kubernetes Security Specialist (CKS) Exam Prep
- The Metadata Endpoint And The Kubelet's Front Door — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Anonymous Access: The Fix That Kills The API Server — Certified Kubernetes Security Specialist (CKS) Exam Prep
- IAM as the Foundation — Cloud Infrastructure & Hyperscaler Architecture
- Policy Simulation and Dry Runs — Cloud Infrastructure & Hyperscaler Architecture
- Security Landing Zones & Centralized Egress Inspection — Cloud Security & DevSecOps Engineering
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Securing the Kubernetes Control Plane & Node Components — Cloud Security & DevSecOps Engineering
- CloudTrail Logging, Integrity Validation & Athena — Cloud Security & DevSecOps Engineering
- Envelope Encryption & Data Protection with KMS — Cloud Security & DevSecOps Engineering
- CIA Triad, Non-Repudiation & Parkerian Hexad — Cybersecurity Fundamentals, GRC & Cryptography
- Defense-in-Depth & Security Control Categories — Cybersecurity Fundamentals, GRC & Cryptography
- Regulatory Compliance: SOC 2, HIPAA, GDPR & PCI-DSS — Cybersecurity Fundamentals, GRC & Cryptography
- Data States: Security at Rest, in Transit, and in Use — Cybersecurity Fundamentals, GRC & Cryptography
- Enterprise Risk Registers & Treatment Plans — Cybersecurity Fundamentals, GRC & Cryptography
- The ASP.NET Core Middleware Pipeline — Modern .NET Core, C# & Enterprise Microservices
- Building Routes with Minimal APIs — Modern .NET Core, C# & Enterprise Microservices
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- Role-Based and Policy-Based Authorization — Modern .NET Core, C# & Enterprise Microservices
- JWT Verification: Asymmetric Keys & Refresh Rotation — Production Full-Stack Engineering
- Role-Based & Attribute Access Control: RBAC & ABAC — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- Authentication, ServiceAccounts And Short Lived Tokens — Kubernetes: Production-Grade Container Orchestration
- RBAC: Roles, Bindings And Least Privilege — Kubernetes: Production-Grade Container Orchestration
- securityContext: Nonroot, Capabilities And Seccomp — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Forbidden Requests And Admission Rejections — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: API Server And Control Plane Failures — Kubernetes: Production-Grade Container Orchestration
- Certificates, Chains And What A Handshake Proves — Linux Fundamentals & Systems Administration
- SSH Keys, The Agent And The Config File — Linux Fundamentals & Systems Administration
- Optimistic UI: useOptimistic Rollbacks & Transitions — Next.js 15 & Modern App Router Architecture
- Server Action Security: Zod Validation & Auth Gates — Next.js 15 & Modern App Router Architecture
- Edge Middleware: Auth Verification & Route Matchers — Next.js 15 & Modern App Router Architecture
- Authentication Versus Authorisation — Application Security & Threat Modeling for Engineers
- Secure Defaults — Application Security & Threat Modeling for Engineers
- Broken Object Level Authorization — Application Security & Threat Modeling for Engineers
- Mass Assignment — Application Security & Threat Modeling for Engineers
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Circuit Breakers — Scalable System Design & Distributed Architecture
References
- OWASP Cheat Sheet Series: Authorization
- IAM: policy evaluation logic
- NIST glossary: authorization
- Introduction to authorization in ASP.NET Core
- man7: credentials(7)
- MDN Web Docs: HTTP authentication