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.
In more detail
Defaults do not compete with deadlines, because a default is what happens when nobody has time to think. Make the cautious setting the one you get for free, make the dangerous one an explicit, reviewable option, and refuse to start in production with a known-unsafe override.
Examples
The course inverts unsafe defaults such as debug on and certificate checks off, and adds a startup check that refuses to run in production with an unsafe override.DEFAULTS = {"debug": False, "verify_tls": True, "allowed_origins": [], "cookie_secure": True}Related terms
- deny by default — The rule that anything not explicitly allowed is refused, including when the facts needed to decide are missing.
- paved road — The documented, supported easy way to build and ship a service in an organisation, which most teams follow because it is easiest.
- debug mode — A setting that makes a service show detailed internals, such as stack traces and configuration, to help developers fix problems.
Taught in
- Secure Defaults — Application Security & Threat Modeling for Engineers
- Container Security: Minimal Bases And Non Root — Application Security & Threat Modeling for Engineers
- How To Stop Drowning In Findings — Application Security & Threat Modeling for Engineers