{ "release": "2026-11-06", "requirements": [ { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E1", "kind": "Evidence item", "title": "FIT ST (Wallet Security Specification)", "text": "Final version, claiming conformance to the Protection Profile; instantiates its operations; mirrors the environmental requirements table; identifies the functional certificate; states the TOE boundary and the architecture variant.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E2", "kind": "Evidence item", "title": "Functional certificate and report", "text": "The functional certificate or attestation for the same product and exact version, with the functional conformity assessment report where available.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E3", "kind": "Evidence item", "title": "Specification of the functionality", "text": "At the level of the interfaces and their parameters, including the interfaces with the WSCA-BE, the WSCD and the Wallet Provider backend.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E4", "kind": "Evidence item", "title": "Development process documentation", "text": "Including vulnerability and patch management.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E5", "kind": "Evidence item", "title": "Design documentation", "text": "At the level of the modules of the module decomposition of the Protection Profile: wallet core; WSCA/WSCD interface; optional remote signing module; presentation and proximity interface; modules specific to the architecture variant.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e5", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E6", "kind": "Evidence item", "title": "Security architecture description", "text": "Self-protection, secure communication channels, key management, attestation handling (Wallet Instance Attestation, Key Attestation), resilience mechanisms (obfuscation, anti-deobfuscation, integrity, debug and platform state detection, screen protection).", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e6", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E7", "kind": "Evidence item", "title": "Source code", "text": "Complete source code of the Wallet Instance, with its build instructions. Failure to provide it counts as an evaluation failure.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e7", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E8", "kind": "Evidence item", "title": "Setup and User Guide (SUG)", "text": "How to install, configure and use the Wallet Instance securely, in the language fixed in the evaluation plan.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e8", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E9", "kind": "Evidence item", "title": "Test samples and access", "text": "Installable builds identical to the production release, target devices or access to them, and test accounts or a working backend, including the WSCA-BE and WSCD access needed to operate the TOE.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e9", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E10", "kind": "Evidence item", "title": "Product identification data", "text": "Application identifier, version name, version code, build or release identifier, signing certificate fingerprint, and a cryptographic digest of the delivered package.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E11", "kind": "Evidence item", "title": "Third-party components", "text": "Libraries and SDKs with versions, as used in the build.", "section": "3 Evidence checklist", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=7" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E12", "kind": "Evidence item", "title": "Update mechanism description", "text": "How updates are produced, signed, distributed and verified, per software component.", "section": "3 Evidence checklist", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E13", "kind": "Evidence item", "title": "Risk assessment", "text": "The product developer's risk assessment for the specific architecture.", "section": "3 Evidence checklist", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E14", "kind": "Evidence item", "title": "Assurance information for components outside the TOE", "text": "WSCD certificate and report; WSCA-BE assurance information where outside the TOE.", "section": "3 Evidence checklist", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e14", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 3", "document_title": "NL-CS Evaluation Instruction for Evaluation Laboratories", "version": "RC1.0", "id": "E15", "kind": "Evidence item", "title": "Test to requirement mapping inputs", "text": "The product developer's own test evidence, if any, for the Protection Profile requirements.", "section": "3 Evidence checklist", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-3#e15", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part3-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VC1", "kind": "Audit criterion", "title": "Every release of the certified Wallet Instance is uniquely identified by applica…", "text": "Every release of the certified Wallet Instance is uniquely identified by application identifier, version name, version code and build or release identifier, and these match the identifiers on the functional certificate and in the FIT ST.", "section": "4.1 Version control (VC)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vc1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VC2", "kind": "Audit criterion", "title": "The source code and build configuration of every release are held under version …", "text": "The source code and build configuration of every release are held under version control with traceable history and controlled access, so that the delivered package can be related to a source revision.", "section": "4.1 Version control (VC)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vc2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VC3", "kind": "Audit criterion", "title": "The signing key and the signing process are controlled, and a change of the sign…", "text": "The signing key and the signing process are controlled, and a change of the signing key is notified to the CB before it is used.", "section": "4.1 Version control (VC)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vc3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VC4", "kind": "Audit criterion", "title": "The list of third-party components, libraries and SDKs per release is maintained…", "text": "The list of third-party components, libraries and SDKs per release is maintained.", "section": "4.1 Version control (VC)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vc4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CM1", "kind": "Audit criterion", "title": "Planned changes to the certified product are notified to the CB before implement…", "text": "Planned changes to the certified product are notified to the CB before implementation.", "section": "4.2 Change management (CM)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cm1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CM2", "kind": "Audit criterion", "title": "Every change is recorded with a description of all differences, not only those t…", "text": "Every change is recorded with a description of all differences, not only those the developer considers security relevant, so that a delta assessment is possible.", "section": "4.2 Change management (CM)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cm2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CM3", "kind": "Audit criterion", "title": "Each change is assessed for security impact, including against the list of chang…", "text": "Each change is assessed for security impact, including against the list of changes in [NP001] section 6.6 that shall not be concluded as covered without new analysis: the user authentication protocol or factors, the interface with the WSCA-BE or WSCD, key handling, attestation handling, resilience mechanisms, trusted list and revocation handling, target platform API level, signing key, distribution channel.", "section": "4.2 Change management (CM)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cm3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CM4", "kind": "Audit criterion", "title": "Changes to the TOE boundary, to the assumptions on the operational environment, …", "text": "Changes to the TOE boundary, to the assumptions on the operational environment, to the environmental requirements or to the identity or version of a certified component are identified as such and are not treated as covered by delta assessment.", "section": "4.2 Change management (CM)", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cm4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CM5", "kind": "Audit criterion", "title": "Changes to the target platform and to the variants for categories of end user de…", "text": "Changes to the target platform and to the variants for categories of end user devices are tracked, because wallet instances are expected to need frequent updates.", "section": "4.2 Change management (CM)", "page": 8, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Annex IV" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cm5", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "UD1", "kind": "Audit criterion", "title": "The product has a feature to perform updates of each software component, and the…", "text": "The product has a feature to perform updates of each software component, and the update process is described and operated as described.", "section": "4.3 Update delivery (UD)", "page": 8, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Annex IX" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#ud1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=8" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "UD2", "kind": "Audit criterion", "title": "Updates are produced from controlled builds, signed with the controlled key, and…", "text": "Updates are produced from controlled builds, signed with the controlled key, and the integrity and authenticity of an update is verified before installation.", "section": "4.3 Update delivery (UD)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#ud2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "UD3", "kind": "Audit criterion", "title": "The distribution channel is the one stated in the FIT ST and any change of chann…", "text": "The distribution channel is the one stated in the FIT ST and any change of channel is notified ([NP001] section 6.6).", "section": "4.3 Update delivery (UD)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#ud3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "UD4", "kind": "Audit criterion", "title": "The time between availability of a security update and its delivery to users, an…", "text": "The time between availability of a security update and its delivery to users, and the share of users on supported versions, are monitored.", "section": "4.3 Update delivery (UD)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#ud4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "UD5", "kind": "Audit criterion", "title": "The Wallet Instance's mechanism for verifying, per wallet unit, that the platfor…", "text": "The Wallet Instance's mechanism for verifying, per wallet unit, that the platform satisfies the assumptions on the end user device remains effective after updates, including the minimum platform version.", "section": "4.3 Update delivery (UD)", "page": 9, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Annex IV" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#ud5", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM1", "kind": "Audit criterion", "title": "The product developer has a vulnerability management policy and procedures that …", "text": "The product developer has a vulnerability management policy and procedures that take into account [ISO/IEC 30111], and that meet the requirements of Annex I to the Cyber Resilience Act as required by Article 5(7) of [IR 2981].", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Art. 5(3)", "CIR 2024/2981 Art. 5(7)" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM2", "kind": "Audit criterion", "title": "Sources of vulnerability information (public databases, dependency advisories, p…", "text": "Sources of vulnerability information (public databases, dependency advisories, platform security bulletins, researcher reports) are monitored and the monitoring is evidenced.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM3", "kind": "Audit criterion", "title": "Each vulnerability is assessed for severity and impact in the context of the cer…", "text": "Each vulnerability is assessed for severity and impact in the context of the certified wallet.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM4", "kind": "Audit criterion", "title": "Critical vulnerabilities and active exploits are notified to the CB within 24 ho…", "text": "Critical vulnerabilities and active exploits are notified to the CB within 24 hours of discovery, and high-severity vulnerabilities within 72 hours. Other vulnerabilities and changes are notified within the timeline of the scheme.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM5", "kind": "Audit criterion", "title": "A vulnerability impact analysis report is prepared for any vulnerability that af…", "text": "A vulnerability impact analysis report is prepared for any vulnerability that affects the software components of the wallet, with the content of Article 5(5), and transmitted to the CB without undue delay.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Art. 5(5)", "CIR 2024/2981 Art. 5(6)" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm5", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM6", "kind": "Audit criterion", "title": "Remediation is carried out commensurately with severity and potential impact, wi…", "text": "Remediation is carried out commensurately with severity and potential impact, with remediation delays recorded.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Art. 12(3)" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm6", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "VM7", "kind": "Audit criterion", "title": "Publicly known and remediated vulnerabilities are disclosed and registered in th…", "text": "Publicly known and remediated vulnerabilities are disclosed and registered in the repositories of Annex V.", "section": "4.4 Vulnerability management (VM)", "page": 9, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2981 Art. 5(9)" ], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#vm7", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=9" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CV1", "kind": "Audit criterion", "title": "The functional certificate remains valid for the certified version, and its susp…", "text": "The functional certificate remains valid for the certified version, and its suspension, withdrawal or expiry is notified to the CB without undue delay.", "section": "4.5 Continued validity of the certification basis (CV)", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cv1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=10" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CV2", "kind": "Audit criterion", "title": "The product developer monitors the validity, version and certification status of…", "text": "The product developer monitors the validity, version and certification status of the WSCD certificate and of other certificates recorded as environmental requirements, and notifies the CB of any change.", "section": "4.5 Continued validity of the certification basis (CV)", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cv2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=10" }, { "document": "NL-CS Part 4", "document_title": "NL-CS Audit Instruction for Operational Processes", "version": "RC1.0", "id": "CV3", "kind": "Audit criterion", "title": "The assumptions on the operational environment and the environmental requirement…", "text": "The assumptions on the operational environment and the environmental requirements of the Protection Profile remain valid for the lifetime of the certificate.", "section": "4.5 Continued validity of the certification basis (CV)", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-part-4#cv3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-part4-RC1.0_-_for_publ.pdf#page=10" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-01", "kind": "Condition", "title": "Vulnerability management", "text": "The UD shall receive regular, timely security updates addressing disclosed vulnerabilities in its first- and third-party components.", "section": "2.1 SC-01 – Vulnerability management", "page": 6, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=6" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-02", "kind": "Condition", "title": "Protections against exploits", "text": "The UD shall follow best practices to protect against hardware and software vulnerabilities in any of its components, like memory corruption attacks and supply chain attacks.", "section": "2.2 SC-02 – Protections against exploits", "page": 6, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=6" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-03", "kind": "Condition", "title": "Trusted firmware", "text": "The UD shall ensure that any code executed with elevated privileges (e.g., code of the bootloader, kernel, OS, and TEE) is trusted and cannot be rolled back to a less secure version.", "section": "2.3 SC-03 – Trusted firmware", "page": 6, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=6" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-04", "kind": "Condition", "title": "Secure random number generator", "text": "The UD shall implement a Random Number Generator (RNG) that provides unpredictable randomness to generate cryptographic keys and nonces (e.g., IVs or challenges), with each output of the RNG being only accessible to a single app.", "section": "2.4 SC-04 – Secure random number generator", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=7" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-05", "kind": "Condition", "title": "Secure cryptographic primitives", "text": "The UD shall provide standard-compliant and vulnerability-free implementations of all cryptographic primitives not implemented by the wallet app itself.", "section": "2.5 SC-05 – Secure cryptographic primitives", "page": 7, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=7" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-06", "kind": "Condition", "title": "Isolated environment for keys", "text": "The UD shall provide an isolated environment for cryptographic keys that 1. Provides means for key generation, key storage, key deletion/zeroization, and use of these keys for cryptographic operations, 2. Does not allow keys inside the environment to be exported / accessed from outside, 3. Provides key attestations as evidence that keys are actually stored in such an environment, and 4. Is purposely designed to mitigate physical and logical tamper and side-channel attacks against the above properties. The environment shall be provided by a dedicated SE or a hardware-backed TEE. As TEEs share their hardware with other processes on the UD, thus greatly increasing their attack surface, the following additional requirements shall apply for such implementations: 5. Only trusted code shall run inside the TEE supported by a secure boot mechanism (cf. SC-03 – Trusted firmware), 6. The memory of TEE shall be strongly isolated from accesses originating outside the isolated environment, and 7. The TEE shall still keep all its security properties in case the normal, rich OS is compromised.", "section": "2.6 SC-06 – Isolated environment for keys", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=8" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-07", "kind": "Condition", "title": "App sandbox", "text": "The UD shall be able to or provide means to isolate app processes, memory, cryptographic keys, and data from unauthorized accesses by other apps or system services. This shall include direct programmatic accesses but also indirect means, like side channels, drawing menus on top of other running apps, or by abusing accessibility services, as well as unwanted use by the UD itself (e.g., for backups or personalization).", "section": "2.7 SC-07 – App sandbox", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=10" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-08", "kind": "Condition", "title": "Integrity attestations", "text": "The UD shall implement a hardware-supported attestation mechanism to prove the integrity of the wallet app at runtime (i.e., that it has not been tampered with). Where OS modifications are likely, the UD shall also provide support in obtaining attestations about the integrity of the OS.", "section": "2.8 SC-08 – Integrity attestations", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=10" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-09", "kind": "Condition", "title": "Secure lock screen", "text": "The UD shall implement a hardware-backed lock screen requiring authentication before granting full access to the device that is resistant to bypass.", "section": "2.9 SC-09 – Secure lock screen", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=10" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-10", "kind": "Condition", "title": "Stored data confidentially", "text": "The UD shall protect app data stored at rest (i.e., in non-volatile memory) from extraction in plaintext by use of a secure memory encryption algorithm.", "section": "2.10 SC-10 – Stored data confidentially", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=11" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-11", "kind": "Condition", "title": "Secure networking", "text": "The UD shall provide the following means for secure networking: 1. Mechanisms to prevent all unencrypted/plaintext networking, and 2. Secure implementations of current network protocols (e.g., TLS 1.3) used for transactions, when not implemented by the wallet app itself.", "section": "2.11 SC-11 – Secure networking", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=11" }, { "document": "NL-CS-WI conditions", "document_title": "Conditions on the Underlying Mobile System for Wallet Instances in a remote HSM architecture", "version": "RC1.1", "id": "SC-12", "kind": "Condition", "title": "User Device privacy", "text": "The UD shall preserve the user’s privacy by not monitoring apps and not providing means to track app users in a way that would disclose sensitive information about the wallet to the UD’s vendor or third parties (e.g., using analytics or device-unique identifiers).", "section": "2.12 SC-12 – User Device privacy", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi-conditions#sc-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-conditions-RC1.1_-_for_publ.pdf#page=11" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_WI_INSTALL", "kind": "Functional security requirement (FSR)", "title": "Wallet Instance Installation and Activation", "text": "Wallet Instance Installation and Activation The WI-(TOE) shall be installed through an official application distribution channel (e.g. Google Play Store or Apple App Store) or through another distribution mechanism providing equivalent protection for the authenticity and integrity of the TOE. The WI-(TOE) shall: • During installation and activation, the TOE shall establish the required association with the Wallet Provider and shall securely provide the required initial information to the Wallet Provider. This information shall include, where applicable: o a unique identifier for the Wallet Instance; o the device model and operating-system version; and o the characteristics of the available keystores and WSCDs required to determine their suitability. • The TOE shall protect the confidentiality, integrity and authenticity of the initial information exchanged with the Wallet Provider. • The TOE shall verify that the installed TOE version and the underlying operating-system environment meet the applicable minimum-security requirements before activating the Wallet Instance. • If the TOE or operating-system environment does not meet the applicable security requirements, the TOE shall prevent activation or security-sensitive Wallet Unit operations and shall inform the User. • During activation, the TOE shall establish the required User authentication mechanisms in accordance with FSR_LOCAL_AUTH and FSP_REMOTE_AUTH. The WI-(TOE) shall provide a User-initiated factory reset function. Upon factory reset, the TOE shall: • delete the PIDs and electronic attestations held by the Wallet Instance; • delete transaction logs and Wallet Instance configuration and settings; • request secure deletion of associated cryptographic assets from the WSCA/WSCD and applicable secure keystores; • prevent the deleted Wallet Unit data and cryptographic assets from being subsequently used by the Wallet Instance; and • inform the User of the consequences of performing the factory reset before the reset is executed.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_wi_install", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=31" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_WIA", "kind": "Functional security requirement (FSR)", "title": "Wallet Instance Attestation", "text": "Wallet Instance Attestation The WI-(TOE) maintains and protects the Wallet Instance Attestation (WIA) and presents the WIA to PID Providers and Attestation Providers as required, enabling them to verify the security properties and status of the Wallet Unit. The TOE shall: • obtain the WIA from the Wallet Provider through an authenticated and integrity-protected communication channel; • verify the authenticity and integrity of the WIA before using or presenting it; • ensure that the WIA applies to the corresponding Wallet Instance; • verify that the WIA is technically valid and has not expired before use; • verify the revocation status of the Wallet Instance as indicated by the WIA before use, where required by the applicable ARF and technical specifications; • protect the WIA against unauthorized disclosure, modification, replacement and replay; and • use the WIA only for the applicable issuance processes and in accordance with the applicable OID4VCI requirements. The TOE shall provide the Wallet Instance Attestation together with the required Proof-of-Possession (PoP) during issuance, as specified by OID4VCI. The technical validity period of a WIA shall be less than 24 hours, measured from the time at which the Wallet Provider verified the integrity of the Wallet Instance to the expiry time indicated in the WIA. The technical validity period shall not be confused with the period for which the Wallet Provider maintains the revocation status of the Wallet Instance. If a WIA is stored in the private storage of the TOE, the WIA shall be protected against unauthorized access, modification and deletion. The TOE shall verify its integrity and validity before use. The TOE must prove its integrity to the Wallet provider before the Wallet provider generates a WIA.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_wia", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=33" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_KEY_ATTEST", "kind": "Functional security requirement (FSR)", "title": "Key Attestation", "text": "Key Attestation The WI-(TOE) maintains and protects Key Attestations (KA) and presents KAs to PID Providers and Attestation Providers, where required, to provide evidence of the security properties of the keys used by the Wallet Unit. The TOE shall: • verify the authenticity and integrity of a KA before using or presenting it; • ensure that a KA is associated with the WSCD in which the corresponding private key is stored; • ensure that the public key(s) attested by a KA correspond to private key(s) stored in the referenced WSCD; • use a KA only for the applicable issuance or re-issuance process and shall not reuse a KA beyond the permitted issuance process; • protect KAs against unauthorized disclosure, modification, replacement and replay; and • verify the validity and revocation status of the relevant KA, WSCD before using the KA where required by the applicable ARF and technical specifications. The TOE shall present a KA only to authorised PID Providers or Attestation Providers during applicable issuance processes and shall not present a KA to a Relying Party. If a KA is stored in the private storage of the TOE, the KA shall be protected against unauthorized access, modification and deletion. The TOE shall verify its integrity before use. The KA shall be used in accordance with the applicable OID4VCI proof mechanism and the cryptographic mechanisms specified by the applicable EU technical specifications.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_key_attest", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=33" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_PROTOCOL", "kind": "Functional security requirement (FSR)", "title": "Secure Wallet Protocol Processing", "text": "Secure Wallet Protocol Processing The WI-(TOE) implements or supports the applicable OpenID4VCI, OpenID4VP, ISO/IEC 18013-5, ISO/IEC 18013-7 and Digital Credentials API flows. The TOE shall protect the Wallet User and the Wallet Unit during these flows against phishing, relay, session-hijacking, replay and transaction-manipulation attacks. The TOE shall: • verify the authenticity and integrity of security-relevant protocol messages before processing them; • ensure that security-sensitive messages are bound to the applicable transaction and communication session; • prevent replay or reuse of security-sensitive protocol messages; • ensure that the transaction presented to the User corresponds to the transaction actually processed and transmitted; and • terminate or reject the affected transaction if the required security checks fail. The TOE shall implement the applicable protocol flows in accordance with the relevant ARF and technical specifications.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_protocol", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=34" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_TRUST_ANCHOR", "kind": "Functional security requirement (FSR)", "title": "Trusted Anchor Management", "text": "Trusted Anchor Management The WI-(TOE) maintains and protects the applicable trusted anchors (CA) required for verification of certificates and signed objects used by the Wallet Unit. The TOE shall: • use only trusted anchors obtained from authorised and applicable trust sources; • protect trusted anchors against unauthorized modification, deletion, replacement.; • verify the integrity and authenticity of trusted-anchor information before using it; • use the applicable trusted anchor to verify the authenticity and integrity of certificates and signed objects; • ensure that the trusted anchor used for verification is applicable to the type of certificate or signed object being verified; and • use trusted-anchor and certificate status information in accordance with the applicable ARF, Trusted List and technical specifications. If trusted-anchor information cannot be successfully authenticated or its integrity cannot be verified, the TOE shall not use that information for security-sensitive verification.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_trust_anchor", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=34" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_ACC_REG_CERT", "kind": "Functional security requirement (FSR)", "title": "Relying Party Access and Registration Certificate Validation", "text": "Relying Party Access and Registration Certificate Validation The WI-(TOE) verifies the Wallet-Relying Party Access Certificate (RP_ACC_CERT) and Wallet-Relying Party Registration Certificate (RP_REG_CERT) before processing a request for disclosure of a PID or electronic attestation from a Relying Party. The TOE shall: • authenticate and validate the RP_ACC_CERT, including its certificate chain, validity and applicable trust anchor; • authenticate and validate the RP_REG_CERT; • verify that the request is associated with the authenticated Relying Party; • verify that the requested attributes are consistent with the information contained in the RP_REG_CERT, where applicable; and • inform the User of the relevant information contained in the RP_ACC_CERT and RP_REG_CERT before disclosure, where required. • inform the User when authentication or validation of the Relying Party fails; • ensure that the authenticated Relying Party and the applicable Service are identified before the User approves a presentation; and • ensure that the Relying Party and Service information presented to the User corresponds to the authenticated RP Access Certificate and applicable RP Registration Certificate. If validation or authentication of the RP_ACC_CERT or RP_REG_CERT fails, the TOE shall not disclose the requested PID or electronic attestation.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_acc_reg_cert", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=34" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_ISSUANCE", "kind": "Functional security requirement (FSR)", "title": "Credential Issuance and Re-Issuance", "text": "Credential Issuance and Re-Issuance The WI-(TOE) shall securely process the issuance and re-issuance of PIDs and electronic attestations in accordance with the applicable ARF and technical specifications. The TOE shall: • request issuance only from an authenticated and authorised PID Provider or Attestation Provider; • provide the applicable WIA and KA information required for the issuance process; • verify that the received PID or electronic attestation corresponds to the credential requested; • verify the authenticity and integrity of the received PID or electronic attestation using the applicable trusted anchor; • verify the validity of the received PID or electronic attestation before storing it; • require User approval before storing the received PID or electronic attestation; • delete a received PID or electronic attestation if a required issuance verification fails and inform the User of the failure; • securely handle failed or refused issuance and re-issuance operations; and • ensure that obsolete credentials are no longer used for presentation where required by the applicable ARF and technical specifications.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_issuance", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_PRESENTATION", "kind": "Functional security requirement (FSR)", "title": "Credential Presentation", "text": "Credential Presentation The WI-(TOE) maintains and protects PIDs and electronic attestations of attributes and presents them to authorised Relying Parties and other authorised entities in accordance with the applicable ARF requirements. The TOE shall: • verify the authenticity and integrity of a PID or electronic attestation before storing or using it; • ensure that the PID or electronic attestation is associated with the corresponding Wallet Unit and, where applicable, the WSCA/WSCD; • protect stored PIDs and electronic attestations against unauthorized disclosure, modification, replacement and deletion; • verify the validity and revocation status of a PID or electronic attestation before presentation, where required by the applicable ARF and technical specifications; • ensure that a PID or electronic attestation is presented only to an authorised entity and only after the applicable authentication and authorization requirements have been satisfied; • allow the User to delete held PIDs and electronic attestations and inform the User of the deletion; and • allow the User to initiate deletion requests towards Relying Parties for PIDs and electronic attestations held by those Relying Parties, where supported by the applicable protocol. The TOE shall not present a PID or electronic attestation if its authenticity, integrity or validity cannot be successfully verified, or if the applicable Relying Party or other recipient has not been successfully authenticated. The TOE shall preserve the cryptographic binding of device-bound PIDs and electronic attestations to the corresponding Wallet Unit and shall ensure that such credentials cannot be used with an unauthorized or different Wallet Unit.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_presentation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_REVOCATION", "kind": "Functional security requirement (FSR)", "title": "The TOE shall regularly check the validity and revocation status of the security…", "text": "The TOE shall regularly check the validity and revocation status of the security-relevant data objects used by the Wallet Unit, including: • PIDs and electronic attestations; • the Wallet Instance Attestation (WIA); • Key Attestations (KA); • the WSCD used by the Wallet Unit; and • the Wallet Unit, where its revocation status is available. The TOE shall perform such checks before using a data object for a security-sensitive operation where required by the applicable ARF and technical specifications. The TOE shall use the applicable revocation or status information provided by the authorised provider and shall verify the authenticity and integrity of that information before relying on it. If the TOE determines that a PID, electronic attestation, WIA, KA, WSCD, or Wallet Unit has been revoked or suspended, the TOE shall: • prevent the affected data object or security function from being used where required by the applicable ARF and technical specifications; and • inform the User of the relevant revocation or suspension and its consequences. If the TOE cannot obtain or validate the required revocation or status information, it shall follow the applicable offline/failure-handling rules and shall not incorrectly treat an unverifiable status as valid where this would compromise the security of the Wallet Unit.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_revocation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=37" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSP_Q_SIGNATURE", "kind": "Functional security requirement (FSR)", "title": "Qualified Electronic Signature and Seal Creation", "text": "Qualified Electronic Signature and Seal Creation The Wallet Unit shall support qualified electronic signature and seal creation using a local, external or remotely managed Qualified Signature Creation Device (QSCD), as applicable. The Wallet Unit shall: • securely interface with the applicable Signature Creation Application (SCA) and QSCD; • ensure that signature or seal creation is performed only for the data approved by the User; • protect the integrity and confidentiality of the data and transaction information exchanged with the SCA/QSCD; • ensure that the signature or seal creation request is bound to the data approved by the User and cannot be replaced or manipulated; • where a remote QSCD is used, verify that the signature creation service is provided by an authorised QTSP, as applicable; and • provide the User with the result of the signature or seal creation, including notification of a failed operation. The WI-(TOE) shall support the mandatory signature and seal formats and interfaces applicable to the selected signature creation mechanism.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsp_q_signature", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_W2W", "kind": "Functional security requirement (FSR)", "title": "Wallet-to-Wallet Interaction", "text": "Wallet-to-Wallet Interaction The WI-(TOE) supports Wallet-to-Wallet (W2W) interactions between Wallet Units in accordance with the applicable ARF and technical specifications. The TOE shall: • establish an authenticated and protected communication channel with the other Wallet Unit; • verify the authenticity of the other Wallet Unit before processing a W2W request; • ensure that the User is informed of the requested attributes or electronic attestations before disclosure; • require User approval before disclosing any attributes or electronic attestations to the other Wallet Unit; • ensure that only the attributes or electronic attestations approved by the User are disclosed; • protect the W2W transaction against eavesdropping, modification, replay and transaction manipulation; and • log the W2W transaction in accordance with FSR_LOG_DATA. The TOE shall support both Holder Wallet Unit mode and Verifier Wallet Unit mode, where these functions are supported by the Wallet Unit. The TOE shall: • enter Holder Wallet Unit mode only following explicit User selection; • enter Verifier Wallet Unit mode only following explicit User selection; • inform the User when entering Holder Wallet Unit mode that this mode is intended for interaction with another natural person using a Wallet Unit; • return to normal Wallet Unit operation when the Wallet Unit is closed or after the applicable period of inactivity; • support W2W attestation presentation only through the applicable ISO/IEC 18013-5 proximity communication mechanisms; • when acting as a Verifier Wallet Unit, authenticate the Verifier and obtain the Verifier's approval before sending a presentation request; • limit the rate at which presentation requests can be sent in accordance with the applicable technical specification; • when acting as a Verifier Wallet Unit, verify received attestations and display the verified attributes to the Verifier; • not persistently store received attestations or attributes when acting as a Verifier Wallet Unit; and • when acting as a Holder Wallet Unit, authenticate the Verifier Wallet Unit before presenting the requested attributes, where the applicable cryptographic proof mechanism is available. If authentication of the Verifier Wallet Unit fails or cannot be performed, the TOE shall inform the User and shall prevent disclosure or allow the User to explicitly decide whether disclosure may proceed, in accordance with the applicable ARF and technical specification.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_w2w", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_MIGRATION", "kind": "Functional security requirement (FSR)", "title": "Wallet Unit Migration", "text": "Wallet Unit Migration The WI-(TOE) shall support migration of the Wallet Unit in accordance with the applicable ARF and Technical Specification 10. The TOE shall: • maintain an up-to-date Migration Object containing the transaction log information and the information required to restore the PIDs and electronic attestations present in the Wallet Unit; • ensure that the Migration Object does not contain WIA or KA; • for each PID and device-bound attestation, store in the Migration Object the information required to request re-issuance, including the attestation type, the PID Provider or Attestation Provider and the applicable service supply points; • ensure that the Migration Object does not contain attribute identifiers, attribute values or private keys associated with a PID or device-bound attestation; • for non-device-bound attestations, support the migration mechanism defined by the applicable ARF, including, where applicable, storing the information required for direct transfer or re-issuance; • allow the User to choose whether attribute identifiers and attribute values associated with a non-device-bound attestation are included in the Migration Object, where applicable; • delete the corresponding entry from the Migration Object when the User deletes a PID or attestation from the Wallet Unit; • store or export the Migration Object to an external or remote storage location supported by the Wallet Unit and selected by the User; • protect the confidentiality, integrity and authenticity of the Migration Object and prevent its use by anyone other than the User; • after installation of a new Wallet Instance, allow the User to import a Migration Object from a supported storage location; • allow the User to select the PIDs and attestations to be restored; • request re-issuance of selected PIDs and device-bound attestations from the respective PID Provider or Attestation Provider, using the normal issuance process; • request issuance of the PID before requesting issuance of other selected attestations; • for non-device-bound attestations, either restore the attestation directly from the Migration Object or request re-issuance, as applicable to the contents of the Migration Object; • ask the User whether the transaction log contained in the Migration Object shall be restored and, where approved, restore the log and append subsequent transactions to it; and • ensure that the migration and re-issuance processes use the applicable security mechanisms and interfaces defined for normal issuance. The TOE shall protect the Migration Object during creation, storage, export, import and processing against unauthorized disclosure, modification, replacement and replay.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_migration", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=39" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_DATA_DELETION", "kind": "Functional security requirement (FSR)", "title": "User Data Deletion Requests", "text": "User Data Deletion Requests The WI-(TOE) shall support User-initiated requests for deletion of User attributes previously presented to Relying Parties in accordance with the applicable ARF and technical specifications. The TOE shall: • allow the User to select one or more Relying Parties for which an attribute deletion request shall be submitted; • generate and transmit the deletion request using the applicable protocol and security mechanisms; • ensure that the deletion request identifies the relevant Relying Party and the data to which the request applies; • protect deletion requests against unauthorized modification and replacement; and • log the initiation and outcome of deletion requests in accordance with FSR_LOG_DATA.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_data_deletion", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_USERDEVICE", "kind": "Resilience security requirement (RSR)", "title": "Minimum User Device Security Platform", "text": "Minimum User Device Security Platform The User Device hosting the Wallet Instance shall provide a hardware-supported security platform consisting, at minimum, of a Trusted Execution Environment (TEE) or Secure Element (SE), integrated with a security-maintained operating system, to provide the security services required by the Wallet Instance. The TOE shall check that the User Device and OS shall at minimum: • provide a TEE or SE providing an isolated execution and storage environment for security-relevant Wallet Instance assets; • ensure that security-relevant device-bound private keys used by the Wallet Instance cannot be exported or cloned from the TEE/SE; • ensure that cryptographic operations using such keys are performed within the protected environment and that the key material is not exposed to the normal OS or other applications; • provide hardware-supported isolation between the protected security environment, the OS kernel and user applications; • provide a trusted boot mechanism that ensures that only authenticated and authorized firmware and OS components are executed with privileged access; • provide OS-enforced application isolation/sandboxing preventing one application from accessing another application's data, memory or processes without authorization; • provide protection against unauthorized privilege escalation, including execution of unauthorized code with OS or kernel privileges; • provide mechanisms for secure and timely security updates of the OS, firmware and security-critical platform components; • provide hardware-backed integrity/attestation mechanisms allowing the security state of relevant platform components to be established; and • provide a secure device-access mechanism protecting the User Device and the protected security environment against unauthorized local access.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_userdevice", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_OPER_MOD", "kind": "Resilience security requirement (RSR)", "title": "Secure Operating Mode", "text": "Secure Operating Mode The WI (TOE) shall establish that it is operating in a security state supported by the Wallet Instance. At a minimum, the TOE shall detect conditions indicating that the security properties of the underlying User Device or OS may have been compromised, including rooting/jailbreaking, unauthorized developer or debug mode, execution in an emulator or app-virtualization environment, or other conditions that invalidate the security assumptions of the TOE. When such a condition is detected, the TOE shall terminate or disable all security-critical Wallet Instance functionality and shall not perform security-critical operations until an acceptable security state has been restored.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_oper_mod", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_SEC_CLR", "kind": "Resilience security requirement (RSR)", "title": "Secure Clearing of Sensitive Data", "text": "Secure Clearing of Sensitive Data The WI (TOE) shall securely clear sensitive assets from memory when they are no longer required. Secure clearing shall use an explicit and effective mechanism appropriate to the asset and execution environment, such as zeroization, and shall not depend solely on garbage collection, memory deallocation or eventual reuse of the memory. The implementation shall ensure that the clearing operation is not removed, optimized away or otherwise altered by the compiler, runtime environment or platform. Where sensitive data may exist in multiple representations or memory areas, all relevant representations shall be appropriately cleared.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_sec_clr", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_CRPTO", "kind": "Resilience security requirement (RSR)", "title": "Use of Approved Cryptography", "text": "Use of Approved Cryptography The WI (TOE) shall use cryptographic mechanisms that provide adequate security for the intended protection period and security strength of the protected assets. At a minimum: • cryptographic keys shall be generated using an approved cryptographically secure random source; • key derivation shall use approved key-derivation functions and appropriate parameters and key sizes; • encryption, decryption, digital signatures, MACs and hashing shall use approved cryptographic algorithms and security parameters; • deprecated, broken or insufficiently secure algorithms and parameter sets shall not be used for security-critical functions; and • cryptographic mechanisms shall be selected and configured in accordance with the applicable ECCG Agreed Cryptographic Mechanisms. Where a cryptographic mechanism required by the TOE is not yet included in the ECCG Agreed Cryptographic Mechanisms, its use shall be subject to an appropriate security assessment and documented justification demonstrating that the mechanism provides sufficient security for the intended purpose and security strength. Such a mechanism shall only be used where its security has been established in accordance with the applicable certification or evaluation framework, and shall be replaced or updated when an applicable ECCG mechanism becomes available. The use of cryptographic mechanisms not yet included in the ECCG Agreed Cryptographic Mechanisms shall therefore be explicitly identified, justified and subject to approval by the applicable certification/evaluation process.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_crpto", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_RNG", "kind": "Resilience security requirement (RSR)", "title": "Cryptographically Secure Random Number Generation", "text": "Cryptographically Secure Random Number Generation The WI-(TOE) must generate random numbers using either: • A hardware RNG through an SE or TEE, and that RNG must be assessed as suitable for cryptographically strong random-number generation. • Or implement a DRBG compliant to NIST SP 800-90A or ISO/IEC 18031. This DRBG must be seeded by at least two sources of entropy: o One external trusted source, (e.g. Wallet Provider HSM/WSCD) o A source from the mobile device The combined entropy must be at least equal to the intended cryptographic key strength, and the entropy must be authenticated before use. Combining of entropy must preserve the entropy strength. The RNG (or DRNG) must be reseeded at least: • when the integrity/confidentiality of its state cannot be assured, such as at launch or after a halted state; and • at least every 24 hours of continuous operation. The reseeding process must add entropy to the existing RNG state, rather than simply replacing it. The DRNG shall generate random values with sufficient entropy and without statistically significant correlation, and shall be demonstrated to be fit for cryptographic purposes using an industry-recognized statistical test suite such as NIST SP 800-22 or AIS-31.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_rng", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_SEC_COD", "kind": "Resilience security requirement (RSR)", "title": "Secure Software Development and Supply Chain", "text": "Secure Software Development and Supply Chain The WI-(TOE) is developed using Secure coding practices, at a minimum: • The TOE shall protect sensitive data and secrets by ensuring that secrets are not hardcoded in the TOE source code or package, and sensitive data is stored encrypted, and only in private storage. • The TOE shall securely handle untrusted or externally supplied data, including intents, deep links, WebView content, and dynamically loaded code, such that: o untrusted content cannot access sensitive native functionality; o does not expose sensitive native functionality to WebView content and does not allow WebViews to load untrusted content; o deep links and intents cannot be abused to bypass security controls; o dynamic code is loaded safely, and only from trusted sources. • The TOE shall use platform-provided security mechanisms, including compiler-provided security features, and shall not use deprecated APIs or functionality that could weaken the TOE's security. • The TOE shall adequately manage platform permissions according to the principle of least privilege and shall use only trusted and appropriately maintained libraries for security-critical functionality. • The TOE package shall not contain malicious or unauthorized code and third party components are regularly checked for known vulnerabilities.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_sec_cod", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_OBF_COD", "kind": "Resilience security requirement (RSR)", "title": "Code and Resource Obfuscation", "text": "Code and Resource Obfuscation The WI-(TOE) may apply code and resource obfuscation to hinder reverse engineering and analysis of security-sensitive functionality and assets. At a minimum, obfuscation shall cover: • control-flow obfuscation of code implementing security mechanisms or handling security-sensitive assets; • symbol renaming of functions, methods, classes and other symbols associated with security-sensitive code; and data and string obfuscation of sensitive data, embedded secrets, strings and other security-relevant resources. Obfuscation shall also cover security-sensitive interfaces, including interfaces to cryptographic functionality and inter-library calls, where exposure of the implementation could facilitate compromise of the TOE. The TOE may additionally implement anti-deobfuscation and anti-analysis techniques to increase the resistance of the obfuscation against automated or manual reverse engineering.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 46, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_obf_cod", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_PYL_ENC", "kind": "Resilience security requirement (RSR)", "title": "Application-Level Payload Encryption", "text": "Application-Level Payload Encryption The WI-(TOE) may protect security-sensitive assets transmitted between the TOE and external entities using application-level encryption in addition to transport-layer protection, where such assets require protection against compromise of the underlying communication channel. Application-level encryption shall provide confidentiality and integrity protection for the protected payload and shall ensure that the payload cannot be disclosed or modified without detection if the underlying transport protection is compromised. Cryptographic keys used for application-level payload protection shall be managed in accordance with the applicable key-management and cryptographic requirements.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 46, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_pyl_enc", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_ATT", "kind": "Resilience security requirement (RSR)", "title": "Device Attestation", "text": "Device Attestation The WI-(TOE) may support device and platform attestation sufficient to establish the relevant security state of the User Device on which the TOE operates. Where attestation evidence is used for security decisions, the TOE shall ensure that the evidence is authentic, integrity protected and sufficiently fresh and that it is associated with the corresponding User Device and Wallet Instance. The TOE shall not rely on attestation evidence that cannot be successfully authenticated, integrity verified or associated with the applicable device.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 46, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_att", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_INTG", "kind": "Resilience security requirement (RSR)", "title": "TOE Integrity Verification", "text": "TOE Integrity Verification The WI-(TOE) may periodically verify the integrity and authenticity of its security-relevant software and resources, including executable code, security-sensitive configuration and other resources required for secure operation. The integrity verification mechanism shall detect unauthorized modification, replacement or removal of the verified code or resources. If the integrity or authenticity verification fails, the TOE shall prevent security-critical functionality and shall not continue operation using the affected code or resources.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 47, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_intg", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_FOCS", "kind": "Resilience security requirement (RSR)", "title": "Protection Against Loss of User Interface Focus", "text": "Protection Against Loss of User Interface Focus The WI-(TOE) may protect security-sensitive user interactions and displayed sensitive assets against loss or unauthorized transfer of user-interface focus. If the TOE detects that focus has been lost while the User is performing a security-sensitive action or while sensitive information is being displayed, the TOE shall: • terminate the affected security-sensitive operation; • prevent the operation from continuing without appropriate re-authentication or renewed User interaction, where required; and • prevent sensitive information from remaining exposed after focus has been lost.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 47, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_focs", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_DYN_TL", "kind": "Resilience security requirement (RSR)", "title": "Protection Against Dynamic Instrumentation and Runtime Manipulation", "text": "Protection Against Dynamic Instrumentation and Runtime Manipulation The WI-(TOE) may implement countermeasures against runtime instrumentation and dynamic analysis techniques that could be used to compromise security-sensitive assets or security functionality. Where such countermeasures are implemented, they should detect or resist techniques including runtime code injection, function hooking, API interception, dynamic debugging and manipulation of security-relevant execution flows. Where a detected instrumentation condition could compromise a security-critical operation, the TOE should terminate the affected operation.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 47, "obligation": "recommended", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_dyn_tl", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_MON", "kind": "Resilience security requirement (RSR)", "title": "Security Monitoring and Attestation", "text": "Security Monitoring and Attestation The WI (TOE) shall collect security-relevant monitoring and attestation information required to detect compromise of the TOE or its supporting User Device and shall securely provide this information to the Wallet Provider. At a minimum, the monitoring information shall include, where applicable: • rooted/jailbroken status; • emulator, virtualization and developer/debug status; • detected modification or tampering attempts, including modification of TOE code, runtime instrumentation and interference with TOE security-relevant interfaces; • TOE integrity status; • relevant User Device and platform security state; • TOE and supported platform versions; and • the unique identifier required to associate the information with the corresponding Wallet Instance. Monitoring and attestation information transmitted to the Wallet Provider shall be protected against unauthorized disclosure, modification and replay. It shall contain sufficient freshness information, such as a timestamp and/or nonce, to detect replay of previously generated evidence. The TOE shall not persistently retain monitoring information unless explicitly required for a security purpose.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_mon", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_DAT_SAN", "kind": "Resilience security requirement (RSR)", "title": "Sanitization of Sensitive Data", "text": "Sanitization of Sensitive Data The TOE shall sanitize sensitive assets, PID attributes and other security-relevant personal data from temporary or secondary storage when they are no longer required. This requirement shall apply, as applicable, to: • migration data; • backups; logs; • caches; • temporary files; • operational data; • crash reports; • diagnostic data; and • other data generated or retained during operation. Sanitization shall ensure that sensitive assets and PID attributes cannot subsequently be recovered or disclosed through such data, unless their retention is explicitly required for an authorized security or operational purpose and appropriate protection is applied.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_dat_san", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_KEY_MNG", "kind": "Resilience security requirement (RSR)", "title": "Secure Key Management", "text": "Secure Key Management The WI (TOE) shall implement key-management mechanisms appropriate to the security strength and intended use of each cryptographic key. At a minimum: • secret and private keys shall be generated, imported or injected only through mechanisms that protect their confidentiality, integrity and authenticity; • keys requiring hardware-backed protection shall be generated or stored using the User Device's hardware-backed keystore, TEE or SE; • security-relevant private keys shall not be exportable from their protected environment; • private or secret keys that must temporarily exist outside the hardware-backed security environment shall be unique per session and shall provide appropriate protection against compromise of previous or subsequent sessions; • key-encryption keys shall provide security strength equal to or greater than the keys they protect; • public keys used for security-critical purposes shall be integrity- and authenticity-protected and authenticated before use; • protection of keys in transit shall not rely solely on transport-channel security where compromise of the channel could expose or enable substitution of the key; • keys shall have explicitly defined usage restrictions and shall not be used for purposes other than those for which they were generated; • cryptographic keys shall be securely destroyed or invalidated when their lifecycle ends; and • keys or security credentials dependent on the User Device's biometric enrollment state shall be invalidated or re-established when the relevant biometric enrollment changes, where required by the platform security model. Key-management mechanisms shall conform to the applicable ECCG Agreed Cryptographic Mechanisms and the security strength required by the TOE.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_key_mng", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_SCRN_PRT", "kind": "Resilience security requirement (RSR)", "title": "Protection of Sensitive User Interface Data", "text": "Protection of Sensitive User Interface Data The WI (TOE) shall protect sensitive information presented through the User Device graphical user interface against unauthorized capture, modification or disclosure. At a minimum, the TOE shall: • prevent or appropriately restrict screenshots and screen recording while sensitive information is displayed; • protect sensitive screens against overlay, tapjacking and other UI-injection attacks; • prevent sensitive information from being unnecessarily exposed through the system clipboard; • prevent unauthorized accessibility services from accessing sensitive information or user input; • prevent sensitive information from being unnecessarily exposed through notifications, previews or other system UI; • provide secure handling of authentication input, including support for platform-provided secure authentication mechanisms where applicable; and • verify that an appropriate secure device lock mechanism is configured before enabling security-critical functionality.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_scrn_prt", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=42" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_PIN_ENTRY", "kind": "Resilience security requirement (RSR)", "title": "Secure PIN Entry", "text": "Secure PIN Entry The WI (TOE) shall protect the knowledge-based authentication factor used for RUAP against unauthorized disclosure, modification and reuse During PIN entry, the TOE shall provide protection against: • screen capture and recording; • overlay and tapjacking attacks; • side-channel leakage; • accessibility-service abuse; • malware attempting to intercept or manipulate the PIN; and • unauthorized modification or substitution of the PIN-entry interface. The PIN shall not be persistently stored or logged by the TOE. Any PIN and security-sensitive data derived from it shall be securely cleared immediately after use and shall not remain recoverable in memory, temporary storage, caches or other TOE-controlled storage. The TOE shall ensure that the PIN is processed only for the intended authentication operation and shall not expose it to third-party applications or unnecessary platform services.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_pin_entry", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=42" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_NO_DEBG", "kind": "Resilience security requirement (RSR)", "title": "Protection Against Debugging and Instrumentation", "text": "Protection Against Debugging and Instrumentation The WI (TOE) shall not contain production debug functionality or debug artifacts that could weaken its security The TOE shall detect and prevent security-critical operation when an unauthorized debugger, runtime instrumentation framework or equivalent debugging mechanism is attached or enabled. Security controls shall not rely solely on the absence of visible debug functionality and shall protect against commonly available mechanisms for bypassing such controls.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_no_debg", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_SEC_CHANNEL", "kind": "Functional security requirement (FSR)", "title": "Secure Communication Channels", "text": "Secure Communication Channels The WI-(TOE) establishes and maintains mutually authenticated and protected communication channels with the WSCA and the Wallet Provider. The communication channels shall provide authentication, confidentiality and integrity protection, and shall protect security-relevant communications against replay and modification. All communication between the WI-(TOE) and the WSCA or the Wallet Provider shall use these protected channels.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_sec_channel", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=32" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_LOCAL_AUTH", "kind": "Functional security requirement (FSR)", "title": "Local User Authentication", "text": "Local User Authentication The WI-(TOE) implements local OS-based authentication. The authentication mechanism shall be multi-factor authentication, including possession of the User's device as one factor and an additional knowledge-based or inherence-based factor. This local OS-based authentication shall be enforced at startup of the WI-(TOE) and before security-sensitive actions which require User authentication, as defined in the applicable Regulation and ARF requirements. The TOE shall ensure that authentication is no longer considered valid after the applicable inactivity timeout and shall require the User to authenticate again before performing protected actions.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_local_auth", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=32" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_REMOTE_AUTH", "kind": "Functional security requirement (FSR)", "title": "Remote User Authentication", "text": "Remote User Authentication The WI-(TOE) implements the WSCA/WSCD-level Remote User Authentication Protocol (RUAP) between the WI-(TOE) and the WSCA/WSCD. The RUAP shall support User authentication meeting the applicable requirements for Level of Assurance High as specified in Commission Implementing Regulation (EU) 2015/1502. In particular, the authentication mechanism shall use at least two authentication factors from different categories and shall implement security controls such that guessing, eavesdropping, replay and manipulation of the authentication communication cannot, with high attack potential, subvert the authentication mechanism. This specific Remote User Authentication Protocol (RUAP), including the use of User Authentication Evidence (UAE) and Authentication Reference Data (ARD), is a PP-specific mechanism defined to implement the required WSCA/WSCD-level User authentication. The protocol shall ensure that: • The Wallet Instance WI-(TOE) must demonstrate the User Authentication Evidence (UAE), which is derived both from a knowledge-based authentication factor (derived from the PIN) and a possession-based authentication factor, which are jointly validated to achieve two-factor authentication and to prevent manipulation or forged attempts; • Remote User Authentication Protocol (RUAP) ensure PIN Verification and ensure that the User has sole control over the critical assets located in the WSCD, such that these assets cannot be used without the User's involvement through the required authentication factors; • The protocol protects the confidentiality and integrity of the authentication data during PIN verification and enrolment, and provides protection against duplication, tampering, eavesdropping and replay attacks, including through freshness and challenge binding; • Each PIN verification is performed through a live and fresh interaction between the WI-(TOE) and the WSCA/WSCD, preventing reuse of previously exchanged authentication information; • During enrolment, the Wallet Instance WI-(TOE) ensures that both the knowledge and possession factors are securely initialized and cryptographically bound to the Authentication Reference Data (ARD). Authentication Reference Data (ARD) is derived and is shared with the WSCA /WSCD during initial enrolment. This binding preserves confidentiality and integrity of the knowledge-based authentication factor (derived from the PIN) and a possession-based authentication factor and prevents compromise also if the confidentiality of the Authentication Reference Data (ARD) is not preserved. • A PUK can be integrated in the protocol to reset the knowledge-based factor in case the PIN was forgotten. • Per-key authentication data shall be sent to the Wallet Instance WI-(TOE) at key generation and be provided at every security-sensitive cryptographic operation of the applicable key, to ensure sole control of the Wallet User before the execution by the WSCD. As part of the enrolment process, the Wallet User initializes the WSCA/WSCD-level User Authentication by instructing the WI-(TOE) to generate the required cryptographic keys within the secure keystore. The User shall provide their PIN during this process, from which the knowledge-based factor is derived and securely incorporated into the authentication mechanism. The WSCA/WSCD-level Remote User Authentication shall be performed before security-sensitive operations involving critical assets located in the WSCD, as defined in the applicable Regulation and ARF requirements.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 32, "obligation": "mandatory", "legal_refs": [ "CIR 2015/1502" ], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_remote_auth", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=32" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_SELECT_DISCLO", "kind": "Functional security requirement (FSR)", "title": "Selective Disclosure and User Consent", "text": "Selective Disclosure and User Consent The WI-(TOE) enforces selective disclosure by ensuring that only User-approved attributes and electronic attestations are released to authorised Relying Parties, consistent with the principles of user consent, data minimisation and selective disclosure. The TOE shall: • display to the User the attributes and electronic attestations requested by the Relying Party before presentation; • process and enforce applicable embedded disclosure policies associated with electronic attestations; • ensure that the User can approve the requested presentation in full or in part; • ensure that no requested attributes or electronic attestations are presented before the applicable disclosure policies have been processed and the User has approved the presentation; • ensure that only the attributes and electronic attestations approved by the User are included in the presentation; and • prevent disclosure if the applicable disclosure policy is not satisfied or the required User approval has not been obtained. • The TOE shall evaluate applicable embedded disclosure policies against the authenticated Relying Party and Service information and shall prevent disclosure if the policy requirements are not satisfied. • The TOE shall ensure that the User approval applies to the actual presentation transaction and to the attributes and electronic attestations that are transmitted to the Relying Party. • The TOE shall retain control over security-sensitive User approval and disclosure decisions and shall not delegate such decisions to a browser, operating-system component or other intermediary application. The TOE shall ensure that selective disclosure is performed in accordance with the applicable ARF and technical specifications and shall support privacy-preserving mechanisms, including unlinkability where required.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_select_disclo", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_MDOC", "kind": "Functional security requirement (FSR)", "title": "mDoc Presentation", "text": "mDoc Presentation The WI-(TOE) supports ISO/IEC 18013-5 mdoc-based presentation flows in accordance with the applicable ARF and technical specifications. The TOE shall: • support the applicable ISO/IEC 18013-5 requirements for mdoc presentation; • verify the authenticity and integrity of received mdoc presentation requests before processing them; • ensure that the mdoc response contains only the attributes and data elements approved by the User and permitted by the applicable disclosure policies; • protect the mdoc presentation against replay, modification and transaction manipulation; • ensure that security-relevant mdoc messages are bound to the applicable presentation session and transaction; and • verify the authenticity and integrity of received mdoc data before using or presenting it. Where an API-mediated presentation mechanism based on ISO/IEC 18013-7 is used, the TOE shall comply with the applicable ISO/IEC 18013-7 requirements and the corresponding EUDI Wallet technical specifications.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_mdoc", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_PSEUDONYM", "kind": "Functional security requirement (FSR)", "title": "Relying Party-Specific Pseudonyms", "text": "Relying Party-Specific Pseudonyms The WI-(TOE) supports the generation, management and presentation of Wallet-Relying Party-specific pseudonyms in accordance with the applicable ARF and technical specifications. The TOE shall: • generate a pseudonym that is specific and unique to the requesting Relying Party; • ensure that the same pseudonym is not used for different Relying Parties where the applicable pseudonym mechanism requires Relying Party-specific pseudonyms; • provide the generated pseudonym to the requesting Relying Party, either standalone or together with the requested PID or electronic attestation; • ensure that the pseudonym is generated and presented only after the Relying Party has been authenticated and the User has approved the applicable transaction; • protect pseudonyms against unauthorized disclosure, modification and replacement; and • allow the User to manage pseudonyms in accordance with the applicable technical specifications. • store the cryptographic information required for pseudonym generation and authentication in the WSCA/WSCD; • ensure that the same pseudonym is not disclosed to different Relying Parties unless explicitly permitted by the applicable pseudonym mechanism and User choice; • allow the User to view, select, manage and delete pseudonyms; • provide the User with sufficient information to distinguish pseudonyms associated with different Relying Parties; • protect pseudonym authentication data against unauthorized disclosure, modification, replacement and deletion; • ensure that User-assigned aliases or other information used by the User to manage pseudonyms are not disclosed to Relying Parties; and • ensure that pseudonyms contain sufficient entropy and are generated using the cryptographic mechanisms specified by the applicable technical specifications. The TOE shall ensure that pseudonym generation and presentation do not unnecessarily disclose the User's legal identity or enable the User to be tracked across different Relying Parties. The TOE shall support User-chosen and managed pseudonyms where required by the applicable ARF and technical specifications.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_pseudonym", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_DPA_REPORT", "kind": "Functional security requirement (FSR)", "title": "Data Protection Authority Reporting", "text": "Data Protection Authority Reporting The WI-(TOE) shall provide the User with a function to initiate a complaint concerning a suspicious or inappropriate Relying Party presentation request to the competent Data Protection Authority (DPA), in accordance with the applicable ARF and national requirements. The TOE shall: • provide access to the applicable Data Protection Authority reporting function through the Wallet Instance; • allow the User to identify the relevant Relying Party and presentation request; • allow the User to provide the information required to substantiate the complaint; • protect the confidentiality and integrity of the report during preparation and transmission; and • record the submitted report in the transaction log so that it can subsequently be presented to the User.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_dpa_report", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_TRST_MRK", "kind": "Functional security requirement (FSR)", "title": "EU Digital Identity Wallet Trust Mark", "text": "EU Digital Identity Wallet Trust Mark The WI-(TOE) displays the official EU Digital Identity Wallet Trust Mark in the User interface. The Trust Mark view shall: • display the official Trust Mark graphics and/or logo; • provide information about the certification status of the Wallet Solution; and • provide links to the official list of certified EUDI Wallet Solutions and the certification information of the Wallet Solution. The TOE shall obtain and protect the Trust Mark information provided by the Wallet Provider and shall ensure that the displayed Trust Mark information cannot be modified by an unauthorized party. The TOE shall ensure that the Trust Mark and related certification information are only displayed for the applicable Wallet Solution and Wallet Instance.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_trst_mrk", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "FSR_LOG_DATA", "kind": "Functional security requirement (FSR)", "title": "Transaction and Operational Logging", "text": "Transaction and Operational Logging The WI-(TOE) shall maintain transaction logs for transactions with Wallet-Relying Parties and other Wallet Units, including unsuccessful transactions and electronic signing and sealing transactions. The transaction logs shall contain, as applicable: • the date and time of the transaction; • the name, contact details and unique identifier of the corresponding Wallet-Relying Party and the Member State in which it is established, or the relevant information from the Wallet Unit Attestation for transactions with another Wallet Unit; • the type of data requested and presented; and • the reason for an unsuccessful transaction. The TOE shall also log reports sent by the User to a Data Protection Authority through the Wallet Unit. The TOE shall protect transaction logs against unauthorized access, modification and deletion and shall ensure their confidentiality, integrity and authenticity. The TOE shall ensure that transaction logs do not contain the actual values of attributes presented, unless explicitly required by applicable legislation. The TOE shall allow the User to access and export the transaction logs in accordance with the applicable technical specifications. The TOE shall allow the User to delete individual transaction-log entries, where permitted by applicable legislation, and shall inform the User before logs are deleted when deletion is required. Transaction logs shall remain available for the period required by applicable Union or national law. Where access to transaction logs by the Wallet Provider is necessary for the provision of Wallet services, the TOE shall only permit such access based on the explicit prior consent of the User, as required by the applicable Regulation. The TOE shall additionally maintain operational and maintenance logs where required for the secure operation and maintenance of the Wallet Instance. Such logs shall be minimized and shall not contain the actual values of attributes presented.", "section": "3.1 WI-(TOE) Functional Security Requirements", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#fsr_log_data", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WI", "document_title": "EN 17640 FITCEM Protection Profile for EUDI Wallet Instance in a remote HSM architecture", "version": "RC1.1", "id": "RSR_MAC", "kind": "Resilience security requirement (RSR)", "title": "Mandatory Access Control and Application Isolation", "text": "Mandatory Access Control and Application Isolation The WI (TOE) shall operate within the security and isolation mechanisms provided by the underlying operating system. The TOE shall not bypass or weaken the OS mandatory access-control, application sandboxing, process-isolation or permission mechanisms. The TOE shall use the principle of least privilege and shall request only the platform permissions required for its intended security and functional purposes.", "section": "3.2 WI-(TOE) Resilience Security Requirements", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wi#rsr_mac", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WI-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-DEDICATED_PLATFROM", "kind": "Condition", "title": "The WSCA operates on a dedicated underlying hardened platform and hardware that …", "text": "The WSCA operates on a dedicated underlying hardened platform and hardware that forms part of its trusted operational environment. This platform is responsible for providing the security mechanisms necessary to protect the WSCA against unauthorised access, modification, interference and exploitation (see detailed requirements in section 5). No applications, services, workloads or processing functions unrelated to the WSCA shall be installed or operated on the hardened platforms and on top dedicated hardware. Consequently, deployment of the WSCA as a shared cloud application is not permitted.", "section": "2 Security requirements Operational Environment", "page": 8, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-dedicated_platfrom", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=8" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-TRUSTED-ADMIN", "kind": "Condition", "title": "Administrators are appropriately trained, follow established policies and guidan…", "text": "Administrators are appropriately trained, follow established policies and guidance, and are trusted to act without malicious intent. They ensure that passwords and credentials have sufficient strength and entropy. The platform enforces dual control for administrative tasks to prevent a single administrator from performing sensitive or potentially malicious actions alone.", "section": "2 Security requirements Operational Environment", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-trusted-admin", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=9" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-GATEWAY", "kind": "Condition", "title": "The WSCA platform shall not be directly exposed to the Internet. External commun…", "text": "The WSCA platform shall not be directly exposed to the Internet. External communication is mediated through a gateway platform positioned between the WSCA platform and the Internet. This provides an additional security boundary for network communication and reduces the direct exposure of the WSCA execution environment. The gateway implements at least DDoS protection, intrusion detection, antivirus functionality and firewall functionality.", "section": "2 Security requirements Operational Environment", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-gateway", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=9" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-DATABASE", "kind": "Condition", "title": "The WSCD and security-relevant databases supporting the WSCA shall be located wi…", "text": "The WSCD and security-relevant databases supporting the WSCA shall be located within the same protected operational environment as the WSCA platform and shall not be directly accessible from untrusted networks.", "section": "2 Security requirements Operational Environment", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-database", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=9" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-WSCD-CHANNEL", "kind": "Condition", "title": "Communication channels between the WSCA and the WSCD and the WSCA the gateway pl…", "text": "Communication channels between the WSCA and the WSCD and the WSCA the gateway platform shall be authenticated and encrypted. The communication mechanism shall protect the confidentiality and integrity of all exchanged security-relevant data and cryptographic commands, and shall prevent unauthorised interception, modification, replay, or impersonation of communicating parties. The communication channel between the WSCA and the WSCD shall use a dedicated physical connection, isolated from all other computer systems.", "section": "2 Security requirements Operational Environment", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-wscd-channel", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=9" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "ENV-ENVIRONMENT", "kind": "Condition", "title": "The TOE and its underlying platform shall be located in a physically secured env…", "text": "The TOE and its underlying platform shall be located in a physically secured environment that protects against unauthorised physical access, tampering, theft, and physical interference. Access shall be restricted to authorised personnel through appropriate physical access controls. Physical security measures shall protect the WSCA, WSCD the databases and the gateway against attacks that could compromise their integrity, confidentiality, or availability, including attacks within the scope of the AVA_VAN.5 vulnerability assessment.", "section": "2 Security requirements Operational Environment", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#env-environment", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=9" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "01", "kind": "Security principle", "title": "Minimal Configuration", "text": "The underlying platform shall be configured with only those operating system components, services, drivers, interfaces and functions that are required for the secure operation of the WSCA. Unnecessary functionality shall be disabled or removed.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "02", "kind": "Security principle", "title": "Limited Execution", "text": "The underlying platform shall restrict execution to authorised software, processes and services required for the operation of the WSCA. Execution of unauthorised software shall be prevented.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "03", "kind": "Security principle", "title": "Least Privilege", "text": "The underlying platform shall ensure that the WSCA and its supporting processes operate with only the privileges necessary to perform their specified functions.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "04", "kind": "Security principle", "title": "Process Isolation", "text": "The underlying platform shall provide isolation between the WSCA and other processes such that an unauthorised process cannot access, modify or interfere with the WSCA or its security-relevant data.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "05", "kind": "Security principle", "title": "Memory Protection", "text": "The underlying platform shall protect memory allocated to the WSCA against unauthorised reading, modification and execution by other processes or users.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "06", "kind": "Security principle", "title": "Controlled Interfaces", "text": "The underlying platform shall restrict access to system interfaces, devices, files, inter-process communication mechanisms and other resources to those required for the operation of the WSCA.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "07", "kind": "Security principle", "title": "Platform Integrity", "text": "The underlying platform shall provide mechanisms to prevent or detect unauthorised modification of platform components that could affect the security of the WSCA.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "08", "kind": "Security principle", "title": "Network Protection", "text": "The underlying platform shall expose only the network services, protocols and ports required for the operation of the WSCA. Direct network access from the WSCA to untrusted networks shall be prevented where it is not required for the WSCA's specified operation.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "09", "kind": "Security principle", "title": "WSCA Data Protection", "text": "The underlying platform shall protect WSCA security-relevant data, including configuration data, credentials and other sensitive information, against unauthorised disclosure, modification or deletion.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "10", "kind": "Security principle", "title": "Privilege Escalation Protection", "text": "The underlying platform shall prevent a process or user operating with limited privileges from obtaining privileges that could be used to compromise or interfere with the WSCA.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "11", "kind": "Security principle", "title": "Security-Relevant Logging", "text": "The underlying platform shall provide logging of security-relevant events necessary to support the detection and investigation of events that could affect the security of the WSCA.", "section": "4 Security Principles for the Underlying Platform", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=12" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "12", "kind": "Security principle", "title": "Vulnerability Management", "text": "The underlying platform shall be maintained using a defined vulnerability and security-update management process to ensure that known vulnerabilities that could affect the WSCA are assessed and appropriately remediated.", "section": "4 Security Principles for the Underlying Platform", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=13" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "13", "kind": "Security principle", "title": "Cyber Security Monitoring", "text": "The underlying platform shall be continuously monitored for security-relevant events, anomalous behaviour, and indicators of compromise that could affect the security of the WSCA. Detected events shall be analysed and, where necessary, trigger appropriate alerts and incident response measures.", "section": "4 Security Principles for the Underlying Platform", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=13" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-01", "kind": "Platform requirement", "title": "The host system shall be configured with only the hardware components required f…", "text": "The host system shall be configured with only the hardware components required for the operation of the WSCA platform. Unnecessary hardware devices and interfaces shall be disabled or removed where technically possible.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-02", "kind": "Platform requirement", "title": "The hardware shall support the platform's mechanisms for restricting execution t…", "text": "The hardware shall support the platform's mechanisms for restricting execution to authorised platform and WSCA software. Hardware mechanisms that could allow unauthorised code execution or bypass platform controls shall be disabled or appropriately controlled.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-03", "kind": "Platform requirement", "title": "Hardware resources and privileged hardware functions shall only be accessible th…", "text": "Hardware resources and privileged hardware functions shall only be accessible through authorised platform mechanisms and to components requiring such access for their specified functions.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-04", "kind": "Platform requirement", "title": "The host hardware shall provide, where supported, hardware-assisted mechanisms f…", "text": "The host hardware shall provide, where supported, hardware-assisted mechanisms for isolating processes and execution environments, including processor privilege levels and virtual memory protection.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-05", "kind": "Platform requirement", "title": "The processor and memory subsystem shall support hardware-assisted memory protec…", "text": "The processor and memory subsystem shall support hardware-assisted memory protection mechanisms. These mechanisms shall be enabled and configured to prevent unauthorised access to memory allocated to the WSCA.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-06", "kind": "Platform requirement", "title": "Physical interfaces and peripheral devices shall be limited to those required fo…", "text": "Physical interfaces and peripheral devices shall be limited to those required for the operation and administration of the WSCA platform. Unnecessary interfaces, such as unused USB, storage or peripheral interfaces, shall be disabled or physically restricted where possible.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-07", "kind": "Platform requirement", "title": "Where supported by the hardware, mechanisms such as a hardware root of trust, Tr…", "text": "Where supported by the hardware, mechanisms such as a hardware root of trust, Trusted Platform Module (TPM), measured boot or Secure Boot shall be used to support verification of the integrity of the platform during system initialisation.", "section": "5.1 Hardware Requirements", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=14" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-08", "kind": "Platform requirement", "title": "Network interfaces shall be limited to those required for WSCA operation and pla…", "text": "Network interfaces shall be limited to those required for WSCA operation and platform administration. Unused network interfaces shall be disabled, and the hardware configuration shall not provide an uncontrolled path to untrusted networks.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-09", "kind": "Platform requirement", "title": "Hardware resources used to store or process WSCA security-relevant data shall be…", "text": "Hardware resources used to store or process WSCA security-relevant data shall be protected against unauthorised physical and logical access. Where hardware security mechanisms are available, they shall be used where required to protect sensitive data.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-10", "kind": "Platform requirement", "title": "The hardware shall support processor and platform security mechanisms that preve…", "text": "The hardware shall support processor and platform security mechanisms that prevent lower-privileged software from directly accessing privileged hardware resources or bypassing the access-control mechanisms of the underlying platform.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-11", "kind": "Platform requirement", "title": "Where hardware security events are relevant to the security of the WSCA, the pla…", "text": "Where hardware security events are relevant to the security of the WSCA, the platform shall provide mechanisms to capture or expose such events to the platform logging and monitoring functions.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-12", "kind": "Platform requirement", "title": "The hardware platform, including firmware and microcode, shall be subject to a d…", "text": "The hardware platform, including firmware and microcode, shall be subject to a defined vulnerability-management process. Security updates addressing vulnerabilities that could affect the WSCA shall be assessed and applied in accordance with the applicable security-update policy.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "HW-13", "kind": "Platform requirement", "title": "The hardware platform shall support the collection and reporting of security-rel…", "text": "The hardware platform shall support the collection and reporting of security-relevant hardware events, where technically available, including hardware faults, integrity violations, and indicators of unauthorised physical or logical access. Such events shall be made available to the platform's security monitoring mechanisms for analysis and, where necessary, trigger appropriate alerts.", "section": "5.1 Hardware Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#hw-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-01", "kind": "Platform requirement", "title": "The boot and initialisation environment shall be configured with only the firmwa…", "text": "The boot and initialisation environment shall be configured with only the firmware, boot components and configuration required to initialise the platform and start the authorised operating system. Unnecessary boot functionality shall be disabled where technically possible.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-02", "kind": "Platform requirement", "title": "The boot process shall permit execution only of authorised firmware, bootloader …", "text": "The boot process shall permit execution only of authorised firmware, bootloader components and operating system components. Unauthorised code shall not be permitted to execute during platform initialisation.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-03", "kind": "Platform requirement", "title": "Boot and initialisation components shall operate with only the privileges and ac…", "text": "Boot and initialisation components shall operate with only the privileges and access to hardware resources necessary to perform platform initialisation and start the authorised operating system.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-04", "kind": "Platform requirement", "title": "The boot environment shall prevent unauthorised or untrusted components from gai…", "text": "The boot environment shall prevent unauthorised or untrusted components from gaining access to or interfering with security-relevant boot processes and initialisation components.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=15" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-05", "kind": "Platform requirement", "title": "The boot environment shall use available hardware and firmware mechanisms to pro…", "text": "The boot environment shall use available hardware and firmware mechanisms to protect memory used during initialisation against unauthorised access or modification.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-06", "kind": "Platform requirement", "title": "Access to firmware configuration, boot interfaces and hardware configuration fun…", "text": "Access to firmware configuration, boot interfaces and hardware configuration functions shall be restricted to authorised personnel or authorised management mechanisms. Unnecessary boot interfaces shall be disabled or otherwise restricted.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-07", "kind": "Platform requirement", "title": "The boot process shall provide mechanisms to verify the authenticity and/or inte…", "text": "The boot process shall provide mechanisms to verify the authenticity and/or integrity of firmware, bootloader and operating system components before they are executed. Where supported, Secure Boot, measured boot or equivalent integrity mechanisms shall be enabled and appropriately configured.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-08", "kind": "Platform requirement", "title": "Network functionality during the boot and initialisation process shall be disabl…", "text": "Network functionality during the boot and initialisation process shall be disabled unless required for a defined platform function. Where network boot or other pre-OS network functionality is required, it shall be restricted to authorised sources and protected against unauthorised modification or execution.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-09", "kind": "Platform requirement", "title": "The boot and initialisation process shall not expose or provide unauthorised acc…", "text": "The boot and initialisation process shall not expose or provide unauthorised access to WSCA security-relevant data stored on the platform. Access to storage containing WSCA data during boot shall be restricted to authorised platform components.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-10", "kind": "Platform requirement", "title": "The boot and initialisation mechanisms shall prevent lower-trust or unauthorised…", "text": "The boot and initialisation mechanisms shall prevent lower-trust or unauthorised components from obtaining privileged execution through manipulation of the boot process, boot configuration or firmware interfaces.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-11", "kind": "Platform requirement", "title": "Where supported, security-relevant boot and integrity events, including failed i…", "text": "Where supported, security-relevant boot and integrity events, including failed integrity checks and unauthorised boot attempts, shall be recorded and made available to the platform's security monitoring mechanisms.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-12", "kind": "Platform requirement", "title": "Firmware, bootloader and other boot components shall be subject to a defined vul…", "text": "Firmware, bootloader and other boot components shall be subject to a defined vulnerability-management process. Security vulnerabilities affecting the integrity or security of the WSCA platform shall be assessed and appropriately remediated.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "BOOT-13", "kind": "Platform requirement", "title": "The boot and initialisation process shall support the detection of security-rele…", "text": "The boot and initialisation process shall support the detection of security-relevant anomalies, including unexpected boot configurations, failed integrity verification, and unauthorised changes to boot components. Detected events shall be reported to the platform's security monitoring mechanisms to enable timely investigation and response.", "section": "5.2 Boot and Initialisation Layer Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#boot-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-01", "kind": "Platform requirement", "title": "The kernel shall be configured with only the functionality, drivers, modules and…", "text": "The kernel shall be configured with only the functionality, drivers, modules and interfaces required for the secure operation of the WSCA platform. Unnecessary kernel functionality shall be disabled or removed where technically possible.", "section": "5.3 Operating System Kernel Requirements", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=16" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-02", "kind": "Platform requirement", "title": "The kernel shall prevent unauthorised kernel modules, drivers or other privilege…", "text": "The kernel shall prevent unauthorised kernel modules, drivers or other privileged code from being loaded or executed. Only authorised and trusted kernel components shall be permitted.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-03", "kind": "Platform requirement", "title": "The kernel shall provide mechanisms to enforce separation between privileged and…", "text": "The kernel shall provide mechanisms to enforce separation between privileged and non-privileged execution and shall ensure that the WSCA operates with only the privileges required for its specified functions.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-04", "kind": "Platform requirement", "title": "The kernel shall provide process isolation mechanisms that prevent one process f…", "text": "The kernel shall provide process isolation mechanisms that prevent one process from accessing, modifying or interfering with another process unless explicitly authorised.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-05", "kind": "Platform requirement", "title": "The kernel shall enforce memory isolation and shall prevent unauthorised process…", "text": "The kernel shall enforce memory isolation and shall prevent unauthorised processes from reading, modifying or executing memory allocated to the WSCA. Hardware-assisted memory protection mechanisms shall be enabled where available.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-06", "kind": "Platform requirement", "title": "Access to kernel interfaces, system calls, devices, IPC mechanisms and other ker…", "text": "Access to kernel interfaces, system calls, devices, IPC mechanisms and other kernel-managed resources shall be restricted according to the privileges and functions of the requesting process.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-07", "kind": "Platform requirement", "title": "The kernel shall provide mechanisms to protect the integrity of its own code, se…", "text": "The kernel shall provide mechanisms to protect the integrity of its own code, security configuration and security-relevant data during operation.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-08", "kind": "Platform requirement", "title": "The kernel network stack shall be configured to expose only the network function…", "text": "The kernel network stack shall be configured to expose only the network functionality required by the WSCA environment. Unnecessary network protocols, interfaces and services shall be disabled.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-09", "kind": "Platform requirement", "title": "The kernel shall enforce access controls preventing unauthorised processes or us…", "text": "The kernel shall enforce access controls preventing unauthorised processes or users from accessing WSCA security-relevant files, memory, devices and other resources.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-10", "kind": "Platform requirement", "title": "The kernel shall provide mechanisms to prevent processes operating with limited …", "text": "The kernel shall provide mechanisms to prevent processes operating with limited privileges from obtaining unauthorised higher privileges or bypassing kernel access-control mechanisms.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-11", "kind": "Platform requirement", "title": "The kernel shall provide logging or security event mechanisms for security-relev…", "text": "The kernel shall provide logging or security event mechanisms for security-relevant events that could indicate an attempt to bypass kernel security controls or compromise the WSCA.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-12", "kind": "Platform requirement", "title": "The kernel and its security-relevant modules and drivers shall be subject to vul…", "text": "The kernel and its security-relevant modules and drivers shall be subject to vulnerability management. Known vulnerabilities that could affect the WSCA shall be assessed and appropriately remediated.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "KERN-13", "kind": "Platform requirement", "title": "The operating system kernel shall support the detection and reporting of securit…", "text": "The operating system kernel shall support the detection and reporting of security-relevant anomalies, including unauthorised privilege escalation, unexpected kernel module loading, violations of access controls, and attempts to exploit kernel vulnerabilities. Detected events shall be made available to the platform's security monitoring mechanisms for analysis and incident response.", "section": "5.3 Operating System Kernel Requirements", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#kern-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=17" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-01", "kind": "Platform requirement", "title": "Only operating system services required for the secure operation, administration…", "text": "Only operating system services required for the secure operation, administration and maintenance of the WSCA shall be installed and enabled.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-02", "kind": "Platform requirement", "title": "System services shall execute only authorised binaries and components. Unauthori…", "text": "System services shall execute only authorised binaries and components. Unauthorised modification or replacement of service executables shall be prevented or detected.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-03", "kind": "Platform requirement", "title": "Each system service required by the WSCA shall operate using the minimum privile…", "text": "Each system service required by the WSCA shall operate using the minimum privileges and system resources necessary for its function.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-04", "kind": "Platform requirement", "title": "System services shall be isolated from the WSCA and from each other to the exten…", "text": "System services shall be isolated from the WSCA and from each other to the extent necessary to prevent compromise of one service from directly compromising the WSCA.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-05", "kind": "Platform requirement", "title": "System services shall operate using the platform's available memory protection m…", "text": "System services shall operate using the platform's available memory protection mechanisms so that they cannot access or modify WSCA memory without authorisation.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-06", "kind": "Platform requirement", "title": "Access to system services shall be restricted to authorised users, processes and…", "text": "Access to system services shall be restricted to authorised users, processes and network endpoints. Unused service interfaces shall be disabled.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-07", "kind": "Platform requirement", "title": "System service configuration and security policies shall be protected against un…", "text": "System service configuration and security policies shall be protected against unauthorised modification.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-08", "kind": "Platform requirement", "title": "Network-facing services shall be limited to those required by the WSCA environme…", "text": "Network-facing services shall be limited to those required by the WSCA environment. Services that are not required shall be disabled and their associated ports shall not be exposed.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-09", "kind": "Platform requirement", "title": "System services shall not provide unauthorised access to WSCA files, configurati…", "text": "System services shall not provide unauthorised access to WSCA files, configuration, credentials or other security-relevant data.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-10", "kind": "Platform requirement", "title": "System services shall be configured to prevent their interfaces or vulnerabiliti…", "text": "System services shall be configured to prevent their interfaces or vulnerabilities from being used to obtain privileges that could compromise the WSCA.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-11", "kind": "Platform requirement", "title": "Security-relevant events generated by system services shall be logged where requ…", "text": "Security-relevant events generated by system services shall be logged where required to detect or investigate activity that could affect WSCA security.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-12", "kind": "Platform requirement", "title": "System services and associated components shall be regularly assessed for vulner…", "text": "System services and associated components shall be regularly assessed for vulnerabilities and security updates shall be applied where required.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "OS-13", "kind": "Platform requirement", "title": "The operating system shall continuously monitor system services for security-rel…", "text": "The operating system shall continuously monitor system services for security-relevant anomalies, including unexpected service behaviour, unauthorised configuration changes, suspicious process activity, and indicators of compromise. Detected events shall be reported to the platform's security monitoring mechanisms for analysis, alerting, and incident response.", "section": "5.4 Operating System / System Services Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#os-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-01", "kind": "Platform requirement", "title": "Only applications and utilities required for the operation, administration and m…", "text": "Only applications and utilities required for the operation, administration and maintenance of the WSCA environment shall be installed.", "section": "5.5 Application Space Requirements", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=18" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-02", "kind": "Platform requirement", "title": "Execution of applications, scripts and utilities shall be restricted to authoris…", "text": "Execution of applications, scripts and utilities shall be restricted to authorised software. Application allow-listing or equivalent controls shall be applied where technically feasible.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-03", "kind": "Platform requirement", "title": "Applications and utilities shall operate with the minimum privileges required fo…", "text": "Applications and utilities shall operate with the minimum privileges required for their intended functions.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-04", "kind": "Platform requirement", "title": "Applications shall be isolated from the WSCA so that compromise of an applicatio…", "text": "Applications shall be isolated from the WSCA so that compromise of an application does not provide direct access to WSCA processes or resources.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-05", "kind": "Platform requirement", "title": "Applications shall not be able to read, modify or execute WSCA memory unless exp…", "text": "Applications shall not be able to read, modify or execute WSCA memory unless explicitly authorised and required for operation.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-06", "kind": "Platform requirement", "title": "Applications shall have access only to the system interfaces, files, devices and…", "text": "Applications shall have access only to the system interfaces, files, devices and services required for their intended functions.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-07", "kind": "Platform requirement", "title": "Application binaries and security-relevant configuration shall be protected agai…", "text": "Application binaries and security-relevant configuration shall be protected against unauthorised modification.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-08", "kind": "Platform requirement", "title": "Applications shall not establish network connections to untrusted networks unles…", "text": "Applications shall not establish network connections to untrusted networks unless explicitly required and authorised.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-09", "kind": "Platform requirement", "title": "Applications shall be prevented from accessing WSCA security-relevant data unles…", "text": "Applications shall be prevented from accessing WSCA security-relevant data unless explicitly authorised.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-10", "kind": "Platform requirement", "title": "Applications shall be configured and controlled to prevent exploitation of appli…", "text": "Applications shall be configured and controlled to prevent exploitation of application vulnerabilities from resulting in unauthorised privilege escalation affecting the WSCA.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-11", "kind": "Platform requirement", "title": "Security-relevant application events that could indicate an attempt to compromis…", "text": "Security-relevant application events that could indicate an attempt to compromise the WSCA environment shall be logged where appropriate.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-12", "kind": "Platform requirement", "title": "Applications installed on the platform shall be subject to vulnerability managem…", "text": "Applications installed on the platform shall be subject to vulnerability management. Unnecessary or unsupported applications shall be removed.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "APP-13", "kind": "Platform requirement", "title": "Applications in the WSCA environment shall be monitored for security-relevant an…", "text": "Applications in the WSCA environment shall be monitored for security-relevant anomalies, including unauthorised execution, unexpected application behaviour, suspicious process activity, and indicators of compromise. Detected events shall be reported to the platform's security monitoring mechanisms for analysis, alerting, and incident response.", "section": "5.5 Application Space Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#app-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-01", "kind": "Platform requirement", "title": "Container images shall contain only the software, libraries and configuration re…", "text": "Container images shall contain only the software, libraries and configuration required for the intended WSCA function.", "section": "5.6 Container / Isolation Layer Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-02", "kind": "Platform requirement", "title": "Only authorised container images and workloads shall be permitted to execute. Co…", "text": "Only authorised container images and workloads shall be permitted to execute. Container images shall originate from controlled and trusted sources.", "section": "5.6 Container / Isolation Layer Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-03", "kind": "Platform requirement", "title": "Containers shall execute with the minimum privileges required. Privileged contai…", "text": "Containers shall execute with the minimum privileges required. Privileged containers shall not be used unless explicitly justified and authorised.", "section": "5.6 Container / Isolation Layer Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=19" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-04", "kind": "Platform requirement", "title": "Containers shall be isolated from the host, other containers and unrelated proce…", "text": "Containers shall be isolated from the host, other containers and unrelated processes using the platform's available isolation mechanisms.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-05", "kind": "Platform requirement", "title": "Container resource controls shall prevent one container from accessing or exhaus…", "text": "Container resource controls shall prevent one container from accessing or exhausting memory resources in a manner that could compromise the WSCA or the underlying platform.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-06", "kind": "Platform requirement", "title": "Container access to host devices, filesystems, kernel interfaces and other host …", "text": "Container access to host devices, filesystems, kernel interfaces and other host resources shall be explicitly restricted. Unnecessary host mounts and device access shall not be permitted.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-07", "kind": "Platform requirement", "title": "Container images, runtime components and container configuration shall be integr…", "text": "Container images, runtime components and container configuration shall be integrity-protected and changes shall be controlled.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-08", "kind": "Platform requirement", "title": "Container network connectivity shall be restricted to the connections required f…", "text": "Container network connectivity shall be restricted to the connections required for WSCA operation. Unnecessary external network access shall be prevented.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-09", "kind": "Platform requirement", "title": "Containers shall not have access to WSCA security-relevant data unless such acce…", "text": "Containers shall not have access to WSCA security-relevant data unless such access is explicitly required for the WSCA function.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-10", "kind": "Platform requirement", "title": "Container configuration and runtime controls shall prevent container processes f…", "text": "Container configuration and runtime controls shall prevent container processes from escaping their isolation boundary or obtaining unauthorised host privileges.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-11", "kind": "Platform requirement", "title": "Container runtime and security events relevant to the protection of the WSCA sha…", "text": "Container runtime and security events relevant to the protection of the WSCA shall be logged and made available for monitoring where appropriate.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-12", "kind": "Platform requirement", "title": "Container images, runtimes and supporting components shall be regularly assessed…", "text": "Container images, runtimes and supporting components shall be regularly assessed for vulnerabilities. Vulnerable or unsupported images and components shall be updated or removed.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "CONT-13", "kind": "Platform requirement", "title": "The container runtime and isolation mechanisms shall be monitored for security-r…", "text": "The container runtime and isolation mechanisms shall be monitored for security-relevant anomalies, including unauthorised container creation or modification, attempted isolation-boundary violations, unexpected resource access, and suspicious workload behaviour. Detected events shall be reported to the platform's security monitoring mechanisms for analysis, alerting, and incident response.", "section": "5.6 Container / Isolation Layer Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#cont-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-01", "kind": "Platform requirement", "title": "The WSCA execution environment shall contain only the runtime components, librar…", "text": "The WSCA execution environment shall contain only the runtime components, libraries, configuration and supporting functionality required by the WSCA.", "section": "5.7 WSCA Execution Environment Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-04", "kind": "Platform requirement", "title": "The WSCA shall be isolated from unrelated applications, services and processes s…", "text": "The WSCA shall be isolated from unrelated applications, services and processes such that compromise of another component does not provide direct access to the WSCA.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-05", "kind": "Platform requirement", "title": "The WSCA execution environment shall enforce memory protection mechanisms preven…", "text": "The WSCA execution environment shall enforce memory protection mechanisms preventing unauthorised access to WSCA memory and security-relevant runtime data.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-06", "kind": "Platform requirement", "title": "The WSCA shall have access only to the platform interfaces, devices, files and s…", "text": "The WSCA shall have access only to the platform interfaces, devices, files and services required for its specified operation.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-07", "kind": "Platform requirement", "title": "WSCA binaries, libraries and security-relevant configuration shall be protected …", "text": "WSCA binaries, libraries and security-relevant configuration shall be protected against unauthorised modification.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-08", "kind": "Platform requirement", "title": "Network communication from the WSCA shall be restricted to explicitly authorised…", "text": "Network communication from the WSCA shall be restricted to explicitly authorised endpoints and protocols required for its operation.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-09", "kind": "Platform requirement", "title": "Security-relevant WSCA data shall be protected against unauthorised disclosure, …", "text": "Security-relevant WSCA data shall be protected against unauthorised disclosure, modification and deletion by the underlying platform and other processes.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-10", "kind": "Platform requirement", "title": "The execution environment shall prevent the WSCA or its supporting components fr…", "text": "The execution environment shall prevent the WSCA or its supporting components from obtaining privileges beyond those required for their specified functions.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-11", "kind": "Platform requirement", "title": "Security-relevant events affecting the WSCA execution environment shall be logge…", "text": "Security-relevant events affecting the WSCA execution environment shall be logged where necessary to support detection and investigation of security events.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-12", "kind": "Platform requirement", "title": "All runtime components, libraries and supporting software on which the WSCA depe…", "text": "All runtime components, libraries and supporting software on which the WSCA depends shall be subject to vulnerability management and security-update processes.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-13", "kind": "Platform requirement", "title": "The WSCA execution environment shall be continuously monitored for security-rele…", "text": "The WSCA execution environment shall be continuously monitored for security-relevant anomalies, including unauthorised changes to runtime components or configuration, unexpected WSCA behaviour, suspicious resource access, and indicators of compromise. Detected events shall be reported to the platform's security monitoring mechanisms for analysis, alerting, and incident response.", "section": "5.7 WSCA Execution Environment Requirements", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=21" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-02", "kind": "Platform requirement", "title": "Only authorised WSCA binaries, libraries and supporting components shall be perm…", "text": "Only authorised WSCA binaries, libraries and supporting components shall be permitted to execute within the WSCA execution environment.", "section": "5.7 WSCA Execution Environment Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA conditions", "document_title": "Conditions for the Underlying Platform Supporting AVA_VAN.5 Evaluation", "version": "RC1.1", "id": "WSCA-03", "kind": "Platform requirement", "title": "The WSCA shall execute with the minimum operating system and platform privileges…", "text": "The WSCA shall execute with the minimum operating system and platform privileges required to perform its specified security functions.", "section": "5.7 WSCA Execution Environment Requirements", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca-conditions#wsca-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-conditions-RC1.1_-_for_publ.pdf#page=20" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_GEN.1", "kind": "Security functional requirement (SFR)", "title": "Audit Data Generation", "text": "FAU_GEN.1.1: The TSF shall generate an audit record of the following auditable events: a) TOE start-up and shutdown; b) All auditable events for the not specified level of audit; c) each signing operation, including the wallet user identifier; d) authentication failure; e) wallet instance and user lifecycle events (registration, suspension, deprovisioning); f) administrative and management operations (FMT_SMF.1); and g) all self-test results (FPT_TST.1) and secure initialization (FPT_INI.1). h) failures listed in FPT_FLS.1 and FPT_RCV.4. i) warning that audit trail is near full capacity (FAU_STG_EXT.3) j) failing checks related to transaction-bound authentication evidence (FIA_UAE_EXT.1) k) failure of establishing or detected attacks on a secure or trusted channel (FTP_PRO.3/* and FPT_ITC.1/*) l) failure of identification or authentication. m)detection of integrity or authenticity errors in stored user data. n) migration of user key bindings from one wallet user to another by the Wallet Provider o) [assignment: other specifically defined auditable events]. FAU_GEN.1.2: The TSF shall record within the audit data at least the following information: a) Date and time of the auditable event, type of event, subject identity (if applicable), and the outcome (success or failure) of the event; b) For each auditable event type, based on the auditable event definitions of the functional components included in the PP, PP-Module, functional package or ST, [assignment: other audit relevant information].", "section": "6.1 Class FAU — Security Audit", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_gen-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_GEN.2", "kind": "Security functional requirement (SFR)", "title": "User identity association", "text": "FAU_GEN.2.1: For audit events resulting from actions of identified users, the TSF shall be able to associate each auditable event with the identity of the user that caused the event.", "section": "6.1 Class FAU — Security Audit", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_gen-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_SAR.1", "kind": "Security functional requirement (SFR)", "title": "Audit review", "text": "FAU_SAR.1.1: The TSF shall provide Wallet Provider with the capability to read [assignment: list of audit information] from the audit data. FAU_SAR.1.2: The TSF shall provide the audit data in a manner suitable for the user to interpret the information.", "section": "6.1 Class FAU — Security Audit", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_sar-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_STG_EXT.1", "kind": "Security functional requirement (SFR)", "title": "Protected Audit Event Storage", "text": "FAU_STG_EXT.1.1: The TSF shall be able to transmit the generated audit data to an external IT entity. FAU_STG_EXT.1.2: The TSF shall be able to store generated audit data on the TOE itself. FAU_STG_EXT.1.3: The TSF shall maintain a [selection: log file, database, buffer, [assignment: other local logging method]] of audit records in the event that an interruption of communication with the remote audit server occurs. FAU_STG_EXT.1.4: The TSF shall be able to store [selection: persistent, non-persistent] audit records locally with a minimum storage size of [assignment: number of records and/or file/buffer size(s)]. FAU_STG_EXT.1.5: The TSF shall reject remote API requests from Wallet Instances when the local storage space for audit data is full. FAU_STG_EXT.1.6: The TSF shall ensure the authenticity and integrity of the audit data when stored on an external IT entity or the TOE itself with cryptographic means.", "section": "6.1 Class FAU — Security Audit", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_stg_ext-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=35" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_STG_EXT.2", "kind": "Security functional requirement (SFR)", "title": "Counting Lost Audit Data", "text": "FAU_STG_EXT.2.1: The TSF shall provide information about the number of dropped audit records the case where the local storage has been filled and the TSF takes one of the actions defined in FAU_STG_EXT.1.5.", "section": "6.1 Class FAU — Security Audit", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_stg_ext-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FAU_STG_EXT.3", "kind": "Security functional requirement (SFR)", "title": "Notification in Case of Possible Audit Data Loss", "text": "FAU_STG_EXT.3.1: The TSF shall generate a warning to inform [selection: Wallet Provider, Technical Administrator] before the audit trail exceeds the local audit trail storage capacity.", "section": "6.1 Class FAU — Security Audit", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fau_stg_ext-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCO_NRO.2", "kind": "Security functional requirement (SFR)", "title": "Enforced proof of origin", "text": "FCO_NRO.2.1: The TSF shall enforce the generation of evidence of origin for transmitted API requests from the Wallet Instance handled by the TOE at all times. FCO_NRO.2.2: The TSF shall be able to relate the Wallet Instance identifier of the originator of the information, and the transaction identifier, UTC timestamp of the information to which the evidence applies. FCO_NRO.2.3: The TSF shall provide a capability to verify the evidence of origin of information to the Wallet Provider given the corresponding audit record is retained by the audit log server.", "section": "6.2 Class FCO — Communication", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fco_nro-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCO_NRR.2", "kind": "Security functional requirement (SFR)", "title": "Enforced proof of receipt", "text": "FCO_NRR.2.1: The TSF shall enforce the generation of evidence of receipt for received API requests from the Wallet Instance handled by the TOE at all times. FCO_NRR.2.2: The TSF shall be able to relate the session identifier of the recipient of the information, and the Wallet Instance’s certificate, public key or thumbprint and the transaction identifier of the information to which the evidence applies. FCO_NRR.2.3: The TSF shall provide a capability to verify the evidence of receipt of information to the Wallet Provider given the corresponding audit record is retained by the audit log server.", "section": "6.2 Class FCO — Communication", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fco_nrr-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=36" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_CKM.1", "kind": "Security functional requirement (SFR)", "title": "Cryptographic key generation", "text": "FCS_CKM.1.1: The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [assignment: cryptographic key generation algorithm] and specified cryptographic key sizes [assignment: cryptographic key sizes] that meet the following: [assignment: list of standards].", "section": "6.3 Class FCS — Cryptographic Support", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_ckm-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=37" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_CKM.2", "kind": "Security functional requirement (SFR)", "title": "Cryptographic key distribution", "text": "FCS_CKM.2.1: The TSF shall distribute cryptographic keys in accordance with a specified cryptographic key distribution method [assignment: cryptographic key distribution method] that meets the following: [assignment: list of standards].", "section": "6.3 Class FCS — Cryptographic Support", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_ckm-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=37" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_CKM.5", "kind": "Security functional requirement (SFR)", "title": "Cryptographic key derivation", "text": "FCS_CKM.5.1: The TSF shall derive cryptographic keys [assignment: key type] from [assignment: input parameters] in accordance with a specified key derivation algorithm [assignment: key derivation algorithm] and specified cryptographic key sizes [assignment: list of key sizes] that meet the following: [assignment: list of standards].", "section": "6.3 Class FCS — Cryptographic Support", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_ckm-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=37" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_CKM.6", "kind": "Security functional requirement (SFR)", "title": "Timing and event of cryptographic key destruction", "text": "FCS_CKM.6.1: The TSF shall destroy all TSF generated and/or maintained keys and key material, including per-key authorisation data when no longer needed, during revocation, deprovisioning, factory reset or authorized deletion is requested. FCS_CKM.6.2: The TSF shall destroy cryptographic keys and keying material specified by FCS_CKM.6.1 in accordance with a specified cryptographic key destruction method [assignment: cryptographic key destruction method] that meets the following: [assignment: list of standards].", "section": "6.3 Class FCS — Cryptographic Support", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_ckm-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=37" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_COP.1", "kind": "Security functional requirement (SFR)", "title": "Cryptographic operation", "text": "FCS_COP.1.1: The TSF shall perform [assignment: list of cryptographic operations]", "section": "6.3 Class FCS — Cryptographic Support", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_cop-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FCS_RBG.1", "kind": "Security functional requirement (SFR)", "title": "Random bit generation (RBG)", "text": "FCS_RBG.1.1: The TSF shall perform deterministic random bit generation services using [assignment: RBG algorithm] in accordance with [assignment: list of standards] after initialization with a seed. FCS_RBG.1.2: The TSF shall use a [selection: TSF noise source [assignment: name of noise source], TSF interface for seeding] for initialized seeding. FCS_RBG.1.3: The TSF shall update the RBG state by [selection: reseeding, uninstantiating and re instantiating] using a [selection: TSF noise source [assignment: name of noise source], TSF interface for seeding] in the following situations: [selection: — never; — on demand; — on the condition: [assignment: condition]; — after [assignment: time]] in accordance with [assignment: list of standards].", "section": "6.3 Class FCS — Cryptographic Support", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fcs_rbg-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACC.1/User_Creation", "kind": "Security functional requirement (SFR)", "title": "Access Control Policy", "text": "FDP_ACC.1.1/User_Creation: The TSF shall enforce the User Creation SFP on - Subject: Wallet Provider or Wallet Instance - Objects: Wallet User - Operations: Create new user The TOE creates a Wallet User with information provided by the subject.", "section": "6.4 Class FDP — User Data Protection", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acc-1-user_creation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACF.1/User_Creation", "kind": "Security functional requirement (SFR)", "title": "Access control functions", "text": "FDP_ACF.1.1/User_Creation: The TSF shall enforce the User Creation SFP to objects based on the following: whether the subject is a Wallet Provider or Wallet Instance authorised to create a new Wallet User. FDP_ACF.1.2/User_Creation: The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: only a Wallet Provider or Wallet Instance who has been authorised for creation of new users can carry out the operation. FDP_ACF.1.3/User_Creation: The TSF shall explicitly authorize access of subjects to objects based on the following additional rules: none. FDP_ACF.1.4/User_Creation: The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [assignment: rules, based on security attributes, that explicitly deny access of subjects to objects].", "section": "6.4 Class FDP — User Data Protection", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acf-1-user_creation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=38" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACC.1/Key_Management", "kind": "Security functional requirement (SFR)", "title": "Access Control Policy", "text": "FDP_ACC.1.1/Key_Creation: The TSF shall enforce the Key Creation SFP on - Subject: Wallet Instance - Objects: Asymmetric key pairs or symmetric keys - Operations: Create or delete new key or key pair Wallet Instances instructs the TOE to request the WSCD to generate/delete new keys/key pairs and assigns it to a Wallet User.", "section": "6.4 Class FDP — User Data Protection", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acc-1-key_management", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=39" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACF.1/Key_Management", "kind": "Security functional requirement (SFR)", "title": "Access control functions", "text": "FDP_ACF.1.1/Key_Creation: The TSF shall enforce the Key Creation SFP to objects based on the following: the wallet instance is authorised to create, delete a symmetric key or asymmetric key pairs for a Wallet User. FDP_ACF.1.2/Key_Creation: The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: the wallet instance requesting the creation of the key or key pair is authorised to carry out the operation. FDP_ACF.1.3/Key_Creation: The TSF shall explicitly authorize access of subjects to objects based on the following additional rules: none. FDP_ACF.1.4/Key_Creation: The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [assignment: rules, based on security attributes, that explicitly deny access of subjects to objects].", "section": "6.4 Class FDP — User Data Protection", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acf-1-key_management", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=39" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACC.1/Operation", "kind": "Security functional requirement (SFR)", "title": "Access Control Policy", "text": "FDP_ACC.1.1/Operation: The TSF shall enforce the Operation SFP on - Subject: Wallet User - Objects: Wallet User user-bound assets (including keys or key pairs) - Operations: (Per-key-authorized) Operations with Wallet User user-bound assets The TOE instructs the WSCD to carry out operations on and with the Wallet Users assets only where it corresponds to an assets within the WSCD-HSM that is bound to the identified Wallet User using per-key-authorization data provided by the wallet instance. - Subject: Wallet User - Objects: Wallet User user-bound assets (including keys or key pairs) - Operations: PIN reset The TOE instructs the WSCD to carry out PIN reset when the correct PUK was provided. - Subject: Wallet User - Objects: Wallet User user bound assets - Operation: Wallet User can clear or delete the Wallet User bound assets or migrate them to a different Wallet Instance. (This does not include the WSCD-stored plaintext private keys, only their reference, keyblobs and management).", "section": "6.4 Class FDP — User Data Protection", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acc-1-operation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=39" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_ACF.1/Operation", "kind": "Security functional requirement (SFR)", "title": "Access control functions", "text": "FDP_ACF.1.1/Operation: The TSF shall enforce the Operation SFP to objects based on the following: whether the subject is a Wallet User or Wallet Provider authorised to carry out the operation or resets the PIN using the correct PUK. FDP_ACF.1.2/Operation: The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: • only an authorized Wallet User is allowed to carry out operations using the keys or key pairs • a Wallet User is only allowed to carry out operations using their user-bound keys. • the authentication evidence is valid and bound to the current transaction. • the identifier of the Wallet User does match the user bound to the key or key pair • the Wallet User is active. • the integrity of all operation related assets was verified. • the Wallet Provider carrying out operations is authorized and authenticated. FDP_ACF.1.3/Operation: The TSF shall explicitly authorize access of subjects to objects based on the following additional rules: none. FDP_ACF.1.4/Operation: The TSF shall explicitly deny access of subjects to objects based on the following additional rules: any direct key access or key export requests for keys residing in the WSCD shall be denied [assignment: additional rules, based on security attributes, that explicitly deny access of subjects to objects].", "section": "6.4 Class FDP — User Data Protection", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_acf-1-operation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=39" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_RIP.2", "kind": "Security functional requirement (SFR)", "title": "Full residual information protection", "text": "FDP_RIP.2.1: The TSF shall ensure that any previous information content of a resource is made unavailable upon the deallocation of the resource from all objects.", "section": "6.4 Class FDP — User Data Protection", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_rip-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_SDI.1", "kind": "Security functional requirement (SFR)", "title": "Stored data integrity monitoring", "text": "FDP_SDI.1.1: The TSF shall monitor user data stored in containers controlled by the TSF or in its operative environment for integrity or authenticity errors on all objects, based on the following attributes: the integrity and authenticity check value bound to each stored object.", "section": "6.4 Class FDP — User Data Protection", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_sdi-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FDP_SDC.1", "kind": "Security functional requirement (SFR)", "title": "Stored data confidentiality", "text": "FDP_SDC.1.1: The TSF shall ensure the confidentiality of the following user data: session keys and WSCA-stored private keys while it is stored in the persistent memory (including the external database).", "section": "6.4 Class FDP — User Data Protection", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fdp_sdc-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_AFL.1/Wallet", "kind": "Security functional requirement (SFR)", "title": "Authentication failure handling", "text": "FIA_AFL.1.1/Wallet: The TSF shall detect when [selection: [assignment: positive integer number], an administrator configurable positive integer within [assignment: range of acceptable values]] unsuccessful authentication attempts occur related to the authentication of the wallet user following FIA_UAE_EXT.1. FIA_AFL.1.2/Wallet: When the defined number of unsuccessful authentication attempts has been met, the TSF shall lock the wallet user and notify the wallet user via an out-of-band notification channel.", "section": "6.5 Class FIA — Identification and Authentication", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_afl-1-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_AFL.1/Provider", "kind": "Security functional requirement (SFR)", "title": "Authentication failure handling", "text": "FIA_AFL.1.1/Provider: The TSF shall detect when [selection: [assignment: positive integer number], an administrator configurable positive integer within [assignment: range of acceptable values]] unsuccessful authentication attempts occur related to the authentication of the wallet provider. FIA_AFL.1.2/Provider: When the defined number of unsuccessful authentication attempts has been met, the TSF shall [assignment: list of actions]", "section": "6.5 Class FIA — Identification and Authentication", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_afl-1-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=40" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_AFL.1/Instance", "kind": "Security functional requirement (SFR)", "title": "Authentication failure handling", "text": "FIA_AFL.1.1/Instance: The TSF shall detect when [selection: [assignment: positive integer number], an administrator configurable positive integer within [assignment: range of acceptable values]] unsuccessful authentication attempts occur related to the authentication of the wallet instance. FIA_AFL.1.2/Instance: When the defined number of unsuccessful authentication attempts has been met, the TSF shall [assignment: list of actions].", "section": "6.5 Class FIA — Identification and Authentication", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_afl-1-instance", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_ATD.1/Wallet", "kind": "Security functional requirement (SFR)", "title": "User attribute definition", "text": "FIA_ATD.1.1/Wallet: The TSF shall maintain the following list of security attributes belonging to individual users: a) wallet instance and wallet user identifier b) the registered Wallet Instance authentication credential, used both for authentication of the communication session and for verification of signatures over User Authentication Evidence c) the Authentication Reference Data against which the knowledge- and possession-based factor of the User Authentication Evidence is verified d) the binding records associating the wallet user with its wrapped key blobs, its attested key pairs and, where the WIA device-binding key pair is managed by the WSCA/WSCD, that key pair e) the per-key authorisation data associated with the wallet user for access to the WSCD-HSM, for the duration of the operation for which it was provided f) the authentication failure counter g) the wallet user status (active / suspended / deprovisioned) h) the integrity check value and version counter bound to the stored attributes of the wallet user i) [assignment: additional user security attributes].", "section": "6.5 Class FIA — Identification and Authentication", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_atd-1-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_ATD.1/Provider", "kind": "Security functional requirement (SFR)", "title": "User attribute definition", "text": "FIA_ATD.1.1/Provider: The TSF shall maintain the following list of security attributes belonging to individual users: a) the Wallet Provider identifier b) the Wallet Provider authentication reference data c) [assignment: additional provider security attributes]", "section": "6.5 Class FIA — Identification and Authentication", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_atd-1-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_USB.1/Wallet", "kind": "Security functional requirement (SFR)", "title": "User-subject binding", "text": "FIA_USB.1.1/Wallet: The TSF shall associate the following user security attributes with subjects acting on the behalf of that user: • the wallet instance and wallet user identifier • the wallet instance and wallet user authentication data • the wallet user status defined in FIA_ATD.1/Wallet • the binding records in FIA_ATD.1.1/Wallet • the per-key authorisation data in FIA_ATD.1.1/Wallet • [assignment: list of user security attributes] FIA_USB.1.2/Wallet: The TSF shall enforce the following rules on the initial association of user security attributes with subjects acting on the behalf of users: • the wallet instance identifier and the registered Wallet Instance authentication credential shall be associated only after successful identification in accordance with FIA_UID.2 and successful establishment of a trusted channel in accordance with FTP_PRO.2/Wallet • the wallet user identifier, the wallet user status, the binding records and the per-key authorisation data shall be associated only after successful verification of authentication evidence in accordance with FIA_UAE_EXT.1 against the Authentication Reference Data registered for that wallet user • only the attributes of the wallet user for whom the identified wallet instance is registered shall be associated • only the binding records and per-key authorisation data for the keys bound to that wallet user shall be associated • no attribute shall be associated where the wallet user status is other than active • no attribute shall be associated where an integrity or authenticity error has been detected in accordance with FDP_SDI.1 on the stored attributes concerned • [assignment: rules for the initial association of attributes] FIA_USB.1.3/Wallet: The TSF shall enforce the following rules governing changes to the user security attributes associated with subjects acting on the behalf of users: • the attributes associated under FIA_USB.1.2/Wallet • shall remain associated only for the operation for which the authentication evidence was verified, and shall be dissociated on completion of that operation or on expiry of the validity window of that evidence, whichever occurs first; • no associated attribute shall be modified at the request of the subject; • the authentication failure counter may change as a result of FIA_AFL.1; • a change of the wallet user status to suspended or deprovisioned shall take effect immediately and shall cause dissociation of all attributes associated with subjects acting on behalf of that wallet user; • a change to the binding records or to the per-key authorisation data shall take effect on the next association only. • [assignment: rules for the changing of attributes].", "section": "6.5 Class FIA — Identification and Authentication", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_usb-1-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=41" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_USB.1/Provider", "kind": "Security functional requirement (SFR)", "title": "User-subject binding", "text": "FIA_USB.1.1/Provider: The TSF shall associate the following user security attributes with subjects acting on the behalf of that user: • the wallet provider identifier • the wallet provider authentication data • [assignment: list of user security attributes] FIA_USB.1.2/Provider: The TSF shall enforce the following rules on the initial association of user security attributes with subjects acting on the behalf of users: • attributes shall be associated only after successful identification in accordance with FIA_UID.2 and successful establishment of a trusted channel in accordance with FTP_PRO.2/Provider. • only the attributes of the Wallet Provider identified by the presented credential shall be associated; • only the role and the management functions for which that Wallet Provider is authorised shall be associated. FIA_USB.1.3/Provider: The TSF shall enforce the following rules governing changes to the user security attributes associated with subjects acting on the behalf of users: • no associated attribute shall change for the duration of the association; • revocation or modification of the Wallet Provider authentication reference data shall cause dissociation of all attributes associated with subjects acting on its behalf; • a change to the role or to the permitted management functions shall take effect on the next association only", "section": "6.5 Class FIA — Identification and Authentication", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_usb-1-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=42" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_UAU.2", "kind": "Security functional requirement (SFR)", "title": "User authentication before any action", "text": "FIA_UAU.2.1: The TSF shall require each user to be successfully authenticated before allowing any other TSF mediated actions on behalf of that user.", "section": "6.5 Class FIA — Identification and Authentication", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_uau-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_UAU.6", "kind": "Security functional requirement (SFR)", "title": "Re-authenticating", "text": "FIA_UAU.6.1: The TSF shall re-authenticate the user under the conditions before each signing request and for each credential management operation.", "section": "6.5 Class FIA — Identification and Authentication", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_uau-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_UID.2", "kind": "Security functional requirement (SFR)", "title": "User identification before any action", "text": "FIA_UID.2.1: The TSF shall require each user to be successfully identified before allowing any TSF-mediated actions on behalf of that user.", "section": "6.5 Class FIA — Identification and Authentication", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_uid-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_UAE_EXT.1", "kind": "Security functional requirement (SFR)", "title": "Transaction-bound authentication evidence", "text": "FIA_UAE_EXT.1.1: The TSF shall generate, for each request to perform an operation in [assignment: list of operations requiring authentication evidence], a challenge with a minimum of 128 bits of entropy obtained from a random bit generation function meeting FCS_RBG.1. FIA_UAE_EXT.1.2: The TSF shall construct, for each challenge, a transaction context comprising the challenge, the identity of the user, the requested operation, and the wallet user identifier and [assignment: other transaction attributes] and shall associate that transaction context with the communication session on which the request was received. FIA_UAE_EXT.1.3: The TSF shall require that authentication evidence cryptographically bound to the transaction context of the requested operation be presented before the TSF performs any operation in operations defined in FIA_UAE_EXT.1.1. FIA_UAE_EXT.1.4: The TSF shall verify presented authentication evidence against the authentication reference data associated with the identified user and shall verify that the evidence demonstrates that each authentication factor in a) the possession-based factor of the wallet user and b) the knowledge-based factor derived from the PIN was verified. FIA_UAE_EXT.1.5: The TSF shall verify that presented authentication evidence was received no more than [assignment: validity period] after the corresponding challenge was issued. FIA_UAE_EXT.1.6: The TSF shall deny the requested operation if any verification required by FIA_UAE_EXT.1.3, FIA_UAE_EXT.1.4 or FIA_UAE_EXT.1.5 fails.", "section": "6.5 Class FIA — Identification and Authentication", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_uae_ext-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FIA_UAE_EXT.2", "kind": "Security functional requirement (SFR)", "title": "Single-use enforcement for authentication evidence", "text": "FIA_UAE_EXT.2.1: The TSF shall maintain a nonce registry covering all transaction identifiers issued and all evidence received within the validity window defined in FIA_UAE_EXT.1.5. FIA_UAE_EXT.2.2: The TSF shall deny the requested operation if the presented authentication evidence refers to a challenge that was not issued by the TSF, that has already been used in successful verification, or whose validity period has expired.", "section": "6.5 Class FIA — Identification and Authentication", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fia_uae_ext-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_SMR.1", "kind": "Security functional requirement (SFR)", "title": "Security roles", "text": "FMT_SMR.1.1: The TSF shall maintain the roles • Wallet User • Wallet Instance • Wallet Provider • [assignment: additional authorized identified roles]. FMT_SMR.1.2: The TSF shall be able to associate users with roles.", "section": "6.6 Class FMT — Security Management", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_smr-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=43" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_SMF.1", "kind": "Security functional requirement (SFR)", "title": "Specification of Management Functions", "text": "FMT_SMF.1.1: The TSF shall be capable of performing the following management functions: • For the Wallet Provider: o TOE unique self-identification of version and configuration o TOE maintenance o Audit data review o Factory Reset o Deletion or reset of user authentication data o [assignment: list of management functions to be provided by the TSF]. • For the Wallet User: o Modifying user authentication data o PIN reset using PUK o Wallet Instance Migration", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_smf-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.1/User_Creation", "kind": "Security functional requirement (SFR)", "title": "Management of security attributes", "text": "FMT_MSA.1.1/User_Creation: The TSF shall enforce the User Creation SFP to restrict the ability to modify the security attributes that are Wallet User related as defined in FIA_USB.1/Wallet to the Wallet Provider or Wallet Instance.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-1-user_creation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.3/User_Creation", "kind": "Security functional requirement (SFR)", "title": "Static attribute initialization", "text": "FMT_MSA.3.1/User_Creation: The TSF shall enforce the User Creation SFP to provide restrictive default values for security attributes that are used to enforce the SFP. FMT_MSA.3.2/User_Creation: The TSF shall allow the Wallet Provider or Wallet Instance to specify alternative initial values to override the default values when an object or information is created.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-3-user_creation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.1/Key_Management", "kind": "Security functional requirement (SFR)", "title": "Management of security attributes", "text": "FMT_MSA.1.1/Key_Management: The TSF shall enforce the Key Management SFP to restrict the ability to modify, delete the security attributes Wallet User keys related attributes as defined in FIA_USB.1/Wallet to the Wallet Instance or Wallet Provider (deletion only).", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-1-key_management", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.3/Key_Management", "kind": "Security functional requirement (SFR)", "title": "Static attribute initialization", "text": "FMT_MSA.3.1/Key_Management: The TSF shall enforce the Key Management SFP to provide restrictive default values for security attributes that are used to enforce the SFP. FMT_MSA.3.2/Key_Management: The TSF shall allow the Wallet Instance to specify alternative initial values to override the default values when an object or information is created.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-3-key_management", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.1/Operation", "kind": "Security functional requirement (SFR)", "title": "Management of security attributes", "text": "FMT_MSA.1.1/Operation: The TSF shall enforce the Operation SFP to restrict the ability to query the security attributes Wallet User keys related attributes as defined in FIA_USB.1/Wallet to the Wallet User.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-1-operation", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MSA.2", "kind": "Security functional requirement (SFR)", "title": "Secure security attributes", "text": "FMT_MSA.2.1: The TSF shall ensure that only secure values are accepted for attributes defined in FIA_USB.1/Wallet and FIA_USB.1/Provider.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_msa-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MTD.1/Provider", "kind": "Security functional requirement (SFR)", "title": "Management of TSF data", "text": "FMT_MTD.1.1/Provider: The TSF shall restrict the ability to modify the Wallet Provider and WSCD authentication data to Wallet Provider.", "section": "6.6 Class FMT — Security Management", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_mtd-1-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=44" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MTD.1/User", "kind": "Security functional requirement (SFR)", "title": "Management of TSF data", "text": "FMT_MTD.1.1/Provider: The TSF shall restrict the ability to modify the their Wallet User authentication data to an authenticated Wallet User. However, delete and clear are available for the Wallet Provider.", "section": "6.6 Class FMT — Security Management", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_mtd-1-user", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FMT_MTD.1/Instance", "kind": "Security functional requirement (SFR)", "title": "Management of TSF data", "text": "FMT_MTD.1.1/Provider: The TSF shall restrict the ability to modify the their Wallet Instance authentication data to an authenticated Wallet Instance. However, delete and clear are available for the Wallet Provider.", "section": "6.6 Class FMT — Security Management", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fmt_mtd-1-instance", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_FLS.1", "kind": "Security functional requirement (SFR)", "title": "Failure with preservation of secure state", "text": "FPT_FLS.1.1: The TSF shall preserve a secure state when the following types of failures occur: WSCD-HSM connection failure; credential store integrity check failure; audit log unavailability; [assignment: additional types of failures in the TSF].", "section": "6.7 Class FPT — Protection of the TSF", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_fls-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_ITC.1", "kind": "Security functional requirement (SFR)", "title": "Inter-TSF confidentiality during transmission", "text": "FPT_ITC.1.1: The TSF shall protect all TSF data transmitted from the TSF to another trusted IT product the WSCD-HSM from unauthorized disclosure during transmission.", "section": "6.7 Class FPT — Protection of the TSF", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_itc-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_ITI.1", "kind": "Security functional requirement (SFR)", "title": "Inter-TSF detection of modification", "text": "FPT_ITI.1.1: The TSF shall provide the capability to detect modification of all TSF data during transmission between the TSF and another trusted IT product the WSCD-HSM within the following metric: [assignment: a defined modification metric]. FPT_ITI.1.2: The TSF shall provide the capability to verify the integrity of all TSF data transmitted between the TSF and another trusted IT product the WSCD-HSM and perform [assignment: action to be taken] if modifications are detected.", "section": "6.7 Class FPT — Protection of the TSF", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_iti-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_RCV.4", "kind": "Security functional requirement (SFR)", "title": "Function recovery", "text": "FPT_RCV.4.1: The TSF shall ensure that all credential management and HSM operations [assignment: additional list of functions and failure scenarios] have the property that the function either completes successfully, or for the indicated failure scenarios, recovers to a consistent and secure state.", "section": "6.7 Class FPT — Protection of the TSF", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_rcv-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_TST.1", "kind": "Security functional requirement (SFR)", "title": "TSF self-testing", "text": "FPT_TST.1.1: The TSF shall run a suite of the following self-tests during initial start-up, periodically during normal operation, at the request of the authorized user to demonstrate the correct operation of correct operation of cryptographic libraries if applicable; WSCD-HSM connectivity and authentication; credential store integrity; audit log availability; and correct operation of the transaction identifier registry [assignment: other parts of the TSF]: [assignment: list of self-tests run by the TSF]. FPT_TST.1.2: The TSF shall provide authorized users with the capability to verify the integrity of [selection: [assignment: parts of TSF data], TSF data]. FPT_TST.1.3: The TSF shall provide authorized users with the capability to verify the integrity of [selection: [assignment: parts of TSF], TSF].", "section": "6.7 Class FPT — Protection of the TSF", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_tst-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=45" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FPT_INI.1", "kind": "Security functional requirement (SFR)", "title": "TSF initalization", "text": "FPT_INI.1.1: The TOE shall provide an initialization function which is self-protected for integrity and authenticity. FPT_INI.1.2: The TOE initialization function shall ensure that certain properties hold on certain elements immediately before establishing the TSF in a secure initial state, as specified in [table: ID 1 – Properties: integrity – Elements: Software binary, configuration; ID 2 – Properties: [assignment: property, for instance authenticity, integrity, correct version] – Elements: [assignment: list of TSF/user firmware, software or data]] FPT_INI.1.3: The TOE initialization function shall detect and respond to errors and failures during initialization such that the TOE: is halted. FPT_INI.1.4: The TOE initialization function shall only interact with the TSF in a restrictive way that allows for the verification of the properties and elements stated in FPT_INI.1.2 during initialization.", "section": "6.7 Class FPT — Protection of the TSF", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#fpt_ini-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_ITC.1/WSCD-HSM", "kind": "Security functional requirement (SFR)", "title": "Inter-TSF trusted channel", "text": "FTP_ITC.1.1/WSCA-HSM: The TSF shall provide a communication channel between itself and another trusted IT product the WSCD-HSM that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from modification or disclosure. FTP_ITC.1.2/WSCA-HSM: The TSF shall permit [selection: the TSF, another trusted IT product] to initiate communication via the trusted channel. FTP_ITC.1.3/WSCA-HSM: The TSF shall initiate communication via the trusted channel for [assignment: list of functions for which a trusted channel is required].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_itc-1-wscd-hsm", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.1/Wallet", "kind": "Security functional requirement (SFR)", "title": "Trusted channel protocol", "text": "FTP_PRO.1.1/Wallet: The TSF shall implement [assignment: trusted channel protocol] acting as [assignment: defined protocol role(s)] in accordance with: [assignment: list of standards]. FTP_PRO.1.2/Wallet: The TSF shall enforce usage of the trusted channel for any communication between the TOE and the Wallet Instance in accordance with: [assignment: list of standards]. FTP_PRO.1.3/Wallet: The TSF shall permit its peer to initiate communication via the trusted channel. FTP_PRO.1.4/Wallet: The TSF shall enforce the following rules for the trusted channel: • The trusted channel shall be mutually authenticated. • [assignment: rules governing operation and use of the trusted channel and/or its protocol]. FTP_PRO.1.5/Wallet: The TSF shall enforce the following static protocol options: [assignment: list of options and references to standards in which each is defined]. FTP_PRO.1.6/Wallet: The TSF shall negotiate one of the following protocol configurations with its peer: [assignment: list of configurations and reference to standards in which each is defined].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-1-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=46" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.2/Wallet", "kind": "Security functional requirement (SFR)", "title": "Trusted channel establishment", "text": "FTP_PRO.2.1/Wallet: The TSF shall establish a shared secret with its peer using one of the following mechanisms: [assignment: list of key establishment mechanisms]. FTP_PRO.2.2/Wallet: The TSF shall authenticate its peer, itself to its peer using one of the following mechanisms: [assignment: list of authentication mechanisms] and according to the following rules: [assignment: list of rules for carrying out the authentication]. FTP_PRO.2.3/Wallet: The TSF shall use [assignment: key derivation function] to derive the following cryptographic keys from a shared secret: [assignment: list of cryptographic keys].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-2-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.3/Wallet", "kind": "Security functional requirement (SFR)", "title": "Trusted channel data protection", "text": "FTP_PRO.3.1/Wallet: The TSF shall protect data in transit from unauthorised disclosure using one of the following mechanisms: [assignment: list of encryption mechanisms]. FTP_PRO.3.2/Wallet: The TSF shall protect data in transit from modification, deletion, insertion, replay, [assignment: other] using one of the following mechanisms: [assignment: list of integrity protection mechanisms].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-3-wallet", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.1/Provider", "kind": "Security functional requirement (SFR)", "title": "Trusted channel protocol", "text": "FTP_PRO.1.1/Provider: The TSF shall implement [assignment: trusted channel protocol] acting as [assignment: defined protocol role(s)] in accordance with: [assignment: list of standards]. FTP_PRO.1.2/Provider: The TSF shall enforce usage of the trusted channel for any communication between the TOE and the Wallet Provider in accordance with: [assignment: list of standards]. FTP_PRO.1.3/Provider: The TSF shall permit its peer to initiate communication via the trusted channel. FTP_PRO.1.4/Provider: The TSF shall enforce the following rules for the trusted channel: [assignment: rules governing operation and use of the trusted channel and/or its protocol]. • The trusted channel shall be mutually authenticated. • [assignment: rules governing operation and use of the trusted channel and/or its protocol]. FTP_PRO.1.5/Provider: The TSF shall enforce the following static protocol options: [assignment: list of options and references to standards in which each is defined]. FTP_PRO.1.6/Provider: The TSF shall negotiate one of the following protocol configurations with its peer: [assignment: list of configurations and reference to standards in which each is defined].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-1-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.2/Provider", "kind": "Security functional requirement (SFR)", "title": "Trusted channel establishment", "text": "FTP_PRO.2.1/Provider: The TSF shall establish a shared secret with its peer using one of the following mechanisms: [assignment: list of key establishment mechanisms]. FTP_PRO.2.2/Provider: The TSF shall authenticate its peer, itself to its peer using one of the following mechanisms: [assignment: list of authentication mechanisms] and according to the following rules: [assignment: list of rules for carrying out the authentication]. FTP_PRO.2.3/Provider: The TSF shall use [assignment: key derivation function] to derive the following cryptographic keys from a shared secret: [assignment: list of cryptographic keys].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-2-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=47" }, { "document": "NL-CS-WSCA", "document_title": "Protection Profile for WSCA in a remote HSM architecture", "version": "RC1.1", "id": "FTP_PRO.3/Provider", "kind": "Security functional requirement (SFR)", "title": "Trusted channel data protection", "text": "FTP_PRO.3.1/Provider: The TSF shall protect data in transit from unauthorised disclosure using one of the following mechanisms: [assignment: list of encryption mechanisms]. FTP_PRO.3.2/Provider: The TSF shall protect data in transit from modification, deletion, insertion, replay, [assignment: other] using one of the following mechanisms: [assignment: list of integrity protection mechanisms].", "section": "6.8 Class FTP — Trusted Path/Channel", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-cs-wsca#ftp_pro-3-provider", "pdf": "/files/edi-stelsel/2026-11-06/NL-CS-WSCA-RC1.1_-_for_publ.pdf#page=48" }, { "document": "NL-FS-P", "document_title": "PID Issuance Service Conformance (Issuance Requirements)", "version": "RC1.0", "id": "ICS-01", "kind": "ICS statement", "title": "PID issuance service supports PID issuance using OpenID4VCI", "text": "PID issuance service supports PID issuance using OpenID4VCI", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 10, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(5)(a)(i)", "CIR 2024/2982 Art. 4", "CIR 2024/2982 Annex I" ], "url": "/edi-stelsel-certification/requirements/nl-fs-p#ics-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-P_EUDI_Wallet_Functional_Certification_-_PID_Issuance_Service_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-P", "document_title": "PID Issuance Service Conformance (Issuance Requirements)", "version": "RC1.0", "id": "ICS-02", "kind": "ICS statement", "title": "PID issuance service supports PID issuance using the NL-specific issuance specif…", "text": "PID issuance service supports PID issuance using the NL-specific issuance specification", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-fs-p#ics-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-P_EUDI_Wallet_Functional_Certification_-_PID_Issuance_Service_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-P", "document_title": "PID Issuance Service Conformance (Issuance Requirements)", "version": "RC1.0", "id": "ICS-03", "kind": "ICS statement", "title": "PID issuance service supports PIDs in mdoc format", "text": "PID issuance service supports PIDs in mdoc format", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 11, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2977 Art. 3" ], "url": "/edi-stelsel-certification/requirements/nl-fs-p#ics-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-P_EUDI_Wallet_Functional_Certification_-_PID_Issuance_Service_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-P", "document_title": "PID Issuance Service Conformance (Issuance Requirements)", "version": "RC1.0", "id": "ICS-04", "kind": "ICS statement", "title": "PID issuance service supports PIDs in SD-JWT VC format", "text": "PID issuance service supports PIDs in SD-JWT VC format", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 11, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2977 Art. 3" ], "url": "/edi-stelsel-certification/requirements/nl-fs-p#ics-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-P_EUDI_Wallet_Functional_Certification_-_PID_Issuance_Service_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-01", "kind": "ICS statement", "title": "Wallet solution supports wallet user authentication", "text": "Wallet solution supports wallet user authentication", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 3" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-02", "kind": "ICS statement", "title": "Wallet solution supports wallet secure cryptographic devices and wallet secure c…", "text": "Wallet solution supports wallet secure cryptographic devices and wallet secure cryptographic applications", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 4", "CIR 2024/2979 Art. 5" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-03", "kind": "ICS statement", "title": "Wallet solution supports wallet instance attestations", "text": "Wallet solution supports wallet instance attestations", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 6", "CIR 2024/2979 Annex 1b" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-04", "kind": "ICS statement", "title": "Wallet solution supports key attestations", "text": "Wallet solution supports key attestations", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 6", "CIR 2024/2979 Annex 1b" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-05", "kind": "ICS statement", "title": "Wallet solution supports revocation of wallet instance attestations and key atte…", "text": "Wallet solution supports revocation of wallet instance attestations and key attestations", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 7", "CIR 2024/2979 Annex 1b" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-06", "kind": "ICS statement", "title": "Wallet solution supports PID and EAA in ISO/IEC 18013-5 (mdoc) format", "text": "Wallet solution supports PID and EAA in ISO/IEC 18013-5 (mdoc) format", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 7" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-07", "kind": "ICS statement", "title": "Wallet solution supports PID and EAA in SD-JWT VC format", "text": "Wallet solution supports PID and EAA in SD-JWT VC format", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 10, "obligation": "mandatory", "legal_refs": [ "CIR 2024/2979 Art. 7" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-08", "kind": "ICS statement", "title": "Wallet solution supports transaction logs", "text": "Wallet solution supports transaction logs", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(4)(d)(i)", "CIR 2024/2979 Art. 9" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-09", "kind": "ICS statement", "title": "Wallet solution supports embedded disclosure policies", "text": "Wallet solution supports embedded disclosure policies", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(5)(e)", "CIR 2024/2979 Art. 10" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-10", "kind": "ICS statement", "title": "Wallet solution supports qualified electronic signatures and seals", "text": "Wallet solution supports qualified electronic signatures and seals", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(e)", "CIR 2024/2979 Art. 11", "CIR 2024/2979 Art. 12" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-11", "kind": "ICS statement", "title": "Wallet solution supports User data export and portability", "text": "Wallet solution supports User data export and portability", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(f)", "CIR 2024/2979 Art. 13" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-12", "kind": "ICS statement", "title": "Wallet solution supports pseudonyms", "text": "Wallet solution supports pseudonyms", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(b)", "CIR 2024/2979 Art. 14" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-13", "kind": "ICS statement", "title": "Wallet solution supports EUDI Wallet Trust Mark", "text": "Wallet solution supports EUDI Wallet Trust Mark", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "mandatory", "legal_refs": [ "eIDAS Art. 5a(5)(a)(iv)", "CIR 2024/2979 Art. 14a" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-14", "kind": "ICS statement", "title": "Wallet solution supports Strong User Authentication", "text": "Wallet solution supports Strong User Authentication", "section": "6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)", "page": 11, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5f(2)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-15", "kind": "ICS statement", "title": "Wallet solution supports attestation issuance", "text": "Wallet solution supports attestation issuance", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "mandatory", "legal_refs": [ "eIDAS Art. 5a(5)(a)(i)", "CIR 2024/2982 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-15", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-16", "kind": "ICS statement", "title": "Wallet solution support attestation issuance using OpenID4VCI", "text": "Wallet solution support attestation issuance using OpenID4VCI", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "recommended", "legal_refs": [ "CIR 2024/2982 Art. 4", "CIR 2024/2982 Annex I" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-16", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-17", "kind": "ICS statement", "title": "Wallet solution support PID issuance using the NL-specific issuance specificatio…", "text": "Wallet solution support PID issuance using the NL-specific issuance specification", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-17", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-18", "kind": "ICS statement", "title": "Wallet solution supports proximity attestation presentations", "text": "Wallet solution supports proximity attestation presentations", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(5)(a)(iii)", "CIR 2024/2982 Art. 5(1)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-18", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-19", "kind": "ICS statement", "title": "Wallet solution supports remote same-device attestation presentations", "text": "Wallet solution supports remote same-device attestation presentations", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(5)(a)(iii)", "CIR 2024/2982 Art. 5(1)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-19", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-20", "kind": "ICS statement", "title": "Wallet solution supports remote cross-device attestation presentations", "text": "Wallet solution supports remote cross-device attestation presentations", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 11, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(5)(a)(iii)", "CIR 2024/2982 Art. 5(1)", "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-20", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=11" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-21", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using OpenID4VP", "text": "Wallet solution supports remote attestation presentation using OpenID4VP", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-21", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-22", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7", "text": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-22", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-23", "kind": "ICS statement", "title": "Wallet solution supports access certificate verification", "text": "Wallet solution supports access certificate verification", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(5)(a)(vii)", "eIDAS Art. 5a(5)(c)", "CIR 2024/2982 Art. 3(1)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-23", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-24", "kind": "ICS statement", "title": "Wallet solution supports registration certificate verification", "text": "Wallet solution supports registration certificate verification", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5b(1)", "CIR 2024/2982 Art. 3(4)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-24", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-25", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using OpenID4VP and non…", "text": "Wallet solution supports remote attestation presentation using OpenID4VP and non-API-mediated transmission (i.e., redirects)", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "optional", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-25", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-26", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using OpenID4VP and API…", "text": "Wallet solution supports remote attestation presentation using OpenID4VP and API-mediated transmission (i.e., the W3C Digital Credentials API)", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-26", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-27", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 a…", "text": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and non-API-mediated transmission (i.e., redirects)", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "optional", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-27", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-28", "kind": "ICS statement", "title": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 a…", "text": "Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and API-mediated transmission (i.e., the W3C Digital Credentials API)", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "CIR 2024/2982 Annex II" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-28", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-29", "kind": "ICS statement", "title": "Wallet solution supports data erasure requests to Relying Parties", "text": "Wallet solution supports data erasure requests to Relying Parties", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(4)(d)(ii)", "eIDAS Art. 5a(5)(a)(ix)", "CIR 2024/2982 Art. 6" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-29", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-30", "kind": "ICS statement", "title": "Wallet solution supports reporting Relying Parties to a DPA", "text": "Wallet solution supports reporting Relying Parties to a DPA", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 12, "obligation": "recommended", "legal_refs": [ "eIDAS Art. 5a(4)(d)(iii)", "eIDAS Art. 5a(5)(a)(x)", "CIR 2024/2982 Art. 7" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-30", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=12" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-31", "kind": "ICS statement", "title": "Wallet solution supports Wallet-to-Wallet attestation presentations", "text": "Wallet solution supports Wallet-to-Wallet attestation presentations", "section": "6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)", "page": 13, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(c)", "eIDAS Art. 5a(5)(a)(vi)" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-31", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-32", "kind": "ICS statement", "title": "Wallet solution supports PID", "text": "Wallet solution supports PID", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 10, "obligation": "mandatory", "legal_refs": [ "eIDAS Art. 5a(4)(a)", "CIR 2024/2977 Art. 3" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-32", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=10" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-33", "kind": "ICS statement", "title": "Wallet solution supports the following types of QEAA: ", "text": "Wallet solution supports the following types of QEAA: ", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 13, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(a)", "CIR 2024/2977 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-33", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-34", "kind": "ICS statement", "title": "Wallet solution supports the following types of PuB-EAA: ", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 13, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(a)", "CIR 2024/2977 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-34", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-35", "kind": "ICS statement", "title": "Wallet solution supports the following types of EAA: ", "text": "Wallet solution supports the following types of EAA: ", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 13, "obligation": "optional", "legal_refs": [ "eIDAS Art. 5a(4)(a)", "CIR 2024/2977 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-35", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-36", "kind": "ICS statement", "title": "Wallet solution supports PIDs and attestations in mdoc format", "text": "Wallet solution supports PIDs and attestations in mdoc format", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 13, "obligation": "recommended", "legal_refs": [ "CIR 2024/2977 Art. 3", "CIR 2024/2977 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-36", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-FS-W", "document_title": "Wallet Solution Conformance (Presentation Requirements)", "version": "RC1.0", "id": "ICS-37", "kind": "ICS statement", "title": "Wallet solution supports PIDs and attestations in SD-JWT VC format", "text": "Wallet solution supports PIDs and attestations in SD-JWT VC format", "section": "6.4 Requirements from CIR 2024/2977 (PID and EAA)", "page": 13, "obligation": "recommended", "legal_refs": [ "CIR 2024/2977 Art. 3", "CIR 2024/2977 Art. 4" ], "url": "/edi-stelsel-certification/requirements/nl-fs-w#ics-37", "pdf": "/files/edi-stelsel/2026-11-06/NL-FS-W_EUDI_Wallet_Functional_Certification_-_Wallet_Solution_Conformance_RC1.0_20261106.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-4.2-02", "kind": "Requirement", "title": "A determination of non-applicability shall not transfer, waive or obscure a resp…", "text": "A determination of non-applicability shall not transfer, waive or obscure a responsibility that remains with the Provider under law, the NL certification system, a certification contract or an outsourcing arrangement.", "section": "4.2 Applicability of conditional requirements", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-4-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=9" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-01", "kind": "Requirement", "title": "The Provider shall establish, implement, maintain and continually improve a docu…", "text": "The Provider shall establish, implement, maintain and continually improve a documented risk-management framework covering the certified provider service.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-02", "kind": "Requirement", "title": "The framework shall define risk ownership, risk acceptance authority, assessment…", "text": "The framework shall define risk ownership, risk acceptance authority, assessment criteria, treatment options, review frequency and escalation thresholds.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-03", "kind": "Requirement", "title": "The Provider shall maintain a current risk assessment addressing threats, vulner…", "text": "The Provider shall maintain a current risk assessment addressing threats, vulnerabilities, dependencies and impacts affecting confidentiality, integrity, availability, authenticity, privacy and sole user control.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-04", "kind": "Requirement", "title": "The Provider shall map its assessment to the system risk register maintained und…", "text": "The Provider shall map its assessment to the system risk register maintained under NL-SYS-04 and shall identify provider-specific additions, assumptions and residual risks.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-05", "kind": "Requirement", "title": "Risk assessment shall cover interfaces and dependencies between the Wallet Provi…", "text": "Risk assessment shall cover interfaces and dependencies between the Wallet Provider, PID Provider, wallet solution, WSCA/WSCD, trust services, access-certificate services, registration-certificate services and other material ecosystem components.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-06", "kind": "Requirement", "title": "The Provider shall reassess risk following significant change, incident, vulnera…", "text": "The Provider shall reassess risk following significant change, incident, vulnerability disclosure, material supplier change, threat-intelligence update or change to applicable legal or scheme requirements.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-07", "kind": "Requirement", "title": "Risk treatment decisions shall identify responsible owners, target dates, requir…", "text": "Risk treatment decisions shall identify responsible owners, target dates, required evidence and residual-risk acceptance.", "section": "5 Risk management framework and risk assessment", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-08", "kind": "Requirement", "title": "Risks that may affect certificate validity, subordinate assurance evidence, nati…", "text": "Risks that may affect certificate validity, subordinate assurance evidence, national admission conditions or another provider shall be reported in accordance with NL-SYS-01 and the applicable provider scheme.", "section": "5 Risk management framework and risk assessment", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=11" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-09", "kind": "Requirement", "title": "The Wallet Provider shall specifically assess risks arising from wallet onboardi…", "text": "The Wallet Provider shall specifically assess risks arising from wallet onboarding, activation, binding to the user, wallet-unit lifecycle operations and integration with the designated PID Provider.", "section": "5 Risk management framework and risk assessment", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=11" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-5-10", "kind": "Requirement", "title": "The PID Provider shall specifically assess risks arising from identity proofing,…", "text": "The PID Provider shall specifically assess risks arising from identity proofing, PID issuance, binding to a wallet unit, status services, revocation, fraud detection and dependencies shared by multiple Wallet Providers.", "section": "5 Risk management framework and risk assessment", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-5-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=11" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.1-01", "kind": "Requirement", "title": "The Provider shall maintain a Provider Practice Statement describing how it impl…", "text": "The Provider shall maintain a Provider Practice Statement describing how it implements the requirements applicable to the certified service.", "section": "6.1 Provider Practice Statement", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.1-02", "kind": "Requirement", "title": "The statement shall define the service scope, supported architectures, provider …", "text": "The statement shall define the service scope, supported architectures, provider roles, trust dependencies, operational responsibilities, control ownership and applicable policy documents.", "section": "6.1 Provider Practice Statement", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.1-03", "kind": "Requirement", "title": "The statement shall identify material deviations, limitations, assumptions and e…", "text": "The statement shall identify material deviations, limitations, assumptions and external services on which conformity depends.", "section": "6.1 Provider Practice Statement", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.1-04", "kind": "Requirement", "title": "The statement shall be approved by accountable management, version-controlled an…", "text": "The statement shall be approved by accountable management, version-controlled and reviewed at least annually and following material change.", "section": "6.1 Provider Practice Statement", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.2-01", "kind": "Requirement", "title": "The Provider shall publish or otherwise make available clear terms and condition…", "text": "The Provider shall publish or otherwise make available clear terms and conditions for users and relevant ecosystem participants before service use.", "section": "6.2 Terms and conditions", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.2-02", "kind": "Requirement", "title": "Terms shall describe the service, user obligations, limitations, support channel…", "text": "Terms shall describe the service, user obligations, limitations, support channels, complaint routes, suspension and termination conditions, privacy information and relevant liability provisions.", "section": "6.2 Terms and conditions", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.2-03", "kind": "Requirement", "title": "The Wallet Provider shall explain wallet eligibility, onboarding, activation, re…", "text": "The Wallet Provider shall explain wallet eligibility, onboarding, activation, recovery, suspension, termination and consequences of loss or compromise.", "section": "6.2 Terms and conditions", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.2-04", "kind": "Requirement", "title": "The PID Provider shall explain PID issuance, validity, status, revocation, corre…", "text": "The PID Provider shall explain PID issuance, validity, status, revocation, correction and user redress procedures.", "section": "6.2 Terms and conditions", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.3-03", "kind": "Requirement", "title": "The Provider shall review the policy at planned intervals and after significant …", "text": "The Provider shall review the policy at planned intervals and after significant incidents, vulnerabilities or changes.", "section": "6.3 Information and network security policy", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.1-01", "kind": "Requirement", "title": "The Provider shall maintain a documented organisational structure with clear acc…", "text": "The Provider shall maintain a documented organisational structure with clear accountability for the certified service.", "section": "7.1.1 General", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.1-02", "kind": "Requirement", "title": "Accountable management shall ensure adequate authority, budget, competence and i…", "text": "Accountable management shall ensure adequate authority, budget, competence and independence for security, privacy, compliance, risk and incident-management functions.", "section": "7.1.1 General", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.1-03", "kind": "Requirement", "title": "The Provider shall identify conflicts of interest and implement controls to pres…", "text": "The Provider shall identify conflicts of interest and implement controls to preserve trustworthy operation and impartial evidence production.", "section": "7.1.2 Organisation reliability", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.1-04", "kind": "Requirement", "title": "Incompatible duties shall be segregated, including development and production ad…", "text": "Incompatible duties shall be segregated, including development and production administration, request and approval, key activation and key use, evidence creation and evidence approval.", "section": "7.1.3 Segregation of duties", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.2-01", "kind": "Requirement", "title": "Personnel and contractors in trusted roles shall be screened to a level proporti…", "text": "Personnel and contractors in trusted roles shall be screened to a level proportionate to their access and responsibilities, subject to applicable law.", "section": "7.2 Human resources", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.2-02", "kind": "Requirement", "title": "Role profiles shall define competence, authority, security responsibilities and …", "text": "Role profiles shall define competence, authority, security responsibilities and required training.", "section": "7.2 Human resources", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.2-03", "kind": "Requirement", "title": "Personnel shall receive introduction and recurring training covering security, p…", "text": "Personnel shall receive introduction and recurring training covering security, privacy, fraud, incident reporting, social engineering and role-specific procedures.", "section": "7.2 Human resources", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.2-04", "kind": "Requirement", "title": "Access and responsibilities shall be reviewed when employment or assignment chan…", "text": "Access and responsibilities shall be reviewed when employment or assignment changes and revoked promptly upon termination.", "section": "7.2 Human resources", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.2-05", "kind": "Requirement", "title": "The Provider shall maintain sufficient staffing and succession arrangements for …", "text": "The Provider shall maintain sufficient staffing and succession arrangements for critical operations, incident response and crisis management.", "section": "7.2 Human resources", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.3-01", "kind": "Requirement", "title": "The Provider shall maintain an inventory of information, software, hardware, cry…", "text": "The Provider shall maintain an inventory of information, software, hardware, cryptographic assets, services, data flows, interfaces and suppliers in the certified scope.", "section": "7.3.1 General requirements", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.3-02", "kind": "Requirement", "title": "Assets shall have assigned owners and be classified according to confidentiality…", "text": "Assets shall have assigned owners and be classified according to confidentiality, integrity, availability, authenticity and privacy needs.", "section": "7.3.2 Assets classification", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.3-03", "kind": "Requirement", "title": "Rules shall govern acceptable use, secure handling, storage, transfer, return, s…", "text": "Rules shall govern acceptable use, secure handling, storage, transfer, return, sanitisation and disposal of assets and media.", "section": "7.3.3 Storage media and asset handling", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.3-04", "kind": "Requirement", "title": "Production datasets, identity evidence, PID data, wallet-unit identifiers, attes…", "text": "Production datasets, identity evidence, PID data, wallet-unit identifiers, attestation material and security logs shall be protected against unauthorised access and inappropriate reuse.", "section": "7.3.3 Storage media and asset handling", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-01", "kind": "Requirement", "title": "Access shall be based on least privilege, need-to-know, role separation and expl…", "text": "Access shall be based on least privilege, need-to-know, role separation and explicit authorisation.", "section": "7.4.1 General", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-02", "kind": "Requirement", "title": "User and privileged access rights shall be approved, uniquely attributable, peri…", "text": "User and privileged access rights shall be approved, uniquely attributable, periodically reviewed and promptly revoked.", "section": "7.4.2 Privileged and system administration accounts", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-03", "kind": "Requirement", "title": "Privileged and system administration shall use dedicated accounts, controlled ad…", "text": "Privileged and system administration shall use dedicated accounts, controlled administration paths and enhanced monitoring.", "section": "7.4.2 Privileged and system administration accounts", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-04", "kind": "Requirement", "title": "Administrative systems shall be isolated from ordinary user environments and pro…", "text": "Administrative systems shall be isolated from ordinary user environments and protected against direct Internet exposure unless specifically justified and controlled.", "section": "7.4.3 Administration systems", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-05", "kind": "Requirement", "title": "Identities used for operational access shall be verified before credentials are …", "text": "Identities used for operational access shall be verified before credentials are issued.", "section": "7.4.4 Identification", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-06", "kind": "Requirement", "title": "Multi-factor authentication shall protect remote access, privileged access and a…", "text": "Multi-factor authentication shall protect remote access, privileged access and access to security-critical systems.", "section": "7.4.5 Authentication", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.4-07", "kind": "Requirement", "title": "Service-to-service access shall use mutually authenticated, authorised and crypt…", "text": "Service-to-service access shall use mutually authenticated, authorised and cryptographically protected mechanisms with controlled credential lifecycles.", "section": "7.4.5 Authentication", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-4-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.5-01", "kind": "Requirement", "title": "The Provider shall maintain a cryptographic policy covering approved algorithms,…", "text": "The Provider shall maintain a cryptographic policy covering approved algorithms, protocols, key lengths, key ownership, key lifecycle, certificate management and cryptographic agility.", "section": "7.5 Cryptographic controls", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.5-02", "kind": "Requirement", "title": "Cryptographic keys shall be generated, stored, used, rotated, backed up, recover…", "text": "Cryptographic keys shall be generated, stored, used, rotated, backed up, recovered, archived and destroyed under documented controls proportionate to their purpose.", "section": "7.5 Cryptographic controls", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.5-03", "kind": "Requirement", "title": "Access to high-impact keys shall require strong authentication, separation of du…", "text": "Access to high-impact keys shall require strong authentication, separation of duties and tamper-resistant protection appropriate to the assessed risk.", "section": "7.5 Cryptographic controls", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.5-04", "kind": "Requirement", "title": "The Provider shall monitor deprecation of algorithms, protocols and cryptographi…", "text": "The Provider shall monitor deprecation of algorithms, protocols and cryptographic products and maintain a transition plan.", "section": "7.5 Cryptographic controls", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.5-05", "kind": "Requirement", "title": "The PID Provider shall protect PID signing or sealing keys and associated status…", "text": "The PID Provider shall protect PID signing or sealing keys and associated status-service keys in accordance with applicable trust-service and scheme requirements.", "section": "7.5 Cryptographic controls", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.6-01", "kind": "Requirement", "title": "Facilities hosting critical systems shall use layered physical access controls, …", "text": "Facilities hosting critical systems shall use layered physical access controls, monitoring, visitor management and access logging.", "section": "7.6 Physical and environmental security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-6-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.6-02", "kind": "Requirement", "title": "Environmental controls shall address power, fire, water, temperature, communicat…", "text": "Environmental controls shall address power, fire, water, temperature, communications failure and other site-specific hazards.", "section": "7.6 Physical and environmental security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-6-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.6-03", "kind": "Requirement", "title": "Physical access rights shall be approved, reviewed and revoked, and anomalies sh…", "text": "Physical access rights shall be approved, reviewed and revoked, and anomalies shall be investigated.", "section": "7.6 Physical and environmental security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-6-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.6-04", "kind": "Requirement", "title": "Where cloud or colocation facilities are used, the Provider shall obtain and ass…", "text": "Where cloud or colocation facilities are used, the Provider shall obtain and assess evidence that physical and environmental requirements are met.", "section": "7.6 Physical and environmental security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-6-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-01", "kind": "Requirement", "title": "The Provider shall maintain documented, approved and tested operating procedures…", "text": "The Provider shall maintain documented, approved and tested operating procedures for security-critical and service-critical activities.", "section": "7.7 Operation security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-02", "kind": "Requirement", "title": "Changes shall be risk-assessed, authorised, tested, traceable and supported by r…", "text": "Changes shall be risk-assessed, authorised, tested, traceable and supported by rollback or recovery arrangements.", "section": "7.7 Operation security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-03", "kind": "Requirement", "title": "Development, test, acceptance and production environments shall be appropriately…", "text": "Development, test, acceptance and production environments shall be appropriately separated.", "section": "7.7 Operation security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-04", "kind": "Requirement", "title": "Secure configuration baselines shall be defined, deployed, monitored and reviewe…", "text": "Secure configuration baselines shall be defined, deployed, monitored and reviewed for deviation.", "section": "7.7 Operation security", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-05", "kind": "Requirement", "title": "Malware protection, endpoint controls, patching and vulnerability remediation sh…", "text": "Malware protection, endpoint controls, patching and vulnerability remediation shall be implemented according to risk and defined target times.", "section": "7.7 Operation security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-06", "kind": "Requirement", "title": "Capacity, availability, performance and security-relevant service health shall b…", "text": "Capacity, availability, performance and security-relevant service health shall be monitored against defined thresholds.", "section": "7.7 Operation security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-07", "kind": "Requirement", "title": "Backup and restoration procedures shall be tested and shall preserve confidentia…", "text": "Backup and restoration procedures shall be tested and shall preserve confidentiality, integrity and recoverability.", "section": "7.7 Operation security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.7-08", "kind": "Requirement", "title": "The Provider shall control production access by developers and shall record and …", "text": "The Provider shall control production access by developers and shall record and review exceptional access.", "section": "7.7 Operation security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-7-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.8-01", "kind": "Requirement", "title": "Networks shall be architected and segmented according to trust level, data sensi…", "text": "Networks shall be architected and segmented according to trust level, data sensitivity and service criticality.", "section": "7.8 Network security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-8-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.8-02", "kind": "Requirement", "title": "Security boundaries shall enforce authenticated and authorised communications an…", "text": "Security boundaries shall enforce authenticated and authorised communications and minimise exposed services.", "section": "7.8 Network security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-8-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.8-03", "kind": "Requirement", "title": "External and inter-provider interfaces shall be inventoried, threat-modelled, pr…", "text": "External and inter-provider interfaces shall be inventoried, threat-modelled, protected and monitored.", "section": "7.8 Network security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-8-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.8-04", "kind": "Requirement", "title": "Network changes, firewall rules, routes, certificates and service endpoints shal…", "text": "Network changes, firewall rules, routes, certificates and service endpoints shall be subject to controlled change management and periodic review.", "section": "7.8 Network security", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-8-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.8-05", "kind": "Requirement", "title": "The Provider shall deploy measures to detect and mitigate denial-of-service, ano…", "text": "The Provider shall deploy measures to detect and mitigate denial-of-service, anomalous traffic, lateral movement and data exfiltration.", "section": "7.8 Network security", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-8-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-01", "kind": "Requirement", "title": "The Provider shall collect, protect, correlate and review security logs sufficie…", "text": "The Provider shall collect, protect, correlate and review security logs sufficient for detection, investigation, certification evidence and legal obligations.", "section": "7.9.1 Monitoring and logging", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-02", "kind": "Requirement", "title": "Time sources shall be synchronised and protected to support reliable event corre…", "text": "Time sources shall be synchronised and protected to support reliable event correlation.", "section": "7.9.1 Monitoring and logging", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-03", "kind": "Requirement", "title": "The Provider shall maintain documented incident response procedures with classif…", "text": "The Provider shall maintain documented incident response procedures with classification, escalation, containment, eradication, recovery and communication steps.", "section": "7.9.2 Incident response", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-04", "kind": "Requirement", "title": "Incidents and vulnerabilities that may affect certified conformity, users, anoth…", "text": "Incidents and vulnerabilities that may affect certified conformity, users, another provider or the trust framework shall be reported to the CAB, Scheme Owner and competent authorities within applicable deadlines.", "section": "7.9.3 Reporting", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-05", "kind": "Requirement", "title": "The Provider shall operate a vulnerability intake and coordinated disclosure pro…", "text": "The Provider shall operate a vulnerability intake and coordinated disclosure process covering its own components and material suppliers.", "section": "7.9.3 Reporting", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-06", "kind": "Requirement", "title": "Events shall be assessed consistently for severity, affected assets, user impact…", "text": "Events shall be assessed consistently for severity, affected assets, user impact, certificate impact, exploitation status and cross-provider consequences.", "section": "7.9.4 Event assessment and classification", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-08", "kind": "Requirement", "title": "The PID Provider shall assess systemic impact where an incident may affect multi…", "text": "The PID Provider shall assess systemic impact where an incident may affect multiple Wallet Providers or issued PIDs.", "section": "7.9.5 Post-incident reviews", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.10-01", "kind": "Requirement", "title": "The Provider shall identify evidence required to demonstrate conformity for init…", "text": "The Provider shall identify evidence required to demonstrate conformity for initial certification, surveillance, special evaluation and recertification.", "section": "7.10 Collection of evidence", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-10-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-01", "kind": "Requirement", "title": "The Provider shall maintain business continuity and disaster recovery arrangemen…", "text": "The Provider shall maintain business continuity and disaster recovery arrangements covering the complete certified service and material dependencies.", "section": "7.11.1 4.1 General", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-02", "kind": "Requirement", "title": "Business impact analysis shall define maximum tolerable disruption, recovery pri…", "text": "Business impact analysis shall define maximum tolerable disruption, recovery priorities, RTOs and RPOs for critical services and data.", "section": "7.11.1 4.1 General", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-03", "kind": "Requirement", "title": "Continuity plans shall address loss of staff, facilities, infrastructure, suppli…", "text": "Continuity plans shall address loss of staff, facilities, infrastructure, supplier service, cryptographic capability and communications.", "section": "7.11.1 4.1 General", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-04", "kind": "Requirement", "title": "Backups shall be protected, geographically or logically separated as appropriate…", "text": "Backups shall be protected, geographically or logically separated as appropriate, and restoration shall be tested at planned intervals.", "section": "7.11.2 Back up", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-05", "kind": "Requirement", "title": "Crisis-management arrangements shall define command, decision rights, communicat…", "text": "Crisis-management arrangements shall define command, decision rights, communications, stakeholder notification and transition back to normal operation.", "section": "7.11.3 Crisis management", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.11-06", "kind": "Requirement", "title": "Continuity and crisis exercises shall include scenarios involving compromise or …", "text": "Continuity and crisis exercises shall include scenarios involving compromise or unavailability of a counterpart Wallet Provider or PID Provider.", "section": "7.11.3 Crisis management", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-11-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.12-01", "kind": "Requirement", "title": "The Provider shall maintain a termination plan that supports an orderly cessatio…", "text": "The Provider shall maintain a termination plan that supports an orderly cessation, transfer or replacement of the certified service.", "section": "7.12 Provider termination and termination plans", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-12-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.12-02", "kind": "Requirement", "title": "The plan shall address user notification, data portability or lawful disposal, r…", "text": "The plan shall address user notification, data portability or lawful disposal, record retention, key and certificate status, supplier exit, continued status information and cooperation with the Scheme Owner and CAB.", "section": "7.12 Provider termination and termination plans", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-12-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.12-03", "kind": "Requirement", "title": "The Wallet Provider plan shall address wallet suspension or migration, user acce…", "text": "The Wallet Provider plan shall address wallet suspension or migration, user access to records, and consequences for active wallet units.", "section": "7.12 Provider termination and termination plans", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-12-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.12-04", "kind": "Requirement", "title": "The PID Provider plan shall address continuity of PID validity status, revocatio…", "text": "The PID Provider plan shall address continuity of PID validity status, revocation information, evidence retention and effects on all dependent wallets.", "section": "7.12 Provider termination and termination plans", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-12-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.12-05", "kind": "Requirement", "title": "The termination plan shall be reviewed and exercised at planned intervals and af…", "text": "The termination plan shall be reviewed and exercised at planned intervals and after material architectural or supplier changes.", "section": "7.12 Provider termination and termination plans", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-12-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.13-01", "kind": "Requirement", "title": "The Provider shall identify and maintain an inventory of legal, regulatory, cont…", "text": "The Provider shall identify and maintain an inventory of legal, regulatory, contractual, certification-scheme and policy obligations applicable to the certified service.", "section": "7.13 Compliance", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-13-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.13-02", "kind": "Requirement", "title": "The Provider shall conduct planned internal audits covering all requirements of …", "text": "The Provider shall conduct planned internal audits covering all requirements of this document and the applicable provider scheme.", "section": "7.13 Compliance", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-13-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.13-03", "kind": "Requirement", "title": "Management shall review conformity, risks, incidents, vulnerabilities, audit res…", "text": "Management shall review conformity, risks, incidents, vulnerabilities, audit results, supplier performance, complaints, objectives and corrective actions at planned intervals.", "section": "7.13 Compliance", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-13-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.13-04", "kind": "Requirement", "title": "Nonconformities shall be recorded, root-caused, corrected and verified for effec…", "text": "Nonconformities shall be recorded, root-caused, corrected and verified for effectiveness within risk-based timescales.", "section": "7.13 Compliance", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-13-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.13-05", "kind": "Requirement", "title": "The Provider shall notify material changes affecting the certified object, assur…", "text": "The Provider shall notify material changes affecting the certified object, assurance evidence or certificate scope before implementation where required by the applicable scheme.", "section": "7.13 Compliance", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-13-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-01", "kind": "Requirement", "title": "The Provider shall maintain a supply-chain security policy covering selection, d…", "text": "The Provider shall maintain a supply-chain security policy covering selection, due diligence, contracting, onboarding, monitoring, change and exit.", "section": "7.14.1 Supply chain policy", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-02", "kind": "Requirement", "title": "Suppliers shall be classified by criticality, access, data handled, substitutabi…", "text": "Suppliers shall be classified by criticality, access, data handled, substitutability and potential impact on certificate validity or service continuity.", "section": "7.14.1 Supply chain policy", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-03", "kind": "Requirement", "title": "Supplier risk assessments shall cover ownership, jurisdiction, financial stabili…", "text": "Supplier risk assessments shall cover ownership, jurisdiction, financial stability, personnel, security posture, vulnerabilities, concentration risk and subcontracting.", "section": "7.14.2 Supply chain procedures and processes", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-04", "kind": "Requirement", "title": "Contracts shall define security, privacy, availability, incident notification, v…", "text": "Contracts shall define security, privacy, availability, incident notification, vulnerability handling, audit rights, evidence access, change notification, data location, return or deletion and termination assistance.", "section": "7.14.2 Supply chain procedures and processes", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-05", "kind": "Requirement", "title": "The Provider shall remain accountable for outsourced activities and shall ensure…", "text": "The Provider shall remain accountable for outsourced activities and shall ensure that the CAB and competent authorities can obtain necessary evidence.", "section": "7.14.3 Responsibility, third-party agreements and SLA", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-06", "kind": "Requirement", "title": "Supplier performance and assurance evidence shall be reviewed at planned interva…", "text": "Supplier performance and assurance evidence shall be reviewed at planned intervals and after material events.", "section": "7.14.3 Responsibility, third-party agreements and SLA", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.14-07", "kind": "Requirement", "title": "The Provider shall maintain exit and substitution plans for suppliers whose fail…", "text": "The Provider shall maintain exit and substitution plans for suppliers whose failure could materially affect the certified service.", "section": "7.14.3 Responsibility, third-party agreements and SLA", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-14-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-4.2-01", "kind": "Requirement", "title": "The Provider shall document, for every requirement marked conditional or role-sp…", "text": "The Provider shall document, for every requirement marked conditional or role-specific, whether it is applicable and the factual basis for that determination.", "section": "4.2 Applicability of conditional requirements", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-4-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=9" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-4.2-03", "kind": "Requirement", "title": "The CAB shall be given sufficient architecture, service-decomposition and respon…", "text": "The CAB shall be given sufficient architecture, service-decomposition and responsibility-allocation information to validate applicability decisions.", "section": "4.2 Applicability of conditional requirements", "page": 9, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-4-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=9" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.3-01", "kind": "Requirement", "title": "The Provider shall maintain an information and network security policy approved …", "text": "The Provider shall maintain an information and network security policy approved by accountable management and aligned with the certified service risk assessment.", "section": "6.3 Information and network security policy", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.9-07", "kind": "Requirement", "title": "Post-incident reviews shall identify root causes, control failures, corrective a…", "text": "Post-incident reviews shall identify root causes, control failures, corrective actions, responsible owners and lessons to be shared with relevant parties.", "section": "7.9.5 Post-incident reviews", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-9-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.10-03", "kind": "Requirement", "title": "Collection and handling of forensic evidence shall preserve integrity, chain of …", "text": "Collection and handling of forensic evidence shall preserve integrity, chain of custody and legal admissibility where relevant.", "section": "7.10 Collection of evidence", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-10-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.10-04", "kind": "Requirement", "title": "The Provider shall maintain traceability from each requirement to implemented co…", "text": "The Provider shall maintain traceability from each requirement to implemented control, evidence source, owner, assessment result and open finding.", "section": "7.10 Collection of evidence", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-10-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.3-02", "kind": "Requirement", "title": "The policy shall allocate security responsibilities, define governance and repor…", "text": "The policy shall allocate security responsibilities, define governance and reporting, and require measurable security objectives.", "section": "6.3 Information and network security policy", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-6.3-04", "kind": "Requirement", "title": "Compliance with the policy shall be monitored and evidenced through management r…", "text": "Compliance with the policy shall be monitored and evidenced through management review, internal audit, metrics and corrective action.", "section": "6.3 Information and network security policy", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-6-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-01", "document_title": "Wallet and PID Provider Requirements", "version": "RC1.0", "id": "REQ-7.10-02", "kind": "Requirement", "title": "Evidence shall be attributable, complete, protected against alteration, retained…", "text": "Evidence shall be attributable, complete, protected against alteration, retained for the prescribed period and retrievable without undue delay.", "section": "7.10 Collection of evidence", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-01#req-7-10-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-01_Wallet_and_PID_Provider_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-01.1", "kind": "Control", "title": "The organisation's mission shall be established, communicated and shall form the…", "text": "The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management.", "section": "4.1.1 GV.OC-01 The organisational mission is understood and informs cybersecurity risk management", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-02.1", "kind": "Control", "title": "The organisation shall demonstrate it understands and considers the needs and ex…", "text": "The organisation shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.", "section": "4.1.2 GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-03.1", "kind": "Control", "title": "Legal and regulatory requirements regarding information and cybersecurity shall …", "text": "Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.", "section": "4.1.3 GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-03.2", "kind": "Control", "title": "Legal, regulatory, and contractual obligations related to information and cybers…", "text": "Legal, regulatory, and contractual obligations related to information and cybersecurity shall be continuously managed to ensure they remain accurate, up to date, and effectively applied.", "section": "4.1.3 GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-04.1", "kind": "Control", "title": "The organisation shall identify, document, and communicate the critical objectiv…", "text": "The organisation shall identify, document, and communicate the critical objectives, capabilities, and services relied upon by external stakeholders, prioritise them based on criticality, and integrate this prioritisation into the risk assessment process", "section": "4.1.4 GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-04.2", "kind": "Control", "title": "The organisation shall define and document cybersecurity requirements for essent…", "text": "The organisation shall define and document cybersecurity requirements for essential operations, validate them through testing and audits, maintain records of results and corrective actions, and regularly update requirements based on evolving risks", "section": "4.1.4 GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-04.3", "kind": "Control", "title": "Redundancy shall be implemented to meet availability requirements as defined by …", "text": "Redundancy shall be implemented to meet availability requirements as defined by the organisation, legislation and/or regulations", "section": "4.1.4 GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-04-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-04.4", "kind": "Control", "title": "Recovery time and recovery point objectives for the resumption of essential ICT/…", "text": "Recovery time and recovery point objectives for the resumption of essential ICT/ OT system processes shall be defined and monitored.", "section": "4.1.4 GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-04-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OC-05.1", "kind": "Control", "title": "The organisation shall identify, document, and communicate its role in the suppl…", "text": "The organisation shall identify, document, and communicate its role in the supply chain, including the external capabilities, services, and dependencies it relies on (upstream), as well as its interactions with downstream stakeholders.", "section": "4.1.5 GV.OC-05 Outcomes, capabilities, and services that the organisation depends on are understood and communicated", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-oc-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-01.1", "kind": "Control", "title": "Information/cybersecurity objectives shall be identified, agreed to by organisat…", "text": "Information/cybersecurity objectives shall be identified, agreed to by organisational stakeholders and approved by senior management", "section": "4.2.1 GV.RM-01 Risk management objectives are established and agreed to by organisational stakeholders", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-02.1", "kind": "Control", "title": "Risk appetite and risk tolerance statements shall be defined, documented, approv…", "text": "Risk appetite and risk tolerance statements shall be defined, documented, approved by senior management, communicated, and maintained.", "section": "4.2.2 GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-03.1", "kind": "Control", "title": "As part of the organisation-wide risk management strategy, a comprehensive strat…", "text": "As part of the organisation-wide risk management strategy, a comprehensive strategy to manage information and cybersecurity risks shall be developed and updated when changes occur.", "section": "4.2.3 GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-03.2", "kind": "Control", "title": "Information and Cybersecurity risks shall be documented, as part of the enterpri…", "text": "Information and Cybersecurity risks shall be documented, as part of the enterprise risk management processes, formally approved by senior management, and updated when changes occur.", "section": "4.2.3 GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-04.1", "kind": "Control", "title": "A high-level plan or vision shall be formally established and clearly communicat…", "text": "A high-level plan or vision shall be formally established and clearly communicated to everyone involved on how to manage risks, including the different strategies the organisation can employ to deal with identified risks based on risk appetite or risk tolerance level.", "section": "4.2.4 GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RM-05.1", "kind": "Control", "title": "To support the high-level risk management vision, the organisation shall establi…", "text": "To support the high-level risk management vision, the organisation shall establish clear lines of communication for cybersecurity risks, including those arising from suppliers and third parties.", "section": "4.2.5 GV.RM-05 Lines of communication across the organisation are established for cybersecurity risks, including risks from suppliers and other third parties", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rm-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-01.1", "kind": "Control", "title": "Organisation's top management shall be responsible and accountable for cybersecu…", "text": "Organisation's top management shall be responsible and accountable for cybersecurity risk and shall foster a culture that is risk-aware, ethical, and continually improving.", "section": "4.3.1 GV.RR-01 Organisational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-02.1", "kind": "Control", "title": "Information security and cybersecurity roles, responsibilities and authorities f…", "text": "Information security and cybersecurity roles, responsibilities and authorities for employees, suppliers, customers, and partners shall be documented, reviewed, authorised, kept up to date, communicated, and coordinated internally and externally.", "section": "4.3.2 GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-03.1", "kind": "Control", "title": "Sufficient resources shall be allocated in line with the cybersecurity risk stra…", "text": "Sufficient resources shall be allocated in line with the cybersecurity risk strategy, roles, responsibilities and policies.", "section": "4.3.3 GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-03.2", "kind": "Control", "title": "The organisation shall assign roles and responsibilities for reviewing and updat…", "text": "The organisation shall assign roles and responsibilities for reviewing and updating response and recovery plans, ensuring they reflect changes in the risk environment and remain effective.", "section": "4.3.3 GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-04.1", "kind": "Control", "title": "Personnel with access to the organisation’s most critical information or technol…", "text": "Personnel with access to the organisation’s most critical information or technology shall be authenticated.", "section": "4.3.4 GV.RR-04 Cybersecurity is included in human resources practices", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-04.2", "kind": "Control", "title": "A cybersecurity process for human resources shall be developed and maintained ap…", "text": "A cybersecurity process for human resources shall be developed and maintained applicable at recruitment, during employment and at termination of employment.", "section": "4.3.4 GV.RR-04 Cybersecurity is included in human resources practices", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.PO-01.1", "kind": "Control", "title": "Policies and procedures for managing information and cybersecurity shall be esta…", "text": "Policies and procedures for managing information and cybersecurity shall be established, documented, reviewed, approved, updated when changes occur, communicated and enforced.", "section": "4.4.1 GV.PO-01 Policy for managing cybersecurity risks is established based on organisational context, cybersecurity strategy, and priorities and is communicated and enforced", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-po-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.PO-01.2", "kind": "Control", "title": "Organisational-wide information and cybersecurity policies and procedures shall …", "text": "Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee its implementation.", "section": "4.4.1 GV.PO-01 Policy for managing cybersecurity risks is established based on organisational context, cybersecurity strategy, and priorities and is communicated and enforced", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-po-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OV-02.1", "kind": "Control", "title": "The information and cybersecurity risk management strategy shall be reviewed and…", "text": "The information and cybersecurity risk management strategy shall be reviewed and adjusted to ensure coverage of organisational requirements and risks.", "section": "4.5.1 GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organisational requirements and risks", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-ov-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.OV-03.1", "kind": "Control", "title": "The organisation's cybersecurity risk management performance shall be evaluated,…", "text": "The organisation's cybersecurity risk management performance shall be evaluated, reviewed and adjusted when necessary", "section": "4.5.2 GV.OV-03 Organisational cybersecurity risk management performance is evaluated and reviewed for adjustments needed", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-ov-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-01.1", "kind": "Control", "title": "A cybersecurity supply chain risk management program, strategy, objectives, poli…", "text": "A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes shall be documented, reviewed, updated when changes occur, and approved by organisational stakeholders.", "section": "4.6.1 GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organisational stakeholders", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-02.1", "kind": "Control", "title": "Third-party providers shall notify any transfer, termination or transition of pe…", "text": "Third-party providers shall notify any transfer, termination or transition of personnel with physical or logical access to business-critical system elements of the organisation.", "section": "4.6.2 GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-03.1", "kind": "Control", "title": "Information- and Cybersecurity supply chain risk management shall be integrated …", "text": "Information- and Cybersecurity supply chain risk management shall be integrated into information/cybersecurity and enterprise risk management, risk assessment, and improvement processes.", "section": "4.6.3 GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-05.1", "kind": "Control", "title": "Requirements for addressing cybersecurity risks and the sharing of sensitive inf…", "text": "Requirements for addressing cybersecurity risks and the sharing of sensitive information in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced.", "section": "4.6.4 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-05.2", "kind": "Control", "title": "Contractual information/cybersecurity requirements for suppliers and external pa…", "text": "Contractual information/cybersecurity requirements for suppliers and external partners shall be implemented to ensure a verifiable flaw resolution process and to ensure that deficiencies identified during information/cybersecurity testing and evaluation are remedied.", "section": "4.6.4 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-05-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-05.3", "kind": "Control", "title": "The organisation shall establish contractual requirements permitting the organis…", "text": "The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.", "section": "4.6.4 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-05-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-06.1", "kind": "Control", "title": "Planning and due diligence shall be carried out to reduce risks before entering …", "text": "Planning and due diligence shall be carried out to reduce risks before entering into formal relationships with suppliers or other third parties.", "section": "4.6.5 GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-07.1", "kind": "Control", "title": "The risks posed by a supplier, its products and services and other third parties…", "text": "The risks posed by a supplier, its products and services and other third parties shall be identified, documented, prioritised, mitigated and assessed at least annually and when changes occur during the relationship.", "section": "4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-07-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-07.2", "kind": "Control", "title": "A documented list of all critical suppliers, vendors and partners of the organis…", "text": "A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security.", "section": "4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-07-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-07.4", "kind": "Control", "title": "The organisation shall ensure conformity with information/cybersecurity contract…", "text": "The organisation shall ensure conformity with information/cybersecurity contractual obligations by suppliers and third-party partners through regular reviews of independent audits, assessments, and third-party evaluations.", "section": "4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-07-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-08.1", "kind": "Control", "title": "The organisation shall identify and document key personnel from relevant supplie…", "text": "The organisation shall identify and document key personnel from relevant suppliers and other third parties to include them in incident planning, response, and recovery activities.", "section": "4.6.7 GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-08-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-09.1", "kind": "Control", "title": "Supply chain security practices shall be integrated into information/cybersecuri…", "text": "Supply chain security practices shall be integrated into information/cybersecurity and enterprise risk management programs, and their performance shall be monitored throughout the product and service life cycle.", "section": "4.6.8 GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-09-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-10.1", "kind": "Control", "title": "Cybersecurity supply chain risk management plans shall include actions and respo…", "text": "Cybersecurity supply chain risk management plans shall include actions and responsibilities for managing risks that may arise after a supplier relationship or service agreement has ended.", "section": "4.6.9 GV.SC-010 Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-10-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-01.1", "kind": "Control", "title": "An inventory of physical and virtual infrastructure assets — such as hardware, n…", "text": "An inventory of physical and virtual infrastructure assets — such as hardware, network devices, and cloud-hosted environments — that support information processing shall be documented, reviewed, and updated as changes occur.", "section": "5.1.1 ID.AM-01 Inventories of hardware managed by the organisation are maintained", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-01.2", "kind": "Control", "title": "The inventory of enterprise assets associated with information and information p…", "text": "The inventory of enterprise assets associated with information and information processing facilities shall reflect changes in the organisation’s context and include all information necessary for effective accountability.", "section": "5.1.1 ID.AM-01 Inventories of hardware managed by the organisation are maintained", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-01.3", "kind": "Control", "title": "When unauthorised hardware is detected, it shall be quarantined for possible exc…", "text": "When unauthorised hardware is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly.", "section": "5.1.1 ID.AM-01 Inventories of hardware managed by the organisation are maintained", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-01.4", "kind": "Control", "title": "Mechanisms for detecting the presence of unauthorised hardware and firmware comp…", "text": "Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified.", "section": "5.1.1 ID.AM-01 Inventories of hardware managed by the organisation are maintained", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-02.1", "kind": "Control", "title": "An inventory of software, digital services, and business systems used within the…", "text": "An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur.", "section": "5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-02.2", "kind": "Control", "title": "The inventory reflecting which software, services and systems are used in the or…", "text": "The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability.", "section": "5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-02.3", "kind": "Control", "title": "The people responsible and accountable for managing software platforms and appli…", "text": "The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.", "section": "5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-02-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-02.4", "kind": "Control", "title": "When unauthorised software is detected, it shall be quarantined for possible exc…", "text": "When unauthorised software is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly.", "section": "5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-02-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-02.5", "kind": "Control", "title": "Mechanisms for detecting the presence of unauthorised software within the organi…", "text": "Mechanisms for detecting the presence of unauthorised software within the organisation’s ICT/OT environment shall be identified.", "section": "5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-02-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-03.2", "kind": "Control", "title": "The organisation's network communication and internal data flows shall be mapped…", "text": "The organisation's network communication and internal data flows shall be mapped, documented, authorised, and updated when changes occur.", "section": "5.1.3 ID.AM-03 Representations of the organisation's authorised network communication and internal and external network data flows are maintained", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-03.3", "kind": "Control", "title": "The organisation's network communication and external data flows shall be mapped…", "text": "The organisation's network communication and external data flows shall be mapped, documented, authorised, and updated when changes occur.", "section": "5.1.3 ID.AM-03 Representations of the organisation's authorised network communication and internal and external network data flows are maintained", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-03-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-04.1", "kind": "Control", "title": "Organisations shall keep a clear and up-to-date list of all external services it…", "text": "Organisations shall keep a clear and up-to-date list of all external services it uses, including how they connect to their systems. These services shall be reviewed and approved before use, and the list shall be updated whenever changes happen.", "section": "5.1.4 ID.AM-04 Inventories of services provided by suppliers are maintained", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-04.2", "kind": "Control", "title": "The organisation shall map, document and authorise the flow of information to/fr…", "text": "The organisation shall map, document and authorise the flow of information to/from external systems and update the flow when changes occur.", "section": "5.1.4 ID.AM-04 Inventories of services provided by suppliers are maintained", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.2", "kind": "Control", "title": "Patches and security updates for Operating Systems and critical system component…", "text": "Patches and security updates for Operating Systems and critical system components shall be installed.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.3", "kind": "Control", "title": "The organisation shall enforce accountability for all its business-critical asse…", "text": "The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 54, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=54" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.4", "kind": "Control", "title": "The organisation shall ensure that the necessary measures are taken to deal with…", "text": "The organisation shall ensure that the necessary measures are taken to deal with loss, misuse, damage, or theft of assets.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 55, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=55" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.5", "kind": "Control", "title": "The organisation shall ensure that disposal actions are approved, tracked, docum…", "text": "The organisation shall ensure that disposal actions are approved, tracked, documented, and verified.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.6", "kind": "Control", "title": "The organisation shall plan, perform and document preventive maintenance and rep…", "text": "The organisation shall plan, perform and document preventive maintenance and repairs on its critical system components according to approved processes and tools.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.7", "kind": "Control", "title": "The organisation shall prevent unauthorised removal of maintenance equipment con…", "text": "The organisation shall prevent unauthorised removal of maintenance equipment containing critical system information of the organisation.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-7", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.9", "kind": "Control", "title": "Maintenance tools and portable storage devices shall be inspected as they enter …", "text": "Maintenance tools and portable storage devices shall be inspected as they enter the facility and shall be protected by anti-malware solutions that scan them for malicious code before they are used on the organisation's systems.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-9", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.10", "kind": "Control", "title": "The organisation shall verify security controls following maintenance or repairs…", "text": "The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.11", "kind": "Control", "title": "Remote maintenance and diagnostic activities of organisational assets shall be p…", "text": "Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.12", "kind": "Control", "title": "Setting up non-local maintenance and diagnostic sessions over remote network con…", "text": "Setting up non-local maintenance and diagnostic sessions over remote network connections shall require strong authenticators and such connections shall be terminated when non-local maintenance is completed.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.13", "kind": "Control", "title": "The organisation shall require remote maintenance diagnostic services to be perf…", "text": "The organisation shall require remote maintenance diagnostic services to be performed from a system that implements security features similar to the security features implemented on the equivalent organisation's critical system.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.1", "kind": "Control", "title": "Threats and vulnerabilities shall be identified in all relevant assets, includin…", "text": "Threats and vulnerabilities shall be identified in all relevant assets, including software, network and system architectures, and facilities that house critical computing assets.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.2", "kind": "Control", "title": "A process shall be established to continuously monitor, identify, and document v…", "text": "A process shall be established to continuously monitor, identify, and document vulnerabilities of the organisation's business critical systems.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.3", "kind": "Control", "title": "The organisation shall establish and maintain a documented process that enables …", "text": "The organisation shall establish and maintain a documented process that enables continuous review, analysis and remediation of vulnerabilities and provides for information sharing where applicable.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 62, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=62" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.4", "kind": "Control", "title": "To ensure that organisation's operations are not adversely affected by the testi…", "text": "To ensure that organisation's operations are not adversely affected by the testing process, performance/load testing and penetration testing on the organisation’s systems shall be carried out with care.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.5", "kind": "Control", "title": "Vulnerability scanning shall not adversely impact system functions.", "text": "Vulnerability scanning shall not adversely impact system functions.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-01.6", "kind": "Control", "title": "Vulnerabilities shall be identified and managed in all relevant assets, includin…", "text": "Vulnerabilities shall be identified and managed in all relevant assets, including software, network and system architectures, and facilities.", "section": "5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded", "page": 64, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-01-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=64" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-02.1", "kind": "Control", "title": "A threat and vulnerability awareness program that includes a cross-organisation …", "text": "A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.", "section": "5.2.2 ID.RA-02 Cyber threat intelligence is received from information-sharing forums and sources", "page": 65, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-02.2", "kind": "Control", "title": "Automated mechanisms shall be implemented to disseminate security alerts and adv…", "text": "Automated mechanisms shall be implemented to disseminate security alerts and advisories to relevant organisation stakeholders.", "section": "5.2.2 ID.RA-02 Cyber threat intelligence is received from information-sharing forums and sources", "page": 65, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-03.1", "kind": "Control", "title": "Threats shall be identified and assessed in relation to all relevant assets, inc…", "text": "Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.", "section": "5.2.3 ID.RA-03 Internal and external threats to the organisation are identified and recorded", "page": 66, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-05.1", "kind": "Control", "title": "The organisation shall conduct risk assessments in which risk is determined by t…", "text": "The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets.", "section": "5.2.4 ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation", "page": 67, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=67" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-05.2", "kind": "Control", "title": "The organisation shall conduct and document risk assessments in which risk is de…", "text": "The organisation shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence.", "section": "5.2.4 ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation", "page": 67, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-05-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=67" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-06.1", "kind": "Control", "title": "Risk responses shall be identified, prioritised, planned, tracked and communicat…", "text": "Risk responses shall be identified, prioritised, planned, tracked and communicated.", "section": "5.2.5 ID.RA-06 Risk responses are selected, prioritised, planned, tracked, and communicated", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-08.1", "kind": "Control", "title": "The organisation shall establish and implement a vulnerability management plan t…", "text": "The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities.", "section": "5.2.6 ID.RA-08 Processes for receiving, analysing, and responding to vulnerability disclosures are established important", "page": 69, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-08-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=69" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-08.2", "kind": "Control", "title": "The organisation shall implement automated mechanisms for disseminating and trac…", "text": "The organisation shall implement automated mechanisms for disseminating and tracking remedial measures related to vulnerability information that automatically handles vulnerability data collection, disseminates information, tracks remedial measures, includes reporting and accountability, and enables continuous monitoring.", "section": "5.2.6 ID.RA-08 Processes for receiving, analysing, and responding to vulnerability disclosures are established important", "page": 70, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-08-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=70" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-02.1", "kind": "Control", "title": "Security tests and exercises, including those conducted with suppliers and relev…", "text": "Security tests and exercises, including those conducted with suppliers and relevant third parties, shall be used to identify areas for improvement.", "section": "5.3.1 ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties", "page": 71, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=71" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.1", "kind": "Control", "title": "The organisation shall conduct post-incident evaluations to analyse lessons lear…", "text": "The organisation shall conduct post-incident evaluations to analyse lessons learned from incident response and recovery and consequently improve processes / procedures / technologies to enhance its cyber resilience.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 71, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=71" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.2", "kind": "Control", "title": "The organisation shall incorporate lessons learned from incident handling activi…", "text": "The organisation shall incorporate lessons learned from incident handling activities into updated or new incident handling processes and/or procedures that are framed by appropriate training after review, approval and testing.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 72, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=72" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.3", "kind": "Control", "title": "The organisation shall identify improvements derived from the monitoring, measur…", "text": "The organisation shall identify improvements derived from the monitoring, measurements, assessments, and lessons learned and consequently translate this into improved processes / procedures / technologies to enhance its cyber resilience (continuous improvement).", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 72, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=72" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.4", "kind": "Control", "title": "The organisation shall collaborate and share information about its critical syst…", "text": "The organisation shall collaborate and share information about its critical system's related security incidents and mitigation measures with designated partners.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 73, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=73" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.6", "kind": "Control", "title": "The organisation shall implement, where feasible, automated mechanisms to facili…", "text": "The organisation shall implement, where feasible, automated mechanisms to facilitate the process of information sharing and collaboration.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 74, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=74" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.7", "kind": "Control", "title": "The organisation shall implement independent teams to assess its processes, best…", "text": "The organisation shall implement independent teams to assess its processes, best practices, and technology solutions to safeguard critical systems and assets.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 75, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-7", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=75" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.8", "kind": "Control", "title": "The organisation shall ensure that the security plan for its critical systems fa…", "text": "The organisation shall ensure that the security plan for its critical systems facilitates the review, testing, and continual improvement of the security protection processes.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 75, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-8", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=75" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.9", "kind": "Control", "title": "The organisation shall conduct specialised assessments including in-depth monito…", "text": "The organisation shall conduct specialised assessments including in-depth monitoring, vulnerability scanning, malicious user testing, insider threat assessment, performance/ load testing, and verification and validation testing on the organisation's critical systems.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 76, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-9", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=76" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-04.1", "kind": "Control", "title": "Contingency and continuity plans shall be established, communicated, maintained,…", "text": "Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved.", "section": "5.3.3 ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved", "page": 77, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=77" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-04.2", "kind": "Control", "title": "The organisation shall coordinate the development and the testing of Incident Re…", "text": "The organisation shall coordinate the development and the testing of Incident Response Plans and other cybersecurity plans that affect operations with stakeholders to ensure that these plans align with overall organisational goals and enhance resilience.", "section": "5.3.3 ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved", "page": 78, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=78" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-01.1", "kind": "Control", "title": "Identities and credentials for authorised users, services, and hardware shall be…", "text": "Identities and credentials for authorised users, services, and hardware shall be managed.", "section": "6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation", "page": 79, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=79" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-01.2", "kind": "Control", "title": "Identities and credentials for authorised users, services and hardware shall be …", "text": "Identities and credentials for authorised users, services and hardware shall be managed through automated mechanisms whenever feasible.", "section": "6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation", "page": 80, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=80" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-01.3", "kind": "Control", "title": "System credentials shall be deactivated after a specified period of inactivity u…", "text": "System credentials shall be deactivated after a specified period of inactivity unless it would compromise the safe operation of (critical) processes.", "section": "6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation", "page": 80, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=80" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-01.4", "kind": "Control", "title": "For transactions within the organisation's critical systems, the organisation sh…", "text": "For transactions within the organisation's critical systems, the organisation shall implement Multi Factor Authentication (MFA), cryptographic certificates, identity tokens, cryptographic keys and other credentials as appropriate and where feasible.", "section": "6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation", "page": 81, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=81" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-01.5", "kind": "Control", "title": "The organisation’s critical systems shall be monitored for atypical use of syste…", "text": "The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.", "section": "6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation", "page": 82, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-01-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=82" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-02.1", "kind": "Control", "title": "The organisation shall implement documented procedures for verifying the identit…", "text": "The organisation shall implement documented procedures for verifying the identity of individuals before issuing credentials that provide access to the organisation's systems.", "section": "6.1.2 PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions", "page": 83, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=83" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-02.2", "kind": "Control", "title": "The organisation shall ensure that unique credentials are used for each authenti…", "text": "The organisation shall ensure that unique credentials are used for each authenticated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access (\"break-glass\" procedures), provided such access is strictly controlled, logged, and reviewed.", "section": "6.1.2 PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions", "page": 83, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=83" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-03.1", "kind": "Control", "title": "All wireless access points used by the organisation, including those providing g…", "text": "All wireless access points used by the organisation, including those providing guest access, shall be securely configured, managed, and monitored to prevent unauthorised access and ensure network integrity.", "section": "6.1.3 PR.AA-03 Users, services, and hardware are authenticated", "page": 84, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=84" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-03.2", "kind": "Control", "title": "Multi-Factor Authentication (MFA) shall be required to access the organisation's…", "text": "Multi-Factor Authentication (MFA) shall be required to access the organisation's networks remotely.", "section": "6.1.3 PR.AA-03 Users, services, and hardware are authenticated", "page": 85, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=85" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-03.3", "kind": "Control", "title": "The organisation shall define, document, and implement usage restrictions, conne…", "text": "The organisation shall define, document, and implement usage restrictions, connection requirements, and authorisation procedures for remote access to its critical systems. These controls shall ensure that only approved users can connect, using secure methods, with access limited to what is necessary for their role.", "section": "6.1.3 PR.AA-03 Users, services, and hardware are authenticated", "page": 86, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-03-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=86" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-03.4", "kind": "Control", "title": "Remote access to the organisation’s critical systems shall be monitored and cryp…", "text": "Remote access to the organisation’s critical systems shall be monitored and cryptographic mechanisms shall be implemented where determined necessary.", "section": "6.1.3 PR.AA-03 Users, services, and hardware are authenticated", "page": 87, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-03-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=87" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-03.5", "kind": "Control", "title": "The security for connections with external systems shall be verified and framed …", "text": "The security for connections with external systems shall be verified and framed by documented agreements.", "section": "6.1.3 PR.AA-03 Users, services, and hardware are authenticated", "page": 87, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-03-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=87" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.1", "kind": "Control", "title": "Access permissions, rights, and authorisations shall be defined, managed, enforc…", "text": "Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 89, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=89" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.2", "kind": "Control", "title": "It shall be determined who needs access to the organisation's business-critical …", "text": "It shall be determined who needs access to the organisation's business-critical information and technology and the means to gain access.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 90, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=90" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.3", "kind": "Control", "title": "Access rights, privileges and authorisations shall be restricted to the systems …", "text": "Access rights, privileges and authorisations shall be restricted to the systems and specific information needed to perform the tasks (the principle of Least Privilege).", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 91, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=91" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.4", "kind": "Control", "title": "No one shall have administrative privileges for routine day-to-day tasks.", "text": "No one shall have administrative privileges for routine day-to-day tasks.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 92, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=92" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.5", "kind": "Control", "title": "Where technically, operationally, and economically feasible — without compromisi…", "text": "Where technically, operationally, and economically feasible — without compromising system integrity, safety, or compliance — automated mechanisms shall be implemented to manage user accounts on critical ICT and OT systems. Feasibility shall be determined based on system capabilities, integration potential, risk assessment, and business impact.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 92, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=92" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.8", "kind": "Control", "title": "Account usage restrictions for specific time periods and locations shall be take…", "text": "Account usage restrictions for specific time periods and locations shall be taken into account in the organisation's security access policy and applied accordingly.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 95, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-8", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=95" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-06.1", "kind": "Control", "title": "Physical access to all organisational assets, including critical zones, shall be…", "text": "Physical access to all organisational assets, including critical zones, shall be managed, monitored, and enforced based on risk.", "section": "6.1.6 PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk", "page": 97, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=97" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-06.2", "kind": "Control", "title": "Physical access controls shall include specific procedures for emergency situati…", "text": "Physical access controls shall include specific procedures for emergency situations, ensuring continued protection of critical and non-critical assets during such events.", "section": "6.1.6 PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk", "page": 98, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-06-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=98" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-06.3", "kind": "Control", "title": "Critical zones shall have additional physical access controls beyond those appli…", "text": "Critical zones shall have additional physical access controls beyond those applied to general facilities.", "section": "6.1.6 PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk", "page": 99, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-06-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=99" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-06.4", "kind": "Control", "title": "Assets located within critical zones shall be physically protected against unaut…", "text": "Assets located within critical zones shall be physically protected against unauthorised access, damage, or interference.", "section": "6.1.6 PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk", "page": 99, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-06-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=99" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-01.1", "kind": "Control", "title": "The organisation shall establish and maintain a cybersecurity awareness and trai…", "text": "The organisation shall establish and maintain a cybersecurity awareness and training programme to ensure that all personnel understand how to perform their tasks securely and responsibly.", "section": "6.2.1 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "page": 101, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=101" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-01.2", "kind": "Control", "title": "The organisation shall include insider threat awareness and reporting in its cyb…", "text": "The organisation shall include insider threat awareness and reporting in its cybersecurity training to help personnel recognise and respond to potential internal risks.", "section": "6.2.1 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "page": 102, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=102" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-01.3", "kind": "Control", "title": "Personnel shall receive training to understand their specific roles, responsibil…", "text": "Personnel shall receive training to understand their specific roles, responsibilities, and priorities during a cybersecurity or information security incident, including the steps they need to follow to respond effectively.", "section": "6.2.1 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "page": 102, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=102" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-01.4", "kind": "Control", "title": "The organisation shall evaluate whether its cybersecurity awareness training is …", "text": "The organisation shall evaluate whether its cybersecurity awareness training is effective in improving knowledge, behaviour, and readiness across the organisation.", "section": "6.2.1 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind", "page": 103, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=103" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-02.1", "kind": "Control", "title": "Members of management bodies shall be able to demonstrate that they have complet…", "text": "Members of management bodies shall be able to demonstrate that they have completed training that gives them a solid understanding of information and cybersecurity and risk management so that they can assess information and cybersecurity risks and their consequences and propose the necessary risk mitigation, considering their roles, responsibilities and authorities.", "section": "6.2.2 PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind", "page": 103, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=103" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-02.2", "kind": "Control", "title": "Individuals in specialised roles shall be provided with awareness and training b…", "text": "Individuals in specialised roles shall be provided with awareness and training before privileges are granted, so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind.", "section": "6.2.2 PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind", "page": 104, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=104" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AT-02.3", "kind": "Control", "title": "Privileged users shall be qualified before privileges are granted, and these use…", "text": "Privileged users shall be qualified before privileges are granted, and these users shall be able to demonstrate the understanding of their roles, responsibilities, and authorities.", "section": "6.2.2 PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind", "page": 104, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-at-02-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=104" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.1", "kind": "Control", "title": "The organisation shall implement software, firmware, and information integrity c…", "text": "The organisation shall implement software, firmware, and information integrity checks to detect unauthorised changes to its critical system components during storage, transport, start-up and when determined necessary.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 106, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=106" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.2", "kind": "Control", "title": "The organisation shall implement automated tools where feasible to provide notif…", "text": "The organisation shall implement automated tools where feasible to provide notification upon discovering discrepancies during integrity verification.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 107, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=107" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.3", "kind": "Control", "title": "The organisation shall define and implement automated responses to detected inte…", "text": "The organisation shall define and implement automated responses to detected integrity violations, using predefined safeguards that are proportionate to the severity and impact of the violation.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 107, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=107" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.4", "kind": "Control", "title": "The organisation shall define and enforce clear policies and practical safeguard…", "text": "The organisation shall define and enforce clear policies and practical safeguards to manage and restrict the use of portable storage media, in order to reduce the risk of data leakage, unauthorised access, and malware introduction.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 108, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=108" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.5", "kind": "Control", "title": "The organisation shall only allow the use of removable media when absolutely nec…", "text": "The organisation shall only allow the use of removable media when absolutely necessary and shall put technical measures in place to block automatic execution of files from these devices.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 109, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=109" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-02.1", "kind": "Control", "title": "Portable storage devices containing system data shall be controlled and protecte…", "text": "Portable storage devices containing system data shall be controlled and protected while in transit and in storage.", "section": "6.3.2 PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected", "page": 111, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=111" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-10.1", "kind": "Control", "title": "The organisation’s critical systems shall be protected against denial-of-service…", "text": "The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.", "section": "6.3.3 PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected", "page": 112, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-10-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=112" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-11.1", "kind": "Control", "title": "Backups for the organisation's business-critical data shall be performed and sto…", "text": "Backups for the organisation's business-critical data shall be performed and stored on a different system from the device on which the original data resides.", "section": "6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested", "page": 112, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-11-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=112" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-11.3", "kind": "Control", "title": "The organisation shall maintain secure backups of business-critical data in a se…", "text": "The organisation shall maintain secure backups of business-critical data in a separate storage location to ensure data availability in case of system failure or data loss. Backup storage shall apply equivalent security controls as the primary environment.", "section": "6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested", "page": 114, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-11-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=114" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-11.4", "kind": "Control", "title": "The organisation shall regularly verify the integrity and recoverability of back…", "text": "The organisation shall regularly verify the integrity and recoverability of backups through coordinated testing with all relevant continuity and incident response functions. Backup testing shall be integrated into broader resilience planning, including business continuity, disaster recovery, and cyber incident response.", "section": "6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested", "page": 115, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-11-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=115" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-11.5", "kind": "Control", "title": "Backups of critical systems (such as operating systems, configurations, and appl…", "text": "Backups of critical systems (such as operating systems, configurations, and applications) shall be kept separate from backups of critical information (such as business data, documents, and databases) to support faster and more reliable recovery.", "section": "6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested", "page": 115, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-11-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=115" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-01.1", "kind": "Control", "title": "The organisation shall develop, document, and maintain a baseline configuration …", "text": "The organisation shall develop, document, and maintain a baseline configuration for its business critical systems.", "section": "6.4.1 PR.PS-01 Configuration management practices are established and applied", "page": 117, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=117" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-01.2", "kind": "Control", "title": "The organisation shall configure its business-critical systems to operate with o…", "text": "The organisation shall configure its business-critical systems to operate with only the essential functions needed for their intended purpose. This includes reviewing and updating baseline configurations to disable any non-essential capabilities.", "section": "6.4.1 PR.PS-01 Configuration management practices are established and applied", "page": 118, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=118" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-01.3", "kind": "Control", "title": "The organisation shall identify and disable specific functions, ports, protocols…", "text": "The organisation shall identify and disable specific functions, ports, protocols, and services within its critical systems that are not required for business operations.", "section": "6.4.1 PR.PS-01 Configuration management practices are established and applied", "page": 118, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=118" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-01.4", "kind": "Control", "title": "The organisation shall implement technical safeguards to enforce a policy of ‘de…", "text": "The organisation shall implement technical safeguards to enforce a policy of ‘deny-all’ and ‘permit-by-exception’ so that only authorised software programmes are executed.", "section": "6.4.1 PR.PS-01 Configuration management practices are established and applied", "page": 119, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=119" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-01.5", "kind": "Control", "title": "Unauthorised configuration changes to organisation's systems shall be monitored …", "text": "Unauthorised configuration changes to organisation's systems shall be monitored and addressed with the appropriate mitigation actions.", "section": "6.4.1 PR.PS-01 Configuration management practices are established and applied", "page": 119, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-01-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=119" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-02.1", "kind": "Control", "title": "The organisation shall enforce restrictions on software usage and installation, …", "text": "The organisation shall enforce restrictions on software usage and installation, and ensure that software is maintained, replaced, or removed based on its associated risk.", "section": "6.4.2 PR.PS-02 Software is maintained, replaced, and removed commensurate with risk", "page": 119, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=119" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-03.1", "kind": "Control", "title": "Hardware used in business-critical environments shall be maintained, replaced, o…", "text": "Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk.", "section": "6.4.3 PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk", "page": 120, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=120" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-04.1", "kind": "Control", "title": "Logs shall be maintained, documented, and monitored.", "text": "Logs shall be maintained, documented, and monitored.", "section": "6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring", "page": 120, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=120" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-04.2", "kind": "Control", "title": "The organisation shall ensure that logbook records contain an authoritative time…", "text": "The organisation shall ensure that logbook records contain an authoritative time source or internal clock time stamp that is compared and synchronised with an authoritative time source.", "section": "6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring", "page": 121, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=121" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-04.5", "kind": "Control", "title": "The organisation shall ensure that authorised personnel can extend or enhance au…", "text": "The organisation shall ensure that authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response.", "section": "6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring", "page": 122, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-04-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=122" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-06.1", "kind": "Control", "title": "Security shall be considered throughout the lifecycle of systems and application…", "text": "Security shall be considered throughout the lifecycle of systems and applications, whether developed internally or acquired externally.", "section": "6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "page": 124, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=124" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-06.3", "kind": "Control", "title": "Secure software development practices shall be integrated into all phases of the…", "text": "Secure software development practices shall be integrated into all phases of the software development lifecycle, and their effectiveness should be regularly monitored and improved.", "section": "6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "page": 125, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-06-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=125" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-06.4", "kind": "Control", "title": "For planned changes to the organisation's critical systems, a security impact an…", "text": "For planned changes to the organisation's critical systems, a security impact analysis shall be performed in a separate test environment before implementation in an operational environment.", "section": "6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "page": 126, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-06-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=126" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.1", "kind": "Control", "title": "Firewalls shall be installed, configured, and actively maintained on all network…", "text": "Firewalls shall be installed, configured, and actively maintained on all networks used by the organisation to protect against unauthorised access and cyber threats.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 127, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=127" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.2", "kind": "Control", "title": "To safeguard critical systems, organisations shall implement network segmentatio…", "text": "To safeguard critical systems, organisations shall implement network segmentation and segregation aligned with trust boundaries and asset criticality, thereby limiting threat propagation and enforcing strict access control", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 128, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=128" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.3", "kind": "Control", "title": "To ensure operational stability and security, the organisation shall, without ex…", "text": "To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 128, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=128" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.4", "kind": "Control", "title": "The organisation shall implement appropriate boundary protection measures to mon…", "text": "The organisation shall implement appropriate boundary protection measures to monitor and control communications at external and key internal boundaries of its critical systems, across both IT and OT environments, to ensure secure and reliable operations.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 129, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=129" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.5", "kind": "Control", "title": "The organisation shall implement, where feasible, authenticated proxy servers or…", "text": "The organisation shall implement, where feasible, authenticated proxy servers or firewalls with URL filtering and threat intelligence capabilities for defined communications traffic between its critical systems and external networks.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 130, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=130" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.6", "kind": "Control", "title": "The organisation shall ensure that its critical systems are designed to fail sec…", "text": "The organisation shall ensure that its critical systems are designed to fail securely and remain protected in the event of an operational failure of a border protection device.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 131, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=131" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.7", "kind": "Control", "title": "The organisation shall ensure that development and test environments are strictl…", "text": "The organisation shall ensure that development and test environments are strictly separated from the production environment, particularly in ICS/OT systems where any crossover could compromise safety, endanger health, or disrupt essential operations.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 132, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-7", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=132" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.8", "kind": "Control", "title": "The organisation shall define, monitor, and control the flow of information and …", "text": "The organisation shall define, monitor, and control the flow of information and data within and between its critical systems to ensure that only authorised and secure exchanges occur, regardless of network boundaries or system architecture.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 133, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-8", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=133" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-01.9", "kind": "Control", "title": "The organisation shall manage interfaces with external telecommunications servic…", "text": "The organisation shall manage interfaces with external telecommunications services as part of its broader network security policy, by defining how traffic is controlled, ensuring the confidentiality and integrity of transmitted information, and reviewing and documenting any exceptions to established rules.", "section": "6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage", "page": 134, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-01-9", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=134" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-02.1", "kind": "Control", "title": "The organisation shall define, implement and maintain policies and procedures re…", "text": "The organisation shall define, implement and maintain policies and procedures related to emergency and safety systems, fire protection systems and environmental controls for its critical systems.", "section": "6.5.2 PR.IR-02 The organisation's technology assets are protected from environmental threats", "page": 135, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=135" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-02.2", "kind": "Control", "title": "The organisation shall implement fire detection devices that activate and notify…", "text": "The organisation shall implement fire detection devices that activate and notify key personnel automatically in the event of a fire.", "section": "6.5.2 PR.IR-02 The organisation's technology assets are protected from environmental threats", "page": 135, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=135" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-03.1", "kind": "Control", "title": "The organisation shall implement mechanisms to ensure that critical systems and …", "text": "The organisation shall implement mechanisms to ensure that critical systems and services remain operational or can be quickly restored during both normal operations and adverse conditions.", "section": "6.5.3 PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations", "page": 136, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=136" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.IR-04.1", "kind": "Control", "title": "Adequate resource capacity planning shall ensure that availability of organisati…", "text": "Adequate resource capacity planning shall ensure that availability of organisation's critical system information processing, networking, telecommunications, and data storage is maintained.", "section": "6.5.4 PR.IR-04 Adequate resource capacity to ensure availability is maintained", "page": 137, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ir-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=137" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-01.1", "kind": "Control", "title": "Firewalls shall be installed and operated at the network boundaries, including e…", "text": "Firewalls shall be installed and operated at the network boundaries, including endpoint firewalls.", "section": "7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events", "page": 138, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=138" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-01.3", "kind": "Control", "title": "The organisation shall monitor and identify unauthorised use of its business cri…", "text": "The organisation shall monitor and identify unauthorised use of its business critical systems through the detection of unauthorised local connections, network connections and remote connections.", "section": "7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events", "page": 139, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-01-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=139" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-01.4", "kind": "Control", "title": "The organisation shall continuously monitor its network to spot signs of cyber t…", "text": "The organisation shall continuously monitor its network to spot signs of cyber threats or unusual activity, using clearly defined rules for what counts as a potential security incident.", "section": "7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events", "page": 140, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-01-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=140" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-02.2", "kind": "Control", "title": "Physical access to the organisation's critical systems and devices, in addition …", "text": "Physical access to the organisation's critical systems and devices, in addition to physical access monitoring to the facility, shall be supplemented by physical intrusion alarms, surveillance equipment, and independent monitoring teams.", "section": "7.1.2 DE.CM-02 The physical environment is monitored to find potentially adverse events", "page": 141, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=141" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-03.1", "kind": "Control", "title": "End point and network protection tools to monitor end-user behaviour for dangero…", "text": "End point and network protection tools to monitor end-user behaviour for dangerous activity shall be implemented.", "section": "7.1.3 DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events", "page": 141, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=141" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-06.1", "kind": "Control", "title": "External service provider activities and services shall be secured and monitored…", "text": "External service provider activities and services shall be secured and monitored to find potentially adverse events.", "section": "7.1.4 DE.CM-06 External service provider activities and services are monitored to find potentially adverse events", "page": 143, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=143" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-06.2", "kind": "Control", "title": "External service providers' conformance with personnel security policies and pro…", "text": "External service providers' conformance with personnel security policies and procedures and contract security requirements shall be monitored relative to their cybersecurity risks.", "section": "7.1.4 DE.CM-06 External service provider activities and services are monitored to find potentially adverse events", "page": 143, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-06-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=143" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-09.1", "kind": "Control", "title": "The organisation shall monitor computing hardware, software, runtime environment…", "text": "The organisation shall monitor computing hardware, software, runtime environments, and their data to detect potentially adverse events.", "section": "7.1.5 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "page": 144, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-09-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=144" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-09.2", "kind": "Control", "title": "The organisation shall implement hardware integrity checks to detect unauthorise…", "text": "The organisation shall implement hardware integrity checks to detect unauthorised tampering of critical system hardware. Controls shall be proportionate to the organisation’s risk profile and operational capacity.", "section": "7.1.5 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "page": 144, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-09-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=144" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-09.3", "kind": "Control", "title": "The organisation's incident response plan shall include measures to detect unaut…", "text": "The organisation's incident response plan shall include measures to detect unauthorised tampering with the hardware of critical systems.", "section": "7.1.5 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "page": 145, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-09-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=145" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-09.4", "kind": "Control", "title": "The organisation shall establish a system to accurately distinguish between legi…", "text": "The organisation shall establish a system to accurately distinguish between legitimate alerts and false positives, ensuring effective detection and removal of malicious code.", "section": "7.1.5 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events", "page": 146, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-09-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=146" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-02.1", "kind": "Control", "title": "Cybersecurity and information security events shall be reviewed and analysed to …", "text": "Cybersecurity and information security events shall be reviewed and analysed to identify potential attack targets and methods, in accordance with applicable laws, regulations, standards, and policies.", "section": "7.2.1 DE.AE-02 Potentially adverse events are analysed to better understand associated activities", "page": 148, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=148" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-03.1", "kind": "Control", "title": "The logging functionality of protection and detection tools shall be enabled. Lo…", "text": "The logging functionality of protection and detection tools shall be enabled. Logs shall be backed up and retained for a predefined period and regularly reviewed to identify unusual or potentially harmful activity.", "section": "7.2.2 DE.AE-03 Information is correlated from multiple sources", "page": 149, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=149" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-03.2", "kind": "Control", "title": "The organisation shall ensure that event data from critical systems is collected…", "text": "The organisation shall ensure that event data from critical systems is collected and correlated using information from multiple relevant sources.", "section": "7.2.2 DE.AE-03 Information is correlated from multiple sources", "page": 149, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=149" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-03.3", "kind": "Control", "title": "The organisation shall combine event analysis with information from vulnerabilit…", "text": "The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility monitoring, where feasible.", "section": "7.2.2 DE.AE-03 Information is correlated from multiple sources", "page": 150, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-03-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=150" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-04.1", "kind": "Control", "title": "The organisation shall assess the negative impacts of detected events on its ope…", "text": "The organisation shall assess the negative impacts of detected events on its operations, assets, and individuals, and shall link these impacts to the results of its risk assessments.", "section": "7.2.3 DE.AE-04 The estimated impact and scope of adverse events are understood", "page": 150, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=150" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-06.1", "kind": "Control", "title": "Information about adverse events shall be promptly delivered to authorised perso…", "text": "Information about adverse events shall be promptly delivered to authorised personnel and systems to enable timely detection, investigation, and response.", "section": "7.2.4 DE.AE-06 Information on adverse events is provided to authorised staff and tools", "page": 151, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=151" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-08.1", "kind": "Control", "title": "Incidents shall be reported when adverse events meet defined and documented inci…", "text": "Incidents shall be reported when adverse events meet defined and documented incident criteria.", "section": "7.2.5 DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria", "page": 152, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-08-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=152" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-01.1", "kind": "Control", "title": "An incident response plan, including defined roles, responsibilities, and author…", "text": "An incident response plan, including defined roles, responsibilities, and authorities, shall be executed during or after a cybersecurity event affecting the organisation's critical systems.", "section": "8.1.1 RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared", "page": 153, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=153" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-01.2", "kind": "Control", "title": "The organisation shall coordinate information/cybersecurity incident response ac…", "text": "The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders.", "section": "8.1.1 RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared", "page": 154, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=154" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-02.1", "kind": "Control", "title": "Information/cybersecurity incident reports shall be triaged and validated in acc…", "text": "Information/cybersecurity incident reports shall be triaged and validated in accordance with the organisation’s incident response procedures.", "section": "8.1.2 RS.MA-02 Incident reports are triaged and validated", "page": 154, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=154" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-03.1", "kind": "Control", "title": "Information/cybersecurity incidents shall be categorised, prioritised and escala…", "text": "Information/cybersecurity incidents shall be categorised, prioritised and escalated as determined in the incident response plan.", "section": "8.1.3 RS.MA-03 Incidents are categorised and prioritised", "page": 155, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=155" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-05.1", "kind": "Control", "title": "Clear criteria shall be defined and applied to determine when incident recovery …", "text": "Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.", "section": "8.1.4 RS.MA-05 The criteria for initiating incident recovery are applied", "page": 156, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=156" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.AN-06.1", "kind": "Control", "title": "Actions performed during an investigation shall be recorded, and the records' in…", "text": "Actions performed during an investigation shall be recorded, and the records' integrity and provenance shall be preserved.", "section": "8.2.2 RS.AN-06 Actions performed during an investigation are recorded, and the records’ integrity and provenance are preserved", "page": 157, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-an-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=157" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.AN-07.1", "kind": "Control", "title": "Incident data and metadata shall be collected and protected to ensure their accu…", "text": "Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.", "section": "8.2.3 RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved", "page": 158, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-an-07-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=158" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.AN-08.1", "kind": "Control", "title": "An incident’s magnitude shall be estimated and validated.", "text": "An incident’s magnitude shall be estimated and validated.", "section": "8.2.4 RS.AN-08 An incident's magnitude is estimated and validated", "page": 158, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-an-08-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=158" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.CO-02.1", "kind": "Control", "title": "Information about cybersecurity incidents shall be communicated to employees in …", "text": "Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand.", "section": "8.3.1 RS.CO-02 Internal and external stakeholders are notified of incidents", "page": 159, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-co-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=159" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.CO-02.2", "kind": "Control", "title": "Cybersecurity incidents shall be shared with relevant external stakeholders with…", "text": "Cybersecurity incidents shall be shared with relevant external stakeholders within the timeframes defined in the Incident Response Plan, including reporting significant incidents to authorities as required by law.", "section": "8.3.1 RS.CO-02 Internal and external stakeholders are notified of incidents", "page": 159, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-co-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=159" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MI-01.1", "kind": "Control", "title": "Cybersecurity incidents shall be contained and eliminated. Any decision to accep…", "text": "Cybersecurity incidents shall be contained and eliminated. Any decision to accept and retain certain cybersecurity risks shall be formally documented.", "section": "8.4.1 RS.MI-01 Incidents are contained", "page": 161, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-mi-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=161" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MI-01.2", "kind": "Control", "title": "The organisation shall detect unauthorised access or data leakage and take appro…", "text": "The organisation shall detect unauthorised access or data leakage and take appropriate mitigation actions, including monitoring of critical systems at external boundaries and key internal points.", "section": "8.4.1 RS.MI-01 Incidents are contained", "page": 161, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-mi-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=161" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.RP-01.1", "kind": "Control", "title": "A recovery process for disasters and information/cybersecurity incidents shall b…", "text": "A recovery process for disasters and information/cybersecurity incidents shall be developed and executed.", "section": "9.1.1 RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process", "page": 163, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-rp-01-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=163" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.RP-02.1", "kind": "Control", "title": "The organisation's essential functions and services shall be continued with litt…", "text": "The organisation's essential functions and services shall be continued with little or no loss of operational continuity, and continuity shall be maintained until full system recovery.", "section": "9.1.2 RC.RP-02 Recovery actions are selected, scoped, prioritised, and performed", "page": 164, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-rp-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=164" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.RP-05.1", "kind": "Control", "title": "The integrity of restored systems and assets shall be verified before they are r…", "text": "The integrity of restored systems and assets shall be verified before they are returned to service. Systems and services shall be fully restored, and normal operations shall be confirmed.", "section": "9.1.3 RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed", "page": 164, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-rp-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=164" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.RP-06.1", "kind": "Control", "title": "The end of incident recovery shall be formally declared based on predefined crit…", "text": "The end of incident recovery shall be formally declared based on predefined criteria, and all incident-related documentation shall be completed and reviewed.", "section": "9.1.4 RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed", "page": 165, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-rp-06-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=165" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.CO-03.1", "kind": "Control", "title": "Recovery activities and progress in restoring operational capabilities shall be …", "text": "Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.", "section": "9.2.1 RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders", "page": 166, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-co-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=166" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.CO-04.1", "kind": "Control", "title": "Public updates on incident recovery shall be shared using approved communication…", "text": "Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures.", "section": "9.2.2 RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging", "page": 166, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-co-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=166" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.CO-04.2", "kind": "Control", "title": "The organisation shall assign a Public Relations Officer (PRO) to manage public …", "text": "The organisation shall assign a Public Relations Officer (PRO) to manage public communications during information/cybersecurity incident recovery, ensuring that public updates are shared while maintaining the confidentiality, integrity, and accuracy of the information.", "section": "9.2.2 RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging", "page": 167, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-co-04-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=167" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RC.CO-04.3", "kind": "Control", "title": "The organisation shall implement a crisis communication strategy to mitigate neg…", "text": "The organisation shall implement a crisis communication strategy to mitigate negative impacts during a crisis and help restore its reputation afterward.", "section": "9.2.2 RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging", "page": 167, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rc-co-04-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=167" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-01.2", "kind": "Control", "title": "Anti-virus, -spyware, and other -malware programs shall be installed and updated…", "text": "Anti-virus, -spyware, and other -malware programs shall be installed and updated.", "section": "7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events", "page": 138, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-01-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=138" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.RR-02.2", "kind": "Control", "title": "The organisation shall appoint a senior-level executive information security off…", "text": "The organisation shall appoint a senior-level executive information security officer.", "section": "4.3.2 GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-rr-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.RA-05.3", "kind": "Control", "title": "Risk assessment results shall be disseminated to relevant stakeholders.", "text": "Risk assessment results shall be disseminated to relevant stakeholders.", "section": "5.2.4 ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-ra-05-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "GV.SC-07.3", "kind": "Control", "title": "The organisation shall audit business-critical third-party service providers for…", "text": "The organisation shall audit business-critical third-party service providers for security compliance.", "section": "4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#gv-sc-07-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-05.1", "kind": "Control", "title": "The organisation’s assets shall be prioritised based on classification, critical…", "text": "The organisation’s assets shall be prioritised based on classification, criticality, and business value.", "section": "5.1.5 ID.AM-05 Assets are prioritised based on classification, criticality, resources, and impact on the mission", "page": 51, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=51" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-07.1", "kind": "Control", "title": "Data that the organisation stores and uses shall be identified.", "text": "Data that the organisation stores and uses shall be identified.", "section": "5.1.6 ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-07-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-07.2", "kind": "Control", "title": "Inventories of data and associated metadata shall be maintained for designated d…", "text": "Inventories of data and associated metadata shall be maintained for designated data types.", "section": "5.1.6 ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-07-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.AM-08.8", "kind": "Control", "title": "The organisation shall pre-approve, monitor and enforce maintenance tools for us…", "text": "The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems.", "section": "5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-am-08-8", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "ID.IM-03.5", "kind": "Control", "title": "Communication of effectiveness of protection technologies shall be shared with r…", "text": "Communication of effectiveness of protection technologies shall be shared with relevant stakeholders.", "section": "5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities", "page": 74, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#id-im-03-5", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=74" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-04.1", "kind": "Control", "title": "Identity assertions shall be protected, conveyed, and verified", "text": "Identity assertions shall be protected, conveyed, and verified", "section": "6.1.4 PR.AA-04 Identity assertions are protected, conveyed, and verified", "page": 88, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-04-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=88" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.6", "kind": "Control", "title": "Separation of duties (SoD) shall be ensured in the management of access rights.", "text": "Separation of duties (SoD) shall be ensured in the management of access rights.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 93, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=93" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.7", "kind": "Control", "title": "Privileged users shall be managed and monitored.", "text": "Privileged users shall be managed and monitored.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 94, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-7", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=94" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.AA-05.9", "kind": "Control", "title": "Privileged users shall be managed, monitored and audited.", "text": "Privileged users shall be managed, monitored and audited.", "section": "6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties", "page": 96, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-aa-05-9", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=96" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.6", "kind": "Control", "title": "The organisation shall protect the confidentiality of its critical assets while …", "text": "The organisation shall protect the confidentiality of its critical assets while at rest.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 109, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-6", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=109" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-01.9", "kind": "Control", "title": "Enterprise assets shall be disposed of safely.", "text": "Enterprise assets shall be disposed of safely.", "section": "6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected", "page": 110, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-01-9", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=110" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-02.2", "kind": "Control", "title": "The organisation shall protect its critical and sensitive information while in t…", "text": "The organisation shall protect its critical and sensitive information while in transit.", "section": "6.3.2 PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected", "page": 111, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=111" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.DS-11.2", "kind": "Control", "title": "The reliability and integrity of backups shall be verified and tested regularly.", "text": "The reliability and integrity of backups shall be verified and tested regularly.", "section": "6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested", "page": 113, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ds-11-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=113" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-04.3", "kind": "Control", "title": "Audit data from the organisation's critical systems shall be moved to an alterna…", "text": "Audit data from the organisation's critical systems shall be moved to an alternative system.", "section": "6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring", "page": 122, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-04-3", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=122" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-04.4", "kind": "Control", "title": "The organisation shall ensure that audit processing failures on the organisation…", "text": "The organisation shall ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses.", "section": "6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring", "page": 122, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-04-4", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=122" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-05.1", "kind": "Control", "title": "Web and e-mail filters shall be installed and used.", "text": "Web and e-mail filters shall be installed and used.", "section": "6.4.5 PR.PS-05 Installation and execution of unauthorised software are prevented", "page": 123, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-05-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=123" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-05.2", "kind": "Control", "title": "Installation and execution of unauthorised software shall be prevented.", "text": "Installation and execution of unauthorised software shall be prevented.", "section": "6.4.5 PR.PS-05 Installation and execution of unauthorised software are prevented", "page": 123, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-05-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=123" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "PR.PS-06.2", "kind": "Control", "title": "Changes and exceptions shall be tested and validated before being implemented in…", "text": "Changes and exceptions shall be tested and validated before being implemented into operational systems.", "section": "6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle", "page": 124, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#pr-ps-06-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=124" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-02.1", "kind": "Control", "title": "The physical environment shall be monitored to find potentially adverse events.", "text": "The physical environment shall be monitored to find potentially adverse events.", "section": "7.1.2 DE.CM-02 The physical environment is monitored to find potentially adverse events", "page": 140, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-02-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=140" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.CM-03.2", "kind": "Control", "title": "End point and network protection tools that monitor end-user behaviour for dange…", "text": "End point and network protection tools that monitor end-user behaviour for dangerous activity shall be managed.", "section": "7.1.3 DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events", "page": 142, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-cm-03-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=142" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "DE.AE-02.2", "kind": "Control", "title": "The organisation shall implement automated mechanisms where feasible to review a…", "text": "The organisation shall implement automated mechanisms where feasible to review and analyse detected events.", "section": "7.2.1 DE.AE-02 Potentially adverse events are analysed to better understand associated activities", "page": 148, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#de-ae-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=148" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.MA-02.2", "kind": "Control", "title": "Automated tools shall be used to support the investigation and impact assessment…", "text": "Automated tools shall be used to support the investigation and impact assessment of validated cybersecurity incidents.", "section": "8.1.2 RS.MA-02 Incident reports are triaged and validated", "page": 155, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-ma-02-2", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=155" }, { "document": "NL-P-02", "document_title": "Essential Entity Requirements", "version": "RC1.0", "id": "RS.AN-03.1", "kind": "Control", "title": "Each incident shall be analysed to determine what occurred and to identify its r…", "text": "Each incident shall be analysed to determine what occurred and to identify its root cause.", "section": "8.2.1 RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident", "page": 157, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-02#rs-an-03-1", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-02_Essential_Entity_Requirements_-_RC1.0_-_for_pub.pdf#page=157" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.2-CR-01", "kind": "Requirement (CR)", "title": "The product context shall be identified and documented, covering the product's i…", "text": "The product context shall be identified and documented, covering the product's intended purpose and reasonably foreseeable use (IPRFU), its functions, its operational environment, an architectural overview, a description of its users including their experience level and security-relevant objectives, and where relevant and useful: general product insights from the market segments involved, including market expectations.", "section": "4.2 Product Context Documentation", "page": 10, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-2-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=10" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.2-CR-02", "kind": "Requirement (CR)", "title": "Where the product includes remote data processing solutions (RDPS), the RDPS sha…", "text": "Where the product includes remote data processing solutions (RDPS), the RDPS shall be considered to be included in the product context.", "section": "4.2 Product Context Documentation", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-2-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=11" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.2-CR-03", "kind": "Requirement (CR)", "title": "A documented procedure shall be maintained for establishing and updating the pro…", "text": "A documented procedure shall be maintained for establishing and updating the product context, including defined triggers for re-evaluation when the application, its RDPS, or its operational environment changes.", "section": "4.2 Product Context Documentation", "page": 11, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-2-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=11" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.3-CR-01", "kind": "Requirement (CR)", "title": "The cybersecurity risk acceptance criteria shall be established. At minimum, the…", "text": "The cybersecurity risk acceptance criteria shall be established. At minimum, the criteria shall account for the product context, regulatory factors, supply chain aspects, the nature of risks, the current state of the art, and user needs.", "section": "4.3 Risk Acceptance Criteria", "page": 12, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-3-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=12" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.4-CR-01", "kind": "Requirement (CR)", "title": "When conducting a product cybersecurity risk assessment, all cybersecurity asset…", "text": "When conducting a product cybersecurity risk assessment, all cybersecurity assets relevant to the product shall be identified, and it shall be determined which cybersecurity properties (confidentiality, integrity, availability, authenticity, and others as applicable) need to be ensured for each. This identification shall be grounded in the product context established under section 5.2, and the resulting asset list with associated cybersecurity properties shall be included in the product's technical documentation. The asset scope is broad and shall consider data assets (e.g. credentials, keys, personal data, configuration data, safety signals, firmware images, logs), functional assets, hardware and software components and interfaces, user-objective assets (health, safety, privacy, availability), and environmental assets (adjacent networks, third parties, public interest, and assets involved in RDPS).", "section": "4.4 Product Cybersecurity Asset Identification", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-4-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=13" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.4-CR-02", "kind": "Requirement (CR)", "title": "In case the application employs AI models, AI-specific assets shall be included …", "text": "In case the application employs AI models, AI-specific assets shall be included in the considerations to identify cybersecurity assets.", "section": "4.4 Product Cybersecurity Asset Identification", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-4-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=14" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.5-CR-01", "kind": "Requirement (CR)", "title": "Drawing on the established product context, product cybersecurity risks shall be…", "text": "Drawing on the established product context, product cybersecurity risks shall be identified. Each identified risk shall specify which asset(s) are targeted, which cybersecurity objective(s) of those assets may be compromised, and the cause of that potential compromise.", "section": "4.5 Product Cybersecurity Risk Identification", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-5-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.5-CR-02", "kind": "Requirement (CR)", "title": "Where publicly known vulnerabilities exist that are relevant to the product's as…", "text": "Where publicly known vulnerabilities exist that are relevant to the product's assets and their associated cybersecurity properties, those publicly known vulnerabilities shall be identified. This obligation is conditional on the availability of such information.", "section": "4.5 Product Cybersecurity Risk Identification", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-5-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.5-CR-03", "kind": "Requirement (CR)", "title": "A documented threat modelling procedure specific to mobile applications shall be…", "text": "A documented threat modelling procedure specific to mobile applications shall be established and maintained, defining the methodology to be applied (e.g., STRIDE, PASTA, attack trees), the threat catalogues to use, the roles responsible for conducting threat modelling, and the trigger conditions under which threat modelling shall be performed or repeated (e.g., new feature introduction, platform OS update, third-party SDK integration).", "section": "4.5 Product Cybersecurity Risk Identification", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-5-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.6-CR-01", "kind": "Requirement (CR)", "title": "For each product cybersecurity risk identified in accordance with 5.5, the likel…", "text": "For each product cybersecurity risk identified in accordance with 5.5, the likelihood of the associated cybersecurity incident occurring shall be estimated.", "section": "4.6 Product Cybersecurity Risk Analysis", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-6-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.6-CR-02", "kind": "Requirement (CR)", "title": "For each product cybersecurity risk identified in accordance with 5.5, the sever…", "text": "For each product cybersecurity risk identified in accordance with 5.5, the severity of impact of the associated cybersecurity incident shall be estimated.", "section": "4.6 Product Cybersecurity Risk Analysis", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-6-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.6-CR-03", "kind": "Requirement (CR)", "title": "For each product cybersecurity risk identified in accordance with 5.5, the cyber…", "text": "For each product cybersecurity risk identified in accordance with 5.5, the cybersecurity incident scenario in which that risk could materialize shall be documented.", "section": "4.6 Product Cybersecurity Risk Analysis", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-6-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.6-CR-04", "kind": "Requirement (CR)", "title": "A repeatable risk analysis methodology for cybersecurity risks shall be defined …", "text": "A repeatable risk analysis methodology for cybersecurity risks shall be defined and documented, specifying the rating scale, criteria, and scoring rationale to be applied consistently across all risk assessments.", "section": "4.6 Product Cybersecurity Risk Analysis", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-6-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.6-CR-05", "kind": "Requirement (CR)", "title": "The rationale and evidence supporting each likelihood and severity result shall …", "text": "The rationale and evidence supporting each likelihood and severity result shall be documented, enabling independent review and auditability of the risk analysis.", "section": "4.6 Product Cybersecurity Risk Analysis", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-6-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.7-CR-01", "kind": "Requirement (CR)", "title": "Every identified risk shall be systematically assessed against the pre-establish…", "text": "Every identified risk shall be systematically assessed against the pre-established risk acceptance criteria to determine whether it can be accepted as-is or shall be subjected to treatment measures.", "section": "4.7 Product Cybersecurity Risk Evaluation and Risk Acceptance", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-7-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.7-CR-02", "kind": "Requirement (CR)", "title": "A risk may be deemed acceptable only when it demonstrably aligns with the predet…", "text": "A risk may be deemed acceptable only when it demonstrably aligns with the predetermined risk acceptance criteria defined in 5.3. Risks that do not meet these criteria shall not be accepted, regardless of other considerations such as cost or feasibility.", "section": "4.7 Product Cybersecurity Risk Evaluation and Risk Acceptance", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-7-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.7-CR-03", "kind": "Requirement (CR)", "title": "When residual risks are shared with users - because the product relies on the op…", "text": "When residual risks are shared with users - because the product relies on the operational environment or user action to provide necessary controls - it shall be verified that the required user mitigations are realistic and achievable for the intended user base, given their expected knowledge and capability. Risk acceptance under these conditions is contingent on this verification.", "section": "4.7 Product Cybersecurity Risk Evaluation and Risk Acceptance", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-7-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.7-CR-04", "kind": "Requirement (CR)", "title": "For each accepted or residual risk, a documented acceptance justification shall …", "text": "For each accepted or residual risk, a documented acceptance justification shall be produced and retained explaining why the risk is considered acceptable. This justification shall reference the risk acceptance criteria from 5.3 and shall describe any conditions of use or operational environment assumptions on which the acceptance is predicated.", "section": "4.7 Product Cybersecurity Risk Evaluation and Risk Acceptance", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-7-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.8-CR-01", "kind": "Requirement (CR)", "title": "For every risk that does not satisfy the established risk acceptance criteria, a…", "text": "For every risk that does not satisfy the established risk acceptance criteria, a treatment option that is appropriate to the product context shall be applied.", "section": "4.8 Product Cybersecurity Risk Treatment", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-8-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.8-CR-02", "kind": "Requirement (CR)", "title": "For each risk subject to treatment, documentation shall be made of the treatment…", "text": "For each risk subject to treatment, documentation shall be made of the treatment option selected and the justification for why that option is appropriate given the product context together with the applicable risk acceptance criteria.", "section": "4.8 Product Cybersecurity Risk Treatment", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-8-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.8-CR-03", "kind": "Requirement (CR)", "title": "Following the application of any risk treatment measure, the affected risks shal…", "text": "Following the application of any risk treatment measure, the affected risks shall be reevaluated to determine whether residual risks indeed meet the established acceptance criteria.", "section": "4.8 Product Cybersecurity Risk Treatment", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-8-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.9-CR-01", "kind": "Requirement (CR)", "title": "Risk communication directed at users shall employ language and methods appropria…", "text": "Risk communication directed at users shall employ language and methods appropriate to the audience; where the audience consists of consumers, the language used shall be clear and free of technical jargon to the extent practicable.", "section": "4.9 Product Cybersecurity Risk Communication", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-9-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.9-CR-02", "kind": "Requirement (CR)", "title": "Where a product is subject to applicable accessibility obligations or where the …", "text": "Where a product is subject to applicable accessibility obligations or where the intended user base includes individuals with impairments, risk communication shall consider formats and using language to ensure each user can meaningfully access the information.", "section": "4.9 Product Cybersecurity Risk Communication", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-9-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.9-CR-03", "kind": "Requirement (CR)", "title": "Risk communication documentation shall address a minimum set of elements: the ci…", "text": "Risk communication documentation shall address a minimum set of elements: the circumstances and foreseeable misuse scenarios that could give rise to significant cybersecurity risks; the mitigation measures users are expected to implement; and the operational conditions under which the product may be used securely.", "section": "4.9 Product Cybersecurity Risk Communication", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-9-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.10-CR-01", "kind": "Requirement (CR)", "title": "Reviews of product cybersecurity risk management activities shall be conducted a…", "text": "Reviews of product cybersecurity risk management activities shall be conducted at planned intervals, where the frequency of those intervals is determined by the risk assessment and the context in which the product operates, and at least once a year - despite design staying the same.", "section": "4.10 Product Cybersecurity Risk Review", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-10-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.10-CR-02", "kind": "Requirement (CR)", "title": "In addition to planned-interval reviews, a review of risk management activities …", "text": "In addition to planned-interval reviews, a review of risk management activities shall be initiated when trigger conditions are met, including product modification, context changes, changes to risk acceptance criteria, changes in cybersecurity risk exposure (including threat landscape changes), identification of a known exploitable vulnerability, occurrence of a severe incident, or obsolescence of a component with cybersecurity impact.", "section": "4.10 Product Cybersecurity Risk Review", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-10-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "5.10-CR-03", "kind": "Requirement (CR)", "title": "Where a review conducted under 5.10-CR-01 or 5.10-CR-02 reveals that existing ri…", "text": "Where a review conducted under 5.10-CR-01 or 5.10-CR-02 reveals that existing risk assessment documentation is affected, the relevant documentation produced under Clause 5 shall be updated accordingly.", "section": "4.10 Product Cybersecurity Risk Review", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#5-10-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.2-CR-01", "kind": "Requirement (CR)", "title": "The product cybersecurity plan shall take the product context from 5.2 into acco…", "text": "The product cybersecurity plan shall take the product context from 5.2 into account, when available, and define, at minimum, every applicable cybersecurity activity defined in Clauses 6 and 7.", "section": "5.2 Product Cybersecurity Planning", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-2-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.2-CR-02", "kind": "Requirement (CR)", "title": "Throughout the entire product lifecycle, the product cybersecurity plan shall be…", "text": "Throughout the entire product lifecycle, the product cybersecurity plan shall be kept current through regular maintenance and review, and the execution of all planned activities shall be actively tracked. Review shall take place not only on a regular schedule but also upon occurrence of defined triggers.", "section": "5.2 Product Cybersecurity Planning", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-2-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.3-CR-01", "kind": "Requirement (CR)", "title": "Product cybersecurity requirements shall be derived from and grounded in the pro…", "text": "Product cybersecurity requirements shall be derived from and grounded in the product context, the decisions made regarding treatment of product cybersecurity risks, and all applicable regulatory requirements.", "section": "5.3 Product Cybersecurity Requirements", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-3-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.3-CR-02", "kind": "Requirement (CR)", "title": "Whenever any of the defined inputs - product context, risk assessment outcomes, …", "text": "Whenever any of the defined inputs - product context, risk assessment outcomes, risk treatment decisions, or applicable regulatory requirements - undergo change, the product cybersecurity requirements shall be reviewed and updated as necessary to remain current and accurate.", "section": "5.3 Product Cybersecurity Requirements", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-3-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=27" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.3-CR-03", "kind": "Requirement (CR)", "title": "Changes to product cybersecurity requirements shall be communicated to all affec…", "text": "Changes to product cybersecurity requirements shall be communicated to all affected development, testing, and operations teams in a timely and documented manner, with impact assessment by each affected party.", "section": "5.3 Product Cybersecurity Requirements", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-3-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=27" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.4-CR-01", "kind": "Requirement (CR)", "title": "A specification of the product's cybersecurity architecture and design shall be …", "text": "A specification of the product's cybersecurity architecture and design shall be produced. This specification shall include the selection of cybersecurity controls chosen to satisfy the cybersecurity requirements established in 6.3.", "section": "5.4 Cybersecurity Architecture and Design", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-4-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-01", "kind": "Requirement (CR)", "title": "The product shall be developed and maintained securely by using a secure develop…", "text": "The product shall be developed and maintained securely by using a secure development environment to prevent unauthorized access, to an extent appropriate given the product's risk profile, design, and scope. This shall be demonstrated by including the development environment in the scope of the provider’s Information Security Management System certified against ISO/IEC 27001 by an accredited certification body.", "section": "5.5 Secure Implementation", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-02", "kind": "Requirement (CR)", "title": "The product shall implement all cybersecurity requirements established in 6.3, i…", "text": "The product shall implement all cybersecurity requirements established in 6.3, in conformance with the cybersecurity architecture and design defined in 6.4.", "section": "5.5 Secure Implementation", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-03", "kind": "Requirement (CR)", "title": "A documented secure coding standard shall be adopted and enforced, applicable to…", "text": "A documented secure coding standard shall be adopted and enforced, applicable to the programming languages and frameworks used in the mobile application, covering at minimum: prohibited functions, memory safety practices, input validation, output encoding, error handling, preventing common security weaknesses, and prohibition of hard-coded credentials.", "section": "5.5 Secure Implementation", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-04", "kind": "Requirement (CR)", "title": "A process shall be established for identifying, reviewing, and approving the use…", "text": "A process shall be established for identifying, reviewing, and approving the use of memoryunsafe programming languages or constructs in the mobile application, and shall document the rationale and compensating controls where their use cannot be avoided.", "section": "5.5 Secure Implementation", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-05", "kind": "Requirement (CR)", "title": "Where secure implementation activities produce deviations from the cybersecurity…", "text": "Where secure implementation activities produce deviations from the cybersecurity architecture and design, reviews shall be triggered of the cybersecurity risk management activities, as defined in 5.10 and all affected cybersecurity product lifecycle activities.", "section": "5.5 Secure Implementation", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-06", "kind": "Requirement (CR)", "title": "The product shall use cryptographic mechanisms that reflect the state of the art…", "text": "The product shall use cryptographic mechanisms that reflect the state of the art and that conform to the cryptographic requirements applicable to the product and agreed within its certification, regulatory, or sectoral context - covering the selection of algorithms, parameters, key sizes, operational modes, random number generation, key lifecycle management, and the deprecation policy. Where the applicable requirements do not designate a specific cryptographic reference, the agreed cryptographic mechanisms defined in the ECCG “Agreed Cryptographic Mechanisms” (ACM) shall be used as the recognised baseline. Where the product is subject to a European Digital Identity Wallet certification scheme or to the EUCC, the applicable ACM version is the one required by that scheme (via the EUCC “Guidelines on Cryptography”) at the time of the conformity assessment or surveillance evaluation; versions issued as drafts or for public review are excluded until adopted. Where the applicable requirements or the ACM do not address a specific mechanism, equivalent state-of-the-art cryptographic guidance shall be applied. Continued conformity as the applicable requirements or the applicable ACM version evolve shall be maintained in accordance with 6.5-CR-09.", "section": "5.5 Secure Implementation", "page": 30, "obligation": "mandatory", "legal_refs": [ "EUCC" ], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-07", "kind": "Requirement (CR)", "title": "The product shall protect cryptographic keys through secure hardware modules. If…", "text": "The product shall protect cryptographic keys through secure hardware modules. If hardwarebased protection is not feasible, the product shall use secure software modules to protect cryptographic keys.", "section": "5.5 Secure Implementation", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-08", "kind": "Requirement (CR)", "title": "A process shall be established for inventorying and verifying all locations in t…", "text": "A process shall be established for inventorying and verifying all locations in the mobile application and its RDPS where cryptographic keys are generated, stored, used, and destroyed. Verification shall ensure that each location meets the cryptographic requirements in this document.", "section": "5.5 Secure Implementation", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-09", "kind": "Requirement (CR)", "title": "A process shall be established for periodically reviewing the protocol inventory…", "text": "A process shall be established for periodically reviewing the protocol inventory (see technical documentation in 6.6) against current state-of-the-art guidance and for identifying protocols that have been deprecated, are vulnerable, or require compensating measures in accordance with 6.5-CR-10.", "section": "5.5 Secure Implementation", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.5-CR-10", "kind": "Requirement (CR)", "title": "When the product relies on legacy or vulnerable protocols, the product shall imp…", "text": "When the product relies on legacy or vulnerable protocols, the product shall implement security measures mitigating protocol issues - such as, but not limited to, multi-factor authentication - sufficient to maintain a security level commensurate with the risks introduced by those protocols.", "section": "5.5 Secure Implementation", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-5-cr-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-01", "kind": "Requirement (CR)", "title": "The product shall maintain an identified list of all integrated components inclu…", "text": "The product shall maintain an identified list of all integrated components including at least the top-level dependencies and the transitive dependencies when technically feasible, in a commonly used machine-readable format. This is referred to as an SBOM (Software Bill Of Materials). A list entry shall include the type of dependency, software producer, unique component identifier (e.g. producer, component name, and component version). The SBOM shall contain the identity of the SBOM author, a version indicator, and a timestamp. When integrating third-party components, the intended purpose and user instructions to address cybersecurity risks of those components are the conditions that shall be adhered to.", "section": "5.6 Technical Product Documentation", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-02", "kind": "Requirement (CR)", "title": "A mapping of upstream dependencies and interdependencies, apart from components,…", "text": "A mapping of upstream dependencies and interdependencies, apart from components, shall be available to support coordination and notification when a vulnerability is discovered, so that related issues can be resolved without undue delay. In case the application employs AI models, any externally supplied element for this employment shall be part of this mapping, including third-party models, training data, augmentation data, MCP servers and agentic skills.", "section": "5.6 Technical Product Documentation", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-03", "kind": "Requirement (CR)", "title": "If a new software build or release is created, or if an inaccuracy is found in t…", "text": "If a new software build or release is created, or if an inaccuracy is found in the current SBOM, a revised SBOM shall be issued.", "section": "5.6 Technical Product Documentation", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-04", "kind": "Requirement (CR)", "title": "Technical documentation and user instructions shall be written in language easil…", "text": "Technical documentation and user instructions shall be written in language easily understood by the user and shall include at least: a) documentation of all logical and physical interfaces and transport protocols with their security properties; b) cybersecurity prerequisites for the deployment environment; c) a description of implemented security functions; d) usage instructions covering installation and hardening; e) data deletion and decommissioning procedures; and f) detailed configuration and maintenance instructions. These topics shall at least cover when applicable: configuration baselines, safe defaults, backup and restore, patching and updating, key rotation, log management including synchronization of time, incident response hooks, and interactions with platform security services (iOS Keychain, Android Keystore, biometric APIs, app sandboxing).", "section": "5.6 Technical Product Documentation", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-05", "kind": "Requirement (CR)", "title": "The product's technical documentation shall provide a detailed specification of …", "text": "The product's technical documentation shall provide a detailed specification of all cryptographic mechanisms employed, including the algorithms used, their parameters, key sizes, operational modes, random generation methods, key lifecycle management, and policy of deprecation.", "section": "5.6 Technical Product Documentation", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.6-CR-06", "kind": "Requirement (CR)", "title": "The product's technical documentation shall include an artefact - such as a cove…", "text": "The product's technical documentation shall include an artefact - such as a coverage matrix - that explicitly links each identified risk to the security function or functions that address it.", "section": "5.6 Technical Product Documentation", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-6-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-01", "kind": "Requirement (CR)", "title": "Verification and validation shall take key elements as input: • the product impl…", "text": "Verification and validation shall take key elements as input: • the product implementation including relevant hardware, software, and remote data processing solutions; • the technical documentation, together with user information and instructions; • the cybersecurity requirements; • the product cybersecurity context including relevant information about use from for example customer input and support cases; • the cybersecurity state-of-the art as described in publications, standards, and guidelines; • the evolving threat landscape applicable to the product, including information on vulnerabilities found in similar products including components.", "section": "5.7 Cybersecurity Verification and Validation", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-02", "kind": "Requirement (CR)", "title": "The cybersecurity verification and validation process shall confirm that the pro…", "text": "The cybersecurity verification and validation process shall confirm that the product is sufficiently secure, meaning it satisfies the cybersecurity requirements established in 6.3 and the levels of the identified risks (see 5.5) meet the acceptance criteria (see 5.3).", "section": "5.7 Cybersecurity Verification and Validation", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-03", "kind": "Requirement (CR)", "title": "Threat scenarios and attack profiles shall be defined, documented, and used as t…", "text": "Threat scenarios and attack profiles shall be defined, documented, and used as the basis for validation testing, derived from the applicable attack potential level (e.g., AVA_VAN level), the risk assessment and the product's cybersecurity context . Each validation testing cycle, these shall be reviewed. The validation testing shall include advanced penetration testing calibrated to the goal, and specialized techniques - including where applicable protocol robustness testing, deep fuzzing, verification of hardened configurations, testing of secure boot/attestation, assessment of hardware key protection, and verifying supply chain integrity. A process for conducting these penetration tests shall be defined including: the scope of testing (including the mobile client, associated RDPS, and communication channels), the minimum qualifications required of testers, the testing methodology to be followed, and the criteria for determining when re-testing is required following remediation.", "section": "5.7 Cybersecurity Verification and Validation", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-04", "kind": "Requirement (CR)", "title": "The V&V process shall validate that all cybersecurity risks associated with inte…", "text": "The V&V process shall validate that all cybersecurity risks associated with integrated components - including third-party software - have been identified and adequately addressed in the product's implemented design.", "section": "5.7 Cybersecurity Verification and Validation", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-05", "kind": "Requirement (CR)", "title": "A process shall be established for assessing supply chain integrity as part of c…", "text": "A process shall be established for assessing supply chain integrity as part of cybersecurity V&V, including verification that the application binary and its dependencies are built from verified sources, that the build pipeline is protected against tampering, and that the deployed artefact matches the verified build output.", "section": "5.7 Cybersecurity Verification and Validation", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-06", "kind": "Requirement (CR)", "title": "Where appropriate to the product's design, risk assessment, and cybersecurity co…", "text": "Where appropriate to the product's design, risk assessment, and cybersecurity context, the V&V process shall encompass key elements: artefact analysis including architecture review, error-handling and input validation, external interface and protocol assessment (including deprecation and encryption/integrity checks), additional security testing, documentation review, and risk treatment alignment verification. See guidance for these key elements.", "section": "5.7 Cybersecurity Verification and Validation", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-07", "kind": "Requirement (CR)", "title": "A process shall be established for selecting, configuring, and maintaining stati…", "text": "A process shall be established for selecting, configuring, and maintaining static application security testing (SAST) tools and dynamic application security testing (DAST) tools appropriate for the mobile platform(s) in scope (iOS, Android, or cross-platform), and the rationale for tool selection relative to the product's technology stack and cybersecurity requirements shall be documented.", "section": "5.7 Cybersecurity Verification and Validation", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-08", "kind": "Requirement (CR)", "title": "Products shall undergo code review conducted by suitably qualified reviewers who…", "text": "Products shall undergo code review conducted by suitably qualified reviewers who are independent of the code's authors; the review scope shall encompass at least misuse patterns and all critical findings shall be remediated prior to release.", "section": "5.7 Cybersecurity Verification and Validation", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-09", "kind": "Requirement (CR)", "title": "The V&V process shall document and identify all test methods and selected test t…", "text": "The V&V process shall document and identify all test methods and selected test tools for cybersecurity V&V activities, including the rationale for their selection relative to the product's risk profile and design, and any deviations from the planned test scope together with their justification.", "section": "5.7 Cybersecurity Verification and Validation", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-10", "kind": "Requirement (CR)", "title": "Cybersecurity V&V activities shall recur throughout the product lifecycle in ali…", "text": "Cybersecurity V&V activities shall recur throughout the product lifecycle in alignment with the vulnerability management activities described in 6.9 and shall not be limited to final development stages. For this purpose, a documented schedule for recurring cybersecurity V&V activities shall be established that specifies, at minimum, the trigger conditions for re-testing (e.g., new release, significant code change, newly disclosed vulnerability affecting a component, change in threat landscape) and the V&V activities required for each trigger type.", "section": "5.7 Cybersecurity Verification and Validation", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.7-CR-11", "kind": "Requirement (CR)", "title": "A security test and review plan shall be developed that is grounded in the produ…", "text": "A security test and review plan shall be developed that is grounded in the product's context, its cybersecurity architecture and design, the defined cybersecurity requirements for the product, the results of the risk assessment, and the results of tests and reviews. The plan shall define what tests and reviews are to be performed, what methodologies to apply, how often, and at what intervals, calibrated to the risk profile associated with the product's intended use.", "section": "5.7 Cybersecurity Verification and Validation", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-7-cr-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-01", "kind": "Requirement (CR)", "title": "Software products and software updates that are distributed as software images o…", "text": "Software products and software updates that are distributed as software images or other distribution artefacts shall be protected against manipulation throughout the entire distribution lifecycle, covering both network transit and storage at rest. For this purpose, a documented build and release pipeline shall be maintained, including automated integrity controls and verification at defined points in the pipeline, including compilation, packaging, signing (conformant to 6.8-CR-05), and release or upload to the distribution channel.", "section": "5.8 Secure Production and Distribution", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-02", "kind": "Requirement (CR)", "title": "Where justified by the product's risk assessment and cybersecurity context, the …", "text": "Where justified by the product's risk assessment and cybersecurity context, the production and distribution activities for digital software products shall incorporate access authentication.", "section": "5.8 Secure Production and Distribution", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-03", "kind": "Requirement (CR)", "title": "Where applicable, user-facing information and instructions distributed digitally…", "text": "Where applicable, user-facing information and instructions distributed digitally shall be protected against manipulation or unauthorized disclosure during distribution, including protection of the communication channels through which they are delivered.", "section": "5.8 Secure Production and Distribution", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-04", "kind": "Requirement (CR)", "title": "Where applicable, information and instructions intended for the user shall be de…", "text": "Where applicable, information and instructions intended for the user shall be delivered and presented in a manner that is accessible to the intended user population.", "section": "5.8 Secure Production and Distribution", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-05", "kind": "Requirement (CR)", "title": "A code-signing process shall be established and maintained for mobile applicatio…", "text": "A code-signing process shall be established and maintained for mobile application distribution artefacts that defines: • the lifecycle management of signing credentials, including Android signing keys/keystores and iOS distribution certificates and provisioning profiles, as applicable; • the roles authorized to approve and perform signing operations; and • the conditions under which signing is permitted. Signing keys used for Android (keystore) or iOS (provisioning profiles and certificates) shall be stored in a secrets management system (e.g. HashiCorp Vault, AWS Secrets Manager) and not in the repository.", "section": "5.8 Secure Production and Distribution", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-06", "kind": "Requirement (CR)", "title": "Multi-factor authentication (MFA) and role-based access controls shall be enforc…", "text": "Multi-factor authentication (MFA) and role-based access controls shall be enforced for all accounts with the ability to publish, update, or manage mobile application releases on distribution platforms (e.g. Google Play Console, Apple App Store Connect), and an access review process shall be maintained for these accounts.", "section": "5.8 Secure Production and Distribution", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-07", "kind": "Requirement (CR)", "title": "The product shall be made identifiable by recording, at minimum, the manufacture…", "text": "The product shall be made identifiable by recording, at minimum, the manufacturer's name, the product name, and a version for recognizability and traceability to support for example vulnerability handling, down-stream software bill of materials (SBOM) generation and verification, and vulnerability information sharing and reporting.", "section": "5.8 Secure Production and Distribution", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-08", "kind": "Requirement (CR)", "title": "A communication mechanism shall be provided through which security-related infor…", "text": "A communication mechanism shall be provided through which security-related information - including advisories, release notes, installation guidance, and notifications - is made available for the product.", "section": "5.8 Secure Production and Distribution", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.8-CR-09", "kind": "Requirement (CR)", "title": "Where the product type, connectivity, and operational context make it feasible, …", "text": "Where the product type, connectivity, and operational context make it feasible, a mechanism enabling security updates to be distributed automatically or semi-automatically shall be provided.", "section": "5.8 Secure Production and Distribution", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-8-cr-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-01", "kind": "Requirement (CR)", "title": "Periodic procedures, automated where possible, shall be performed for monitoring…", "text": "Periodic procedures, automated where possible, shall be performed for monitoring of internal and external information that may affect the product's risk assessment as defined in 5.4 to 5.7, covering at least cybersecurity incidents and vulnerabilities, at intervals that are justifiable given the product context. Documentation shall include activities, frequency, sources, and the roles responsible for execution and review.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-02", "kind": "Requirement (CR)", "title": "The risks of verified cybersecurity incidents, changes in the threat landscape, …", "text": "The risks of verified cybersecurity incidents, changes in the threat landscape, and discovered vulnerabilities shall be assessed aligned with the risk assessment methodology established under 5.4 to 5.7.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-03", "kind": "Requirement (CR)", "title": "Upon discovery of a new vulnerability, documentation of that vulnerability shall…", "text": "Upon discovery of a new vulnerability, documentation of that vulnerability shall be produced and communicated to relevant parties where the risk assessment and cybersecurity context make such communication appropriate.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-04", "kind": "Requirement (CR)", "title": "Verified cybersecurity incidents and discovered vulnerabilities shall be treated…", "text": "Verified cybersecurity incidents and discovered vulnerabilities shall be treated in a timely manner, with the urgency and nature of treatment proportionate to the risk assessment outcome and the specific cybersecurity context of the product.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-05", "kind": "Requirement (CR)", "title": "Where cybersecurity incident or vulnerability have residual risk, that risk shal…", "text": "Where cybersecurity incident or vulnerability have residual risk, that risk shall be communicated to stakeholders using the communication processes and channels established under Clause 5.9, where relevant.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.9-CR-06", "kind": "Requirement (CR)", "title": "At a minimum, the following designated internal and external sources shall be dr…", "text": "At a minimum, the following designated internal and external sources shall be drawn upon when monitoring for vulnerabilities: the EU Vulnerability Database, externally reported vulnerabilities, outputs from regular testing, and regular review activities.", "section": "5.9 Product Cybersecurity Monitoring and Issue Management", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-9-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.10-CR-01", "kind": "Requirement (CR)", "title": "Secure decommissioning shall be prepared by identifying cybersecurity aspects of…", "text": "Secure decommissioning shall be prepared by identifying cybersecurity aspects of decommissioning, all confidential assets requiring deletion and their location, establishing appropriate actions for any third-party-operated components, defining the method of user communication and what that communication needs to include, and documenting all manufacturer-side activities required to achieve secure decommissioning.", "section": "5.10 Secure Decommissioning", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-10-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.10-CR-02", "kind": "Requirement (CR)", "title": "Where user-facing decommissioning instructions are required, those instructions …", "text": "Where user-facing decommissioning instructions are required, those instructions shall address, as applicable: removal and export of user data, removal of security-relevant configuration data, disconnection from the operational environment, secure disposal of the product, and advance notice of any automated data deletion including its scope and timing.", "section": "5.10 Secure Decommissioning", "page": 51, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-10-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=51" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-01", "kind": "Requirement (CR)", "title": "Before selecting and integrating any third-party component into a product, due d…", "text": "Before selecting and integrating any third-party component into a product, due diligence shall be carried out on a number of aspects when applicable. This shall include verifying alignment of the component's intended purpose with its planned use in the product, confirming the absence of known vulnerabilities, and determining whether additional cybersecurity testing is needed. For commercial components, the availability of CE marking and an EU Declaration of Conformity shall be checked. For FOSS components, assessment shall be performed of maintenance activity, availability of a vulnerability disclosure process, stewardship by a recognized organization, evidence of cybersecurity-by-design practices, and availability of security updates. In addition, license obligations shall be identified, documented, and managed prior to integration and throughout the component lifecycle.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-02", "kind": "Requirement (CR)", "title": "Both the third-party component itself and the manner in which it is integrated i…", "text": "Both the third-party component itself and the manner in which it is integrated into the product shall be addressed within the risk assessment and risk treatment activities required by Clause 5.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-03", "kind": "Requirement (CR)", "title": "Third-party components and their integration into the product shall be included …", "text": "Third-party components and their integration into the product shall be included in verification and validation specified in clause 6.7.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-04", "kind": "Requirement (CR)", "title": "Ongoing monitoring of third-party components shall be maintained for the duratio…", "text": "Ongoing monitoring of third-party components shall be maintained for the duration of the product's lifecycle, so that vulnerabilities relevant to the product can be identified, in line with the monitoring activities set out in clause 6.9. This is a continuous obligation and does not end once initial integration is complete.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-05", "kind": "Requirement (CR)", "title": "Where a vulnerability is discovered in a commercial third-party component, the v…", "text": "Where a vulnerability is discovered in a commercial third-party component, the vulnerability shall be documented, disclosed to the responsible third-party, and remediated following the applicable vulnerability disclosure and handling procedures. The responsible third-party may be a supplier, service provider, or any party capable of facilitating handling of the vulnerability.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-06", "kind": "Requirement (CR)", "title": "Where the manufacturer discovers a vulnerability in a FOSS component and develop…", "text": "Where the manufacturer discovers a vulnerability in a FOSS component and develops a fix, that fix shall be communicated to the open-source project concerned. Where it is possible to do so, the fix shall also be contributed upstream to the original project, under the terms of the applicable source code license.", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "6.11-CR-07", "kind": "Requirement (CR)", "title": "Third-party component suppliers shall be assessed for maintenance activity (leve…", "text": "Third-party component suppliers shall be assessed for maintenance activity (level of support or having reached end-of-support) on an annual basis. A documented policy shall be established and maintained to define the maximum permissible period between the public disclosure of a vulnerability in a third-party component and the release of a remediated version or the implementation of an accepted compensating control, differentiated by vulnerability severity. If a supplier fails to meet the timeframe or support is below the documented threshold, a risk assessment shall be performed on the potential consequences of this support issue, which may lead to eventually deprecating the corresponding component(s).", "section": "5.11 Third-Party Component Cybersecurity Management", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#6-11-cr-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.1-CR-01", "kind": "Requirement (CR)", "title": "Operational security measures shall be maintained across all activities involvin…", "text": "Operational security measures shall be maintained across all activities involving the receipt and communication of vulnerability information or reports.", "section": "6.1 Operational Security of Vulnerability Handling", "page": 55, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-1-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=55" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.1-CR-02", "kind": "Requirement (CR)", "title": "Access to vulnerability information shall be restricted, when it has not yet bee…", "text": "Access to vulnerability information shall be restricted, when it has not yet been publicly disclosed, where applicable, to only those individuals who require it in order to fulfil their responsibilities within the vulnerability handling process.", "section": "6.1 Operational Security of Vulnerability Handling", "page": 55, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-1-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=55" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.2-CR-01", "kind": "Requirement (CR)", "title": "A vulnerability handling policy shall be established, implemented, and followed.", "text": "A vulnerability handling policy shall be established, implemented, and followed.", "section": "6.2 Facilities for Vulnerability Handling", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-2-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.2-CR-02", "kind": "Requirement (CR)", "title": "The vulnerability handling policy shall describe the organization’s overall dire…", "text": "The vulnerability handling policy shall describe the organization’s overall direction, principles, and responsibilities for handling potential vulnerabilities in products; set out how information about those vulnerabilities will be safeguarded against disclosure before remediation is available; establish a planned timeframe for remediation development; and explain the approach to the regular testing and review activities defined in 6.7.", "section": "6.2 Facilities for Vulnerability Handling", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-2-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.2-CR-03", "kind": "Requirement (CR)", "title": "Continuous monitoring shall be in place whether the vulnerability handling proce…", "text": "Continuous monitoring shall be in place whether the vulnerability handling process is operating effectively.", "section": "6.2 Facilities for Vulnerability Handling", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-2-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.2-CR-04", "kind": "Requirement (CR)", "title": "The vulnerability handling policy shall support all activities defined in the vu…", "text": "The vulnerability handling policy shall support all activities defined in the vulnerability disclosure policy described in 7.3", "section": "6.2 Facilities for Vulnerability Handling", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-2-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.2-CR-05", "kind": "Requirement (CR)", "title": "A documented process shall be established for evaluating, approving, and recordi…", "text": "A documented process shall be established for evaluating, approving, and recording decisions to delay full vulnerability publication under the conditions specified in 7.7-CR-05, including defined criteria for the risk evaluation, designated approval authority, maximum permissible delay duration, and a procedure for communicating the disclosure date to affected users of the mobile application.", "section": "6.2 Facilities for Vulnerability Handling", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-2-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-01", "kind": "Requirement (CR)", "title": "A coordinated vulnerability disclosure policy shall be established, implemented,…", "text": "A coordinated vulnerability disclosure policy shall be established, implemented, followed, and made publicly available in an accessible form", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-02", "kind": "Requirement (CR)", "title": "The CVD policy shall include contact mechanisms accessible through multiple sens…", "text": "The CVD policy shall include contact mechanisms accessible through multiple sensory modalities, ensuring users with diverse impairments are not excluded.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-03", "kind": "Requirement (CR)", "title": "The CVD policy shall explicitly set out what parties can expect with respect to …", "text": "The CVD policy shall explicitly set out what parties can expect with respect to ongoing communication throughout the vulnerability disclosure process.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-04", "kind": "Requirement (CR)", "title": "The CVD policy shall address each of the following areas: the expected contents …", "text": "The CVD policy shall address each of the following areas: the expected contents of a vulnerability report; options for secure communication; the scope of the program; publication arrangements; and recognition of reporters.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-05", "kind": "Requirement (CR)", "title": "A disclosure process shall be established so that details about a vulnerability …", "text": "A disclosure process shall be established so that details about a vulnerability are not made public until the vulnerability has been remediated.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-06", "kind": "Requirement (CR)", "title": "Secure communication mechanisms for vulnerability disclosure shall be made known…", "text": "Secure communication mechanisms for vulnerability disclosure shall be made known to reporters and stakeholders.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-07", "kind": "Requirement (CR)", "title": "The vulnerability reporting process shall include an option that allows reporter…", "text": "The vulnerability reporting process shall include an option that allows reporters to submit information without disclosing their identity.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-08", "kind": "Requirement (CR)", "title": "Security controls applied to communication channels shall not create unreasonabl…", "text": "Security controls applied to communication channels shall not create unreasonable barriers that prevent external parties from contacting the organization.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-09", "kind": "Requirement (CR)", "title": "A public reporting channel shall be made available, using the accessible methods…", "text": "A public reporting channel shall be made available, using the accessible methods specified in 7.3-CR-02, so that vulnerability information or reports can be received.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-10", "kind": "Requirement (CR)", "title": "A system for assigning and maintaining identifiers or tracking numbers to report…", "text": "A system for assigning and maintaining identifiers or tracking numbers to reported vulnerabilities shall be implemented to support ongoing traceability of each report.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-11", "kind": "Requirement (CR)", "title": "Receipt shall be confirmed of a potential vulnerability report to the reporter w…", "text": "Receipt shall be confirmed of a potential vulnerability report to the reporter within a response window that is defined and published as part of the coordinated vulnerability disclosure policy.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.3-CR-12", "kind": "Requirement (CR)", "title": "Vulnerability reports submitted through channels that do not meet the security s…", "text": "Vulnerability reports submitted through channels that do not meet the security standards described in 7.1 should still be accepted rather than rejected on the basis of the submission method alone.", "section": "6.3 Coordinated Vulnerability Disclosure Facilities", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-3-cr-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-01", "kind": "Requirement (CR)", "title": "Where a vulnerability report does not contain enough detail to support assessmen…", "text": "Where a vulnerability report does not contain enough detail to support assessment, the necessary additional information shall be requested from the reporter.", "section": "6.4 Intake in Vulnerability Handling", "page": 62, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=62" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-02", "kind": "Requirement (CR)", "title": "A structured triage of each reported vulnerability shall be performed.", "text": "A structured triage of each reported vulnerability shall be performed.", "section": "6.4 Intake in Vulnerability Handling", "page": 62, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=62" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-03", "kind": "Requirement (CR)", "title": "Risk resulting from the vulnerability shall be evaluated aligned with the method…", "text": "Risk resulting from the vulnerability shall be evaluated aligned with the methodology specified in 5.4 to 5.7.", "section": "6.4 Intake in Vulnerability Handling", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-04", "kind": "Requirement (CR)", "title": "Each vulnerability shall be assigned a handling priority, derived from both the …", "text": "Each vulnerability shall be assigned a handling priority, derived from both the risk evaluation result and the risk profile specific to the product.", "section": "6.4 Intake in Vulnerability Handling", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-05", "kind": "Requirement (CR)", "title": "If the assessed risk level of a vulnerability surpasses the manufacturer's defin…", "text": "If the assessed risk level of a vulnerability surpasses the manufacturer's defined risk threshold, the vulnerability resolution process shall be expedited.", "section": "6.4 Intake in Vulnerability Handling", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.4-CR-06", "kind": "Requirement (CR)", "title": "When a vulnerability has been reported through a coordinated disclosure process,…", "text": "When a vulnerability has been reported through a coordinated disclosure process, the originating reporter shall be notified of the outcome of the intake activity, if possible.", "section": "6.4 Intake in Vulnerability Handling", "page": 64, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-4-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=64" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.5-CR-01", "kind": "Requirement (CR)", "title": "Communication with reporters and all relevant stakeholders shall be initiated an…", "text": "Communication with reporters and all relevant stakeholders shall be initiated and sustained throughout the vulnerability handling process.", "section": "6.5 Communication with Stakeholders in Vulnerability Handling", "page": 64, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-5-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=64" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.5-CR-02", "kind": "Requirement (CR)", "title": "When communicating with users, communication channels and formats shall be emplo…", "text": "When communicating with users, communication channels and formats shall be employed that are accessible to a broad range of users.", "section": "6.5 Communication with Stakeholders in Vulnerability Handling", "page": 65, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-5-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.6-CR-01", "kind": "Requirement (CR)", "title": "A formal remediation decision shall be made and documented for each identified v…", "text": "A formal remediation decision shall be made and documented for each identified vulnerability, determining the course of action to address it.", "section": "6.6 Remediation in Vulnerability Handling", "page": 65, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-6-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.6-CR-02", "kind": "Requirement (CR)", "title": "Following the remediation decision, a concrete action plan shall be established …", "text": "Following the remediation decision, a concrete action plan shall be established that specifies what steps will be taken and sets a defined timeline for their completion.", "section": "6.6 Remediation in Vulnerability Handling", "page": 66, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-6-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.6-CR-03", "kind": "Requirement (CR)", "title": "Once a decision to remediate a vulnerability has been made, the necessary activi…", "text": "Once a decision to remediate a vulnerability has been made, the necessary activities shall be carried out to produce that remediation.", "section": "6.6 Remediation in Vulnerability Handling", "page": 66, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-6-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.6-CR-04", "kind": "Requirement (CR)", "title": "Where it is technically feasible to do so, security updates shall be delivered i…", "text": "Where it is technically feasible to do so, security updates shall be delivered independently of functional updates, rather than bundled together.", "section": "6.6 Remediation in Vulnerability Handling", "page": 66, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-6-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.6-CR-05", "kind": "Requirement (CR)", "title": "Any remediation applied to address a vulnerability shall undergo testing to conf…", "text": "Any remediation applied to address a vulnerability shall undergo testing to confirm that the associated risk has been adequately reduced and that no unacceptable adverse effects on the product or its users have been introduced.", "section": "6.6 Remediation in Vulnerability Handling", "page": 67, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-6-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=67" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-01", "kind": "Requirement (CR)", "title": "Security updates shall be made available at no cost, except where a manufacturer…", "text": "Security updates shall be made available at no cost, except where a manufacturer and a business user have explicitly agreed otherwise for a purpose-built product with digital elements.", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-02", "kind": "Requirement (CR)", "title": "After a security update has been made ready, it shall be released to users witho…", "text": "After a security update has been made ready, it shall be released to users without undue delay.", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-03", "kind": "Requirement (CR)", "title": "Where the delivery of a security update is not entirely automated, clear install…", "text": "Where the delivery of a security update is not entirely automated, clear installation instructions shall be supplied to users.", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-04", "kind": "Requirement (CR)", "title": "After a vulnerability has been resolved, information shall be provisioned in lin…", "text": "After a vulnerability has been resolved, information shall be provisioned in line with the coordinated vulnerability disclosure (CVD) policy established under 7.3; where suitable, such information may be presented in summarized or aggregated form, in a format readable by humans, in a widely recognized machine-readable format, and include, as a minimum, the following elements to allow recipients to assess relevance and take appropriate remediation action: • a description of the vulnerability • a vulnerability identifier • information sufficient to identify the affected product • the potential impact of the vulnerability • the severity of the vulnerability • detailed remediation instructions • the date of release and any subsequent update date", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 69, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=69" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-05", "kind": "Requirement (CR)", "title": "Complete publication of vulnerability information shall be deferred in order to …", "text": "Complete publication of vulnerability information shall be deferred in order to allow adequate time for security update distribution, in case all three of the following conditions are simultaneously satisfied: • the risks associated with full disclosure outweigh its security benefits at that time. • Sufficient information about the resolved vulnerability is made available to users in a manner that does not enable an attacker to exploit it. • Users are notified of the scheduled date on which all vulnerability information will be publicly disclosed.", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 70, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=70" }, { "document": "NL-P-03", "document_title": "Secure Software Development & Vulnerability Management Practices for Wallet and PID Providers", "version": "RC1.0", "id": "7.7-CR-06", "kind": "Requirement (CR)", "title": "Following the release of a remediation, post-release activities shall be execute…", "text": "Following the release of a remediation, post-release activities shall be executed that encompass maintaining the vulnerability case record and tracking the effectiveness of the applied remediation.", "section": "6.7 Release of Security Updates and Information in Vulnerability Handling", "page": 70, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-03#7-7-cr-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-03_-_SecSoftDev__VulnMngt_-_RC1.0_-_for_pub.pdf#page=70" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.1-01", "kind": "Requirement", "title": "The PID Provider shall not issue a PID to a Wallet Unit that already holds an ac…", "text": "The PID Provider shall not issue a PID to a Wallet Unit that already holds an active Logical PID issued by that PID Provider.", "section": "5.1 Pre-Issuance Requirements and Eligibility", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.1-02", "kind": "Requirement", "title": "The PID Provider shall cancel a PID that has been generated but not issued withi…", "text": "The PID Provider shall cancel a PID that has been generated but not issued within the maximum retention period defined in its documented issuance procedures, together with the personal data associated with that PID.", "section": "5.1 Pre-Issuance Requirements and Eligibility", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=15" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.1-03", "kind": "Requirement", "title": "[CONDITIONAL] Where a PID is generated in advance of issuance, the PID Provider …", "text": "[CONDITIONAL] Where a PID is generated in advance of issuance, the PID Provider shall re-verify, immediately before issuance, that no ground preventing issuance has arisen since the PID was generated, including loss of eligibility, a change in the attributes held by the authoritative population register, decease, a fraud signal, or the identity document having been reported lost or stolen.", "section": "5.1 Pre-Issuance Requirements and Eligibility", "page": 16, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.1-04", "kind": "Requirement", "title": "The PID Provider shall not issue a PID to a Wallet Unit of a Wallet Provider whi…", "text": "The PID Provider shall not issue a PID to a Wallet Unit of a Wallet Provider while an active Logical PID issued by that PID Provider in the name of the same person is held in another Wallet Unit of that same Wallet Provider, unless the Technical PIDs of that Logical PID have been revoked in accordance with ISS-5.1-05.", "section": "5.1 Pre-Issuance Requirements and Eligibility", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=16" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.1-05", "kind": "Requirement", "title": "The PID Provider shall revoke the Technical PIDs referred to in ISS-5.1-04 only …", "text": "The PID Provider shall revoke the Technical PIDs referred to in ISS-5.1-04 only after all other conditions for issuing the further PID have been met, including the confirmation required by ISS-5.4-04 where that requirement applies.", "section": "5.1 Pre-Issuance Requirements and Eligibility", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-01", "kind": "Requirement", "title": "The PID Provider shall verify, before issuing a PID, that the Wallet Unit presen…", "text": "The PID Provider shall verify, before issuing a PID, that the Wallet Unit presents a Wallet Instance Attestation that is valid, has not expired, and has not been revoked.", "section": "5.2 Wallet Unit Verification", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-02", "kind": "Requirement", "title": "The PID Provider shall verify, before issuing a PID, that the issuer of the Wall…", "text": "The PID Provider shall verify, before issuing a PID, that the issuer of the Wallet Instance Attestation is present in the applicable trusted list.", "section": "5.2 Wallet Unit Verification", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-03", "kind": "Requirement", "title": "The PID Provider shall not issue a PID unless the Wallet Unit has provided the W…", "text": "The PID Provider shall not issue a PID unless the Wallet Unit has provided the Wallet Trust Evidence required to establish that its cryptographic device satisfies the conditions for Assurance Level High.", "section": "5.2 Wallet Unit Verification", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-04", "kind": "Requirement", "title": "The PID Provider shall not bind a PID to a public key unless it has verified pro…", "text": "The PID Provider shall not bind a PID to a public key unless it has verified proof of possession of the corresponding private key as specified in CRED-REQ-PROC-4.6.2.1-0 of [5].", "section": "5.2 Wallet Unit Verification", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-05", "kind": "Requirement", "title": "The PID Provider shall verify, using the key provenance attestation provided dur…", "text": "The PID Provider shall verify, using the key provenance attestation provided during issuance, that the PID binding key pair is generated and held in a cryptographic device certified at a level appropriate for Assurance Level High.", "section": "5.2 Wallet Unit Verification", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.2-06", "kind": "Requirement", "title": "The PID Provider shall not rely on trusted-list data whose current validity cann…", "text": "The PID Provider shall not rely on trusted-list data whose current validity cannot be confirmed when validating the Wallet Unit.", "section": "5.2 Wallet Unit Verification", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-01", "kind": "Requirement", "title": "The PID Provider shall verify that the unique identifier established for the sub…", "text": "The PID Provider shall verify that the unique identifier established for the subject during identity proofing corresponds to the identity that was authenticated in the same identity-proofing session.", "section": "5.3.1 General Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-02", "kind": "Requirement", "title": "The PID Provider shall not introduce, into the PID or into the data it generates…", "text": "The PID Provider shall not introduce, into the PID or into the data it generates during issuance, any identifier or reused value - other than the PID attributes themselves - that would enable a third party to correlate separate Technical PIDs or issuance events independently of the attributes disclosed under the User's control from PID representations.", "section": "5.3.1 General Requirements", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-03", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall verify, during identity proofing, that the presented identity document chip is genuine and has not been cloned, using the chip's active authentication mechanism or an equivalent anti-cloning mechanism.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 20, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-04", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall accept the identity document only if validation of the issuer signature on the chip data against the country signing public key infrastructure returns a complete, fully-passed result.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 20, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-05", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall establish that the identity document chip is read live during the identity-proofing session.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 20, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-06", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall not accept a previously captured or stored chip readout in place of a live read of the identity document.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 21, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-07", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document and a status service for that identity document is available, the PID Provider shall check the status of the presented identity document before completing identity proofing.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 21, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-08", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall not complete identity proofing where the status check, or any other information available to it, indicates that the identity document is reported lost, stolen, or revoked.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 21, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-09", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall complete identity proofing only after the chip of the identity document has confirmed successful verification of the document PIN.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 21, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-10", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall protect the exchange in which the identity document is electronically authenticated against interception and modification by a party interposed between the identity document and the PID Provider.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 22, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-11", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall record the number of failed PACE or PINverification attempts that occurred, within the same identity-proofing session, before a successful attempt.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 22, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-12", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall flag, for investigation, an identity-proofing session in which the number of failed PACE or PIN-verification attempts before a successful attempt exceeds a defined threshold.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 22, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-13", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall record the identity document's chip identifier together with the national identification number established during each identity-proofing session.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 23, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.3-14", "kind": "Requirement", "title": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digi…", "text": "[CONDITIONAL] If the PID Provider performs the identity proofing based on a digital identity document, the PID Provider shall flag, for investigation, an identity document chip identifier that has been recorded together with more than one distinct national identification number.", "section": "5.3.2 Identity Proofing Using a Digital Identity Document", "page": 23, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-3-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-01", "kind": "Requirement", "title": "The PID Provider shall reject an issuance request that does not contain a valid,…", "text": "The PID Provider shall reject an issuance request that does not contain a valid, unused freshness value bound to the authenticated wallet session.", "section": "5.4 PID Issuance Request and Authorisation", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-02", "kind": "Requirement", "title": "The PID Provider shall not authorise issuance unless every required precondition…", "text": "The PID Provider shall not authorise issuance unless every required precondition has been successfully completed, comprising Wallet Unit trust verification, user identity verification, and the eligibility check.", "section": "5.4 PID Issuance Request and Authorisation", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-03", "kind": "Requirement", "title": "The PID Provider shall log an issuance request rejected for failing a freshness …", "text": "The PID Provider shall log an issuance request rejected for failing a freshness or replay check, together with the reason for rejection.", "section": "5.4 PID Issuance Request and Authorisation", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-04", "kind": "Requirement", "title": "[CONDITIONAL] Where one or more contact methods are registered for a person, the…", "text": "[CONDITIONAL] Where one or more contact methods are registered for a person, the PID Provider shall not authorise the issuance of a PID in that person's name to a Wallet Unit that does not yet hold a Logical PID of that person unless the person has entered in the issuance flow the one-time code that the PID Provider has sent through a registered contact method.", "section": "5.4 PID Issuance Request and Authorisation", "page": 24, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-05", "kind": "Requirement", "title": "The PID Provider shall ensure that every message that carries a one-time code un…", "text": "The PID Provider shall ensure that every message that carries a one-time code under ISS-5.4-04 names the Wallet Provider of the Wallet Unit concerned, states that a new Wallet Unit is being set up in the person's name, warns the person never to share the code with anyone, and contains no link, QR code, or telephone number to call.", "section": "5.4 PID Issuance Request and Authorisation", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.4-06", "kind": "Requirement", "title": "The PID Provider shall invalidate a one-time code issued under ISS-5.4-04 or ISS…", "text": "The PID Provider shall invalidate a one-time code issued under ISS-5.4-04 or ISS-5.7-21 after its first successful use, after the end of a defined validity period, and after a defined number of failed entry attempts.", "section": "5.4 PID Issuance Request and Authorisation", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-01", "kind": "Requirement", "title": "The PID Provider shall not generate a PID unless a complete and current set of t…", "text": "The PID Provider shall not generate a PID unless a complete and current set of the required attributes has been obtained from the authoritative population register.", "section": "5.5 PID Generation and Signing", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-02", "kind": "Requirement", "title": "The PID Provider shall populate each mandatory PID attribute in accordance with …", "text": "The PID Provider shall populate each mandatory PID attribute in accordance with the applicable national value convention, including the defined fall-back values where an attribute value is not available.", "section": "5.5 PID Generation and Signing", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-03", "kind": "Requirement", "title": "The PID Provider shall not fetch, process, or store any optional attribute that …", "text": "The PID Provider shall not fetch, process, or store any optional attribute that has been excluded at national level.", "section": "5.5 PID Generation and Signing", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-04", "kind": "Requirement", "title": "The PID Provider shall bind the PID to the dedicated PID binding public key prov…", "text": "The PID Provider shall bind the PID to the dedicated PID binding public key provided for that PID and to no other key.", "section": "5.5 PID Generation and Signing", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-05", "kind": "Requirement", "title": "The PID Provider shall sign the PID using a signing key whose certificate chains…", "text": "The PID Provider shall sign the PID using a signing key whose certificate chains to a trust anchor published in the applicable trusted list.", "section": "5.5 PID Generation and Signing", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-06", "kind": "Requirement", "title": "The PID Provider shall use the PID signing key only within the authorised issuan…", "text": "The PID Provider shall use the PID signing key only within the authorised issuance process.", "section": "5.5 PID Generation and Signing", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-07", "kind": "Requirement", "title": "The PID Provider shall set the validity period of the PID so that it does not ex…", "text": "The PID Provider shall set the validity period of the PID so that it does not exceed the maximum PID lifetime defined by national policy.", "section": "5.5 PID Generation and Signing", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.5-08", "kind": "Requirement", "title": "The PID Provider shall set the validity period of the PID so that it does not ex…", "text": "The PID Provider shall set the validity period of the PID so that it does not extend beyond the validity of the Wallet Unit to which the PID is issued.", "section": "5.5 PID Generation and Signing", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-5-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.6-01", "kind": "Requirement", "title": "The PID Provider shall not release a PID to the Wallet Unit before authenticatio…", "text": "The PID Provider shall not release a PID to the Wallet Unit before authentication of the Wallet Unit and of the holder has completed successfully.", "section": "5.6 Secure PID Delivery", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-6-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.6-02", "kind": "Requirement", "title": "The PID Provider shall deliver the PID to the Wallet Unit using the issuance pro…", "text": "The PID Provider shall deliver the PID to the Wallet Unit using the issuance protocol specified in [5].", "section": "5.6 Secure PID Delivery", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-6-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.6-03", "kind": "Requirement", "title": "The PID Provider shall record the outcome of each issuance, including any refusa…", "text": "The PID Provider shall record the outcome of each issuance, including any refusal of the issued PID by the Wallet Unit and any case where the Wallet Unit does not respond.", "section": "5.6 Secure PID Delivery", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-6-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.6-04", "kind": "Requirement", "title": "The PID Provider shall classify a PID that has left its systems as issued, regar…", "text": "The PID Provider shall classify a PID that has left its systems as issued, regardless of whether the Wallet Unit confirms its acceptance.", "section": "5.6 Secure PID Delivery", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-6-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.6-05", "kind": "Requirement", "title": "The PID Provider shall revoke a PID that it has classified as issued where the W…", "text": "The PID Provider shall revoke a PID that it has classified as issued where the Wallet Unit reports that the PID was not accepted.", "section": "5.6 Secure PID Delivery", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-6-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-01", "kind": "Requirement", "title": "The PID Provider shall register each issued PID, including its identifier, its v…", "text": "The PID Provider shall register each issued PID, including its identifier, its validity end date, and its status, in the PID Provider's administration and status service.", "section": "5.7 Post-Issuance Status Service Registration", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-02", "kind": "Requirement", "title": "The PID Provider shall record, for each issued PID, the Wallet Unit to which tha…", "text": "The PID Provider shall record, for each issued PID, the Wallet Unit to which that PID was issued.", "section": "5.7 Post-Issuance Status Service Registration", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-03", "kind": "Requirement", "title": "The PID Provider shall record the withdrawal of a PID that has already been deli…", "text": "The PID Provider shall record the withdrawal of a PID that has already been delivered to a Wallet Unit as a revocation with a corresponding entry in the status service.", "section": "5.7 Post-Issuance Status Service Registration", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-04", "kind": "Requirement", "title": "The PID Provider shall record each issuance event in a tamper-evident log with s…", "text": "The PID Provider shall record each issuance event in a tamper-evident log with sufficient detail to support conformity assessment and incident investigation.", "section": "5.7 Post-Issuance Status Service Registration", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-05", "kind": "Requirement", "title": "The PID Provider shall notify the person identified in the PID, through a channe…", "text": "The PID Provider shall notify the person identified in the PID, through a channel independent of the Wallet Unit, when a PID is issued in that person's name.", "section": "5.7 Post-Issuance Status Service Registration", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-05A", "kind": "Requirement", "title": "The PID Provider shall notify the person in whose name a PID was requested, thro…", "text": "The PID Provider shall notify the person in whose name a PID was requested, through a channel independent of the Wallet Unit, when a request to issue a PID in that person's name does not result in issuance because identity proofing or another eligibility check failed, inviting that person to raise an alarm if they did not make the request.", "section": "5.7 Post-Issuance Status Service Registration", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-05a", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-06", "kind": "Requirement", "title": "The PID Provider shall notify the identified person, through a channel independe…", "text": "The PID Provider shall notify the identified person, through a channel independent of the Wallet Unit, when more than one Logical PID issued by that PID Provider is active in that person's name.", "section": "5.7 Post-Issuance Status Service Registration", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=31" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-07", "kind": "Requirement", "title": "The PID Provider shall offer the person the opportunity to register one or more …", "text": "The PID Provider shall offer the person the opportunity to register one or more contact methods that are capable of delivering a notification to the person without delay.", "section": "5.7 Post-Issuance Status Service Registration", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=31" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-08", "kind": "Requirement", "title": "The PID Provider shall ensure that the notification referred to in ISS-5.7-06 st…", "text": "The PID Provider shall ensure that the notification referred to in ISS-5.7-06 states explicitly that the activation of a further Wallet Unit that the person did not perform or authorise or that was done on request of someone else, may result in financial loss or identity theft to that person.", "section": "5.7 Post-Issuance Status Service Registration", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=31" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-09", "kind": "Requirement", "title": "The PID Provider shall include, in the notification referred to in ISS-5.7-06, a…", "text": "The PID Provider shall include, in the notification referred to in ISS-5.7-06, a means for the person to revoke the newly issued PID through a low-threshold procedure.", "section": "5.7 Post-Issuance Status Service Registration", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-10", "kind": "Requirement", "title": "The PID Provider shall require the use of its standard revocation procedure to r…", "text": "The PID Provider shall require the use of its standard revocation procedure to revoke any PID, other than the newly issued PID referred to in ISS-5.7-09, that is active in that person's name.", "section": "5.7 Post-Issuance Status Service Registration", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-11", "kind": "Requirement", "title": "The PID Provider shall record, for each national identification number, the numb…", "text": "The PID Provider shall record, for each national identification number, the number of Wallet Units to which a PID for that national identification number is currently issued and within its Administrative Validity Period, and the timestamps of each issuance and renewal request relating to that national identification number.", "section": "5.7 Post-Issuance Status Service Registration", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-12", "kind": "Requirement", "title": "The PID Provider shall flag, for investigation, a national identification number…", "text": "The PID Provider shall flag, for investigation, a national identification number whose active-Logical-PID count or issuance-or-renewal-request rate exceeds a defined threshold.", "section": "5.7 Post-Issuance Status Service Registration", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-13", "kind": "Requirement", "title": "The PID Provider shall record, where available to it, the network origin or loca…", "text": "The PID Provider shall record, where available to it, the network origin or locality indicator of each issuance or renewal request.", "section": "5.7 Post-Issuance Status Service Registration", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-14", "kind": "Requirement", "title": "The PID Provider shall flag, for investigation, two issuance or renewal requests…", "text": "The PID Provider shall flag, for investigation, two issuance or renewal requests relating to the same national identification number whose recorded network origin or locality indicators are inconsistent with the time elapsed between them.", "section": "5.7 Post-Issuance Status Service Registration", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-15", "kind": "Requirement", "title": "The PID Provider shall subject each case that this specification requires to be …", "text": "The PID Provider shall subject each case that this specification requires to be flagged for investigation to a defined investigation and response procedure.", "section": "5.7 Post-Issuance Status Service Registration", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-15", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-16", "kind": "Requirement", "title": "The PID Provider shall record, for each issued PID, the Wallet Provider that pro…", "text": "The PID Provider shall record, for each issued PID, the Wallet Provider that provided the Wallet Unit to which the PID was issued and the date of issuance.", "section": "5.7 Post-Issuance Status Service Registration", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-16", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-17", "kind": "Requirement", "title": "The PID Provider shall state, in each notification referred to in ISS-5.7-05 and…", "text": "The PID Provider shall state, in each notification referred to in ISS-5.7-05 and ISS-5.7-06, the Wallet Provider and the date of issuance recorded under ISS-5.7-16 for the Wallet Unit concerned.", "section": "5.7 Post-Issuance Status Service Registration", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-17", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-18", "kind": "Requirement", "title": "The PID Provider shall list, in the notification referred to in ISS-5.7-06, ever…", "text": "The PID Provider shall list, in the notification referred to in ISS-5.7-06, every Wallet Unit in which an active Logical PID is held in the person's name, stating for each the Wallet Provider and the date of issuance, and invite the person to revoke any Wallet Unit that is suspicious or no longer in use through the standard revocation procedure referred to in ISS-5.7-10.", "section": "5.7 Post-Issuance Status Service Registration", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-18", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-19", "kind": "Requirement", "title": "The PID Provider shall not disclose to a Wallet Unit, or offer through a Wallet …", "text": "The PID Provider shall not disclose to a Wallet Unit, or offer through a Wallet Unit a means to revoke, any other Wallet Unit in which a PID is held in the name of the same person.", "section": "5.7 Post-Issuance Status Service Registration", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-19", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-20", "kind": "Requirement", "title": "The PID Provider shall, at the first issuance of a PID in a person's name, colle…", "text": "The PID Provider shall, at the first issuance of a PID in a person's name, collect from the person both a mobile telephone number that is able to receive text messages and an e-mail address, and register them as contact methods under ISS-5.7-07 unless the person explicitly declines.", "section": "5.7 Post-Issuance Status Service Registration", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-20", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-21", "kind": "Requirement", "title": "The PID Provider shall register a contact method only after the person has enter…", "text": "The PID Provider shall register a contact method only after the person has entered a one-time code that the PID Provider has sent to that contact method.", "section": "5.7 Post-Issuance Status Service Registration", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-21", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-22", "kind": "Requirement", "title": "The PID Provider shall replace a registered contact method only after the person…", "text": "The PID Provider shall replace a registered contact method only after the person has entered a one-time code that the PID Provider has sent to the contact method that is being replaced, except where ISS-5.7-24 applies.", "section": "5.7 Post-Issuance Status Service Registration", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-22", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-23", "kind": "Requirement", "title": "The PID Provider shall notify every contact method registered before a change, t…", "text": "The PID Provider shall notify every contact method registered before a change, through that contact method, when a registered contact method has been replaced.", "section": "5.7 Post-Issuance Status Service Registration", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-23", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-24", "kind": "Requirement", "title": "The PID Provider shall, where the person has no access to a contact method that …", "text": "The PID Provider shall, where the person has no access to a contact method that is to be replaced, replace it only after identity proofing in accordance with clause 4.3, at the same assurance level as required for initial issuance, has been completed for that person.", "section": "5.7 Post-Issuance Status Service Registration", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-24", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-25", "kind": "Requirement", "title": "The PID Provider shall flag, for investigation, a network origin indicator recor…", "text": "The PID Provider shall flag, for investigation, a network origin indicator recorded under ISS-5.7-13 that is linked to issuance or renewal requests for more than a defined number of distinct national identification numbers within a defined period.", "section": "5.7 Post-Issuance Status Service Registration", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-25", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-26", "kind": "Requirement", "title": "The PID Provider shall limit the retention of the network origin indicators reco…", "text": "The PID Provider shall limit the retention of the network origin indicators recorded under ISS-5.7-13 to a period determined as part of its risk assessment.", "section": "5.7 Post-Issuance Status Service Registration", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-26", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "ISS-5.7-27", "kind": "Requirement", "title": "The PID Provider shall use the network origin indicators recorded under ISS5.7-1…", "text": "The PID Provider shall use the network origin indicators recorded under ISS5.7-13 for no purpose other than the detection of fraud.", "section": "5.7 Post-Issuance Status Service Registration", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#iss-5-7-27", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-01", "kind": "Requirement", "title": "ISS-4.4-01 applies in this context as well.", "text": "ISS-4.4-01 applies in this context as well.", "section": "6.1 Replenishment Triggers and Threshold", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-02", "kind": "Requirement", "title": "The PID Provider shall not replenish Technical PIDs to a Wallet Unit for which t…", "text": "The PID Provider shall not replenish Technical PIDs to a Wallet Unit for which the Administrative Validity Period has ended.", "section": "6.1 Replenishment Triggers and Threshold", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-03", "kind": "Requirement", "title": "The PID Provider shall verify, before issuing replenished Technical PIDs, that t…", "text": "The PID Provider shall verify, before issuing replenished Technical PIDs, that the attribute values of the Logical PID remain current.", "section": "6.1 Replenishment Triggers and Threshold", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-04", "kind": "Requirement", "title": "The PID Provider shall revoke the outstanding Technical PIDs of a Logical PID wh…", "text": "The PID Provider shall revoke the outstanding Technical PIDs of a Logical PID when a revocation condition for that Logical PID is established.", "section": "6.1 Replenishment Triggers and Threshold", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-05", "kind": "Requirement", "title": "The PID Provider shall not continue automatic replenishment to a Wallet Unit for…", "text": "The PID Provider shall not continue automatic replenishment to a Wallet Unit for which it has received an indication that the Wallet Unit or its device is no longer under the legitimate user's control.", "section": "6.1 Replenishment Triggers and Threshold", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-06", "kind": "Requirement", "title": "The PID Provider shall not treat an indication that a Wallet Unit or its device …", "text": "The PID Provider shall not treat an indication that a Wallet Unit or its device is no longer under the legitimate user's control as qualifying under REP-5.1-05 unless the reliability of that indication has been established through a defined verification procedure.", "section": "6.1 Replenishment Triggers and Threshold", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-07", "kind": "Requirement", "title": "The PID Provider shall record the timestamp and the Technical-PID count of each …", "text": "The PID Provider shall record the timestamp and the Technical-PID count of each batch replenishment performed for a Wallet Unit.", "section": "6.1 Replenishment Triggers and Threshold", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-08", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, a maximum batc…", "text": "The PID Provider shall determine, as part of its risk assessment, a maximum batch size and a maximum number of outstanding Technical PIDs per Wallet Unit.", "section": "6.1 Replenishment Triggers and Threshold", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-09", "kind": "Requirement", "title": "The PID Provider shall not exceed the maximum batch size or the maximum number o…", "text": "The PID Provider shall not exceed the maximum batch size or the maximum number of outstanding Technical PIDs per Wallet Unit, determined under REP-5.1-08, when replenishing a Wallet Unit.", "section": "6.1 Replenishment Triggers and Threshold", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-10", "kind": "Requirement", "title": "The PID Provider shall, when it establishes that the attribute values held for a…", "text": "The PID Provider shall, when it establishes that the attribute values held for a person by the Authentic Source have changed from those carried by the outstanding Technical PIDs of the Logical PID, revoke the outstanding Technical PIDs that carry the superseded values.", "section": "6.1 Replenishment Triggers and Threshold", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.1-11", "kind": "Requirement", "title": "The PID Provider shall, when it establishes that the attribute values held for a…", "text": "The PID Provider shall, when it establishes that the attribute values held for a person by the Authentic Source have changed from those carried by the outstanding Technical PIDs of the Logical PID, henceforth issue new Technical PIDs carrying the updated attribute values.", "section": "6.1 Replenishment Triggers and Threshold", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-1-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-01", "kind": "Requirement", "title": "ISS-4.6-02 applies also in the context of replenishment.", "text": "ISS-4.6-02 applies also in the context of replenishment.", "section": "6.2 Batch Request and Issuance Protocol", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-02", "kind": "Requirement", "title": "The PID Provider shall verify the authenticity and integrity of the refresh toke…", "text": "The PID Provider shall verify the authenticity and integrity of the refresh token presented in a replenishment request.", "section": "6.2 Batch Request and Issuance Protocol", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-03", "kind": "Requirement", "title": "The PID Provider shall verify that the refresh token is cryptographically bound …", "text": "The PID Provider shall verify that the refresh token is cryptographically bound to the Wallet Unit that holds the Logical PID to be replenished.", "section": "6.2 Batch Request and Issuance Protocol", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-04", "kind": "Requirement", "title": "The PID Provider shall reject a replenishment request whose refresh token is exp…", "text": "The PID Provider shall reject a replenishment request whose refresh token is expired or has been revoked.", "section": "6.2 Batch Request and Issuance Protocol", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-05", "kind": "Requirement", "title": "ISS-4.2-04 applies also in the context of replenishment.", "text": "ISS-4.2-04 applies also in the context of replenishment.", "section": "6.2 Batch Request and Issuance Protocol", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-06", "kind": "Requirement", "title": "The PID Provider shall verify, using the key provenance attestation provided for…", "text": "The PID Provider shall verify, using the key provenance attestation provided for a batch of replenished Technical PIDs, that the PID binding key pair of every Technical PID in that batch is generated and held in a cryptographic device certified at a level appropriate for Assurance Level High.", "section": "6.2 Batch Request and Issuance Protocol", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-07", "kind": "Requirement", "title": "ISS-4.5-05 applies also in the context of replenishment.", "text": "ISS-4.5-05 applies also in the context of replenishment.", "section": "6.2 Batch Request and Issuance Protocol", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-09", "kind": "Requirement", "title": "The PID Provider shall issue each replenished Technical PID as a credential that…", "text": "The PID Provider shall issue each replenished Technical PID as a credential that is distinct from every other Technical PID of the same Logical PID.", "section": "6.2 Batch Request and Issuance Protocol", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-10", "kind": "Requirement", "title": "The PID Provider shall not release a replenished Technical PID to the Wallet Uni…", "text": "The PID Provider shall not release a replenished Technical PID to the Wallet Unit before verification of the refresh token and validation of the Wallet Unit have completed successfully.", "section": "6.2 Batch Request and Issuance Protocol", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-11", "kind": "Requirement", "title": "The PID Provider shall deliver each replenished Technical PID to the Wallet Unit…", "text": "The PID Provider shall deliver each replenished Technical PID to the Wallet Unit over a channel that provides confidentiality, integrity, and endpoint authentication bound to the authenticated Wallet Unit.", "section": "6.2 Batch Request and Issuance Protocol", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-12", "kind": "Requirement", "title": "ISS-4.7-01 applies also in the context of replenishment.", "text": "ISS-4.7-01 applies also in the context of replenishment.", "section": "6.2 Batch Request and Issuance Protocol", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-13", "kind": "Requirement", "title": "ISS-4.7-04 applies also in the context of replenishment.", "text": "ISS-4.7-04 applies also in the context of replenishment.", "section": "6.2 Batch Request and Issuance Protocol", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.2-14", "kind": "Requirement", "title": "The PID Provider shall protect any exchange with the authentic source performed …", "text": "The PID Provider shall protect any exchange with the authentic source performed during replenishment against interception and modification.", "section": "6.2 Batch Request and Issuance Protocol", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-2-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.4-01", "kind": "Requirement", "title": "The PID Provider shall mark a Technical PID as expired or inactive in its admini…", "text": "The PID Provider shall mark a Technical PID as expired or inactive in its administration once its technical validity period has ended or the Wallet Unit has reported that it was not accepted.", "section": "6.4 Exhausted Credential Cleanup", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.4-02", "kind": "Requirement", "title": "The PID Provider shall retain the audit log entries relating to a Technical PID …", "text": "The PID Provider shall retain the audit log entries relating to a Technical PID for the defined retention period, including after that Technical PID has been marked as inactive in the PID Provider's administration.", "section": "6.4 Exhausted Credential Cleanup", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REP-6.4-03", "kind": "Requirement", "title": "The PID Provider shall determine the retention period referred to in REP-5.4-02 …", "text": "The PID Provider shall determine the retention period referred to in REP-5.4-02 as part of its risk assessment.", "section": "6.4 Exhausted Credential Cleanup", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#rep-6-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-01", "kind": "Requirement", "title": "The PID Provider shall not perform Batch Replenishment of a Logical PID after it…", "text": "The PID Provider shall not perform Batch Replenishment of a Logical PID after its Administrative Validity Period has ended without Renewal.", "section": "7.1 Renewal Triggers and Conditions", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-02", "kind": "Requirement", "title": "REP-5.1-02 applies also in the context of renewal.", "text": "REP-5.1-02 applies also in the context of renewal.", "section": "7.1 Renewal Triggers and Conditions", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-03", "kind": "Requirement", "title": "ISS-4.1-02 applies also in the context of renewal.", "text": "ISS-4.1-02 applies also in the context of renewal.", "section": "7.1 Renewal Triggers and Conditions", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-04", "kind": "Requirement", "title": "ISS-4.1-03 applies also in the context of renewal.", "text": "ISS-4.1-03 applies also in the context of renewal.", "section": "7.1 Renewal Triggers and Conditions", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-05", "kind": "Requirement", "title": "The PID Provider shall record the timestamp of each renewal request together wit…", "text": "The PID Provider shall record the timestamp of each renewal request together with the outcome of the re-identification performed for that request.", "section": "7.1 Renewal Triggers and Conditions", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.1-06", "kind": "Requirement", "title": "The PID Provider shall flag, for investigation, a Logical PID whose renewal requ…", "text": "The PID Provider shall flag, for investigation, a Logical PID whose renewal requests show a frequency or a pattern relative to re-identification outcomes that exceeds a defined threshold.", "section": "7.1 Renewal Triggers and Conditions", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-1-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.2-01", "kind": "Requirement", "title": "The PID Provider shall verify the identity of the person to whom the Logical PID…", "text": "The PID Provider shall verify the identity of the person to whom the Logical PID was issued, applying the identity-proofing requirements of clause 4.3 at the same assurance level required for initial issuance, before renewing that Logical PID.", "section": "7.2 Re-identification Requirements", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.3-01", "kind": "Requirement", "title": "ISS-4.4-01 applies also in the context of renewal.", "text": "ISS-4.4-01 applies also in the context of renewal.", "section": "7.3 Renewal Request and Authorisation", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.3-02", "kind": "Requirement", "title": "The PID Provider shall not authorise a renewal unless the person's identity has …", "text": "The PID Provider shall not authorise a renewal unless the person's identity has been verified, no ground precluding renewal is present, and the request has been shown to originate from the Wallet Unit holding the Logical PID to be renewed.", "section": "7.3 Renewal Request and Authorisation", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.3-03", "kind": "Requirement", "title": "The PID Provider shall verify that a renewal request is bound to the Logical PID…", "text": "The PID Provider shall verify that a renewal request is bound to the Logical PID to be renewed by requiring proof of possession of the private key corresponding to the existing PID binding public key of that Logical PID.", "section": "7.3 Renewal Request and Authorisation", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-01", "kind": "Requirement", "title": "ISS-4.5-01 applies also in the context of renewal.", "text": "ISS-4.5-01 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-02", "kind": "Requirement", "title": "REP-5.2-14 applies also in the context of renewal.", "text": "REP-5.2-14 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-03", "kind": "Requirement", "title": "ISS-4.5-02 applies also in the context of renewal.", "text": "ISS-4.5-02 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-04", "kind": "Requirement", "title": "ISS-4.5-03 applies also in the context of renewal.", "text": "ISS-4.5-03 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-05", "kind": "Requirement", "title": "ISS-4.5-04 applies also in the context of renewal.", "text": "ISS-4.5-04 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-06", "kind": "Requirement", "title": "ISS-4.2-05 applies also in the context of renewal.", "text": "ISS-4.2-05 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-07", "kind": "Requirement", "title": "ISS-4.5-05 applies also in the context of renewal.", "text": "ISS-4.5-05 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-08", "kind": "Requirement", "title": "ISS-4.5-06 applies also in the context of renewal.", "text": "ISS-4.5-06 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-09", "kind": "Requirement", "title": "ISS-4.5-07 applies also in the context of renewal.", "text": "ISS-4.5-07 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.4-10", "kind": "Requirement", "title": "ISS-4.5-08 applies also in the context of renewal.", "text": "ISS-4.5-08 applies also in the context of renewal.", "section": "7.4 PID Generation and Signing", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-4-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-01", "kind": "Requirement", "title": "ISS-4.6-01 applies also in the context of renewal.", "text": "ISS-4.6-01 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-02", "kind": "Requirement", "title": "ISS-4.6-02 applies also in the context of renewal.", "text": "ISS-4.6-02 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-03", "kind": "Requirement", "title": "ISS-4.6-04 applies also in the context of renewal.", "text": "ISS-4.6-04 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-04", "kind": "Requirement", "title": "ISS-4.6-05 applies also in the context of renewal.", "text": "ISS-4.6-05 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-05", "kind": "Requirement", "title": "ISS-4.7-01 applies also in the context of renewal.", "text": "ISS-4.7-01 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-06", "kind": "Requirement", "title": "The PID Provider shall notify the identified person, over a channel that ensures…", "text": "The PID Provider shall notify the identified person, over a channel that ensures the integrity and authenticity of the notification and is independent of the Wallet Unit, when their Logical PID has been renewed.", "section": "7.5 Delivery of the PID", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-04P Part 1", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 1", "version": "RC1.0", "id": "REN-7.5-07", "kind": "Requirement", "title": "ISS-4.7-04 applies also in the context of renewal.", "text": "ISS-4.7-04 applies also in the context of renewal.", "section": "7.5 Delivery of the PID", "page": 50, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-1#ren-7-5-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part1_-_RC1.0_-_for_pub.pdf#page=50" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-01", "kind": "Requirement", "title": "When the PID Provider learns, from a reliable source, that the Wallet Unit to wh…", "text": "When the PID Provider learns, from a reliable source, that the Wallet Unit to which it has issued Technical PIDs, or the device hosting that Wallet Unit, is no longer under the legitimate user's control, the PID Provider shall revoke the outstanding Technical PIDs it has issued to that Wallet Unit.", "section": "5.1 Revocation Triggers and Conditions", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=13" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-02", "kind": "Requirement", "title": "The PID Provider shall revoke the outstanding Technical PIDs it has issued to a …", "text": "The PID Provider shall revoke the outstanding Technical PIDs it has issued to a Wallet Unit when a revocation condition applies, including loss of eligibility of the subject, the decease of the subject, confirmed fraud, or a substantiated request from the legitimate user.", "section": "5.1 Revocation Triggers and Conditions", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=13" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-03", "kind": "Requirement", "title": "The PID Provider shall not treat an indication that a revocation condition appli…", "text": "The PID Provider shall not treat an indication that a revocation condition applies as a ground for revocation unless the reliability of that indication has been established through a defined verification procedure.", "section": "5.1 Revocation Triggers and Conditions", "page": 13, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=13" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-04", "kind": "Requirement", "title": "When a revocation condition for a Logical PID is established, the PID Provider s…", "text": "When a revocation condition for a Logical PID is established, the PID Provider shall revoke every outstanding Technical PID of that Logical PID that it has issued to the Wallet Unit, including Technical PIDs issued through batch replenishment.", "section": "5.1 Revocation Triggers and Conditions", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=14" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-05", "kind": "Requirement", "title": "The PID Provider shall revoke every outstanding Technical PID it has issued to a…", "text": "The PID Provider shall revoke every outstanding Technical PID it has issued to a Wallet Unit when that Wallet Unit is revoked.", "section": "5.1 Revocation Triggers and Conditions", "page": 14, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=14" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.1-06", "kind": "Requirement", "title": "The PID Provider shall end the Administrative Validity Period of a Logical PID i…", "text": "The PID Provider shall end the Administrative Validity Period of a Logical PID issued to a Wallet Unit when it revokes the Technical PIDs of that Logical PID.", "section": "5.1 Revocation Triggers and Conditions", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-1-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=15" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.1-07", "kind": "Requirement", "title": "[CONDITIONAL] Where the authentic source provides event-driven notification of t…", "text": "[CONDITIONAL] Where the authentic source provides event-driven notification of the decease of a person or of a loss of eligibility of a person, the PID Provider shall subscribe to that notification for each person in whose name a Logical PID is active and treat a received notification as an indication that a revocation condition applies under REV-4.103.", "section": "5.1 Revocation Triggers and Conditions", "page": 15, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-1-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=15" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.1-08", "kind": "Requirement", "title": "The PID Provider shall, when the decease of a person has been established as a r…", "text": "The PID Provider shall, when the decease of a person has been established as a revocation condition, notify every Wallet Provider that provided a Wallet Unit to which a PID of that person was issued, so that each of them is able to revoke the Wallet Unit concerned.", "section": "5.1 Revocation Triggers and Conditions", "page": 15, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-1-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=15" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-01", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, the maximum ti…", "text": "The PID Provider shall determine, as part of its risk assessment, the maximum time within which the Technical PIDs are revoked after a revocation condition has been established.", "section": "5.2 Revocation Procedures", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=16" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-02", "kind": "Requirement", "title": "The maximum time determined under REV-4.2-01 shall not exceed the maximum time f…", "text": "The maximum time determined under REV-4.2-01 shall not exceed the maximum time for revoking an electronic attestation of attributes set out in ETSI TS 119 471 [7], clause 4.2.5.1.", "section": "5.2 Revocation Procedures", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=16" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-03", "kind": "Requirement", "title": "The PID Provider shall complete the revocation of the Technical PIDs within the …", "text": "The PID Provider shall complete the revocation of the Technical PIDs within the maximum time it has determined under REV-4.2-01.", "section": "5.2 Revocation Procedures", "page": 16, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=16" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-04", "kind": "Requirement", "title": "The PID Provider shall record, for each revocation, the identity of the revoked …", "text": "The PID Provider shall record, for each revocation, the identity of the revoked Technical PIDs, the revocation condition, the outcome of its verification, and the time of revocation.", "section": "5.2 Revocation Procedures", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-05", "kind": "Requirement", "title": "The PID Provider shall not reinstate a Technical PID once it has been revoked.", "text": "The PID Provider shall not reinstate a Technical PID once it has been revoked.", "section": "5.2 Revocation Procedures", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-06", "kind": "Requirement", "title": "The PID Provider shall periodically verify the validity status of each Wallet Un…", "text": "The PID Provider shall periodically verify the validity status of each Wallet Unit to which it has issued Technical PIDs that have not reached a terminal state.", "section": "5.2 Revocation Procedures", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=17" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.2-07", "kind": "Requirement", "title": "The PID Provider shall determine the interval of the verification under REV4.2-0…", "text": "The PID Provider shall determine the interval of the verification under REV4.2-06 as part of its risk assessment.", "section": "5.2 Revocation Procedures", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-2-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-08", "kind": "Requirement", "title": "The PID Provider shall provide the person, after authentication at assurance lev…", "text": "The PID Provider shall provide the person, after authentication at assurance level substantial or high as defined in [2] and through a means that is not a Wallet Unit, with an overview of every Wallet Unit to which a PID in that person's name has been issued, stating for each the Wallet Provider, the date of issuance and the status.", "section": "5.2 Revocation Procedures", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-09", "kind": "Requirement", "title": "The PID Provider shall, on a request made by the person in the overview referred…", "text": "The PID Provider shall, on a request made by the person in the overview referred to in REV-5.2-08, revoke the Technical PIDs issued to the Wallet Unit concerned in accordance with REV-4.1-05.", "section": "5.2 Revocation Procedures", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=18" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-10", "kind": "Requirement", "title": "The PID Provider shall forward a request under REV-5.2-09 to the Wallet Provider…", "text": "The PID Provider shall forward a request under REV-5.2-09 to the Wallet Provider that provided the Wallet Unit concerned, so that the Wallet Provider revokes the Wallet Unit.", "section": "5.2 Revocation Procedures", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-11", "kind": "Requirement", "title": "The PID Provider shall provide a reporting point through which a person reports …", "text": "The PID Provider shall provide a reporting point through which a person reports the loss, theft or compromise of a Wallet Unit without authenticating through any Wallet Unit.", "section": "5.2 Revocation Procedures", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-12", "kind": "Requirement", "title": "The PID Provider shall forward a report received under REV-5.2-11 to every Walle…", "text": "The PID Provider shall forward a report received under REV-5.2-11 to every Wallet Provider that provided a Wallet Unit to which a PID of the reporting person was issued.", "section": "5.2 Revocation Procedures", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-13", "kind": "Requirement", "title": "The PID Provider shall verify, before acting on a report under REV-5.2-11 or on …", "text": "The PID Provider shall verify, before acting on a report under REV-5.2-11 or on a request under REV-5.2-09, that the person making it is the person in whose name the PIDs were issued, by a means that does not depend on a Wallet Unit.", "section": "5.2 Revocation Procedures", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=19" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-14", "kind": "Requirement", "title": "The PID Provider shall ensure that a revocation initiated by an employee of the …", "text": "The PID Provider shall ensure that a revocation initiated by an employee of the PID Provider takes effect only after a second employee has approved it, and that both approvals are recorded in a tamper-evident log.", "section": "5.2 Revocation Procedures", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-15", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, the maximum ti…", "text": "The PID Provider shall determine, as part of its risk assessment, the maximum time within which the second approval under REV-5.2-14 is given.", "section": "5.2 Revocation Procedures", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-15", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.2-16", "kind": "Requirement", "title": "The PID Provider shall ensure that the second approval under REV-5.2-14 is given…", "text": "The PID Provider shall ensure that the second approval under REV-5.2-14 is given within the maximum time determined under REV-5.2-15.", "section": "5.2 Revocation Procedures", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-2-16", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-01", "kind": "Requirement", "title": "The PID Provider shall include in each Technical PID the reference to the status…", "text": "The PID Provider shall include in each Technical PID the reference to the status mechanism through which the revocation status of that Technical PID is made available, as required by ETSI TS 119 471 [7] and the attestation format profile ETSI TS 119 472-1 [8].", "section": "5.3 Status Service Update", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=20" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-02", "kind": "Requirement", "title": "The PID Provider shall include in each Technical PID the identifier or index tha…", "text": "The PID Provider shall include in each Technical PID the identifier or index that distinguishes that Technical PID within its status mechanism, as required by ETSI TS 119 471 [7].", "section": "5.3 Status Service Update", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-03", "kind": "Requirement", "title": "The PID Provider shall set the revocation status of a Technical PID in its statu…", "text": "The PID Provider shall set the revocation status of a Technical PID in its status mechanism to revoked when that Technical PID is revoked.", "section": "5.3 Status Service Update", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-04", "kind": "Requirement", "title": "The PID Provider need not maintain revocation-status information for a Technical…", "text": "The PID Provider need not maintain revocation-status information for a Technical PID whose validity period is less than 24 hours, provided that this is stated in its PID provision policy.", "section": "5.3 Status Service Update", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=21" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-05", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, the maximum de…", "text": "The PID Provider shall determine, as part of its risk assessment, the maximum delay between the revocation of a Technical PID and the availability of its revoked status in the status mechanism.", "section": "5.3 Status Service Update", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-06", "kind": "Requirement", "title": "The maximum delay determined under REV-4.3-05 shall not cause the revoked status…", "text": "The maximum delay determined under REV-4.3-05 shall not cause the revoked status of a Technical PID to become available later than the maximum time for revoking and publishing the status of an electronic attestation of attributes set out in ETSI TS 119 471 [7], clause 4.2.5.1.", "section": "5.3 Status Service Update", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.3-07", "kind": "Requirement", "title": "The PID Provider shall make the revoked status of a Technical PID available in t…", "text": "The PID Provider shall make the revoked status of a Technical PID available in the status mechanism within the maximum delay it has determined under REV-4.3-05.", "section": "5.3 Status Service Update", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-3-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=22" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.4-01", "kind": "Requirement", "title": "The PID Provider shall notify the Wallet User when the Technical PIDs issued to …", "text": "The PID Provider shall notify the Wallet User when the Technical PIDs issued to that Wallet User's Wallet Unit are revoked.", "section": "5.4 Wallet User Notification", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=23" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.4-02", "kind": "Requirement", "title": "The PID Provider shall deliver the revocation notification to the Wallet User th…", "text": "The PID Provider shall deliver the revocation notification to the Wallet User through the government electronic mailbox (MijnOverheid Berichtenbox).", "section": "5.4 Wallet User Notification", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=23" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.4-03", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, the maximum ti…", "text": "The PID Provider shall determine, as part of its risk assessment, the maximum time within which the Wallet User is notified after the Technical PIDs issued to that user's Wallet Unit are revoked.", "section": "5.4 Wallet User Notification", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=23" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-4.4-04", "kind": "Requirement", "title": "The revocation notification shall identify the revoked PID and state that it can…", "text": "The revocation notification shall identify the revoked PID and state that it can no longer be used.", "section": "5.4 Wallet User Notification", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-4-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.4-05", "kind": "Requirement", "title": "The PID Provider shall send the revocation notification referred to in REV-4.401…", "text": "The PID Provider shall send the revocation notification referred to in REV-4.401, in addition to the government electronic mailbox, through a contact method registered by the person with the PID Provider.", "section": "5.4 Wallet User Notification", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "REV-5.4-06", "kind": "Requirement", "title": "The PID Provider shall state in the revocation notification the Wallet Provider …", "text": "The PID Provider shall state in the revocation notification the Wallet Provider and the date of issuance of the Wallet Unit to which the revoked PIDs were issued.", "section": "5.4 Wallet User Notification", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#rev-5-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=24" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.1-01", "kind": "Requirement", "title": "The PID Provider shall detect, in its administration, when the validity period o…", "text": "The PID Provider shall detect, in its administration, when the validity period of a Technical PID has ended.", "section": "6.1 Expiry Detection and Notification", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=25" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.1-02", "kind": "Requirement", "title": "The PID Provider shall cease to treat a Technical PID as valid in its administra…", "text": "The PID Provider shall cease to treat a Technical PID as valid in its administration once the validity period of that Technical PID has ended.", "section": "6.1 Expiry Detection and Notification", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=25" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.1-03", "kind": "Requirement", "title": "The PID Provider shall notify the Wallet User when the Administrative Validity P…", "text": "The PID Provider shall notify the Wallet User when the Administrative Validity Period of a Logical PID issued to that Wallet User's Wallet Unit is approaching its end.", "section": "6.1 Expiry Detection and Notification", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=25" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.1-04", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, how far in adv…", "text": "The PID Provider shall determine, as part of its risk assessment, how far in advance of the end of the Administrative Validity Period the notification under EXP-5.1-03 is sent.", "section": "6.1 Expiry Detection and Notification", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.2-01", "kind": "Requirement", "title": "The PID Provider shall not revoke a Technical PID solely because its validity pe…", "text": "The PID Provider shall not revoke a Technical PID solely because its validity period has ended.", "section": "6.2 Post-Expiry Behaviour", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.2-02", "kind": "Requirement", "title": "The PID Provider need not maintain revocation-status information for a Technical…", "text": "The PID Provider need not maintain revocation-status information for a Technical PID after its validity period has ended.", "section": "6.2 Post-Expiry Behaviour", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=26" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.3-01", "kind": "Requirement", "title": "The PID Provider shall retain, after the expiry of a Technical PID, only the per…", "text": "The PID Provider shall retain, after the expiry of a Technical PID, only the personal data and records that remain necessary for status publication, audit, or legal obligations.", "section": "6.3 Pre-Deletion Security Measures", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.4-01", "kind": "Requirement", "title": "The PID Provider shall remove expired Technical PIDs from its administration in …", "text": "The PID Provider shall remove expired Technical PIDs from its administration in accordance with a defined cleanup procedure.", "section": "6.4 Expired PID Cleanup and Deletion", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.4-02", "kind": "Requirement", "title": "The PID Provider shall determine, as part of its risk assessment, the retention …", "text": "The PID Provider shall determine, as part of its risk assessment, the retention period after which expired Technical PID records are removed.", "section": "6.4 Expired PID Cleanup and Deletion", "page": 27, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=27" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "EXP-5.4-03", "kind": "Requirement", "title": "The PID Provider shall not remove records that are required for audit or statusp…", "text": "The PID Provider shall not remove records that are required for audit or statuspublication purposes before the end of their retention period.", "section": "6.4 Expired PID Cleanup and Deletion", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#exp-5-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=28" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "DEL-6.1-01", "kind": "Requirement", "title": "The Wallet Unit shall allow the Wallet User to delete a PID it holds, on the use…", "text": "The Wallet Unit shall allow the Wallet User to delete a PID it holds, on the user's own initiative.", "section": "7.1 User-Initiated Deletion", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#del-6-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "DEL-6.1-02", "kind": "Requirement", "title": "When a PID is deleted, the Wallet Unit shall erase the PID's attribute data and …", "text": "When a PID is deleted, the Wallet Unit shall erase the PID's attribute data and associated key material so that it cannot be recovered from the Wallet Unit.", "section": "7.1 User-Initiated Deletion", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#del-6-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "DEL-6.1-03", "kind": "Requirement", "title": "The Wallet Unit shall obtain confirmation from the Wallet User before deleting a…", "text": "The Wallet Unit shall obtain confirmation from the Wallet User before deleting a PID.", "section": "7.1 User-Initiated Deletion", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#del-6-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=29" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "DEL-6.2-01", "kind": "Requirement", "title": "The Wallet Unit shall not notify the PID Provider of a user-initiated deletion o…", "text": "The Wallet Unit shall not notify the PID Provider of a user-initiated deletion of a PID.", "section": "7.2 PID Provider Notification", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#del-6-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=30" }, { "document": "NL-P-04P Part 2", "document_title": "PID Issuance & Lifecycle Management Requirements, Part 2", "version": "RC1.0", "id": "DEL-6.3-01", "kind": "Requirement", "title": "The Wallet Unit shall inform the Wallet User, when they delete a PID, that delet…", "text": "The Wallet Unit shall inform the Wallet User, when they delete a PID, that deletion does not revoke the PID and that revocation must be requested separately if required.", "section": "7.3 PID Revocation", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04p-part-2#del-6-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04P_PID_Issuance__LifecycleMngt_-reqs-part2_-_RC1.0_for_pub.pdf#page=30" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-01", "kind": "Requirement", "title": "The Wallet Provider shall sign the Wallet Instance software package using a priv…", "text": "The Wallet Provider shall sign the Wallet Instance software package using a private key associated with the Wallet Provider’s registered identity in the target distribution platform’s certificate infrastructure, such that the distribution platform or device can verify the signature before permitting installation.", "section": "5.1 Secure Software Distribution and Delivery", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-02", "kind": "Requirement", "title": "The Wallet Provider shall distribute the Wallet Instance software exclusively th…", "text": "The Wallet Provider shall distribute the Wallet Instance software exclusively through distribution channels that enforce signature verification of the software package as a condition of delivery to the Wallet User’s device.", "section": "5.1 Secure Software Distribution and Delivery", "page": 17, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=17" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance verifies the integrity…", "text": "The Wallet Provider shall ensure that the Wallet Instance verifies the integrity of its own software prior to initializing any Wallet Unit functionality, by performing a cryptographic check of the installed package against a reference value established at install time and protected within the device's hardware-backed key store or WSCD.", "section": "5.1 Secure Software Distribution and Delivery", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-04", "kind": "Requirement", "title": "The Wallet Provider shall hold the private signing key used for the Wallet Insta…", "text": "The Wallet Provider shall hold the private signing key used for the Wallet Instance software package in a hardware security module (HSM) that requires multi-person authorisation for each signing operation and that is certified to FIPS 140-3 Level 3, Common Criteria EAL4+, or an equivalent recognised level.", "section": "5.1 Secure Software Distribution and Delivery", "page": 18, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=18" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-05", "kind": "Requirement", "title": "The Wallet Provider shall record, in a tamper-evident log retained for at least …", "text": "The Wallet Provider shall record, in a tamper-evident log retained for at least 12 months, every administrative action that modifies the Wallet Instance software package, the code-signing infrastructure, or the configuration of the distribution channel, together with the identity of the operators and the time of the action.", "section": "5.1 Secure Software Distribution and Delivery", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.1-06", "kind": "Requirement", "title": "The Wallet Provider shall verify, before incorporating any third-party software …", "text": "The Wallet Provider shall verify, before incorporating any third-party software component into a Wallet Instance software build, that the component's distribution origin is authenticated through a cryptographic signature or hash that traces to a publisher identity declared in the Wallet Provider's approved-supplier list.", "section": "5.1 Secure Software Distribution and Delivery", "page": 19, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-1-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=19" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance, at installation and a…", "text": "The Wallet Provider shall ensure that the Wallet Instance, at installation and at each subsequent launch, verifies that the operating system version and security patch level of the host device meets the minimum requirements documented by the Wallet Provider, and refuses to activate Wallet Unit functionality on devices that do not meet those requirements.", "section": "5.2 Device Security Pre-Checks", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance detects the presence o…", "text": "The Wallet Provider shall ensure that the Wallet Instance detects the presence of root access or jailbreak conditions on the host device and, where such conditions are detected, refuses to finalize Wallet Instance Installation.", "section": "5.2 Device Security Pre-Checks", "page": 20, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=20" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-03", "kind": "Requirement", "title": "The Wallet Provider shall implement runtime anti-tampering controls in the Walle…", "text": "The Wallet Provider shall implement runtime anti-tampering controls in the Wallet Instance that detect attempts to instrument, hook, or modify the application's execution at runtime.", "section": "5.2 Device Security Pre-Checks", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit refuses to finalize Wallet…", "text": "The Wallet Provider shall ensure that the Wallet Unit refuses to finalize Wallet Instance installation when the runtime anti-tampering controls detect an attempt to instrument, hook, or modify the application's execution.", "section": "5.2 Device Security Pre-Checks", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-05", "kind": "Requirement", "title": "The Wallet Provider shall document and enforce minimum security requirements for…", "text": "The Wallet Provider shall document and enforce minimum security requirements for devices on which the Wallet Instance may be installed and operated, including at minimum: a screen lock mechanism using a PIN, password, or biometric factor; the availability of a hardware-backed key store; and a supported operating system version receiving security updates from the platform vendor.", "section": "5.2 Device Security Pre-Checks", "page": 21, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=21" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-06", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Secure Cryptographic Device use…", "text": "The Wallet Provider shall ensure that the Wallet Secure Cryptographic Device used by the Wallet Unit is operated solely under the Wallet Provider’s control, holds a valid security certification appropriate for the applicable Assurance Level prior to its first use by a Wallet Unit, and remains under the Wallet Provider’s exclusive operational control throughout the entire lifetime of the Wallet Unit.", "section": "5.2 Device Security Pre-Checks", "page": 22, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=22" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.2-07", "kind": "Requirement", "title": "The Wallet Provider shall implement mechanisms in the Wallet Instance to detect …", "text": "The Wallet Provider shall implement mechanisms in the Wallet Instance to detect the presence of known malicious applications or anomalous runtime conditions on the host device that could expose Wallet Unit key material or credentials to unauthorised access, and shall, upon detection, prevent Wallet Unit operations involving access to key material until the threat is resolved.", "section": "5.2 Device Security Pre-Checks", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-2-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.3-01", "kind": "Requirement", "title": "The Wallet Provider shall distribute the Wallet Instance exclusively through the…", "text": "The Wallet Provider shall distribute the Wallet Instance exclusively through the official app store of the operating system of the Wallet User's device; or, where distribution through alternative channels is necessary, shall implement a mechanism enabling even a Wallet User with low digital savviness to verify the authenticity of the Wallet Instance prior to installation and shall provide the Wallet User with clear instructions for completing that verification.", "section": "5.3 Installation Process Security", "page": 23, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=23" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.3-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance requests only those de…", "text": "The Wallet Provider shall ensure that the Wallet Instance requests only those device permissions strictly necessary for the functioning of declared Wallet Unit features, and shall present the Wallet User with a plain-language explanation of the purpose of each permission at the time it is requested.", "section": "5.3 Installation Process Security", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.3-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance, at the time of instal…", "text": "The Wallet Provider shall ensure that the Wallet Instance, at the time of installation, operates within an operating system-enforced isolation boundary that prevents co-located applications from accessing, reading, or modifying data stored by the Wallet Instance, including PID credentials, Electronic Attestations of Attributes, cryptographic key material, and any personal data processed by the Wallet Instance.", "section": "5.3 Installation Process Security", "page": 24, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=24" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.3-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance is shipped with a secu…", "text": "The Wallet Provider shall ensure that the Wallet Instance is shipped with a secure default configuration such that no Wallet Unit functionality is accessible prior to completion of the initial activation process and no personal data is transmitted by the Wallet Instance before the Wallet User has accepted all required privacy disclosures.", "section": "5.3 Installation Process Security", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.4-01", "kind": "Requirement", "title": "The Wallet Provider shall present the Wallet User, prior to completing installat…", "text": "The Wallet Provider shall present the Wallet User, prior to completing installation of the Wallet Instance, with clear and comprehensible information about the nature of the wallet, the categories of personal data processed, the applicable terms and conditions, and the security responsibilities of the Wallet User.", "section": "5.4 Wallet User Information and Consent", "page": 25, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=25" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.4-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet User is presented with the Wall…", "text": "The Wallet Provider shall ensure that the Wallet User is presented with the Wallet Provider's terms of service prior to completing installation of the Wallet Instance, that acceptance constitutes an explicit Wallet User action, and that the Wallet Instance is not operable until that acceptance has been recorded.", "section": "5.4 Wallet User Information and Consent", "page": 26, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "INST-5.4-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, prior to completing installation of the W…", "text": "The Wallet Provider shall ensure that, prior to completing installation of the Wallet Instance, the Wallet User is provided with a clear and complete description of all categories of personal data processed by the Wallet Unit, the purposes for which each category is processed, and the legal basis under Article 6 of the GDPR applicable to each processing activity.", "section": "5.4 Wallet User Information and Consent", "page": 26, "obligation": "mandatory", "legal_refs": [ "GDPR" ], "url": "/edi-stelsel-certification/requirements/nl-p-04w#inst-5-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=26" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.1-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all communication between the Wallet Insta…", "text": "The Wallet Provider shall ensure that all communication between the Wallet Instance (WI) and the Wallet Secure Cryptographic Application (WSCA) during Wallet Unit activation is conducted over a channel that is mutually authenticated and integrity-protected, so that activation data cannot be intercepted, replayed, or tampered with by a third party.", "section": "6.1 WSCD/WSCA Initialisation", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.1-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all private keys attested in a Key Attesta…", "text": "The Wallet Provider shall ensure that all private keys attested in a Key Attestation and all private keys of device-bound PIDs and attestations are generated within the Wallet Secure Cryptographic Device (WSCD), and that those private keys are never extracted from the WSCD in the clear at any point during or after activation.", "section": "6.1 WSCD/WSCA Initialisation", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.1-03", "kind": "Requirement", "title": "The Wallet Provider shall verify, before signing and issuing a Key Attestation, …", "text": "The Wallet Provider shall verify, before signing and issuing a Key Attestation, that the public keys to be included in that Key Attestation correspond to private keys that were generated by and are stored in the WSCA/WSCD described in that attestation, and that those private keys remain under the exclusive control of the Wallet User.", "section": "6.1 WSCD/WSCA Initialisation", "page": 28, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=28" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-01", "kind": "Requirement", "title": "The Wallet Provider shall, before issuing a Wallet Instance Attestation, verify …", "text": "The Wallet Provider shall, before issuing a Wallet Instance Attestation, verify that the requesting Wallet Instance is a genuine instance of its Wallet Solution and that the attestation request has not been replayed, forged, or submitted by an unauthorised party.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance, during Wallet Unit ac…", "text": "The Wallet Provider shall ensure that the Wallet Instance, during Wallet Unit activation, authenticates the Wallet Provider backend before transmitting any device or WSCD information, so that the Wallet Instance can verify it is communicating with the genuine Wallet Provider and not an impostor.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 29, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=29" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each Key Attestation is cryptographically …", "text": "The Wallet Provider shall ensure that each Key Attestation is cryptographically bound to the keystore of the Wallet Unit by including one or more public keys in the Key Attestation whose corresponding private keys are generated by and stored exclusively in the WSCA/WSCD of the Wallet Unit, so that each Key Attestation is tied to a specific, unique WSCD instance.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each Key Attestation contains, at minimum:…", "text": "The Wallet Provider shall ensure that each Key Attestation contains, at minimum: (a) information describing the storage type and the security certification of the WSCA/WSCD or keystore in which the attested private keys are stored; and (b) one or more public keys corresponding to private keys generated by and stored in that WSCA/WSCD or keystore.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each Wallet Instance Attestation contains,…", "text": "The Wallet Provider shall ensure that each Wallet Instance Attestation contains, at minimum: (a) information enabling PID Providers and Attestation Providers to check the revocation status of that Wallet Instance Attestation; and (b) a Wallet Unit identifier that does not enable tracking of the Wallet User across transactions.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 30, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=30" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-06", "kind": "Requirement", "title": "The Wallet Provider shall sign each Wallet Instance Attestation and each Key Att…", "text": "The Wallet Provider shall sign each Wallet Instance Attestation and each Key Attestation using only cryptographic algorithms included in the ECCG Agreed Cryptographic Mechanisms [6].", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=31" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-07", "kind": "Requirement", "title": "The Wallet Provider shall bind each Key Attestation to the specific issuance con…", "text": "The Wallet Provider shall bind each Key Attestation to the specific issuance context in which it is presented, either by incorporating a nonce provided by the PID Provider or Attestation Provider into the Key Attestation, or by presenting the Key Attestation together with a Proof-of-Possession signed over that nonce using a private key attested in that Key Attestation.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 31, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=31" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-08", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all unique elements of each Wallet Instanc…", "text": "The Wallet Provider shall ensure that all unique elements of each Wallet Instance Attestation and each Key Attestation — including the attestation identifier used for revocation status checking, the attested public keys, and the Wallet Provider's signature — have a negligible probability of having the same value across all such attestations issued by that Wallet Provider.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-09", "kind": "Requirement", "title": "The Wallet Provider shall manage the validity periods of Wallet Instance Attesta…", "text": "The Wallet Provider shall manage the validity periods of Wallet Instance Attestations and Key Attestations such that a non-revoked Wallet Unit can at all times present a Wallet Instance Attestation and a Key Attestation each with a remaining validity period of at least 31 days, and shall set validity periods taking into account the risk that such an attestation could become a vector for tracking the Wallet User across multiple issuance transactions.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-10", "kind": "Requirement", "title": "The Wallet Provider shall re-issue Wallet Instance Attestations and Key Attestat…", "text": "The Wallet Provider shall re-issue Wallet Instance Attestations and Key Attestations to a non-revoked Wallet Unit as needed throughout the lifetime of the Wallet Unit, ensuring continuity of the Wallet Unit's ability to receive PIDs and device-bound attestations without requiring re-activation.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 32, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-10", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=32" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-11", "kind": "Requirement", "title": "The Wallet Provider shall ensure that device binding for all PIDs and deviceboun…", "text": "The Wallet Provider shall ensure that device binding for all PIDs and devicebound attestations is implemented by having the WSCA/WSCD or keystore generate a dedicated public-private key pair for each PID or device-bound attestation, and by ensuring that the corresponding private key is generated within and remains protected by the WSCA/WSCD or keystore throughout the lifetime of the attestation.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-11", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-12", "kind": "Requirement", "title": "The Wallet Provider shall ensure that every public key to which a PID or a devic…", "text": "The Wallet Provider shall ensure that every public key to which a PID or a device-bound attestation is bound at issuance is a public key attested in a Key Attestation issued to that Wallet Unit.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 33, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-12", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=33" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-13", "kind": "Requirement", "title": "The Wallet Provider shall establish and maintain a documented policy governing t…", "text": "The Wallet Provider shall establish and maintain a documented policy governing the issuance of Wallet Instance Attestations and Key Attestations that satisfies the requirements of clauses 6 and 7 of [9].", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-13", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.2-14", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the revocation-status-maintenance period o…", "text": "The Wallet Provider shall ensure that the revocation-status-maintenance period of each Wallet Instance Attestation and each Key Attestation it issues to a Wallet Unit is at least as long as the longest administrative validity period of any PID or device-bound Electronic Attestation of Attributes issued into that Wallet Unit on the basis of that Wallet Instance Attestation or Key Attestation, and that the revocation status is maintained throughout that period.", "section": "6.2 Wallet Instance Attestation and Key Attestation Issuance", "page": 34, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-2-14", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=34" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.3-01", "kind": "Requirement", "title": "The Wallet Provider shall establish the binding between the Wallet Instance and …", "text": "The Wallet Provider shall establish the binding between the Wallet Instance and the Wallet Unit by issuing a Wallet Unit Attestation only to a Wallet Instance whose installation has been successfully verified through a platform-level attestation mechanism provided by the device operating system.", "section": "6.3 Wallet Instance – Wallet Unit Binding", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.3-02", "kind": "Requirement", "title": "The Wallet Provider shall not use persistent device fingerprinting for fraud mon…", "text": "The Wallet Provider shall not use persistent device fingerprinting for fraud monitoring or risk assessment purposes; where device-specific identifiers are collected during activation for legitimate operational purposes, the Wallet Provider shall limit collection to the minimum necessary, shall not derive or retain a persistent fingerprint for Wallet User tracking, and shall inform the Wallet User in accordance with the requirements of the General Data Protection Regulation.", "section": "6.3 Wallet Instance – Wallet Unit Binding", "page": 35, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=35" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.3-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each Wallet Instance holds cryptographic m…", "text": "The Wallet Provider shall ensure that each Wallet Instance holds cryptographic material that can be used to identify unambiguously the Wallet Instance in a way that this cryptographic data cannot be cloned to another device.", "section": "6.3 Wallet Instance – Wallet Unit Binding", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.3-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the WSCA authenticates the Wallet Instance…", "text": "The Wallet Provider shall ensure that the WSCA authenticates the Wallet Instance before performing any cryptographic operation on its behalf, by challenging the Wallet Instance to produce a proof of possession of the cryptographic data mentioned in ACT-5.3-03.", "section": "6.3 Wallet Instance – Wallet Unit Binding", "page": 36, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=36" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-01", "kind": "Requirement", "title": "The Wallet Provider shall offer the Wallet User the opportunity to authenticate …", "text": "The Wallet Provider shall offer the Wallet User the opportunity to authenticate to an existing Wallet User account before offering the creation of a new Wallet User account during Wallet Unit activation.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-02", "kind": "Requirement", "title": "The Wallet Provider shall not collect or process personal identity data about th…", "text": "The Wallet Provider shall not collect or process personal identity data about the Wallet User during Wallet Unit activation beyond what is strictly necessary to complete the activation process and to comply with applicable legal obligations.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 37, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=37" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that any modification to the Wallet Unit accoun…", "text": "The Wallet Provider shall ensure that any modification to the Wallet Unit account configuration after activation requires authenticated and authorised proof from the Wallet Unit or, for emergency procedures, a fresh verification of the Wallet User's identity, and cannot be performed unilaterally by the Wallet Provider without the Wallet User's involvement.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-04", "kind": "Requirement", "title": "The Wallet Provider shall present the Wallet User with configurable privacy sett…", "text": "The Wallet Provider shall present the Wallet User with configurable privacy settings during activation, and shall ensure that the default configuration of any optional data processing activity is set to the option that minimises data collection unless the Wallet User has explicitly selected otherwise.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 38, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=38" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-05", "kind": "Requirement", "title": "The Wallet Provider shall establish and maintain a Wallet User account mechanism…", "text": "The Wallet Provider shall establish and maintain a Wallet User account mechanism that enables the Wallet User to request revocation of the Wallet Unit independently of physical access to the device on which the Wallet Instance is installed.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.4-06", "kind": "Requirement", "title": "The Wallet Provider shall design the Wallet User account for revocation such tha…", "text": "The Wallet Provider shall design the Wallet User account for revocation such that the revocation mechanism is accessible to the Wallet User under adverse conditions — including loss of the device, physical displacement, limited access to communications, or a state of stress — while being sufficiently protected against unauthorised use to prevent a third party from revoking the Wallet Unit of another person without that person's authorisation.", "section": "6.4 Wallet User Account Setup with Wallet Provider", "page": 39, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=39" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.5-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all authentication verification data assoc…", "text": "The Wallet Provider shall ensure that all authentication verification data associated with authentication factors enrolled during activation is stored either within the WSCA/WSCD or in platform-provided hardware-backed key storage, and is not accessible to any application other than the Wallet Instance.", "section": "6.5 Wallet User Authentication Setup", "page": 40, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=40" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.5-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each authentication factor enrolled during…", "text": "The Wallet Provider shall ensure that each authentication factor enrolled during Wallet Unit activation is cryptographically bound to that specific Wallet Unit, such that the same factor presented from any other device, copy, or instance cannot authenticate the holder for actions performed by the Wallet Unit.", "section": "6.5 Wallet User Authentication Setup", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.5-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit limits the number of conse…", "text": "The Wallet Provider shall ensure that the Wallet Unit limits the number of consecutive unsuccessful authentication attempts for each knowledge-based factor to a value not exceeding ten, beyond which the factor is locked until the Wallet User re-establishes proof of holder identity through an out-of-band procedure operated by the Wallet Provider.", "section": "6.5 Wallet User Authentication Setup", "page": 41, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=41" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.5-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet User authentication mechanism e…", "text": "The Wallet Provider shall ensure that the Wallet User authentication mechanism established during Wallet Unit activation consists of at least two factors of different categories, each verified by the Wallet Secure Cryptographic Application of the Wallet Unit, such that no Wallet Unit operation involving Person Identification Data, the Wallet Unit Attestation, or other attestations at security level High can complete based solely on the Wallet User-device operating-system authentication mechanism.", "section": "6.5 Wallet User Authentication Setup", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.6-01", "kind": "Requirement", "title": "The Wallet Provider shall present the Wallet User with the option to restore a M…", "text": "The Wallet Provider shall present the Wallet User with the option to restore a Migration Object from another Wallet Unit from the Wallet User.", "section": "6.6 Migration Object import", "page": 42, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-6-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=42" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.6-02", "kind": "Requirement", "title": "When the Wallet User provides a Migration Object, the Wallet Unit shall, upon re…", "text": "When the Wallet User provides a Migration Object, the Wallet Unit shall, upon receiving the decryption password from the Wallet User, import all data from the Migration Object.", "section": "6.6 Migration Object import", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-6-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.6-03", "kind": "Requirement", "title": "After import of the data from a Migration Object, the Wallet Unit shall offer to…", "text": "After import of the data from a Migration Object, the Wallet Unit shall offer to guide the Wallet User through the re-issuance of the key bound PID and attestations, allowing the Wallet User to select which PID and EAA to have re-issued at that moment.", "section": "6.6 Migration Object import", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-6-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.6-04", "kind": "Requirement", "title": "If the Wallet User has not chosen to re-issue all PID and EAA in one go, the Wal…", "text": "If the Wallet User has not chosen to re-issue all PID and EAA in one go, the Wallet User should have the opportunity to restart the process at a later stage.", "section": "6.6 Migration Object import", "page": 43, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-6-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=43" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.6-05", "kind": "Requirement", "title": "The Wallet Unit shall support all restore mechanisms specified in [7].", "text": "The Wallet Unit shall support all restore mechanisms specified in [7].", "section": "6.6 Migration Object import", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-6-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-01", "kind": "Requirement", "title": "The Wallet Provider shall present the Wallet User with an explicit choice about …", "text": "The Wallet Provider shall present the Wallet User with an explicit choice about whether to create a Migration Object during the Wallet Unit activation process, before the activation process is considered complete.", "section": "6.7 Migration Object Setup", "page": 44, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=44" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-02", "kind": "Requirement", "title": "When presenting the Migration Object choice, the Wallet Provider shall inform th…", "text": "When presenting the Migration Object choice, the Wallet Provider shall inform the Wallet User in plain language that without a Migration Object: (a) there will be no list of PID and Wallet Bound EAA for the new Wallet Unit to request reissuance; (b) the transaction log will not be preserved, and the Wallet User will have no means to demonstrate past transactions in the event of a dispute, fraud, or security incident; (c) there will be no mechanism for migrating the non Wallet Bound EAA to a new Wallet Unit.", "section": "6.7 Migration Object Setup", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-03", "kind": "Requirement", "title": "The Wallet Provider shall not complete Wallet Unit activation until the Wallet U…", "text": "The Wallet Provider shall not complete Wallet Unit activation until the Wallet User has explicitly confirmed their choice regarding the Migration Object.", "section": "6.7 Migration Object Setup", "page": 45, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=45" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-04", "kind": "Requirement", "title": "[CONDITIONAL] Where the Wallet User chooses to create a Migration Object during …", "text": "[CONDITIONAL] Where the Wallet User chooses to create a Migration Object during activation, the Wallet Unit shall require the Wallet User to designate a storage location for the Migration Object before the activation process is considered complete.", "section": "6.7 Migration Object Setup", "page": 46, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that at least one storage option offered for th…", "text": "The Wallet Provider shall ensure that at least one storage option offered for the Migration Object is EU based and under the Wallet User’s exclusive control and is not a location controlled by the Wallet Provider.", "section": "6.7 Migration Object Setup", "page": 46, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=46" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "ACT-6.7-06", "kind": "Requirement", "title": "The Wallet Unit shall create the Migration Object in accordance with [7].", "text": "The Wallet Unit shall create the Migration Object in accordance with [7].", "section": "6.7 Migration Object Setup", "page": 47, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#act-6-7-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=47" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "OPS-7.1-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that non-identity attestations stored in the Wa…", "text": "The Wallet Provider shall ensure that non-identity attestations stored in the Wallet Unit are protected against unauthorised access or modification by mechanisms equivalent to those applied to PID credentials stored in the same Wallet Unit.", "section": "7.1 Security Requirements for Non-PID Use Cases", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#ops-7-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "OPS-7.1-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit discloses data from nonide…", "text": "The Wallet Provider shall ensure that the Wallet Unit discloses data from nonidentity attestations only in response to a verified relying party request and only to the minimum extent necessary to fulfil that request.", "section": "7.1 Security Requirements for Non-PID Use Cases", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#ops-7-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "OPS-7.1-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit in the operational state w…", "text": "The Wallet Provider shall ensure that the Wallet Unit in the operational state without PID does not complete presentations of credentials or attestations whose issuance or validity depends on a PID credential bound to that Wallet Unit.", "section": "7.1 Security Requirements for Non-PID Use Cases", "page": 48, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#ops-7-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=48" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "OPS-7.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit generates and securely sto…", "text": "The Wallet Provider shall ensure that the Wallet Unit generates and securely stores within the WSCD all key material required for PID issuance before initiating a PID issuance request with a PID Provider.", "section": "7.2 Preparedness for PID Issuance", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#ops-7-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "OPS-7.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit presents the Wallet User w…", "text": "The Wallet Provider shall ensure that the Wallet Unit presents the Wallet User with a clear description of the PID issuance process and obtains the Wallet User's explicit consent before initiating a PID issuance request with a PID Provider.", "section": "7.2 Preparedness for PID Issuance", "page": 49, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#ops-7-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=49" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.1-01", "kind": "Requirement", "title": "The Wallet Unit shall obtain the registration certificate of a PID Provider excl…", "text": "The Wallet Unit shall obtain the registration certificate of a PID Provider exclusively from the credential issuer metadata published by that PID Provider, as profiled in [5].", "section": "8.1 PID Issuance request", "page": 51, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=51" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.1-02", "kind": "Requirement", "title": "The Wallet Unit shall verify, prior to submitting a PID issuance request, that t…", "text": "The Wallet Unit shall verify, prior to submitting a PID issuance request, that the registration certificate and the access certificate of the PID Provider contain the same unique identifier for that PID Provider.", "section": "8.1 PID Issuance request", "page": 51, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=51" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.1-03", "kind": "Requirement", "title": "The Wallet Unit shall not submit a PID issuance request where the verification s…", "text": "The Wallet Unit shall not submit a PID issuance request where the verification specified in PID-8.1-02 does not confirm that both certificates contain the same unique identifier.", "section": "8.1 PID Issuance request", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.1-04", "kind": "Requirement", "title": "The Wallet Unit shall inform the Wallet User where verification of the PID Provi…", "text": "The Wallet Unit shall inform the Wallet User where verification of the PID Provider's registration certificate does not confirm that the PID Provider is registered and explain the danger to the Wallet User.", "section": "8.1 PID Issuance request", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit accepts PID only after the…", "text": "The Wallet Provider shall ensure that the Wallet Unit accepts PID only after the PID Provider has confirmed, through identity proofing at Level of Assurance High as specified in [2], that the Wallet User is the natural person to whom the PID data uniquely and unambiguously corresponds.", "section": "8.2 Binding Wallet Unit to Wallet User Identity Verification", "page": 52, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=52" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the identity proofing result presented by …", "text": "The Wallet Provider shall ensure that the identity proofing result presented by the PID Provider refers unambiguously to the same Wallet User session and Wallet Unit that initiated the PID issuance request, such that the result of identity proofing performed for one Wallet User cannot be redirected to a different Wallet Unit.", "section": "8.2 Binding Wallet Unit to Wallet User Identity Verification", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.2-03", "kind": "Requirement", "title": "The Wallet Provider shall implement controls to detect and interrupt PID issuanc…", "text": "The Wallet Provider shall implement controls to detect and interrupt PID issuance flows that exhibit patterns inconsistent with legitimate first-time or renewal issuance for a single Wallet Unit, including repeated rapid issuance attempts and concurrent issuance sessions for the same Wallet Unit.", "section": "8.2 Binding Wallet Unit to Wallet User Identity Verification", "page": 53, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=53" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.2-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that PID binding is initiated only upon verifie…", "text": "The Wallet Provider shall ensure that PID binding is initiated only upon verified and cryptographically confirmed successful completion of the required identity verification steps, and that any PID issuance session associated with a failed, interrupted, or unverifiable identity verification result is rejected and cancelled prior to PID storage.", "section": "8.2 Binding Wallet Unit to Wallet User Identity Verification", "page": 54, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=54" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.2-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit does not simultaneously st…", "text": "The Wallet Provider shall ensure that the Wallet Unit does not simultaneously store more than one active PID credential purporting to identify the same natural person, and shall require the Wallet User to remove any existing active PID credential issued by a different PID Provider before a new PID credential from that different PID Provider can be accepted and stored.", "section": "8.2 Binding Wallet Unit to Wallet User Identity Verification", "page": 55, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=55" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-01", "kind": "Requirement", "title": "The Wallet Unit shall verify, prior to accepting a PID credential, that the sign…", "text": "The Wallet Unit shall verify, prior to accepting a PID credential, that the signing certificate of the PID Provider that issued the credential traces to a trust anchor published by the European Commission in the list of trusted entities applicable to PID Providers.", "section": "8.3 Secure PID Reception Process", "page": 55, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=55" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-02", "kind": "Requirement", "title": "The Wallet Unit shall reject a PID credential whose signing certificate traces t…", "text": "The Wallet Unit shall reject a PID credential whose signing certificate traces to a trust anchor other than a trust anchor published by the European Commission in the list of trusted entities applicable to PID Providers, established in accordance with [12].", "section": "8.3 Secure PID Reception Process", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, for each PID issuance, the Wallet Unit ge…", "text": "The Wallet Provider shall ensure that, for each PID issuance, the Wallet Unit generates a dedicated asymmetric key pair (the PID binding key pair) within the Wallet Secure Cryptographic Device (WSCD), and that the PID issuance request submitted to the PID Provider includes a cryptographic proof of possession of the PID binding private key together with a Key Attestation from the Wallet Provider confirming that the PID binding private key is generated, stored within, and non-extractable from the WSCD.", "section": "8.3 Secure PID Reception Process", "page": 56, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=56" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the PID Provider binds the issued PID cred…", "text": "The Wallet Provider shall ensure that the PID Provider binds the issued PID credential to the PID binding public key, such that the credential can only be presented by the Wallet Unit holding the corresponding PID binding private key.", "section": "8.3 Secure PID Reception Process", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon any PID issuance or re-issuance, the…", "text": "The Wallet Provider shall ensure that, upon any PID issuance or re-issuance, the Wallet Unit generates a PID binding key pair that is unique to that issuance event and has not been used as the PID binding key pair for any other PID credential issued to the same Wallet Unit, so that the compromise of one PID binding private key does not affect the security of any other PID credential.", "section": "8.3 Secure PID Reception Process", "page": 57, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=57" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-06", "kind": "Requirement", "title": "The Wallet Unit shall verify the cryptographic integrity and authenticity of a r…", "text": "The Wallet Unit shall verify the cryptographic integrity and authenticity of a received PID credential before storing it, including verification of the PID Provider's digital signature over the credential, the credential's validity period, and conformance of the credential format with the applicable technical specification.", "section": "8.3 Secure PID Reception Process", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-07", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the delivery of a PID credential from the …", "text": "The Wallet Provider shall ensure that the delivery of a PID credential from the PID Provider to the Wallet Unit takes place in conformance with the requirements specified in ETSI TS 119 472-3 [5], applying any additional protective measures required to prevent observation, modification, or interception of the credential payload by parties intermediating the communication path.", "section": "8.3 Secure PID Reception Process", "page": 58, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=58" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.3-08", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, before the Wallet Unit signs the proof of…", "text": "The Wallet Provider shall ensure that, before the Wallet Unit signs the proof of possession that binds a PID credential to the Wallet Unit, the Wallet User has successfully authenticated to the Wallet Unit using the authentication mechanism established during Wallet Unit activation.", "section": "8.3 Secure PID Reception Process", "page": 59, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-3-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=59" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.4-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the PID binding private key associated wit…", "text": "The Wallet Provider shall ensure that the PID binding private key associated with each issued PID credential is generated within the WSCD of the Wallet Unit, stored exclusively within that WSCD, and protected from extraction in plaintext form throughout the lifecycle of that PID credential.", "section": "8.4 PID Storage and Protection", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.4-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all personal data stored by the Wallet Ins…", "text": "The Wallet Provider shall ensure that all personal data stored by the Wallet Instance, including Person Identification Data, Electronic Attestations of Attributes, transaction log entries, and any other personal data of the Wallet User, is encrypted at rest using a cryptographic key whose use is authorized only after successful Wallet User authentication via the authentication mechanism established during Wallet Unit activation.", "section": "8.4 PID Storage and Protection", "page": 60, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=60" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.4-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit requires successful Wallet…", "text": "The Wallet Provider shall ensure that the Wallet Unit requires successful Wallet User authentication before presenting any PID credential to a relying party, using the authentication mechanism established during Wallet Unit activation at the assurance level applicable to the Wallet Unit.", "section": "8.4 PID Storage and Protection", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.4-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit requires successful Wallet…", "text": "The Wallet Provider shall ensure that the Wallet Unit requires successful Wallet User authentication, using the authentication mechanism established during Wallet Unit activation, before rendering any value of a Person Identification Data attribute in its Wallet User interface.", "section": "8.4 PID Storage and Protection", "page": 61, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=61" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.5-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the PID activation process verifies, throu…", "text": "The Wallet Provider shall ensure that the PID activation process verifies, through the authentication mechanism established during Wallet Unit Activation, that the Wallet User completing the activation is the same individual who initiated PID issuance, before the Wallet Unit transitions to a state in which PID presentation is permitted.", "section": "8.5 Wallet User Activation of PID", "page": 62, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=62" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "PID-8.5-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit requires the Wallet User's…", "text": "The Wallet Provider shall ensure that the Wallet Unit requires the Wallet User's explicit confirmation before marking a received PID credential as active and available for presentation to relying parties.", "section": "8.5 Wallet User Activation of PID", "page": 63, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#pid-8-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=63" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.1-01", "kind": "Requirement", "title": "The Wallet Provider shall apply the same documented change-control, codesigning,…", "text": "The Wallet Provider shall apply the same documented change-control, codesigning, and distribution-channel controls to every Wallet Instance software update as those required for initial deployment, such that no update bypasses or relaxes the controls established for the original software release.", "section": "9.1 Software Updates and Patches", "page": 64, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=64" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.1-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that each update to the Wallet Instance is veri…", "text": "The Wallet Provider shall ensure that each update to the Wallet Instance is verified, before deployment, to confirm that the update does not remove or reduce the operating system-level isolation mechanisms that protect data stored by the Wallet Instance from access by co-located applications, and shall refuse to apply an update that would reduce the Wallet Instance's isolation capabilities below the level verified during installation.", "section": "9.1 Software Updates and Patches", "page": 64, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=64" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.1-03", "kind": "Requirement", "title": "[CONDITIONAL] Where the Wallet Provider permits rollback to a previous software …", "text": "[CONDITIONAL] Where the Wallet Provider permits rollback to a previous software version of the Wallet Instance, the Wallet Provider shall ensure that the rollback does not result in the reinstatement of a version with known security vulnerabilities or a reduction of the security baseline established by the version in force before the rollback.", "section": "9.1 Software Updates and Patches", "page": 65, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.1-04", "kind": "Requirement", "title": "The Wallet Provider shall notify the Wallet User when an update to the Wallet In…", "text": "The Wallet Provider shall notify the Wallet User when an update to the Wallet Instance is available.", "section": "9.1 Software Updates and Patches", "page": 65, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=65" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.1-05", "kind": "Requirement", "title": "[CONDITIONAL] Where an update to the Wallet Instance remediates a security vulne…", "text": "[CONDITIONAL] Where an update to the Wallet Instance remediates a security vulnerability or is necessary to maintain the security baseline of the Wallet Unit, the Wallet Provider shall make the installation of that update a precondition for continued use of the Wallet Unit.", "section": "9.1 Software Updates and Patches", "page": 66, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.2-01", "kind": "Requirement", "title": "The Wallet Provider shall define and enforce a maximum inactivity period after w…", "text": "The Wallet Provider shall define and enforce a maximum inactivity period after which an authenticated session within the Wallet Unit is automatically invalidated and the Wallet User is required to re-authenticate before any Wallet Unit operation may proceed.", "section": "9.2 Re-authentication and Session Management", "page": 66, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=66" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit requires Wallet User re-au…", "text": "The Wallet Provider shall ensure that the Wallet Unit requires Wallet User re-authentication before performing any sensitive operation, including presentation of credentials to a relying party, modification of enrolled authentication factors, and access to stored PID or attestation data following session expiry.", "section": "9.2 Re-authentication and Session Management", "page": 67, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=67" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.2-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit does not retain PID data o…", "text": "The Wallet Provider shall ensure that the Wallet Unit does not retain PID data or other personal data in unprotected memory or storage beyond the scope of a single presentation transaction, and that any temporary copies of such data created during a transaction are securely erased upon completion or termination of that transaction.", "section": "9.2 Re-authentication and Session Management", "page": 67, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=67" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.3-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all cryptographic key material subject to …", "text": "The Wallet Provider shall ensure that all cryptographic key material subject to rotation is generated within the WSCD and remains within the WSCD throughout the key rotation process, and that superseded key material is irrevocably deleted from the WSCD upon successful completion of rotation.", "section": "9.3 Key Rotation and Renewal", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.3-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that key rotation and Wallet Unit software upda…", "text": "The Wallet Provider shall ensure that key rotation and Wallet Unit software update operations are performed in a manner that preserves the security level of the Wallet Unit throughout the operation, such that no transient or permanent reduction in cryptographic strength occurs, and that any operation that cannot be completed without reducing security is automatically aborted and the Wallet Unit restored to its pre-operation security state.", "section": "9.3 Key Rotation and Renewal", "page": 68, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=68" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.3-03", "kind": "Requirement", "title": "The Wallet Provider shall implement and document procedures for renewing Wallet …", "text": "The Wallet Provider shall implement and document procedures for renewing Wallet Instance Attestations and Key Attestations before their expiry date and shall ensure that the expiry of such an attestation does not cause an unplanned interruption to Wallet Unit availability.", "section": "9.3 Key Rotation and Renewal", "page": 69, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=69" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.3-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that renewal of the Wallet Instance Attestation…", "text": "The Wallet Provider shall ensure that renewal of the Wallet Instance Attestation and the Key Attestation and re-issuance of PID credentials and Electronic Attestations of Attributes during the maintenance phase applies the same security controls, cryptographic key generation procedures, and assurance requirements as the initial issuance process for the same credential type, and shall not implement a renewal path that bypasses or reduces any security requirement that applied during initial issuance.", "section": "9.3 Key Rotation and Renewal", "page": 69, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=69" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon expiry of the validity period of a P…", "text": "The Wallet Provider shall ensure that, upon expiry of the validity period of a PID credential or Electronic Attestation of Attributes, the Wallet Unit refuses to present the expired credential to any Relying Party.", "section": "9.4 PID and EAA Lifecycle Management", "page": 70, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=70" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon revocation of a PID credential or El…", "text": "The Wallet Provider shall ensure that, upon revocation of a PID credential or Electronic Attestation of Attributes by its Provider, the Wallet Unit refuses to present the revoked credential to any Relying Party, and shall implement a mechanism to check and maintain awareness of the revocation status of all PID credentials and Electronic Attestations of Attributes stored in the Wallet Unit.", "section": "9.4 PID and EAA Lifecycle Management", "page": 70, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=70" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit clearly indicates the expi…", "text": "The Wallet Provider shall ensure that the Wallet Unit clearly indicates the expired or revoked status of any PID credential or Electronic Attestation of Attributes in any Wallet User interface that displays the credential.", "section": "9.4 PID and EAA Lifecycle Management", "page": 71, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=71" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-04", "kind": "Requirement", "title": "The Wallet Provider shall apply, to every renewal or re-issuance of a PID creden…", "text": "The Wallet Provider shall apply, to every renewal or re-issuance of a PID credential or Electronic Attestation of Attributes to the Wallet Unit, the same authentication, identity-proofing, and cryptographic-binding requirements as those required for the initial issuance of that credential type.", "section": "9.4 PID and EAA Lifecycle Management", "page": 72, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=72" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit provides the Wallet User w…", "text": "The Wallet Provider shall ensure that the Wallet Unit provides the Wallet User with the ability to delete individual attestations, and that deletion results in the removal of the credential data from the Wallet Unit.", "section": "9.4 PID and EAA Lifecycle Management", "page": 72, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=72" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.4-06", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon deletion of a PID credential or an E…", "text": "The Wallet Provider shall ensure that, upon deletion of a PID credential or an Electronic Attestation of Attributes from the Wallet Unit, every registration of that credential with an operating system interface through which relying parties can request its presentation is removed.", "section": "9.4 PID and EAA Lifecycle Management", "page": 73, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-4-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=73" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all Wallet User support processes for Wall…", "text": "The Wallet Provider shall ensure that all Wallet User support processes for Wallet Unit-related requests include verification of the Wallet User's identity before any action affecting the Wallet Unit account is taken by support staff.", "section": "9.5 Wallet User Support", "page": 73, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=73" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that any process by which a Wallet User who is …", "text": "The Wallet Provider shall ensure that any process by which a Wallet User who is unable to authenticate using an existing enrolled authentication factor resets that authentication factor requires identity re-verification at an assurance level equivalent to the assurance level of the Wallet Unit before the reset is permitted.", "section": "9.5 Wallet User Support", "page": 74, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=74" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-03", "kind": "Requirement", "title": "The Wallet Provider shall establish, maintain, and communicate to the Users a cl…", "text": "The Wallet Provider shall establish, maintain, and communicate to the Users a clear and accessible procedure through which a Wallet User can report the confirmed or suspected loss or theft of the device hosting the Wallet Unit without requiring physical access to the original device.", "section": "9.5 Wallet User Support", "page": 74, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=74" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-04", "kind": "Requirement", "title": "The Wallet Provider shall, upon receiving a credible report of loss or theft of …", "text": "The Wallet Provider shall, upon receiving a credible report of loss or theft of the device hosting a Wallet Unit, revoke that Wallet Unit promptly and prior to establishing any replacement Wallet Unit for the same Wallet User.", "section": "9.5 Wallet User Support", "page": 74, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=74" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the process for establishing a replacement…", "text": "The Wallet Provider shall ensure that the process for establishing a replacement Wallet Unit following a confirmed or suspected compromise of the existing Wallet Unit or its authentication factors applies the same security requirements as the initial installation and activation process, including identity verification at the applicable Assurance Level for each credential type to be re-issued.", "section": "9.5 Wallet User Support", "page": 75, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=75" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-06", "kind": "Requirement", "title": "The Wallet Provider shall ensure that a revocation of a Wallet Unit, or the esta…", "text": "The Wallet Provider shall ensure that a revocation of a Wallet Unit, or the establishment of a replacement Wallet Unit under MAINT-9.5-05, that support staff carry out on behalf of a Wallet User takes effect only after a second member of staff has approved it.", "section": "9.5 Wallet User Support", "page": 75, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=75" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-07", "kind": "Requirement", "title": "The Wallet Provider shall record the two approvals under MAINT-9.5-06 in a log t…", "text": "The Wallet Provider shall record the two approvals under MAINT-9.5-06 in a log that is protected against undetected modification.", "section": "9.5 Wallet User Support", "page": 76, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=76" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-08", "kind": "Requirement", "title": "The Wallet Provider shall determine, as part of its risk assessment, the maximum…", "text": "The Wallet Provider shall determine, as part of its risk assessment, the maximum time within which the second approval under MAINT-9.5-06 is given.", "section": "9.5 Wallet User Support", "page": 76, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=76" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.5-09", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the second approval under MAINT9.5-06 is g…", "text": "The Wallet Provider shall ensure that the second approval under MAINT9.5-06 is given within the maximum time determined under MAINT-9.5-08.", "section": "9.5 Wallet User Support", "page": 76, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-5-09", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=76" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-01", "kind": "Requirement", "title": "The Wallet Provider shall document the scope and limitations of the Wallet Unit …", "text": "The Wallet Provider shall document the scope and limitations of the Wallet Unit backup mechanism (the Migration Object), including which data elements are included in and excluded from the backup, and shall communicate these limitations to the Wallet User before the Wallet User activate the automated backup creation.", "section": "9.6 Backup and Restore", "page": 76, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=76" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that any backup is encrypted before being store…", "text": "The Wallet Provider shall ensure that any backup is encrypted before being stored or transmitted outside the Wallet Unit, using an encryption password that is known only to the Wallet User.", "section": "9.6 Backup and Restore", "page": 77, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=77" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-03", "kind": "Requirement", "title": "The Wallet Provider shall inform the Wallet User that the encryption password sh…", "text": "The Wallet Provider shall inform the Wallet User that the encryption password should be stored separately from the backup in a location that is only accessible to the Wallet User.", "section": "9.6 Backup and Restore", "page": 77, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=77" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the confidentiality of the backup data doe…", "text": "The Wallet Provider shall ensure that the confidentiality of the backup data does not depend on the storage location, such that the backup remains unreadable to the Wallet Provider and to the operator of any storage location offered or used, and the ability to decrypt it rests solely on a secret held by the Wallet User.", "section": "9.6 Backup and Restore", "page": 77, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=77" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that when a Wallet User restores a backup to a …", "text": "The Wallet Provider shall ensure that when a Wallet User restores a backup to a different device the target Wallet Unit will remind the Wallet User to revoke the source Wallet Unit if it will no longer be used by the Wallet User and provide him with any information that the Wallet Provider may collect that would help the Wallet User to do so.", "section": "9.6 Backup and Restore", "page": 78, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=78" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-06", "kind": "Requirement", "title": "The Wallet Provider shall update the Migration Object to reflect the current sta…", "text": "The Wallet Provider shall update the Migration Object to reflect the current state of all PID credentials, attestations, and transaction log entries after every transaction performed by the Wallet Unit. A transaction for the purposes of this requirement includes any presentation of a PID or EAA to a relying party, any issuance or deletion of an attestation, and any key rotation event.", "section": "9.6 Backup and Restore", "page": 78, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=78" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-07", "kind": "Requirement", "title": "The Wallet Provider shall not present a Migration Object to the Wallet User as c…", "text": "The Wallet Provider shall not present a Migration Object to the Wallet User as current if the Migration Object does not reflect the most recently confirmed wallet state, without displaying an accompanying notification that the Migration Object is outdated.", "section": "9.6 Backup and Restore", "page": 79, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=79" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.6-08", "kind": "Requirement", "title": "[CONDITIONAL] The Wallet Provider shall ensure that, where the Wallet Unit canno…", "text": "[CONDITIONAL] The Wallet Provider shall ensure that, where the Wallet Unit cannot update the Migration Object because the storage location selected by the Wallet User is no longer accessible to it, the Wallet Unit prompts the Wallet User to restore access to that location or to select a new storage location.", "section": "9.6 Backup and Restore", "page": 79, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-6-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=79" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.7-01", "kind": "Requirement", "title": "The Wallet Provider shall monitor the continued adequacy of the authentication f…", "text": "The Wallet Provider shall monitor the continued adequacy of the authentication factors associated with each Wallet Unit for the applicable Assurance Level and shall require the Wallet User to establish new or updated authentication factors — through a process that meets the same security requirements as the initial activation — where the operating system, Wallet Secure Cryptographic Device, or applicable conformity framework indicates that existing factors no longer meet the requirements for the applicable Assurance Level.", "section": "9.7 Security and Compliance Monitoring", "page": 80, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-7-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=80" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.7-02", "kind": "Requirement", "title": "The Wallet Provider shall conduct documented periodic reviews of the security co…", "text": "The Wallet Provider shall conduct documented periodic reviews of the security controls and procedures governing the Wallet Unit infrastructure, at intervals not exceeding twelve months, to verify that the controls remain effective and continue to satisfy the requirements for the applicable Assurance Level, and shall document identified findings and implement remediation within a timeframe commensurate with the severity of each finding.", "section": "9.7 Security and Compliance Monitoring", "page": 81, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-7-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=81" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.8-01", "kind": "Requirement", "title": "The Wallet Provider shall maintain a documented data management policy that spec…", "text": "The Wallet Provider shall maintain a documented data management policy that specifies, for each category of operational record generated during the Wallet Unit's active lifetime, the legal basis for retention, the defined retention period, the storage protection requirements, and the deletion or anonymisation mechanism, and shall implement and consistently apply this policy across all Wallet Units and associated backend systems.", "section": "9.8 Data Management and Retention", "page": 81, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-8-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=81" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.9-01", "kind": "Requirement", "title": "The Wallet Provider shall retrieve, at intervals not exceeding 24 hours, the cur…", "text": "The Wallet Provider shall retrieve, at intervals not exceeding 24 hours, the current version of each trusted list as specified in [8] and of each list of trusted entities established in accordance with [12] that is applicable to the parties with which its Wallet Units interact.", "section": "9.9 Trust Anchor Management", "page": 82, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-9-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=82" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.9-02", "kind": "Requirement", "title": "The Wallet Provider shall distribute to every non-revoked Wallet Unit each trust…", "text": "The Wallet Provider shall distribute to every non-revoked Wallet Unit each trust anchor that has been newly published in a list retrieved under MAINT-9.9-01.", "section": "9.9 Trust Anchor Management", "page": 82, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-9-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=82" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.9-03", "kind": "Requirement", "title": "The Wallet Provider shall withdraw from every valid Wallet Unit each trust ancho…", "text": "The Wallet Provider shall withdraw from every valid Wallet Unit each trust anchor that has been removed from, or invalidated in, a list retrieved under MAINT-9.9-01.", "section": "9.9 Trust Anchor Management", "page": 83, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-9-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=83" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MAINT-9.9-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that a Wallet Unit accepts only the trust ancho…", "text": "The Wallet Provider shall ensure that a Wallet Unit accepts only the trust anchors distributed to it by the Wallet Provider under MAINT-9.9-02.", "section": "9.9 Trust Anchor Management", "page": 84, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#maint-9-9-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=84" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.1-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that migration of a Wallet Unit is initiated so…", "text": "The Wallet Provider shall ensure that migration of a Wallet Unit is initiated solely by the Wallet User from the source Wallet Unit, including where the target Wallet Unit is operated by a different Wallet Provider, and that no authorisation, approval, or notification by the Wallet Provider is required as a precondition for initiating migration.", "section": "10.1 Migration Initiation and Authorisation", "page": 85, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=85" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that at all times an updated Migration Object w…", "text": "The Wallet Provider shall ensure that at all times an updated Migration Object will be available in the storage location selected by the Wallet User.", "section": "10.2 Secure Data Transfer Mechanisms", "page": 85, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=85" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Migration Object is stored in external…", "text": "The Wallet Provider shall ensure that the Migration Object is stored in external or remote storage only in an encrypted form that protects its confidentiality, integrity, and authenticity, and that only the Wallet User holds the cryptographic material required to decrypt it.", "section": "10.2 Secure Data Transfer Mechanisms", "page": 86, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=86" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.2-03", "kind": "Requirement", "title": "Prior to presenting the Wallet User with the option to finalise migration and re…", "text": "Prior to presenting the Wallet User with the option to finalise migration and revoke the source Wallet Unit, the Wallet Provider shall verify that the target Wallet Unit is in an active state.", "section": "10.2 Secure Data Transfer Mechanisms", "page": 86, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=86" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.2-04", "kind": "Requirement", "title": "The Wallet Provider shall revoke the source Wallet Unit upon the Wallet User’s e…", "text": "The Wallet Provider shall revoke the source Wallet Unit upon the Wallet User’s explicit decision to finalise the migration.", "section": "10.2 Secure Data Transfer Mechanisms", "page": 87, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=87" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.2-05", "kind": "Requirement", "title": "The Wallet Provider shall not prevent or delay revocation of the source Wallet U…", "text": "The Wallet Provider shall not prevent or delay revocation of the source Wallet Unit on the grounds that the Wallet User has not yet requested reissuance of some or all Electronic Attestations of Attributes held in the source Wallet Unit.", "section": "10.2 Secure Data Transfer Mechanisms", "page": 87, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=87" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.3-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, before completing Wallet Unit reestablish…", "text": "The Wallet Provider shall ensure that, before completing Wallet Unit reestablishment on the target device, the target device undergoes the same device security assessment as is required during Wallet Instance installation, including verification that the device meets the minimum hardware and software security requirements defined in the Wallet Provider's security policy and that a WSCD meeting the applicable security certification requirements is available on the target device.", "section": "10.3 New Device Security Verification", "page": 88, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=88" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.4-01", "kind": "Requirement", "title": "The Wallet Provider shall issue a new Wallet Instance Attestation and a new Key …", "text": "The Wallet Provider shall issue a new Wallet Instance Attestation and a new Key Attestation for the new device following the same security verification process applied during their initial issuance, including WSCD certification verification and platform attestation.", "section": "10.4 Wallet Unit Re-establishment on New Device", "page": 89, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=89" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.4-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that device binding on the new device is establ…", "text": "The Wallet Provider shall ensure that device binding on the new device is established using a key pair newly generated within the WSCD of the new device and that no device-bound private key is transferred from the old device to the new device.", "section": "10.4 Wallet Unit Re-establishment on New Device", "page": 89, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=89" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.4-03", "kind": "Requirement", "title": "The Wallet Provider shall require the Wallet User to establish authentication fa…", "text": "The Wallet Provider shall require the Wallet User to establish authentication factors on the target device through a procedure that meets the same security requirements as the initial setup of authentication factors during Wallet Unit activation, prior to the migration process being considered complete.", "section": "10.4 Wallet Unit Re-establishment on New Device", "page": 89, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=89" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.5-01", "kind": "Requirement", "title": "The Wallet Provider shall point out the dangers to the Wallet User of a valid Wa…", "text": "The Wallet Provider shall point out the dangers to the Wallet User of a valid Wallet Unit that is not under control of the Wallet User and ask the Wallet User if the old Wallet Unit should be revoked.", "section": "10.5 Old Device Decommissioning", "page": 90, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=90" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.5-02", "kind": "Requirement", "title": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to…", "text": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to be revoked and the old Wallet Unit is managed by the same Wallet Provider, the Wallet Provider shall start the process to revoke the old Wallet Unit.", "section": "10.5 Old Device Decommissioning", "page": 90, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=90" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.5-03", "kind": "Requirement", "title": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to…", "text": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to be revoked and the old Wallet Unit is not managed by the same Wallet Provider, the Wallet Provider shall give the best possible instructions to the Wallet User what actions the Wallet User should undertake in order to get the old Wallet Unit revoked.", "section": "10.5 Old Device Decommissioning", "page": 91, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-5-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=91" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.5-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all key material held by the WSCD, all PID…", "text": "The Wallet Provider shall ensure that all key material held by the WSCD, all PID credentials and Electronic Attestations of Attributes, and all personal data stored by the Wallet Instance are permanently and irrecoverably deleted from the device before the Wallet Instance uninstallation process completes.", "section": "10.5 Old Device Decommissioning", "page": 91, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-5-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=91" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.5-05", "kind": "Requirement", "title": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to…", "text": "[CONDITIONAL] If the Wallet User has indicated a need for the old Wallet Unit to be revoked and the old Wallet Unit is managed by the same Wallet Provider, the Wallet Provider shall ensure that that all cryptographic key material and personal data stored in the old Wallet Unit are irrecoverably deleted from the old device and that the Wallet Instance is uninstalled from the old device the next time when the Wallet Instance connects again with the WSCA.", "section": "10.5 Old Device Decommissioning", "page": 92, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-5-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=92" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.6-01", "kind": "Requirement", "title": "The Wallet Provider shall verify that the deletion of all cryptographic key mate…", "text": "The Wallet Provider shall verify that the deletion of all cryptographic key material and personal data from the source Wallet Unit has completed, and shall record the outcome of that verification.", "section": "10.6 Secure Deletion of Keys and Attestations on Old Device", "page": 92, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-6-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=92" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.6-02", "kind": "Requirement", "title": "[CONDITIONAL] Where the deletion of key material and personal data from the sour…", "text": "[CONDITIONAL] Where the deletion of key material and personal data from the source Wallet Unit has not been confirmed within a period defined and documented by the Wallet Provider, the Wallet Provider shall revoke the source Wallet Unit irrespective of that confirmation.", "section": "10.6 Secure Deletion of Keys and Attestations on Old Device", "page": 93, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-6-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=93" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.6-03", "kind": "Requirement", "title": "[CONDITIONAL] Where the deletion of key material and personal data from the sour…", "text": "[CONDITIONAL] Where the deletion of key material and personal data from the source Wallet Unit has been confirmed under MIG-10.6-01, the Wallet Provider shall revoke the source Wallet Unit if it has not already been revoked.", "section": "10.6 Secure Deletion of Keys and Attestations on Old Device", "page": 93, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-6-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=93" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.7-01", "kind": "Requirement", "title": "[CONDITIONAL] Where the source Wallet Unit is no longer accessible to the Wallet…", "text": "[CONDITIONAL] Where the source Wallet Unit is no longer accessible to the Wallet User, the Wallet Provider shall enable the Wallet User to re-establish the Wallet Unit on a new device by restoring a Migration Object, without requiring any participation by the source device.", "section": "10.7 Recovery to a New Device When the Source Device Is Unavailable", "page": 94, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-7-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=94" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.7-02", "kind": "Requirement", "title": "The Wallet Provider shall require identity proofing at the assurance level appli…", "text": "The Wallet Provider shall require identity proofing at the assurance level applicable to initial PID issuance before any PID credential is re-issued during a recovery performed under this clause.", "section": "10.7 Recovery to a New Device When the Source Device Is Unavailable", "page": 94, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-7-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=94" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.7-03", "kind": "Requirement", "title": "[CONDITIONAL] Where a recovery under this clause is performed and the source Wal…", "text": "[CONDITIONAL] Where a recovery under this clause is performed and the source Wallet Unit is managed by the same Wallet Provider, the Wallet Provider shall revoke the source Wallet Unit, treating the Wallet User’s assertion that the source device is no longer under their control as the trigger for that revocation.", "section": "10.7 Recovery to a New Device When the Source Device Is Unavailable", "page": 94, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-7-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=94" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.7-04", "kind": "Requirement", "title": "[CONDITIONAL] Where a recovery under this clause is performed and the source Wal…", "text": "[CONDITIONAL] Where a recovery under this clause is performed and the source Wallet Unit is managed by a different Wallet Provider, the Wallet Provider shall give the Wallet User the best possible instructions on the actions the Wallet User should undertake in order to get the source Wallet Unit revoked.", "section": "10.7 Recovery to a New Device When the Source Device Is Unavailable", "page": 95, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-7-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=95" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MIG-10.7-05", "kind": "Requirement", "title": "The Wallet Provider shall apply to the re-establishment of the Wallet Unit on th…", "text": "The Wallet Provider shall apply to the re-establishment of the Wallet Unit on the new device under this clause the same new device security verification and reestablishment controls that apply to a migration, as set out in clauses 10.3 and 10.4.", "section": "10.7 Recovery to a New Device When the Source Device Is Unavailable", "page": 95, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mig-10-7-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=95" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.1-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Unit requires an explicit confi…", "text": "The Wallet Provider shall ensure that the Wallet Unit requires an explicit confirmation step from the Wallet User before proceeding with uninstallation and presents the Wallet User with a clear statement of the consequences of uninstallation, including the irreversible loss of all key bound credentials stored in the Wallet Unit.", "section": "11.1 Wallet User-Initiated Uninstallation", "page": 97, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=97" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.1-02", "kind": "Requirement", "title": "The Wallet Provider shall, prior to completing the Wallet Instance uninstallatio…", "text": "The Wallet Provider shall, prior to completing the Wallet Instance uninstallation process, inform the Wallet User that all PID credentials, attestations and transaction logs stored in the Wallet Unit will be permanently deleted and are not recoverable after uninstallation, and shall require explicit Wallet User confirmation before proceeding.", "section": "11.1 Wallet User-Initiated Uninstallation", "page": 97, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=97" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.1-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, prior to completing the Wallet Instance u…", "text": "The Wallet Provider shall ensure that, prior to completing the Wallet Instance uninstallation process, an updated Migration Object is available in the storage location selected by the Wallet User, that the Wallet User confirms to still have access to that location and verify that the Wallet User still has knowledge of the Migration Object.", "section": "11.1 Wallet User-Initiated Uninstallation", "page": 98, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=98" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.1-04", "kind": "Requirement", "title": "[CONDITIONAL] If one of the checks in UNINST-11.1-03 is not met, the Wallet Prov…", "text": "[CONDITIONAL] If one of the checks in UNINST-11.1-03 is not met, the Wallet Provider shall ensure that Wallet Unit uninstallation only proceeds after renewed confirmation by the Wallet User.", "section": "11.1 Wallet User-Initiated Uninstallation", "page": 98, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=98" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all active sessions and pending transactio…", "text": "The Wallet Provider shall ensure that all active sessions and pending transactions within the Wallet Unit are terminated before the uninstallation process begins.", "section": "11.2 Pre-Uninstallation Security Measures", "page": 98, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=98" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Provider backend is notified of…", "text": "The Wallet Provider shall ensure that the Wallet Provider backend is notified of the uninstallation event before or upon completion of the uninstallation process, enabling the Wallet Provider to initiate appropriate deregistration or revocation actions.", "section": "11.2 Pre-Uninstallation Security Measures", "page": 99, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=99" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.3-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all private keys associated with the Walle…", "text": "The Wallet Provider shall ensure that all private keys associated with the Wallet Unit, including keys attested in a Key Attestation, credential-binding keys, and Wallet User authentication keys, are irrecoverably deleted from the WSCD and from all application storage locations during uninstallation.", "section": "11.3 Data Cleanup and Deletion", "page": 99, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=99" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.3-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all PID credentials and attestations store…", "text": "The Wallet Provider shall ensure that all PID credentials and attestations stored in the Wallet Unit are irrecoverably deleted during uninstallation.", "section": "11.3 Data Cleanup and Deletion", "page": 99, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=99" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.3-03", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all cached data, temporary files, session …", "text": "The Wallet Provider shall ensure that all cached data, temporary files, session tokens, and application state related to Wallet Unit operations are irrecoverably deleted during uninstallation.", "section": "11.3 Data Cleanup and Deletion", "page": 100, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=100" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.3-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the WSCA and WSCD are cleared of all key m…", "text": "The Wallet Provider shall ensure that the WSCA and WSCD are cleared of all key material, configuration data, and application-specific data stored within them as part of the uninstallation process.", "section": "11.3 Data Cleanup and Deletion", "page": 100, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=100" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.3-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon Wallet Instance uninstallation, all …", "text": "The Wallet Provider shall ensure that, upon Wallet Instance uninstallation, all operational records and transaction logs associated with the uninstalled Wallet Unit that are held in the Wallet Provider's backend systems are either deleted or anonymised in accordance with the applicable data protection requirements, except where those records are required to be retained under a legal obligation, in which case the retained records shall be limited to what is strictly necessary, retained only for the minimum required period, and access-controlled to prevent use for any purpose other than compliance with that obligation.", "section": "11.3 Data Cleanup and Deletion", "page": 100, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-3-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=100" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.4-01", "kind": "Requirement", "title": "The Wallet Provider shall revoke the Wallet Instance Attestation and the Key Att…", "text": "The Wallet Provider shall revoke the Wallet Instance Attestation and the Key Attestation associated with a Wallet Unit at the time of Wallet Instance uninstallation regardless of whether the Wallet User intends to install the Wallet Instance again on the same or a different device.", "section": "11.4 Revocation and Deregistration", "page": 101, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=101" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.5-01", "kind": "Requirement", "title": "The Wallet Provider shall provide the Wallet User with confirmation that the uni…", "text": "The Wallet Provider shall provide the Wallet User with confirmation that the uninstallation process has completed, including confirmation that the Wallet Unit has been deregistered with the Wallet Provider and has been revoked.", "section": "11.5 Verification of Complete Removal", "page": 102, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-5-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=102" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "UNINST-11.5-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the uninstallation process results in no r…", "text": "The Wallet Provider shall ensure that the uninstallation process results in no recoverable Wallet Unit data remaining on the device, including private keys, credentials, cached data, and application configuration files.", "section": "11.5 Verification of Complete Removal", "page": 102, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#uninst-11-5-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=102" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-01", "kind": "Requirement", "title": "The Wallet Provider shall implement mechanisms to detect security breaches affec…", "text": "The Wallet Provider shall implement mechanisms to detect security breaches affecting Wallet Units, including monitoring for indicators of device compromise, and shall initiate revocation procedures upon confirmed detection of a breach affecting a Wallet Unit.", "section": "12.1 Revocation Triggers and Conditions", "page": 103, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=103" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-02", "kind": "Requirement", "title": "The Wallet Provider shall revoke a Wallet Unit when required to do so by applica…", "text": "The Wallet Provider shall revoke a Wallet Unit when required to do so by applicable law or by a competent supervisory authority, within the timeframes mandated by the applicable legal requirement.", "section": "12.1 Revocation Triggers and Conditions", "page": 103, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=103" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-03", "kind": "Requirement", "title": "The Wallet Provider shall establish and maintain a documented procedure for acce…", "text": "The Wallet Provider shall establish and maintain a documented procedure for accepting and processing requests for permanent revocation of a Wallet Unit submitted by an authorised party other than the Wallet Unit holder, including requests submitted in consequence of the death or legal incapacity of the natural person to whom the Wallet Unit is issued, and shall provide a mechanism that enables such requests to be submitted and verified without requiring participation of the Wallet Unit holder.", "section": "12.1 Revocation Triggers and Conditions", "page": 103, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=103" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-04", "kind": "Requirement", "title": "The Wallet Provider shall establish processes for Wallet Users or other competen…", "text": "The Wallet Provider shall establish processes for Wallet Users or other competent parties to notify suspected device compromise.", "section": "12.1 Revocation Triggers and Conditions", "page": 104, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=104" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-05", "kind": "Requirement", "title": "The Wallet Provider shall revoke a Wallet Unit for which credible evidence of fr…", "text": "The Wallet Provider shall revoke a Wallet Unit for which credible evidence of fraudulent use or sufficient indication of suspected compromise has been identified and shall record the basis and supporting evidence for the revocation decision.", "section": "12.1 Revocation Triggers and Conditions", "page": 104, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=104" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-06", "kind": "Requirement", "title": "The Wallet Provider shall ensure that a Wallet User can initiate revocation of t…", "text": "The Wallet Provider shall ensure that a Wallet User can initiate revocation of their own Wallet Unit through a means that does not depend on access to the Wallet Unit’s device, on authentication factors or credentials that are typically kept or carried together with that device, or on any secret or credential that the Wallet User would typically only store in a fixed location such as their home.", "section": "12.1 Revocation Triggers and Conditions", "page": 105, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=105" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-07", "kind": "Requirement", "title": "The Wallet Provider shall, after authenticating the PID Provider as the sender, …", "text": "The Wallet Provider shall, after authenticating the PID Provider as the sender, revoke a Wallet Unit when the PID Provider forwards a request for revocation of that Wallet Unit on behalf of the person in whose name a PID was issued to it.", "section": "12.1 Revocation Triggers and Conditions", "page": 105, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=105" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.1-08", "kind": "Requirement", "title": "The Wallet Provider shall treat a notice from the PID Provider of the decease of…", "text": "The Wallet Provider shall treat a notice from the PID Provider of the decease of a Wallet Holder as a request under REV-12.1-03 for permanent revocation of the Wallet Unit to which the notice relates.", "section": "12.1 Revocation Triggers and Conditions", "page": 105, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-1-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=105" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that revocation requests submitted by parties o…", "text": "The Wallet Provider shall ensure that revocation requests submitted by parties other than the Wallet User are subject to verification of the authority of the requesting party to trigger revocation before the request is acted upon.", "section": "12.2 Revocation Procedures", "page": 106, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=106" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that a revoked Wallet Unit is disabled within a…", "text": "The Wallet Provider shall ensure that a revoked Wallet Unit is disabled within a defined maximum timeframe following the revocation decision.", "section": "12.2 Revocation Procedures", "page": 106, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=106" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-03", "kind": "Requirement", "title": "The Wallet Provider shall document and enforce that maximum permissible delay be…", "text": "The Wallet Provider shall document and enforce that maximum permissible delay between the revocation decision and the effective disabling of the Wallet Unit.", "section": "12.2 Revocation Procedures", "page": 107, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=107" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-04", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, upon revocation of a Wallet Unit, the rev…", "text": "The Wallet Provider shall ensure that, upon revocation of a Wallet Unit, the revocation status of the associated Wallet Instance Attestation and Key Attestation is published to the applicable revocation status mechanism without undue delay, enabling parties interacting with the Wallet Unit to detect the revocation prior to accepting transactions with the revoked Wallet Unit.", "section": "12.2 Revocation Procedures", "page": 107, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=107" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-05", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance ceases to display the …", "text": "The Wallet Provider shall ensure that the Wallet Instance ceases to display the European Digital Identity Wallet Trust Mark referred to in [13] from the moment the Wallet Instance Attestation of that Wallet Unit is revoked.", "section": "12.2 Revocation Procedures", "page": 107, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-05", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=107" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-06", "kind": "Requirement", "title": "The Wallet Provider shall ensure that revocation of a Wallet Unit is permanent a…", "text": "The Wallet Provider shall ensure that revocation of a Wallet Unit is permanent and irreversible, and shall not provide any mechanism, interface, process, or administrative function through which a permanently revoked Wallet Unit can be restored to an active or operational state.", "section": "12.2 Revocation Procedures", "page": 108, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-06", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=108" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-07", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the Wallet Instance Attestation issued to …", "text": "The Wallet Provider shall ensure that the Wallet Instance Attestation issued to each Wallet Unit contains a reference to the revocation status mechanism maintained by the Wallet Provider, enabling relying parties and PID Providers to determine the current revocation status of the Wallet Unit at the time of any transaction.", "section": "12.2 Revocation Procedures", "page": 109, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-07", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=109" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.2-08", "kind": "Requirement", "title": "The Wallet Provider shall, whenever it revokes the Wallet Instance Attestation o…", "text": "The Wallet Provider shall, whenever it revokes the Wallet Instance Attestation of a Wallet Unit — on revocation of the Wallet Unit under this clause, on uninstallation of the Wallet Instance, or on revocation of a source Wallet Unit during migration — set to revoked the revocation status of every Wallet Instance Attestation it has issued to that Wallet Unit, including any such attestation whose technical validity period has expired but whose revocation status the Wallet Provider still maintains, so that the revocation status reference recorded by a PID Provider or Attestation Provider at issuance reflects the revocation throughout the lifetime of the PID or attestation issued against it.", "section": "12.2 Revocation Procedures", "page": 109, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-2-08", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=109" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.3-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that the revocation status of the Wallet Instan…", "text": "The Wallet Provider shall ensure that the revocation status of the Wallet Instance Attestation and of the Key Attestation is published to the applicable attestation status list within a defined and documented maximum time period following the triggering event for revocation, and shall make that attestation status list available in a format and at a location that enables PID Providers and Attestation Providers to query the revocation status of any such attestation without requiring authenticated access to the status service.", "section": "12.3 Impact on PIDs and Attestations", "page": 110, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=110" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.3-02", "kind": "Requirement", "title": "[CONDITIONAL] Where the Wallet Instance Attestation or the Key Attestation is is…", "text": "[CONDITIONAL] Where the Wallet Instance Attestation or the Key Attestation is issued in the mobile document format specified in [11], the Wallet Provider shall publish its revocation status by means of an attestation status list or an attestation revocation list as specified in [12].", "section": "12.3 Impact on PIDs and Attestations", "page": 111, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=111" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.3-03", "kind": "Requirement", "title": "[CONDITIONAL] Where the Wallet Instance Attestation or the Key Attestation is is…", "text": "[CONDITIONAL] Where the Wallet Instance Attestation or the Key Attestation is issued in the selectively disclosable JSON Web Token verifiable credential format, the Wallet Provider shall publish its revocation status by means of an attestation status list as specified in [10].", "section": "12.3 Impact on PIDs and Attestations", "page": 111, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=111" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.4-01", "kind": "Requirement", "title": "The Wallet Provider shall ensure that all private keys stored in the remote WSCD…", "text": "The Wallet Provider shall ensure that all private keys stored in the remote WSCD that are associated with a revoked Wallet Unit are irrecoverably deleted and that the revocation event is recorded in a tamper-evident audit log.", "section": "12.4 Data Deletion Requirements", "page": 112, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=112" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.4-02", "kind": "Requirement", "title": "The Wallet Provider shall ensure that, following permanent revocation of a Walle…", "text": "The Wallet Provider shall ensure that, following permanent revocation of a Wallet Unit, all personal data associated with the revoked Wallet Unit that is held in the Wallet Provider's backend systems is deleted or anonymised in accordance with the applicable data protection requirements, except where those records are required to be retained under a legal obligation, in which case the retained data shall be limited to what is strictly necessary, retained only for the minimum required period, and access-controlled to prevent use for any purpose other than compliance with that obligation.", "section": "12.4 Data Deletion Requirements", "page": 112, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-4-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=112" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "REV-12.4-03", "kind": "Requirement", "title": "The Wallet Provider shall retain audit logs related to Wallet Unit revocation fo…", "text": "The Wallet Provider shall retain audit logs related to Wallet Unit revocation for a period sufficient to support legal proceedings, supervisory audit, and incident investigation, and shall ensure that the retention period does not exceed the maximum period permitted under applicable data protection law.", "section": "12.4 Data Deletion Requirements", "page": 113, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#rev-12-4-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=113" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.1-01", "kind": "Requirement", "title": "The Wallet Provider shall operate a monitoring capability that detects, across e…", "text": "The Wallet Provider shall operate a monitoring capability that detects, across every lifecycle state of a Wallet Unit, patterns indicative of compromise or fraudulent use in the backend interactions it receives from that Wallet Unit, including a frequency of those interactions inconsistent with normal operation and a device or Wallet Secure Cryptographic Device profile presented in an interaction that is inconsistent with the profile recorded for that Wallet Unit at activation or at a subsequent re-attestation.", "section": "13.1 General Monitoring and Fraud Detection", "page": 114, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-1-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=114" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.1-02", "kind": "Requirement", "title": "The Wallet Provider shall document, for each anomaly condition detected under MO…", "text": "The Wallet Provider shall document, for each anomaly condition detected under MON-13.1-01, the investigation procedure applied and the response available, up to and including revocation of the Wallet Unit.", "section": "13.1 General Monitoring and Fraud Detection", "page": 114, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-1-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=114" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.1-03", "kind": "Requirement", "title": "The Wallet Provider shall provide the Wallet User with a means of reporting susp…", "text": "The Wallet Provider shall provide the Wallet User with a means of reporting suspected compromise or misuse of a Wallet Unit that does not require the Wallet User to authenticate to that Wallet Unit.", "section": "13.1 General Monitoring and Fraud Detection", "page": 115, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-1-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=115" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.2-01", "kind": "Requirement", "title": "[CONDITIONAL] For a Wallet Unit that holds no PID credential, the Wallet Provide…", "text": "[CONDITIONAL] For a Wallet Unit that holds no PID credential, the Wallet Provider shall base the monitoring required under MON-13.1-01 on the Wallet Instance Attestation and Key Attestation status queries, the software update check-ins, and the reports of suspected compromise that it receives from the Wallet Unit at that stage.", "section": "13.2 State-Specific Monitoring Inputs", "page": 115, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-2-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=115" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.2-02", "kind": "Requirement", "title": "[CONDITIONAL] For a Wallet Unit that holds a PID credential, the Wallet Provider…", "text": "[CONDITIONAL] For a Wallet Unit that holds a PID credential, the Wallet Provider shall extend the monitoring required under MON-13.1-01 to the trust anchor distribution channel, the software update check-ins, and any migration-initiation request it receives from the Wallet Unit.", "section": "13.2 State-Specific Monitoring Inputs", "page": 116, "obligation": "conditional", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-2-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=116" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.3-01", "kind": "Requirement", "title": "The Wallet Provider shall monitor the application distribution channels through …", "text": "The Wallet Provider shall monitor the application distribution channels through which the Wallet Instance is made available for counterfeit, modified, or look-alike applications that impersonate the Wallet Instance.", "section": "13.3 Monitoring of the Application and Web Ecosystem", "page": 116, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-3-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=116" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.3-02", "kind": "Requirement", "title": "The Wallet Provider shall, upon identifying a counterfeit, modified, or lookalik…", "text": "The Wallet Provider shall, upon identifying a counterfeit, modified, or lookalike application that impersonates the Wallet Instance, pursue its removal from the application distribution channel on which it is offered.", "section": "13.3 Monitoring of the Application and Web Ecosystem", "page": 117, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-3-02", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=117" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.3-03", "kind": "Requirement", "title": "The Wallet Provider shall monitor for websites that impersonate the Wallet Provi…", "text": "The Wallet Provider shall monitor for websites that impersonate the Wallet Provider in order to deceive Wallet Users.", "section": "13.3 Monitoring of the Application and Web Ecosystem", "page": 117, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-3-03", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=117" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.3-04", "kind": "Requirement", "title": "The Wallet Provider shall, upon identifying a website that impersonates the Wall…", "text": "The Wallet Provider shall, upon identifying a website that impersonates the Wallet Provider or the Wallet Instance, pursue its takedown.", "section": "13.3 Monitoring of the Application and Web Ecosystem", "page": 117, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-3-04", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=117" }, { "document": "NL-P-04W", "document_title": "EUDI Wallet Lifecycle Specification", "version": "RC1.0", "id": "MON-13.4-01", "kind": "Requirement", "title": "The Wallet Provider shall maintain a means of contacting the Wallet User over a …", "text": "The Wallet Provider shall maintain a means of contacting the Wallet User over a push channel that the Wallet User will see without opening the Wallet Instance and that is independent of the Wallet Instance, for use in warning the Wallet User when compromise of the Wallet Unit is suspected.", "section": "13.4 Wallet User Warning Channel", "page": 118, "obligation": "mandatory", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/nl-p-04w#mon-13-4-01", "pdf": "/files/edi-stelsel/2026-11-06/NL-P-04W_Wallet_Onboarding__Lifecycle_Mngt_-_reqs_-_RC1.0_-_for_pub.pdf#page=118" }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#1", "kind": "OWASP MAS requirement", "title": "The app encrypts sensitive data stored in private storage.", "text": "The app encrypts sensitive data stored in private storage.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r1", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#2", "kind": "OWASP MAS requirement", "title": "The app encrypts sensitive data stored outside of private storage.", "text": "The app encrypts sensitive data stored outside of private storage.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r2", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#3", "kind": "OWASP MAS requirement", "title": "The app stores cryptographic keys inside the platform-provided secure keystore.", "text": "The app stores cryptographic keys inside the platform-provided secure keystore.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r3", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#4", "kind": "OWASP MAS requirement", "title": "The app does not hardcode sensitive data in the application package.", "text": "The app does not hardcode sensitive data in the application package.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r4", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#5", "kind": "OWASP MAS requirement", "title": "The app excludes sensitive data from application logs.", "text": "The app excludes sensitive data from application logs.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r5", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#6", "kind": "OWASP MAS requirement", "title": "The app excludes sensitive data from backups.", "text": "The app excludes sensitive data from backups.", "section": "MASVS-STORAGE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r6", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#7", "kind": "OWASP MAS requirement", "title": "The app properly encrypts sensitive data.", "text": "The app properly encrypts sensitive data.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r7", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#8", "kind": "OWASP MAS requirement", "title": "The app properly hashes sensitive data.", "text": "The app properly hashes sensitive data.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r8", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#9", "kind": "OWASP MAS requirement", "title": "The app properly uses Message Authentication Codes (MACs).", "text": "The app properly uses Message Authentication Codes (MACs).", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r9", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#10", "kind": "OWASP MAS requirement", "title": "The app properly generates cryptographic signatures.", "text": "The app properly generates cryptographic signatures.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r10", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#11", "kind": "OWASP MAS requirement", "title": "The app properly verifies cryptographic signatures.", "text": "The app properly verifies cryptographic signatures.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r11", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#12", "kind": "OWASP MAS requirement", "title": "The app properly generates random numbers.", "text": "The app properly generates random numbers.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r12", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#13", "kind": "OWASP MAS requirement", "title": "The app securely generates cryptographic keys.", "text": "The app securely generates cryptographic keys.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r13", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#14", "kind": "OWASP MAS requirement", "title": "The app derives cryptographic keys using approved key derivation functions.", "text": "The app derives cryptographic keys using approved key derivation functions.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r14", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#15", "kind": "OWASP MAS requirement", "title": "The app rotates cryptographic keys regularly.", "text": "The app rotates cryptographic keys regularly.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r15", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#16", "kind": "OWASP MAS requirement", "title": "The app restricts access to cryptographic keys.", "text": "The app restricts access to cryptographic keys.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r16", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#17", "kind": "OWASP MAS requirement", "title": "The app verifies that the device has a secure lock configured.", "text": "The app verifies that the device has a secure lock configured.", "section": "MASVS-CRYPTO", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r17", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#18", "kind": "OWASP MAS requirement", "title": "The app enforces authentication and authorization on its components.", "text": "The app enforces authentication and authorization on its components.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r18", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#19", "kind": "OWASP MAS requirement", "title": "The app enables auto-fill support for credential providers.", "text": "The app enables auto-fill support for credential providers.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r19", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#20", "kind": "OWASP MAS requirement", "title": "The app implements local authentication securely.", "text": "The app implements local authentication securely.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r20", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#21", "kind": "OWASP MAS requirement", "title": "The app does not allow fallback to non-biometric credentials for sensitive transactions.", "text": "The app does not allow fallback to non-biometric credentials for sensitive transactions.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r21", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#22", "kind": "OWASP MAS requirement", "title": "The app invalidates keys after any enrollment of new biometric data.", "text": "The app invalidates keys after any enrollment of new biometric data.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r22", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#23", "kind": "OWASP MAS requirement", "title": "The app enforces step-up authentication before granting access to sensitive functionality.", "text": "The app enforces step-up authentication before granting access to sensitive functionality.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r23", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#24", "kind": "OWASP MAS requirement", "title": "The app makes sensitive data inaccessible after session termination.", "text": "The app makes sensitive data inaccessible after session termination.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r24", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#25", "kind": "OWASP MAS requirement", "title": "The app ensures non-repudiation for critical actions.", "text": "The app ensures non-repudiation for critical actions.", "section": "MASVS-AUTH", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r25", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#26", "kind": "OWASP MAS requirement", "title": "The app encrypts all network traffic.", "text": "The app encrypts all network traffic.", "section": "MASVS-NETWORK", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r26", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#27", "kind": "OWASP MAS requirement", "title": "The app validates certificates for all network traffic.", "text": "The app validates certificates for all network traffic.", "section": "MASVS-NETWORK", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r27", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#28", "kind": "OWASP MAS requirement", "title": "The app correctly implements identity pinning.", "text": "The app correctly implements identity pinning.", "section": "MASVS-NETWORK", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r28", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#29", "kind": "OWASP MAS requirement", "title": "The app securely handles deep links.", "text": "The app securely handles deep links.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r29", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#30", "kind": "OWASP MAS requirement", "title": "The app uses the clipboard securely and only with user consent.", "text": "The app uses the clipboard securely and only with user consent.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r30", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#31", "kind": "OWASP MAS requirement", "title": "The app only permits trusted app extensions to interact with it.", "text": "The app only permits trusted app extensions to interact with it.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r31", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#32", "kind": "OWASP MAS requirement", "title": "The app securely handles intents.", "text": "The app securely handles intents.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r32", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#33", "kind": "OWASP MAS requirement", "title": "The app does not expose sensitive native functionality to WebView content.", "text": "The app does not expose sensitive native functionality to WebView content.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r33", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#34", "kind": "OWASP MAS requirement", "title": "The app only allows trusted WebView content to access local resources.", "text": "The app only allows trusted WebView content to access local resources.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r34", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#35", "kind": "OWASP MAS requirement", "title": "The app only allows trusted content in WebViews.", "text": "The app only allows trusted content in WebViews.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r35", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#36", "kind": "OWASP MAS requirement", "title": "The app does not unnecessarily expose sensitive data through its user interface.", "text": "The app does not unnecessarily expose sensitive data through its user interface.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r36", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#37", "kind": "OWASP MAS requirement", "title": "The app does not unnecessarily expose sensitive data through system notifications.", "text": "The app does not unnecessarily expose sensitive data through system notifications.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r37", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#38", "kind": "OWASP MAS requirement", "title": "The app removes or masks sensitive data from its views when moved to the background, when being recorded or when a screenshot is taken.", "text": "The app removes or masks sensitive data from its views when moved to the background, when being recorded or when a screenshot is taken.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r38", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#39", "kind": "OWASP MAS requirement", "title": "The app protects its sensitive screens against overlay attacks.", "text": "The app protects its sensitive screens against overlay attacks.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r39", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#40", "kind": "OWASP MAS requirement", "title": "The app prevents sensitive data from being exposed to, or captured by, accessibility services.", "text": "The app prevents sensitive data from being exposed to, or captured by, accessibility services.", "section": "MASVS-PLATFORM", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r40", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#41", "kind": "OWASP MAS requirement", "title": "The app detects if it is running on an unsupported OS version and reacts appropriately.", "text": "The app detects if it is running on an unsupported OS version and reacts appropriately.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r41", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#42", "kind": "OWASP MAS requirement", "title": "The app targets the latest platform version.", "text": "The app targets the latest platform version.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r42", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#43", "kind": "OWASP MAS requirement", "title": "The app detects if it must be updated and reacts appropriately.", "text": "The app detects if it must be updated and reacts appropriately.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r43", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#44", "kind": "OWASP MAS requirement", "title": "The app's third-party components are regularly checked for known vulnerabilities.", "text": "The app's third-party components are regularly checked for known vulnerabilities.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r44", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#45", "kind": "OWASP MAS requirement", "title": "The app uses the compiler-provided security features of the platform.", "text": "The app uses the compiler-provided security features of the platform.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r45", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#46", "kind": "OWASP MAS requirement", "title": "The app does not use deprecated APIs or functionality.", "text": "The app does not use deprecated APIs or functionality.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r46", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#47", "kind": "OWASP MAS requirement", "title": "The app uses standard APIs for security-critical functionality.", "text": "The app uses standard APIs for security-critical functionality.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r47", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#48", "kind": "OWASP MAS requirement", "title": "The app package does not contain malicious code.", "text": "The app package does not contain malicious code.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r48", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#49", "kind": "OWASP MAS requirement", "title": "The app loads dynamic code safely from trusted sources.", "text": "The app loads dynamic code safely from trusted sources.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r49", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#50", "kind": "OWASP MAS requirement", "title": "The app securely handles untrusted data.", "text": "The app securely handles untrusted data.", "section": "MASVS-CODE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r50", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#51", "kind": "OWASP MAS requirement", "title": "The app detects if it runs on a rooted/jailbroken device and reacts appropriately.", "text": "The app detects if it runs on a rooted/jailbroken device and reacts appropriately.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r51", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#52", "kind": "OWASP MAS requirement", "title": "The app detects when it is running inside an app-virtualization environment.", "text": "The app detects when it is running inside an app-virtualization environment.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r52", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#53", "kind": "OWASP MAS requirement", "title": "The app detects when it is running in an emulated or virtual device environment.", "text": "The app detects when it is running in an emulated or virtual device environment.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r53", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#54", "kind": "OWASP MAS requirement", "title": "The app implements device attestation.", "text": "The app implements device attestation.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r54", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#55", "kind": "OWASP MAS requirement", "title": "The app detects attacks by malware.", "text": "The app detects attacks by malware.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r55", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#56", "kind": "OWASP MAS requirement", "title": "The app implements app attestation.", "text": "The app implements app attestation.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r56", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#57", "kind": "OWASP MAS requirement", "title": "The app verifies the integrity of its resources.", "text": "The app verifies the integrity of its resources.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r57", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#58", "kind": "OWASP MAS requirement", "title": "The app detects unauthorized changes to its code and execution flow at runtime.", "text": "The app detects unauthorized changes to its code and execution flow at runtime.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r58", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#59", "kind": "OWASP MAS requirement", "title": "The app implements code obfuscation.", "text": "The app implements code obfuscation.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r59", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#60", "kind": "OWASP MAS requirement", "title": "The app applies resource obfuscation to hinder reverse engineering.", "text": "The app applies resource obfuscation to hinder reverse engineering.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r60", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#61", "kind": "OWASP MAS requirement", "title": "The app does not contain debug artifacts.", "text": "The app does not contain debug artifacts.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r61", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#62", "kind": "OWASP MAS requirement", "title": "The app applies application-level payload encryption in addition to transport-layer encryption.", "text": "The app applies application-level payload encryption in addition to transport-layer encryption.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r62", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#63", "kind": "OWASP MAS requirement", "title": "The app disables debug mechanisms.", "text": "The app disables debug mechanisms.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r63", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#64", "kind": "OWASP MAS requirement", "title": "The app detects debugger attachment at runtime and responds to protect sensitive operations.", "text": "The app detects debugger attachment at runtime and responds to protect sensitive operations.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r64", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#65", "kind": "OWASP MAS requirement", "title": "The app detects dynamic analysis tools and responds to protect sensitive operations.", "text": "The app detects dynamic analysis tools and responds to protect sensitive operations.", "section": "MASVS-RESILIENCE", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r65", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#66", "kind": "OWASP MAS requirement", "title": "The app adequately manages permissions.", "text": "The app adequately manages permissions.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r66", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#67", "kind": "OWASP MAS requirement", "title": "The app uses anonymization or pseudonymisation measures.", "text": "The app uses anonymization or pseudonymisation measures.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r67", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#68", "kind": "OWASP MAS requirement", "title": "The app does not use persistent or unique identifiers in a way that enables user tracking.", "text": "The app does not use persistent or unique identifiers in a way that enables user tracking.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r68", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#69", "kind": "OWASP MAS requirement", "title": "The app uses privacy-preserving functionality.", "text": "The app uses privacy-preserving functionality.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r69", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#70", "kind": "OWASP MAS requirement", "title": "The app informs the user about the privacy implications before performing an action.", "text": "The app informs the user about the privacy implications before performing an action.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r70", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#71", "kind": "OWASP MAS requirement", "title": "The app uses adequate defaults for privacy relevant actions.", "text": "The app uses adequate defaults for privacy relevant actions.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r71", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#72", "kind": "OWASP MAS requirement", "title": "The app provides an adequate privacy policy.", "text": "The app provides an adequate privacy policy.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r72", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#73", "kind": "OWASP MAS requirement", "title": "The app adequately declares all user collected data.", "text": "The app adequately declares all user collected data.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r73", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#74", "kind": "OWASP MAS requirement", "title": "The app adequately declares all tracking domains it connects to.", "text": "The app adequately declares all tracking domains it connects to.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r74", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#75", "kind": "OWASP MAS requirement", "title": "The app offers reproducible builds. (OUT OF SCOPE for the OWASP MAS EUDIW Profile)", "text": "The app offers reproducible builds. (OUT OF SCOPE for the OWASP MAS EUDIW Profile)", "section": "MASVS-PRIVACY", "page": null, "obligation": "out of scope", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r75", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#76", "kind": "OWASP MAS requirement", "title": "The app provides adequate controls to manage user data.", "text": "The app provides adequate controls to manage user data.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r76", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#77", "kind": "OWASP MAS requirement", "title": "The app provides adequate controls over the visibility of user data.", "text": "The app provides adequate controls over the visibility of user data.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r77", "pdf": null }, { "document": "OWASP MAS EUDI Wallet profile", "document_title": "OWASP MAS EUDI Wallet Profile Requirements Catalogue", "version": "v1.0", "id": "#78", "kind": "OWASP MAS requirement", "title": "The app requests user consent prior to any data processing.", "text": "The app requests user consent prior to any data processing.", "section": "MASVS-PRIVACY", "page": null, "obligation": "profile requirement", "legal_refs": [], "url": "/edi-stelsel-certification/requirements/owasp-mas-eudiw#r78", "pdf": null } ] }