attack surface
Everything an attacker could try to use against a system: open ports, installed programs, accounts and settings.
In more detail
Every extra package, service, open port or account is something that might have a flaw or be misused. Removing what is not needed and tightly controlling the rest shrinks the attack surface, for example by using minimal base images or publishing only the ports you need.
Examples
Multi-stage builds leave compilers, shells and package managers out of the production image.Counting every route with whether it needs authentication and whether it changes stateRelated terms
- load balancer — A server that spreads incoming requests across several copies of a service so no single copy is overloaded.
- private subnet — A subnet with no route to an internet gateway, so nothing on the internet can start a connection to resources inside it.
- least privilege — Giving every program and person only the access they need, and nothing more.
- minimal base image — A base image with as little inside as possible, such as Alpine, a slim variant or a distroless image, to shrink size and attack surface.
- vulnerability — A weakness in software or configuration that an attacker could use to cause harm.
- multi-stage build — A Dockerfile with several FROM stages, where later stages copy only what they need from earlier ones.
- non-root user — An ordinary user account with limited rights, which a container should run its service as.
- JRE — The JVM plus the Java standard library: everything needed to run a compiled Java program, but no compiler.
- setuid — A permission bit on an executable that makes it run with the file owner's identity instead of the identity of the user who started it.
- listening socket — A socket that has claimed a local address and port and is waiting to accept incoming connections.
- firewall — Software or a device that allows or blocks network traffic according to rules about direction, interface, protocol, port and source.
- entry point — Any place where something from outside can send input into a system, such as a web route, a message queue or a file upload.
Taught in
- Load Balancing and DNS — Cloud Infrastructure & Hyperscaler Architecture
- Least Privilege Enforcement & CIEM Architecture — Cloud Security & DevSecOps Engineering
- Vendor & Third-Party Risk Management Programs — Cybersecurity Fundamentals, GRC & Cryptography
- Environment, Secret Files And Runtime Restrictions — Docker Architecture & Production Containers
- Containerization Architecture: Multi-Stage Dockerfiles — Production Full-Stack Engineering
- Shipping in Scratch and Distroless Images — Concurrent Systems Programming with Go
- The Virtual Machine, The Kit And The Runtime — Modern Java: Virtual Threads & High-Throughput Services
- Packaging Into A Container — Modern Java: Virtual Threads & High-Throughput Services
- securityContext: Nonroot, Capabilities And Seccomp — Kubernetes: Production-Grade Container Orchestration
- Setuid, Setgid, And Root Through sudo — Linux Fundamentals & Systems Administration
- The Threat Model Habit — Application Security & Threat Modeling for Engineers
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- Container Security: Minimal Bases And Non Root — Application Security & Threat Modeling for Engineers