Zero-Trust Implementation Gap

Zero-Trust Implementation Gap: Detailed Explanation with Case Laws

1. Introduction

The Zero-Trust Implementation Gap refers to the difference between the security objectives of a zero-trust cybersecurity framework and the extent to which those objectives are actually implemented within an organisation's information technology environment.

Zero Trust is a cybersecurity approach based on the principle that no user, device, application, network connection or system should automatically receive access merely because it is located within an organisation's internal network.

Instead, access must be continuously evaluated through identity verification, authentication, authorisation, device security, network conditions and other relevant risk factors.

The traditional cybersecurity model relied heavily on perimeter-based protection. Once a user or device entered an organisation's internal network, it could receive relatively broad access to internal systems. This approach became increasingly inadequate as organisations adopted cloud computing, remote working, mobile applications, outsourced IT services and interconnected financial platforms.

Zero Trust seeks to address these weaknesses through continuous verification, least-privilege access, micro-segmentation, strong identity management and continuous monitoring.

However, many organisations adopt only selected Zero-Trust technologies without implementing the complete security architecture. For example, an organisation may introduce multifactor authentication while continuing to operate excessive administrator privileges, unmanaged devices, poorly segmented networks and outdated legacy applications.

This difference between formal adoption and effective implementation constitutes the Zero-Trust Implementation Gap.

In Spain, the issue is particularly relevant to banks, insurance companies, payment service providers, public institutions, financial-market operators and other organisations processing sensitive personal and financial information.

There is no single Spanish statute formally titled the Zero-Trust Implementation Act. Instead, the relevant legal obligations arise from cybersecurity, data protection, financial-sector regulation, operational resilience and information-security requirements under Spanish, European Union and international frameworks.

2. Meaning and Concept of Zero Trust

Zero Trust is a cybersecurity architecture based on the principle commonly expressed as:

Never trust automatically; always verify access according to the applicable security requirements.

It does not mean that every connection must be treated as malicious. Rather, it means that access decisions must be supported by appropriate identity, security and contextual assessments.

The principal elements include:

Identity verification: Confirming the identity of users, administrators, service accounts and applications.

Multifactor authentication: Requiring additional authentication factors where appropriate.

Least-privilege access: Giving users only the permissions necessary to perform their duties.

Device security: Assessing whether devices meet security requirements before granting access.

Network segmentation: Separating systems and limiting unnecessary communication between them.

Continuous monitoring: Monitoring access, behaviour and security events.

Risk-based access decisions: Adjusting access permissions according to relevant security risks.

Data protection: Protecting sensitive information through encryption, access controls and appropriate handling procedures.

Incident response: Detecting, containing and investigating suspicious activities.

Continuous reassessment: Reviewing access permissions and security policies as circumstances change.

The implementation gap arises when these principles are not consistently translated into operational controls.

3. Historical Development of the Zero-Trust Concept

3.1 Traditional Perimeter-Based Security

Earlier cybersecurity systems primarily relied on firewalls, antivirus software and network boundaries.

Organisations attempted to protect internal systems by separating trusted internal networks from external networks.

Once an individual successfully entered the internal network, the organisation frequently treated that individual as relatively trustworthy.

This approach created several weaknesses:

Compromised accounts could access internal resources.

Malicious insiders could exploit excessive permissions.

Attackers could move laterally between systems.

Remote devices created additional security risks.

Cloud services weakened traditional network boundaries.

3.2 Emergence of Zero Trust

The term Zero Trust became widely associated with the work of John Kindervag at Forrester Research around 2010.

The approach challenged the traditional assumption that internal networks should automatically be trusted.

Later developments included the National Institute of Standards and Technology's Zero Trust Architecture publication.

NIST Special Publication 800-207, published in 2020, established an important technical reference framework.

It describes Zero Trust Architecture as an approach that focuses on protecting resources rather than relying exclusively on network location.

3.3 European Adoption

