Glossary
Security by design
Definition
Security by design considers protection from the start of a product or process, rather than adding it after decisions are fixed.
It treats protection as an early design requirement and reduces avoidable exposure through the way a product or process is built. Design choices still need implementation checks and maintenance, and do not guarantee a defect-free product.
A customer may include “Security by design” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Security by design makes protection a requirement while a product or process is being planned. It asks how misuse could occur, which information needs protection and which design choices can remove avoidable exposure. The aim is to reduce dependence on customers finding and fixing preventable weaknesses themselves.
For software, this can influence account permissions, data separation and the way sensitive actions are approved. It is not a claim that a product has no vulnerabilities. Design choices still need implementation checks and maintenance.
Imagine a small supplier building a client portal. Designing each customer account to access only its own documents is a basic security requirement. Adding a warning to staff after the portal exposes every customer's files would not address the design problem.
Name the threat addressed by each design choice and check implementation through testing and maintenance. A sound design can still be undermined by unsafe defaults or later changes; the phrase alone does not prove how the product works.