GDPR Art. 32 × NIS2 Art. 21
A fictitious scenario showing how Scutaria maps two distinct frameworks without forcing an artificial legal equivalence.
Mandatory Methodological Notice
- The scenario below is entirely fictitious. The organization, service, evidence, and decisions presented do not exist.
- This content illustrates a cross-analysis and traceability method. It does not constitute legal advice.
- It does not prove GDPR compliance, NIS2 compliance, or joint compliance of any real system.
- It demonstrates no legal equivalence between GDPR Article 32 and NIS2 Article 21.
- Any real conclusion requires a human, contextualized, and legally competent analysis.
Intersecting two frameworks
Each framework retains its integrity, its scope, and its evidence chain.
The origin of obligations
Regulation (EU) 2016/679 of 27 April 2016 (GDPR)
Art. 32 — Security of processing
Methodological paraphrase (non-verbatim) — the official text prevails
Official referencesTaking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risks, the controller and the processor implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.
- Act of
- Published in OJ L 119 of , p. 1
- CELEX 32016R0679
- ELI http://data.europa.eu/eli/reg/2016/679/oj
This demonstration aims for alignment with ELI; it does not claim systematic ELI implementation.
Directive (EU) 2022/2555 of 14 December 2022 (NIS2)
Art. 21 — Cybersecurity risk-management measures
Methodological paraphrase (non-verbatim) — the official text prevails
Official referencesMember States ensure that essential and important entities take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of network and information systems which those entities use for their operations.
- Act of
- Published in OJ L 333 of , p. 80
- CELEX 32022L2555
- ELI http://data.europa.eu/eli/dir/2022/2555/oj
This demonstration aims for alignment with ELI; it does not claim systematic ELI implementation.
Interpretation applied to the fictitious scenario
SO-001 The organization must implement security measures protecting personal data processed by the "MedPortal" service, based on the risks to the rights and freedoms of natural persons.
Scope strictly limited to personal data protection (confidentiality, integrity, availability).
Working draft — validation in progressSO-002 The organization must have implemented risk analysis and information security policies to protect the "MedPortal" service ensuring its critical business continuity.
Scope focused on information system security and service provision continuity (not just data).
Working draft — validation in progressMeeting points and divergences
Potential overlap
Both texts require technical and organizational measures proportionate to risks (risk-based approach).
Strict distinction
GDPR protects the rights of data subjects. NIS2 protects service continuity and information system resilience.
Rationale : The risk analysis process can serve as a common methodological core, but the evaluated risk scenarios differ (data breach vs. production halt).
This mapping indicates that the same security policy can contribute to both compliance paths, without automatic equivalence.
Applicability to the "MedPortal" system
RGPD / GDPR
Does the "MedPortal" service process personal data?
APPLICABLEMedPortal hosts and processes pseudonymized health data. Article 32 is fully applicable.
Fictitious decision.
NIS2
Is the organization operating "MedPortal" an essential or important entity under NIS2?
APPLICABLEHypothesis: The organization is classified as an "essential entity" (healthcare sector). MedPortal is a critical IS for its operations.
Hypothesis of subjection not legally verified in this demo.
Evaluation of the same evidence on two paths
The admissibility of evidence is assessed differently depending on the target.
Three distinct objects: the evidence validation (admissibility), its contribution to the coverage of each sub-obligation, and the human decision (section 07, DEC-001). Values that the narrative does not establish are shown as "To be confirmed".
EV-001 Governance document Information Systems Security Policy (ISSP)
Evidence limit : The ISSP sets theoretical rules.
Covers access management (useful for GDPR confidentiality). The ISSP documents the measures.
Covers business continuity management (useful for NIS2 resilience).
EV-002 Analysis report Risk Analysis (Unified DPIA)
Evidence limit : The document focuses exclusively on risks to individuals (privacy, discrimination).
Properly identifies risks to personal data.
Omits risks of service unavailability via ransomware affecting the supply chain, which are required under NIS2.
Coverage assessment by sub-obligation
RGPD / GDPR
The DPIA (EV-002) properly identifies risks to personal data. The ISSP documents the measures.
Evidence of effective implementation of technical measures (security tests) is missing.
Organizational measures are defined, but the effectiveness of technical measures is not demonstrated by a test (Art. 32(1)d).
Action: Provide a pentest report on MedPortal.
NIS2
The ISSP sets theoretical rules.
The risk analysis does not cover information system continuity (EV-002 does not cover this point). Incident response tests are absent.
Without a risk analysis covering the overall availability of the IS, the foundation of NIS2 Art. 21 is not satisfied.
Action: Perform and provide a comprehensive risk analysis including cyber threats to the continuity of the MedPortal service.
Separate examination to be continued
Asymmetrical evidence requests — no compliance stated
Maturity regarding GDPR Art. 32 is partial, requiring evidence of testing. Maturity regarding NIS2 Art. 21 is highly insufficient, as the initial risk analysis is not adapted to the directive's scope.
Linked objects
SRC-001SRC-002SO-001SO-002MAP-001AD-001AD-002EV-001EV-002COV-001COV-002RP-001
Automatic Equivalence Proposal Rejected
"The organization has drafted a Data Protection Impact Assessment (DPIA). Therefore, it simultaneously meets the risk analysis requirements of the GDPR (Art. 32) and NIS2 (Art. 21)."
Rejection motive
The scopes of application are not identical. The DPIA protects individuals; the NIS2 analysis protects the functioning of society and the economy. Evidence valid for one may be irrelevant for the other. The conclusion requires two attributed and contextualized reasoning paths.
Illustrative JSON Structure
Below is an illustrative example of the Scutaria data structure for this fictitious scenario. This JSON is not a production export. It contains no real, personal, or confidential data. The official references (CELEX, ELI) are real; the scenario is fictitious.
View the illustrative JSON structure
JSON Structure — illustrative example only
{
"_note": "ILLUSTRATIVE EXAMPLE ONLY — fictitious data, no legal value, not a production export",
"scenario": {
"id": "GDPR-NIS2-DEMO-001",
"fictitious": true,
"nature": "Fictitious methodological scenario (organisation, service, people, evidence and decisions); real regulatory sources"
},
"sources": [
{
"id": "SRC-001",
"realSource": true,
"regulation": "Regulation (EU) 2016/679 of 27 April 2016 (GDPR)",
"article": "Art. 32(1)",
"celex": "32016R0679",
"eli": "http://data.europa.eu/eli/reg/2016/679/oj",
"adoptionDate": "2016-04-27",
"ojPublication": {
"series": "L",
"number": 119,
"date": "2016-05-04",
"page": 1
},
"language": "en",
"textType": "methodologicalParaphrase",
"passage": "Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risks, the controller and the processor implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.",
"provenanceHash": "No real document fingerprint is exposed in this demonstration."
},
{
"id": "SRC-002",
"realSource": true,
"regulation": "Directive (EU) 2022/2555 of 14 December 2022 (NIS2)",
"article": "Art. 21(1)",
"celex": "32022L2555",
"eli": "http://data.europa.eu/eli/dir/2022/2555/oj",
"adoptionDate": "2022-12-14",
"ojPublication": {
"series": "L",
"number": 333,
"date": "2022-12-27",
"page": 80
},
"language": "en",
"textType": "methodologicalParaphrase",
"passage": "Member States ensure that essential and important entities take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of network and information systems which those entities use for their operations.",
"provenanceHash": "No real document fingerprint is exposed in this demonstration."
}
],
"subObligations": [
{
"id": "SO-001",
"sourceRef": "SRC-001",
"workStatus": "Working draft — validation in progress",
"limitScope": "Scope strictly limited to personal data protection (confidentiality, integrity, availability)."
},
{
"id": "SO-002",
"sourceRef": "SRC-002",
"workStatus": "Working draft — validation in progress",
"limitScope": "Scope focused on information system security and service provision continuity (not just data)."
}
],
"mapping": {
"id": "MAP-001",
"status": "UNCONFIRMED MAPPING",
"note": "Working mappings with documented rationale; their individual validation remains to be established.",
"limits": "This mapping indicates that the same security policy can contribute to both compliance paths, without automatic equivalence."
},
"applicabilityDecisions": [
{
"id": "AD-001",
"subObligationRef": "SO-001",
"answer": "APPLICABLE",
"assignedTo": "DPO (fictitious)",
"date": "2026-10-01",
"limits": "Fictitious decision."
},
{
"id": "AD-002",
"subObligationRef": "SO-002",
"answer": "APPLICABLE",
"assignedTo": "CISO (fictitious)",
"date": "2026-10-01",
"limits": "Hypothesis of subjection not legally verified in this demo."
}
],
"evidences": [
{
"id": "EV-001",
"label": "Information Systems Security Policy (ISSP)",
"limits": "The ISSP sets theoretical rules.",
"coverageContributions": [
{
"subObligationRef": "SO-001",
"validation": {
"status": "ADMISSIBLE",
"label": "Admissible"
},
"level": "TO_CONFIRM",
"note": "Covers access management (useful for GDPR confidentiality). The ISSP documents the measures."
},
{
"subObligationRef": "SO-002",
"validation": {
"status": "ADMISSIBLE",
"label": "Admissible"
},
"level": "TO_CONFIRM",
"note": "Covers business continuity management (useful for NIS2 resilience)."
}
],
"assignedTo": "Internal auditor (fictitious)",
"date": "2026-10-02"
},
{
"id": "EV-002",
"label": "Risk Analysis (Unified DPIA)",
"limits": "The document focuses exclusively on risks to individuals (privacy, discrimination).",
"coverageContributions": [
{
"subObligationRef": "SO-001",
"validation": {
"status": "ADMISSIBLE",
"label": "Admissible"
},
"level": "TO_CONFIRM",
"note": "Properly identifies risks to personal data."
},
{
"subObligationRef": "SO-002",
"validation": {
"status": "TO_CONFIRM",
"label": "Admissibility to be confirmed"
},
"level": "TO_CONFIRM",
"note": "Omits risks of service unavailability via ransomware affecting the supply chain, which are required under NIS2."
}
],
"assignedTo": "Internal auditor (fictitious)",
"date": "2026-10-03"
}
],
"coverages": [
{
"id": "COV-001",
"subObligationRef": "SO-001",
"evidenceRefs": [
"EV-001",
"EV-002"
],
"level": "PARTIAL",
"covered": "The DPIA (EV-002) properly identifies risks to personal data. The ISSP documents the measures.",
"missing": "Evidence of effective implementation of technical measures (security tests) is missing."
},
{
"id": "COV-002",
"subObligationRef": "SO-002",
"evidenceRefs": [
"EV-001",
"EV-002"
],
"level": "NOT_COVERED",
"covered": "The ISSP sets theoretical rules.",
"missing": "The risk analysis does not cover information system continuity (EV-002 does not cover this point). Incident response tests are absent."
}
],
"humanDecision": {
"id": "DEC-001",
"decision": "Asymmetrical evidence requests — no compliance stated",
"assignedTo": "Cross-functional compliance manager (fictitious)",
"date": "2026-10-05",
"linkedObjects": [
"SRC-001",
"SRC-002",
"SO-001",
"SO-002",
"MAP-001",
"AD-001",
"AD-002",
"EV-001",
"EV-002",
"COV-001",
"COV-002",
"RP-001"
]
},
"rejectedProposal": {
"id": "RP-001",
"proposal": "\"The organization has drafted a Data Protection Impact Assessment (DPIA). Therefore, it simultaneously meets the risk analysis requirements of the GDPR (Art. 32) and NIS2 (Art. 21).\" ",
"origin": "Assistance proposal (cross-analysis tool — outside the authority chain)",
"status": "Rejected",
"rejectionMotive": "The scopes of application are not identical. The DPIA protects individuals; the NIS2 analysis protects the functioning of society and the economy. Evidence valid for one may be irrelevant for the other. The conclusion requires two attributed and contextualized reasoning paths.",
"rejectedBy": "Cross-functional compliance manager (fictitious)",
"date": "2026-10-04"
}
}