Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Security by design means treating security as an architectural requirement from the first sketch, rather than a set of controls bolted on once the system already works.

What Is Security by Design?
Security by design means the security properties of a system are decided while the system is being designed, by the people designing it, and are treated as requirements rather than as a review gate near the end. The alternative—building the thing, then asking a security team what is wrong with it—produces findings that arrive when the architecture is already fixed and the release date is three weeks away.
Jerome Saltzer and Michael Schroeder set out eight design principles in 1975, and most of them still describe the difference between a system that resists attack and one that does not:
The NCSC’s secure design principles cover similar ground in modern language, organised around establishing context, making compromise difficult, making disruption difficult, making compromise detection easier, and reducing the impact of compromise.
The principles become real through ordinary engineering practice. Security requirements are written into the backlog as acceptance criteria, with abuse cases alongside use cases. Threat modelling happens at design review for anything that crosses a trust boundary. Authentication, authorisation, logging, and secrets handling come from shared libraries rather than being reimplemented per service. Dependency scanning, static analysis, and secret detection run in the pipeline, and a failing security gate stops the build in the same way a failing unit test does.
Two shifts have changed the conversation recently. The first is language choice: the joint CISA and NSA guidance published in December 2023 pressed developers towards memory-safe languages, after years of analysis showing that around 70% of serious vulnerabilities in large C and C++ codebases stem from memory safety errors. The second is supply chain provenance—signed builds, pinned dependencies, and a software bill of materials—which only works if it is designed into the pipeline rather than produced by hand for an audit.
Article 25 of UK GDPR makes data protection by design and by default a legal obligation for controllers. It requires appropriate technical and organisational measures, such as pseudonymisation and data minimisation, to be implemented both when determining the means of processing and during the processing itself. The ICO’s guidance is explicit that this cannot be satisfied by a privacy review at the end of a project, and a data protection impact assessment under Article 35 is the usual vehicle for showing the thinking.
Other regimes point the same way. The NIS Regulations 2018 are assessed against the NCSC Cyber Assessment Framework, which expects security to be considered in system design. PCI DSS v4.0 requires secure software development practices and threat identification during design for in-scope applications. For financial entities, DORA requires ICT systems to be designed for resilience rather than retrofitted.
The economics are well understood and routinely ignored. Fixing a design flaw after release costs many times what it costs to change a diagram, and some flaws—an authorisation model that trusts a client-supplied identifier, a protocol with no replay protection—cannot be patched without rewriting the feature. Teams nevertheless defer security work because the deadline is visible and the breach is hypothetical.
What breaks the pattern is making the secure route the path of least resistance: templates, platform guardrails, and golden paths that give developers authentication, logging, and encryption for free. Pair that with secure by default configuration and most teams get better outcomes from less effort. If you want design decisions challenged before they are built, our infrastructure and architecture review services do exactly that.
At the point where requirements and architecture are being decided, not at the pre-release review. The most expensive findings are design flaws, and a design flaw discovered after launch often cannot be patched without rebuilding the feature. A short threat modelling session at design review catches most of them for the cost of an hour.
They overlap but are not identical. Shifting left usually means running security testing earlier in the pipeline, which is mostly about finding implementation bugs sooner. Security by design concerns the architecture itself: trust boundaries, authorisation models, failure behaviour, and data flows. Automated scanning will not find a flawed authorisation model, but a design review will.
That controllers implement appropriate technical and organisational measures, such as pseudonymisation and data minimisation, both when deciding how processing will work and while it is running, and that by default only the personal data necessary for each purpose is processed. The ICO expects evidence of this thinking, typically through a data protection impact assessment and documented design decisions.
Use structure rather than expertise. Keep a short checklist of design questions for every change: what crosses a trust boundary, who is authorised to do what, what happens when a dependency fails, and what is logged. Adopt frameworks and libraries that provide authentication and output encoding by default, and use the NCSC and OWASP guidance as your reference.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.