European organisations increasingly adopted Zero-Trust principles in response to:

Cloud computing expansion.

Remote working.

Ransomware attacks.

Supply-chain compromises.

Identity theft.

Financial-sector cyber risks.

Regulatory requirements concerning operational resilience.

In Spain, the development of Zero-Trust implementation has been influenced by EU cybersecurity legislation, GDPR, financial-sector supervisory requirements and the National Security Scheme.

4. The Zero-Trust Implementation Gap in Spain

Spain does not impose a single universal legal obligation requiring every organisation to implement a complete Zero-Trust Architecture.

However, organisations may have binding obligations to implement appropriate cybersecurity controls, access management, authentication, monitoring, incident response and risk-management systems.

The implementation gap arises when organisations fail to translate these legal and technical obligations into effective operational safeguards.

Common examples include:

4.1 Incomplete Identity and Access Management

An organisation may introduce multifactor authentication for ordinary employees but fail to apply equivalent protection to privileged accounts, administrators, service accounts or remote-access systems.

This creates opportunities for attackers to compromise high-value identities.

4.2 Excessive Privileges

Employees may retain access to financial databases, customer information or administrative systems even after their job responsibilities change.

This violates the security principle of least privilege and increases the risk of unauthorised access.

4.3 Inadequate Network Segmentation

An organisation may maintain a single interconnected network in which a compromised workstation can communicate with sensitive databases and critical applications.

Without appropriate segmentation, attackers may move laterally after obtaining initial access.

4.4 Weak Third-Party Access Controls

Banks and financial institutions frequently depend on external technology providers, cloud platforms, software developers and maintenance contractors.

If third-party access is not appropriately restricted and monitored, the organisation may face serious supply-chain cybersecurity risks.

4.5 Inadequate Continuous Monitoring

Some organisations rely on periodic security assessments without continuously reviewing access patterns, suspicious logins or unusual system activity.

This creates a gap between formal security policies and real-time security operations.

4.6 Legacy Systems

Older applications may not support modern authentication, device verification or granular access restrictions.

Organisations sometimes retain these systems because replacing them is expensive or operationally difficult.

However, legacy infrastructure must still be managed through appropriate compensating controls.

4.7 Weak Security Governance

A Zero-Trust programme may fail because responsibility is divided between IT departments, cybersecurity teams, compliance officers and senior management without clear accountability.

A successful programme requires coordinated governance, documented responsibilities and measurable security outcomes.

5. Spanish Legal Framework Governing Zero-Trust Implementation

Although Zero Trust is not a separately codified legal obligation in Spain, several legal instruments establish requirements that overlap with its principles.

5.1 Organic Law 3/2018 on Personal Data Protection and the Guarantee of Digital Rights

Organic Law 3/2018 supplements the GDPR in Spain.

It regulates personal data protection and establishes domestic provisions concerning the exercise of data-protection rights.

Zero-Trust controls are relevant because organisations processing personal data must protect that information against unauthorised access, unlawful processing and accidental loss.

The law must be interpreted together with the GDPR.

5.2 Regulation (EU) 2016/679: General Data Protection Regulation

The GDPR is one of the most important legal sources relevant to Zero-Trust implementation.

Article 5(1)(f) requires personal data to be processed in a manner that ensures appropriate security, including protection against unauthorised or unlawful processing and accidental loss, destruction or damage.

Article 24 requires controllers to implement appropriate technical and organisational measures to ensure and demonstrate compliance.

Article 25 establishes data protection by design and by default.

Article 32 requires appropriate technical and organisational security measures, taking account of the state of the art, implementation costs, the nature and scope of processing, context, purposes and risks.

These provisions are particularly relevant to:

Strong authentication.

Role-based access controls.

Encryption.

Access logging.

Continuous security monitoring.

Privileged-account management.

Incident response.

Periodic security testing.

A failure to implement appropriate access controls may result in GDPR liability where the circumstances establish a breach of the applicable obligations.

