The revised Swiss Federal Act on Data Protection (nDSG, SR 235.1), which entered into force on 1 September 2023, and its implementing Data Protection Ordinance (DSV/OPDo) together constitute the most technically specific Swiss data-protection framework to date. For European organisations that must keep sensitive personal data outside the reach of foreign jurisdiction, the combination of Swiss legal structure, FDPIC enforcement expectations and the newly finalised NIST post-quantum cryptography standards FIPS 203, FIPS 204 and FIPS 205 creates a coherent and defensible architecture. This article maps those obligations precisely, for compliance officers, CISOs and IT decision-makers who need more than a general overview.
What the nDSG and DSV/OPDo Actually Require Technically
The nDSG and DSV/OPDo impose risk-proportionate technical and organisational measures (TOMs) rather than fixed algorithm mandates, but the FDPIC’s interpretive guidance makes the operational expectations concrete.
Article 8 nDSG establishes the principle of privacy by design and by default. The DSV/OPDo, in Articles 1 through 4, operationalises this by requiring controllers and processors to implement measures that, at minimum, ensure the confidentiality, integrity, availability and traceability of personal data. For sensitive personal data, defined in Article 5(c) nDSG to include health data, biometric data, data on religious or political views, and data on administrative or criminal proceedings, the bar is explicitly higher.
The four concrete technical categories the DSV/OPDo names are: pseudonymisation, encryption, access control, and logging of access and changes. Encryption must reflect the current state of technology. The FDPIC interprets “state of the art” by reference to recognised standards bodies, which in practice means NIST publications carry direct regulatory weight in Swiss supervisory assessments.
Mapping DSV/OPDo Obligations to NIST FIPS 203, 204 and 205
NIST published FIPS 203 (ML-KEM, Module-Lattice-Based Key Encapsulation Mechanism), FIPS 204 (ML-DSA, Module-Lattice-Based Digital Signature Algorithm) and FIPS 205 (SLH-DSA, Stateless Hash-Based Digital Signature Algorithm) as final standards in August 2024. These are the first post-quantum cryptography (PQC) standards carrying the weight of a US federal requirement, and they serve as the global technical benchmark that regulators worldwide, including the FDPIC, reference when assessing whether an operator’s cryptographic choices are current.
| DSV/OPDo Requirement | Conventional Baseline | PQC Implementation (NIST FIPS) |
|---|---|---|
| Confidentiality of data in transit and at rest | AES-256 + RSA-2048 or ECDH key exchange | AES-256 retained; key encapsulation replaced by ML-KEM (FIPS 203) |
| Authenticity and integrity of signed records | RSA-PSS or ECDSA | ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) for long-lived signatures |
| Access control with cryptographic identity | X.509 certificates with RSA or EC keys | Hybrid certificates combining classical and ML-DSA keys during transition |
| Traceability and audit logging | SHA-256 hash chains | SHA-3 family; SLH-DSA for tamper-evident log signatures |
The practical implication is that a sovereign infrastructure operator running Swiss-hosted services must, for new deployments involving sensitive personal data, demonstrate awareness of the quantum threat and a documented migration path to at least ML-KEM for key encapsulation. Legacy RSA-based key exchange is not automatically non-compliant today, but an operator who cannot explain why they have not yet migrated faces a harder conversation with the FDPIC during an inspection.
The Swiss Legal Architecture: Why IRSG Creates a Structurally Different Posture
Switzerland’s absence of a domestic compelled-disclosure statute equivalent to the US CLOUD Act or FISA Section 702 is not a regulatory gap but a deliberate structural feature that benefits data subjects whose information is held in Switzerland.
Under the Swiss Federal Act on International Mutual Assistance in Criminal Matters (IRSG, SR 351.1), any foreign request for personal data held by a Swiss entity must proceed through a formal mutual legal assistance (MLA) channel. The Swiss Federal Office of Justice reviews each request. Swiss courts can and do reject requests that conflict with Swiss data protection law or fundamental rights. There is no mechanism analogous to a National Security Letter, which in the US context requires neither judicial oversight nor disclosure to the target.
This contrasts directly with EU-based hosting. The EU e-Evidence Regulation (Regulation 2023/1543), which entered application in 2026, allows competent authorities in one EU member state to issue a European Production Order directly to a service provider established in another member state, bypassing the traditional MLA channel. For multinational regulated organisations, this creates a meaningful exposure: data held by an EU-based provider can be subject to a production order from any of 27 member states, with limited advance notice to the data subject or controller.
Switzerland is not an EU member state and is not subject to the e-Evidence Regulation. Combined with Switzerland’s constitutional protection of privacy under Article 13 of the Federal Constitution and the IRSG’s judicial-review requirement, this creates what practitioners correctly describe as a structurally stronger legal posture, not merely a different one.
FDPIC Enforcement Expectations and Documentation Practice
The FDPIC does not publish a named-algorithm list, but supervisory inspections and published guidance reveal consistent expectations for operators handling sensitive personal data at scale.
First, the RoPA under Article 12 nDSG must describe TOMs at a level of specificity sufficient for the FDPIC to assess whether they are proportionate. A description reading “data is encrypted” is insufficient. An acceptable entry names the algorithm (for example, AES-256-GCM for data at rest, ML-KEM-768 for key encapsulation in transit), the key management system, the rotation period, and the process for detecting and responding to key compromise.
Second, the FDPIC expects documented reviews of cryptographic choices at a cadence proportionate to the threat environment. Given the Federal Council’s 2024 Digital and Cyber Strategy, which explicitly acknowledges quantum computing as an emerging systemic risk, operators who last reviewed their cryptographic posture before the NIST PQC finalisation in August 2024 should treat that event as a mandatory review trigger.
According to IBM’s Cost of a Data Breach Report 2024, the average total cost of a data breach reached USD 4.88 million globally, the highest figure in the report’s history. The same report’s 2023 edition found that 45% of breaches involved data stored in cloud environments. These figures underline why the FDPIC frames encryption strength as a risk-management instrument rather than a formality.
FINMA, Healthcare and the Federal Council’s Quantum Position
For Swiss-regulated financial institutions, FINMA Circular 2023/1 on Operational Risks and Resilience adds a sector-specific layer. The circular requires supervised institutions to maintain a current inventory of critical systems, to apply state-of-the-art cyber controls, and to test resilience continuously. While the circular does not name post-quantum algorithms, its requirement to address emerging technology risks operates as a standing obligation to track and implement NIST PQC standards as they mature.
The Swiss Federal Council’s 2024 position paper on quantum computing risks, issued under the National Cyber Strategy, explicitly identifies the “harvest now, decrypt later” attack model as a near-term threat to long-lived sensitive data. Financial transaction records, medical histories and legal documents that must remain confidential for decades are precisely the categories at risk. The Federal Council’s guidance translates into a practical obligation for both FINMA-supervised institutions and cantonal health authorities: data classified as requiring long-term confidentiality should be encrypted under PQC algorithms before quantum-capable adversaries reach cryptographically relevant scale, a threshold most national security agencies place within the next ten to fifteen years.
PQC Encryption and the Schrems II Equivalence Test for EU Data Processed in Switzerland
When a Swiss processor handles EU personal data transferred under GDPR Standard Contractual Clauses (SCCs), the controller must conduct a Transfer Impact Assessment (TIA) confirming that Switzerland provides essentially equivalent protection to the EU, as required by the Court of Justice of the European Union’s Schrems II judgment (C-311/18, July 2020).
The two-dimensional test involves legal protection (absence of disproportionate government access) and technical protection (encryption strong enough to render intercepted data inaccessible). Swiss law satisfies the legal dimension through the IRSG framework described above. PQC-level encryption under FIPS 203 (ML-KEM) for key encapsulation and FIPS 204 (ML-DSA) for digital signatures satisfies the technical dimension by ensuring that even a successful traffic interception today cannot be decrypted by a quantum-capable adversary in the future.
The contractual obligations under the SCCs also require the Swiss processor to notify the EU controller promptly if it receives a governmental access request, to challenge such requests where legally possible, and to apply the TOMs described in Annex II of the SCC. A processor operating under nDSG and DSV/OPDo who documents PQC algorithm choices, key management and incident response in the RoPA and in the SCC Annex II can demonstrate compliance with both Swiss and EU requirements from a single documented framework, reducing audit overhead considerably.
FAQ
Does the revised Swiss FADP (nDSG) specify which encryption algorithms must be used?
The nDSG and DSV/OPDo do not mandate named algorithms by statute. They require state-of-the-art technical measures proportionate to the risk. The FDPIC interprets this by reference to recognised standards, making NIST FIPS publications, including FIPS 203, 204 and 205, the expected baseline for new deployments handling sensitive personal data.
Can a US authority compel a Swiss cloud provider to disclose data under the CLOUD Act or FISA 702?
No. Switzerland is not subject to the CLOUD Act or FISA 702. Any US request must proceed through the IRSG and the bilateral Swiss-US MLAT, where Swiss courts review each case. This is structurally different from EU-based providers whose US parent companies remain directly subject to US extraterritorial law.
How does PQC encryption satisfy the Schrems II essentially equivalent protection test for EU data transferred to Switzerland?
Schrems II requires both legal and technical protection. Switzerland’s IRSG eliminates compelled mass access equivalent to FISA 702, satisfying the legal dimension. ML-KEM (FIPS 203) and ML-DSA (FIPS 204) encryption satisfies the technical dimension by making intercepted data computationally inaccessible to future quantum-capable adversaries, addressing the harvest-now-decrypt-later threat that classical encryption cannot.
What does FINMA Circular 2023/1 require regarding cryptographic resilience?
FINMA Circular 2023/1 requires supervised institutions to apply state-of-the-art controls against cyber threats and to address emerging technology risks. Institutions whose threat models now include quantum-capable adversaries must document and implement a PQC migration plan to satisfy the circular’s operational resilience obligations, even though the circular does not name specific post-quantum algorithms.
How should a sovereign infrastructure operator document algorithm choices for an FDPIC inspection?
The RoPA under Article 12 nDSG must record the specific algorithm (for example ML-KEM-768 per FIPS 203), the key length, the key management procedure, the rationale for those choices relative to data sensitivity and threat horizon, and the review cycle. Inspectors assess whether documentation demonstrates conscious, risk-proportionate decision-making rather than default or legacy configurations.
Hoe Qsentinel dit oplost
Qsentinel is the managed Nextcloud Enterprise workspace, enhanced by Qsentinel with post-quantum encryption and sovereign private AI, hosted in Switzerland or on-premise, out of reach of the CLOUD Act.
