deny by default
The rule that anything not explicitly allowed is refused, including when the facts needed to decide are missing.
In more detail
Unknown methods, fields, origins, key identifiers and credentials should all fail clearly. A system that fails open grants access whenever something unexpected happens.
Example
In the course a route with no declared policy raises an error instead of being served, which turns a forgotten check into a failing test for the engineer who added the route.Related terms
- authorization — Deciding whether an already identified caller may perform a particular action on a particular resource.
- key identifier — A short name in a token header, kid, that says which of the verifier’s trusted keys was used to sign it.
- input validation — Checking that data from a user, file or caller is acceptable before using it, and rejecting or asking again if not.
- fail open — What a security control does when it breaks or cannot decide: failing open lets the request through, while failing closed blocks it.
- implicit deny — The refusal a permission system gives when no rule allows a request, even though nothing explicitly denied it.
- NetworkPolicy — A Kubernetes object that controls which pods may send traffic to or receive traffic from which others, by labels, namespaces and IP ranges.
- secure by default — Designing software so the setting you get by typing nothing is the safe one, and anything riskier must be asked for by name.
Taught in
- Excessive Agency — AI Engineering: LLM Apps, RAG & Agents
- RBAC Contrasted With ABAC — Modern API Architecture: REST, GraphQL & gRPC
- Scopes And Key Rotation — Modern API Architecture: REST, GraphQL & gRPC
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Kubernetes NetworkPolicies & Microsegmentation — Cloud Security & DevSecOps Engineering
- Policy-as-Code Architecture: OPA & Rego Syntax — Cloud Security & DevSecOps Engineering
- Secure Defaults — Application Security & Threat Modeling for Engineers
- Moving To A Secret Manager — Application Security & Threat Modeling for Engineers
- Workload Identity — Application Security & Threat Modeling for Engineers
- Broken Object Level Authorization — Application Security & Threat Modeling for Engineers
References
- OWASP Cheat Sheet Series: Authorization: deny by default
- OWASP: fail securely
- OWASP Authorization Cheat Sheet: deny by default