5.3 Law 36/2015 on National Security

Law 36/2015 establishes the Spanish national security framework.

It provides a basis for national security planning and coordination, including the protection of essential interests and critical capabilities.

Its relevance to Zero Trust is indirect but important where cybersecurity risks affect national security or critical infrastructure.

5.4 Royal Decree 311/2022: National Security Scheme

Royal Decree 311/2022 regulates the National Security Scheme (Esquema Nacional de Seguridad or ENS).

The ENS establishes security principles and minimum requirements for information systems within its scope, particularly public-sector systems and relevant service providers.

Its security requirements include:

Access control.

Identification and authentication.

Protection of communications.

Activity logging.

Incident management.

Security monitoring.

Risk assessment.

Operational continuity.

Supply-chain security.

These requirements are closely aligned with important Zero-Trust principles.

However, ENS applicability depends on the organisation and system concerned. It should not automatically be assumed that every private company is directly subject to every ENS requirement.

5.5 Law 11/2022, General Telecommunications Law

Law 11/2022 regulates the Spanish telecommunications sector.

It contains obligations relevant to telecommunications networks, service providers, security and regulatory supervision.

Its relevance to Zero Trust arises from the need to protect communications infrastructure and services against security threats.

5.6 Royal Decree-Law 12/2018 on Network and Information Systems Security

Royal Decree-Law 12/2018 implemented Spain's original NIS framework.

It established cybersecurity obligations for operators of essential services and relevant digital service providers.

The framework was subsequently affected by the EU's NIS2 Directive and the continuing development of Spanish implementation measures.

The current applicability of particular obligations must therefore be assessed in light of the updated EU and Spanish legal framework.

5.7 Directive (EU) 2022/2555: NIS2 Directive

The NIS2 Directive strengthened cybersecurity obligations for entities operating in important and essential sectors.

Its requirements include:

Risk analysis and information-system security policies.

Incident handling.

Business continuity.

Supply-chain security.

Security in network and information systems acquisition and maintenance.

Vulnerability handling and disclosure.

Access-control policies.

Multifactor authentication where appropriate.

Cybersecurity training.

Zero-Trust implementation can provide a practical approach for meeting several of these security objectives.

However, the NIS2 Directive does not require every covered entity to adopt a product or architecture formally marketed as Zero Trust.

5.8 Regulation (EU) 2022/2554: Digital Operational Resilience Act

The Digital Operational Resilience Act (DORA) became applicable on 17 January 2025.

It establishes a comprehensive framework for digital operational resilience in the EU financial sector.

DORA applies to a wide range of financial entities, subject to its scope and specific exemptions.

Its requirements concern:

ICT risk management.

Protection and prevention.

Detection of ICT incidents.

Response and recovery.

Backup and restoration.

Digital operational resilience testing.

ICT third-party risk management.

Reporting of major ICT-related incidents.

Zero-Trust principles are particularly relevant to identity management, access restrictions, network security, monitoring and third-party controls.

DORA is especially important for Spanish banks, investment firms, insurance companies and other covered financial entities.

6. Zero Trust and Spanish Banking Regulation

Spanish banks operate within a detailed legal framework governing cybersecurity, operational risk and financial stability.

Law 10/2014 on the regulation, supervision and solvency of credit institutions provides an important domestic regulatory framework.

Royal Decree 84/2015 develops aspects of the legal regime governing credit institutions.

Banco de España exercises supervisory responsibilities under the applicable Spanish and European framework.

For significant institutions within the Banking Union, the ECB exercises direct prudential supervision under the Single Supervisory Mechanism.

Zero-Trust principles support the management of operational and ICT risks by helping institutions:

Restrict access to customer-account databases.

Secure administrator privileges.

Monitor suspicious employee activity.

Restrict third-party system access.

Protect payment-processing infrastructure.

Prevent unauthorised lateral movement.

Secure remote banking operations.

Reduce the consequences of compromised credentials.

