security by design
/sɪˈkjʊə.rə.ti baɪ dɪˈzaɪn/noun
Security by design includes security in software requirements, architecture and development from the first design. The team continues assessing and reducing risks throughout the lifecycle.
We use security by design for this healthcare platform to protect patient data from the first architecture decisions.
With security by design, a team treats security as a regular part of software development. It identifies early which data and functions need protection, how they could be misused and which measures are appropriate. These decisions inform architecture, code and application management.
Security from the first design
The approach starts with requirements and design. A team can decide which data it really needs to store, who gets access and what happens if a component fails. It translates these decisions into measures such as strong Glossary · In briefauthenticationAuthentication is the process by which a system verifies the claimed identity of a user, device or application.Read more, limited permissions, Glossary · In briefencryptionEncryption converts readable data into encrypted data using an algorithm and a cryptographic key. Only the correct key can make the data readable again.Read more and secure defaults.
Security by design continues beyond design. During development, the team reviews changes, tests security measures and tracks Glossary · In briefdependencyA dependency is a software component or system that other software needs in order to build or run, such as a library, framework or external service.Read more. After a Glossary · In briefreleaseA release is an identifiable software version prepared to be made available to users. It brings together one or more checked changes.Read more, updates, Glossary · In briefmonitoringMonitoring systematically tracks software, infrastructure or processes through measurements and checks. Deviations can trigger alerts so an administrator can investigate.Read more and vulnerability fixes remain necessary. New features and changing threats can introduce new risks.
How it differs from adding security afterwards
If security is examined only just before launch, fundamental choices may already be difficult to change. Examples include a Glossary · In briefdata modelA data model describes which data a system records, how that data is related and which rules it must satisfy.Read more storing unnecessary personal data or an architecture giving one account excessive access. Security by design reveals these risks earlier so the team can address them during design and implementation.
The approach does not automatically make software secure or error-free. Even a carefully designed system can contain vulnerabilities. Glossary · In briefcode reviewA code review is an assessment of a code change by another developer. They check its behaviour, readability, and maintainability, among other things, before the change is merged.Read more, security tests, updates and periodic Glossary · In briefsecurity auditA security audit is a structured examination of a digital system's security. The auditor assesses technical measures and processes against agreed requirements and records findings.Read more remain necessary. Security by design describes when and how security is considered; it is not a one-off check or guarantee.