Security by design
Statement
Security is integrated into the design, development, deployment and operation of digital solutions and public services from the outset and throughout their lifecycle, ensuring appropriate protection of information, systems and services, including their confidentiality, integrity and availability.
Identifier |
|
|---|---|
Category |
|
Interoperability layers |
|
Governance model |
|
Influence on DPS lifecycle |
|
Influence on DPS attributes |
|
Scope |
Business agnostic |
ELAP release |
4.0.0 |
Rationale
Security should be treated as an inherent architectural concern rather than as a set of measures added after a solution has been designed. Security requirements and controls should therefore be considered throughout the entire lifecycle of digital solutions and public services and be proportionate to the identified risks.
Security by Design encompasses the protection of information, systems and services, including their confidentiality, integrity and availability, together with other relevant security properties such as authenticity and non-repudiation. Confidentiality protects sensitive information against unauthorised access and disclosure, while integrity protects information against unauthorised or improper modification, corruption or destruction and provides assurance that information has not been improperly altered during its storage, processing or exchange. Non-repudiation supports accountability by providing verifiable evidence of relevant actions or transactions, helping to ensure that their origin, submission, receipt or approval cannot subsequently be unjustifiably denied.
Integrating these security considerations from the outset reduces vulnerabilities and the risks of unauthorised access, disclosure, alteration, loss or disruption. It contributes to maintaining trust in digital public services, supports secure information exchange across organisational boundaries, improves resilience and facilitates compliance with applicable security, cybersecurity and other regulatory requirements.
Implications
Public administrations should identify security requirements and risks from the earliest stages of solution design and review them throughout the solution lifecycle. Appropriate organisational and technical security measures should be incorporated into the architecture according to the nature of the information and services concerned and the identified risks.
Solutions should protect sensitive information against unauthorised access and disclosure and protect information against unauthorised or improper modification, corruption and destruction. Appropriate measures should include, where applicable, information classification, access controls based on roles and responsibilities, secure authentication and authorisation mechanisms, and appropriate cryptographic mechanisms for information at rest and in transit.
Solutions should incorporate mechanisms that enable the integrity and authenticity of information to be verified, particularly when information is exchanged between systems or organisations. Where accountability for specific actions or transactions is required, solutions should also provide appropriate verifiable evidence supporting non-repudiation. Depending on the context and level of assurance required, this may include cryptographic mechanisms, digital signatures, qualified trust services, secure logging and audit mechanisms supporting integrity, authenticity and non-repudiation.
Changes to information and relevant system resources should be appropriately controlled and, where required, traceable. Logging, audit trails and monitoring mechanisms should support the detection and investigation of unauthorised modifications and other security incidents and provide appropriate accountability.
Security measures should address relevant security properties, including confidentiality, integrity, availability, authenticity and non-repudiation, according to the needs and risk profile of the service. Architectures should also support secure information exchange across organisational boundaries and appropriate identity and trust management mechanisms.
Security should be continuously maintained through appropriate monitoring, vulnerability and incident management, auditing, testing, updating and regular review of security controls. Security responsibilities should be clearly established, and relevant personnel should have appropriate security awareness and training.
Source
Security and Privacy Underlying Principle (8) of the European Interoperability Framework (EIF)
The European Interoperability Framework is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services.