A bank that formally claims to follow Zero Trust but maintains unrestricted privileged access may still have serious operational and regulatory weaknesses.

7. Zero-Trust Implementation Gap and GDPR Liability

The relationship between Zero Trust and the GDPR is particularly important because inadequate access controls may expose personal information.

For example, a financial institution may maintain customer records containing names, addresses, account information, identification documents and transaction histories.

If employees or external service providers can access these records without appropriate authorisation, the organisation may fail to satisfy the GDPR's security requirements.

Article 32 requires security measures appropriate to the risks.

However, the GDPR does not establish a universal technical checklist requiring every controller to use the same security architecture.

The legal assessment depends on the processing activities, risks, available technology and the measures actually implemented.

A Zero-Trust system may help demonstrate compliance, but adopting a Zero-Trust label does not automatically establish GDPR compliance.

8. Important Case Laws Relevant to Zero-Trust Implementation

There is no widely recognised Spanish or EU judgment establishing a standalone legal doctrine called the Zero-Trust Implementation Gap.

Nevertheless, several judgments concerning cybersecurity, data protection, access controls and organisational security provide important legal guidance.

8.1 Wirtschaftsakademie Schleswig-Holstein, C-210/16

Case: Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein v Wirtschaftsakademie Schleswig-Holstein GmbH, CJEU, Case C-210/16, judgment of 5 June 2018.

The case concerned the responsibility of an administrator of a Facebook fan page for certain processing of personal data.

The CJEU held that the administrator could be considered a joint controller together with Facebook in relation to the processing activities concerned.

Importance for Zero Trust:

Organisations cannot automatically avoid data-protection responsibilities by relying on external technology providers.

Responsibilities must be assessed according to actual influence over processing.

Third-party access and data-processing arrangements require appropriate governance.

The judgment is relevant to Zero-Trust programmes involving cloud providers, outsourced IT services and external platforms.

8.2 Fashion ID, C-40/17

Case: Fashion ID GmbH & Co. KG v Verbraucherzentrale NRW eV, CJEU, Case C-40/17, judgment of 29 July 2019.

The case concerned a website operator that embedded a Facebook social plugin, resulting in the collection and transmission of visitors' personal data.

The CJEU examined joint controllership and the responsibilities of website operators.

Importance for Zero Trust:

The judgment demonstrates that organisations must understand and govern data flows involving external services.

Zero-Trust implementation should therefore include:

Monitoring external integrations.

Restricting unnecessary data access.

Evaluating third-party service providers.

Identifying where personal information is transmitted.

Establishing appropriate responsibility arrangements.

8.3 Österreichische Post, C-300/21

Case: UI v Österreichische Post AG, CJEU, Case C-300/21, judgment of 4 May 2023.

The case concerned compensation for non-material damage resulting from an alleged GDPR infringement.

The CJEU held that a GDPR infringement alone does not automatically establish a right to compensation. A claimant must demonstrate damage and a causal connection with the infringement, although EU law does not permit a minimum seriousness threshold for non-material damage.

Importance for Zero Trust:

The judgment is relevant when security failures involving unauthorised access or disclosure lead to claims for compensation.

It clarifies that liability under Article 82 GDPR requires an infringement, damage and a causal link.

8.4 Natsionalna agentsia za prihodite, C-340/21

Case: VB v Natsionalna agentsia za prihodite, CJEU, Case C-340/21, judgment of 14 December 2023.

The case concerned a cyberattack against a Bulgarian public authority that resulted in the disclosure of personal data.

The CJEU examined the obligations of controllers under Article 32 GDPR and the circumstances in which non-material damage may be compensated.

The Court clarified that the occurrence of a cyberattack does not automatically prove that the controller's security measures were inappropriate. However, the controller must demonstrate that its measures were appropriate to the risks.

It also explained that a data subject's fear of possible misuse of personal data may, depending on the circumstances, constitute non-material damage.

Importance for Zero Trust:

This judgment is particularly relevant to the implementation gap because it emphasises that cybersecurity compliance must be assessed by examining the actual measures adopted.

Organisations should be able to demonstrate:

Risk-based access controls.

Appropriate authentication.

Security monitoring.

Protection of stored information.

Regular evaluation of security measures.

Effective incident-management procedures.

A written cybersecurity policy alone is insufficient if the actual security arrangements are inadequate.

8.5 Meta Platforms Ireland, C-252/21

Case: Meta Platforms Ireland Ltd v Bundeskartellamt, CJEU, Case C-252/21, judgment of 4 July 2023.

The case concerned the relationship between competition law and personal data processing by a digital platform.

The CJEU examined the legal conditions governing the processing of personal data and the relationship between the GDPR and competition law.

Importance for Zero Trust:

The judgment is relevant to organisations that combine extensive data processing with digital services.

It demonstrates the importance of lawful data processing, transparency and accountability in complex technological environments.

Although it is not a direct cybersecurity judgment, its reasoning is relevant to governance of access to personal and financial information.

8.6 CJEU Case C-311/18: Data Protection Commissioner v Facebook Ireland and Maximillian Schrems

Case: Data Protection Commissioner v Facebook Ireland Ltd and Maximillian Schrems, CJEU, Case C-311/18, judgment of 16 July 2020.

The judgment concerned international transfers of personal data and the protection required when data is transferred outside the European Economic Area.

The CJEU invalidated the EU-US Privacy Shield and examined the use of standard contractual clauses.

Importance for Zero Trust:

Organisations must assess the security and legal environment of international data transfers.

Third-party access to information must be properly controlled.

Data protection cannot be achieved solely through contractual documentation.

Technical and organisational safeguards must be evaluated in practice.

The judgment is relevant to cloud-based Zero-Trust systems involving international service providers.

9. The Zero-Trust Implementation Gap in Financial Institutions

Financial institutions face particular challenges because their systems process sensitive customer information and support critical financial operations.

9.1 Identity and Authentication Failures

Financial institutions may introduce multifactor authentication for customers while failing to apply equally strong protection to employees, administrators and service accounts.

This creates opportunities for credential theft and privilege abuse.

9.2 Privileged Access Management Failures

Administrator accounts often have access to sensitive systems.

If privileged accounts are not restricted, monitored and periodically reviewed, a compromised administrator account may expose large amounts of customer information.

9.3 Inadequate Third-Party Security

Banks depend on software providers, cloud services, payment processors and external maintenance contractors.

A failure to control third-party access may expose critical systems to supply-chain attacks.

9.4 Incomplete Network Segmentation

A bank may have separate customer-facing and internal systems but still allow unnecessary communication between critical applications.

This can increase the impact of a cyberattack.

9.5 Insufficient Monitoring

If institutions do not monitor unusual access patterns, suspicious transactions and abnormal system behaviour, attackers may remain undetected for extended periods.

9.6 Weak Incident Response

An organisation may have cybersecurity policies but lack practical procedures for isolating compromised accounts, disabling suspicious access and restoring affected systems.

This represents a significant difference between formal security adoption and operational implementation.

10. Regulatory Consequences of the Zero-Trust Implementation Gap

The failure to implement appropriate security measures may lead to several forms of legal and regulatory liability.

10.1 GDPR Administrative Fines

Under Article 83 GDPR, supervisory authorities may impose administrative fines for infringements of the Regulation.

The amount depends on the nature, gravity and duration of the infringement, the degree of responsibility, the measures taken to mitigate damage and other statutory factors.

10.2 Compensation Claims

Article 82 GDPR provides a right to compensation where a person suffers material or non-material damage as a result of an infringement of the GDPR.

A claimant must establish the relevant infringement, damage and causal connection.

10.3 Financial Supervisory Measures

Financial institutions may face supervisory measures where weaknesses in ICT risk management or operational resilience breach applicable regulatory requirements.

DORA establishes specific obligations for covered financial entities and provides a supervisory framework for their enforcement.

10.4 Contractual Liability

An organisation may also face contractual claims where inadequate security measures result in breach of contractual obligations.

The Spanish Civil Code, particularly Articles 1101 and 1106, provides the general framework for contractual liability and compensation for legally recoverable losses.

10.5 Criminal Liability

In serious circumstances, cyber incidents may involve criminal offences under the Spanish Criminal Code.

Depending on the conduct, relevant provisions may include:

Article 197: Certain unlawful acts involving the discovery and disclosure of secrets and personal information.

Article 197 bis: Unauthorised access to computer systems and related conduct.

Articles 264 and following: Damage to computer systems and data.

Criminal liability depends on the specific elements of the offence and cannot be presumed merely because an organisation has experienced a cybersecurity incident.

11. Practical Example: Zero-Trust Failure in a Spanish Bank

Consider a Spanish bank that introduces multifactor authentication for customer accounts but does not implement adequate controls for employees and external IT contractors.

An attacker obtains the credentials of an external contractor.

Because the contractor's account has excessive privileges and is not restricted to specific systems, the attacker gains access to internal financial databases.

The attacker then accesses customer information and transfers data to an external server.

This incident may reveal several implementation failures:

Inadequate identity verification.

Excessive privileges.

Failure to restrict third-party access.

Inadequate network segmentation.

Insufficient monitoring.

Weak incident-response arrangements.

The bank may face regulatory scrutiny under GDPR, DORA and applicable Spanish banking legislation.

If customers suffer compensable damage, claims may also arise under Article 82 GDPR or relevant national legal provisions.

The incident demonstrates that multifactor authentication alone does not constitute a complete Zero-Trust architecture.

12. Measures to Close the Zero-Trust Implementation Gap

Spanish organisations should adopt a structured approach to implementing Zero-Trust principles.

12.1 Establish a Comprehensive Identity Framework

Every user, device, application and service account should have an identifiable security profile.

Authentication should reflect the sensitivity of the system and the level of risk.

12.2 Apply Least-Privilege Access

Permissions should be restricted to what is necessary for each user's responsibilities.

Privileged access should receive enhanced protection and regular review.

12.3 Introduce Network Segmentation

Sensitive databases, payment systems and administrative infrastructure should be separated through appropriate technical controls.

12.4 Secure Third-Party Relationships

Organisations should evaluate external providers, restrict contractor access, monitor outsourced activities and establish appropriate contractual security requirements.

12.5 Implement Continuous Monitoring

Security teams should monitor suspicious authentication attempts, unusual data transfers, privilege changes and abnormal system activity.

12.6 Conduct Regular Security Assessments

Organisations should evaluate the effectiveness of security controls through penetration testing, vulnerability assessments, access reviews and incident simulations.

12.7 Establish Accountability

Senior management, cybersecurity teams, compliance departments and data-protection officers should have clearly defined responsibilities.

12.8 Maintain Evidence of Compliance

Organisations should preserve relevant security policies, access logs, risk assessments, incident reports and audit records.

This documentation can help demonstrate compliance with GDPR, DORA and other applicable legal requirements.

13. Future Developments

The Zero-Trust Implementation Gap is likely to become increasingly important as financial services become more digital and interconnected.

Several developments will influence its future:

Artificial Intelligence: Automated systems may improve threat detection but also create new risks involving identity manipulation, automated attacks and unauthorised access.

Cloud Computing: Organisations will need stronger controls over cloud identities, application permissions and external service providers.

Digital Payments: Payment systems will require continuous authentication, transaction monitoring and protection against account compromise.

Operational Resilience: DORA will continue to influence the management of ICT risks within the European financial sector.

Cybersecurity Regulation: NIS2 and other EU cybersecurity initiatives will strengthen the importance of risk-based security governance.

Supply-Chain Security: Organisations will increasingly need to evaluate the cybersecurity practices of technology suppliers and outsourced service providers.

The development of Zero Trust should therefore be understood as a continuing process rather than a one-time technological implementation.

14. Conclusion

The Zero-Trust Implementation Gap represents the difference between an organisation's stated commitment to Zero-Trust cybersecurity and the actual effectiveness of its security controls.

In Spain, this issue is governed through a combination of EU data-protection legislation, Spanish cybersecurity rules, financial-sector regulation and operational-resilience requirements.

The GDPR, particularly Articles 5, 24, 25 and 32, establishes important requirements for protecting personal data. DORA strengthens ICT risk-management obligations for financial entities, while the National Security Scheme provides a security framework for public-sector systems and other systems within its scope.

Judicial decisions such as Wirtschaftsakademie, Fashion ID, Österreichische Post, Natsionalna agentsia za prihodite and Schrems II demonstrate the importance of accountability, appropriate security measures, third-party governance and effective data protection.

However, none of these judgments establishes a standalone legal doctrine called the Zero-Trust Implementation Gap. They provide legal principles that can be applied when assessing failures in the implementation of modern cybersecurity controls.

Ultimately, effective Zero-Trust implementation requires more than multifactor authentication or the purchase of cybersecurity software. It requires continuous identity verification, least-privilege access, secure devices, network segmentation, third-party risk management, monitoring, incident response and demonstrable organisational accountability.

For Spanish financial institutions, closing this gap is essential to protecting customer information, maintaining operational resilience, satisfying regulatory obligations and preserving confidence in the financial system.

15. Important Legal Authorities and Case Laws

A. Spanish Legislation

Spanish Constitution of 1978.

Organic Law 3/2018 on Personal Data Protection and the Guarantee of Digital Rights.

Law 10/2014 on the Regulation, Supervision and Solvency of Credit Institutions.

Royal Decree 311/2022 regulating the National Security Scheme.

Royal Decree-Law 12/2018 on the Security of Networks and Information Systems.

Law 36/2015 on National Security.

Law 11/2022, General Telecommunications Law.

Spanish Civil Code, Articles 1091, 1101, 1106 and 1255.

Spanish Criminal Code, Articles 197, 197 bis and 264 and following.

B. European Union Legislation

Regulation (EU) 2016/679 – General Data Protection Regulation.

Directive (EU) 2022/2555 – NIS2 Directive.

Regulation (EU) 2022/2554 – Digital Operational Resilience Act.

Regulation (EU) No 1024/2013 – Single Supervisory Mechanism.

Directive (EU) 2016/1148 – Original NIS Directive, historically relevant to the development of European cybersecurity regulation.

C. Important Judicial Decisions

Wirtschaftsakademie Schleswig-Holstein, C-210/16, 5 June 2018 – Joint controllership and responsibility for personal data processing.

Fashion ID, C-40/17, 29 July 2019 – Data protection responsibilities involving embedded third-party technology.

Data Protection Commissioner v Facebook Ireland and Schrems, C-311/18, 16 July 2020 – International data transfers and safeguards for personal information.

Österreichische Post, C-300/21, 4 May 2023 – Compensation for material and non-material damage under Article 82 GDPR.

Natsionalna agentsia za prihodite, C-340/21, 14 December 2023 – Cyberattacks, appropriate security measures and compensation for data-protection infringements.

Meta Platforms Ireland, C-252/21, 4 July 2023 – Personal data processing, legal basis and the interaction between data protection and competition law.

Legal qualification: These decisions are not Spanish judgments establishing a specific Zero-Trust doctrine. They are CJEU authorities interpreting EU legislation applicable in Spain. Their relevance is to the legal obligations concerning security, personal data, accountability and third-party processing that may be supported by Zero-Trust architecture.

LawGratis provides pro bono legal aid and resources to empower communities. Join us in making justice reachable for everyone! Follow our community on Instagram, YouTube, Facebook, and LinkedIn.

LEAVE A COMMENT