NL-P-04P Part 2 requirements
This page lists every requirement of NL-P-04P Part 2 (PID Issuance & Lifecycle Management Requirements, Part 2, version RC1.0) as published on 6 November 2026. The PDF is authoritative: each requirement links to the page it is on. You can also read the full text or search all requirements.
52 entries: 52 requirements. Obligation: 51 mandatory, 1 conditional.
Legal basis of the document: eIDAS, CIR 2015/1502, CIR 2024/2977, CIR 2024/2981.
5.1 Revocation Triggers and Conditions
Read section 5.1 in the full text
REV-4.1-01
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.
Requirement · obligation: mandatory · PDF page 13
REV-4.1-02
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.
Requirement · obligation: mandatory · PDF page 13
REV-4.1-03
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.
Requirement · obligation: mandatory · PDF page 13
REV-4.1-04
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.
Requirement · obligation: mandatory · PDF page 14
REV-4.1-05
The PID Provider shall revoke every outstanding Technical PID it has issued to a Wallet Unit when that Wallet Unit is revoked.
Requirement · obligation: mandatory · PDF page 14
Referenced by: REV-5.2-09
REV-4.1-06
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.
Requirement · obligation: mandatory · PDF page 15
REV-5.1-07
[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.
Requirement · obligation: conditional · PDF page 15
How a CAB verifies this: A CAB verifies this requirement by reviewing the interface description with the authentic source and the subscription configuration, and by examining records of received events and of the revocations that followed.
REV-5.1-08
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.
Requirement · obligation: mandatory · PDF page 15
How a CAB verifies this: A CAB verifies this requirement by reviewing the procedure and its interface with the Wallet Providers, and by examining records of past decease cases for the notifications sent.
5.2 Revocation Procedures
Read section 5.2 in the full text
REV-4.2-01
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.
Requirement · obligation: mandatory · PDF page 16
Referenced by: REV-4.2-02, REV-4.2-03
REV-4.2-02
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.
Requirement · obligation: mandatory · PDF page 16
REV-4.2-03
The PID Provider shall complete the revocation of the Technical PIDs within the maximum time it has determined under REV-4.2-01.
Requirement · obligation: mandatory · PDF page 16
REV-4.2-04
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.
Requirement · obligation: mandatory · PDF page 17
REV-4.2-05 — The PID Provider shall not reinstate a Technical PID once it has been revoked.
The PID Provider shall not reinstate a Technical PID once it has been revoked.
Requirement · obligation: mandatory · PDF page 17
REV-4.2-06
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.
Requirement · obligation: mandatory · PDF page 17
REV-4.2-07 — The PID Provider shall determine the interval of the verification under REV4.2-06 as part of its risk assessment.
The PID Provider shall determine the interval of the verification under REV4.2-06 as part of its risk assessment.
Requirement · obligation: mandatory · PDF page 18
REV-5.2-08
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.
Requirement · obligation: mandatory · PDF page 18
How a CAB verifies this: A CAB verifies this requirement by reviewing the design of the overview and its authentication, for instance by inspecting that the overview is not reachable from a Wallet Unit, and by examining a sample of overviews against the administration.
Referenced by: REV-5.2-09
REV-5.2-09
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.
Requirement · obligation: mandatory · PDF page 18
How a CAB verifies this: A CAB verifies this requirement by reviewing the revocation flow and by examining records of past requests and of the revocations that followed.
Referenced by: REV-5.2-10, REV-5.2-13
REV-5.2-10
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.
Requirement · obligation: mandatory · PDF page 19
How a CAB verifies this: A CAB verifies this requirement by reviewing the interface and by examining records of forwarded requests and of the Wallet Provider's confirmation.
REV-5.2-11
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.
Requirement · obligation: mandatory · PDF page 19
How a CAB verifies this: A CAB verifies this requirement by reviewing the description of the reporting point and by examining that it works without a Wallet Unit.
Referenced by: REV-5.2-12, REV-5.2-13
REV-5.2-12
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.
Requirement · obligation: mandatory · PDF page 19
How a CAB verifies this: A CAB verifies this requirement by reviewing the procedure and by examining records of past reports for the forwarded messages.
REV-5.2-13
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.
Requirement · obligation: mandatory · PDF page 19
How a CAB verifies this: A CAB verifies this requirement by reviewing the procedure and by examining records of past reports for the verification performed.
REV-5.2-14
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.
Requirement · obligation: mandatory · PDF page 20
How a CAB verifies this: A CAB verifies this requirement by reviewing the procedure and the supporting system, and by examining a sample of employee-initiated revocations for the two approvals.
Referenced by: REV-5.2-15, REV-5.2-16
REV-5.2-15
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.
Requirement · obligation: mandatory · PDF page 20
How a CAB verifies this: A CAB verifies this requirement by reviewing the risk assessment and the documented maximum time.
Referenced by: REV-5.2-16
REV-5.2-16
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.
Requirement · obligation: mandatory · PDF page 20
How a CAB verifies this: A CAB verifies this requirement by reviewing the monitoring and by examining records of approval times.
5.3 Status Service Update
Read section 5.3 in the full text
REV-4.3-01
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].
Requirement · obligation: mandatory · PDF page 20
REV-4.3-02
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].
Requirement · obligation: mandatory · PDF page 21
REV-4.3-03
The PID Provider shall set the revocation status of a Technical PID in its status mechanism to revoked when that Technical PID is revoked.
Requirement · obligation: mandatory · PDF page 21
REV-4.3-04
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.
Requirement · obligation: mandatory · PDF page 21
REV-4.3-05
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.
Requirement · obligation: mandatory · PDF page 22
Referenced by: REV-4.3-06, REV-4.3-07
REV-4.3-06
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.
Requirement · obligation: mandatory · PDF page 22
REV-4.3-07
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.
Requirement · obligation: mandatory · PDF page 22
5.4 Wallet User Notification
Read section 5.4 in the full text
REV-4.4-01
The PID Provider shall notify the Wallet User when the Technical PIDs issued to that Wallet User's Wallet Unit are revoked.
Requirement · obligation: mandatory · PDF page 23
REV-4.4-02
The PID Provider shall deliver the revocation notification to the Wallet User through the government electronic mailbox (MijnOverheid Berichtenbox).
Requirement · obligation: mandatory · PDF page 23
REV-4.4-03
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.
Requirement · obligation: mandatory · PDF page 23
REV-4.4-04 — The revocation notification shall identify the revoked PID and state that it can no longer be used.
The revocation notification shall identify the revoked PID and state that it can no longer be used.
Requirement · obligation: mandatory · PDF page 24
REV-5.4-05
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.
Requirement · obligation: mandatory · PDF page 24
How a CAB verifies this: A CAB verifies this requirement by reviewing the notification service and by examining a sample of revocations for the notices sent.
REV-5.4-06
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.
Requirement · obligation: mandatory · PDF page 24
How a CAB verifies this: A CAB verifies this requirement by reviewing the notification templates and by examining a sample of notices.
6.1 Expiry Detection and Notification
Read section 6.1 in the full text
EXP-5.1-01 — The PID Provider shall detect, in its administration, when the validity period of a Technical PID has ended.
The PID Provider shall detect, in its administration, when the validity period of a Technical PID has ended.
Requirement · obligation: mandatory · PDF page 25
EXP-5.1-02
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.
Requirement · obligation: mandatory · PDF page 25
EXP-5.1-03
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.
Requirement · obligation: mandatory · PDF page 25
Referenced by: EXP-5.1-04
EXP-5.1-04
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.
Requirement · obligation: mandatory · PDF page 26
6.2 Post-Expiry Behaviour
Read section 6.2 in the full text
EXP-5.2-01 — The PID Provider shall not revoke a Technical PID solely because its validity period has ended.
The PID Provider shall not revoke a Technical PID solely because its validity period has ended.
Requirement · obligation: mandatory · PDF page 26
EXP-5.2-02
The PID Provider need not maintain revocation-status information for a Technical PID after its validity period has ended.
Requirement · obligation: mandatory · PDF page 26
6.3 Pre-Deletion Security Measures
Read section 6.3 in the full text
EXP-5.3-01
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.
Requirement · obligation: mandatory · PDF page 27
6.4 Expired PID Cleanup and Deletion
Read section 6.4 in the full text
EXP-5.4-01
The PID Provider shall remove expired Technical PIDs from its administration in accordance with a defined cleanup procedure.
Requirement · obligation: mandatory · PDF page 27
EXP-5.4-02
The PID Provider shall determine, as part of its risk assessment, the retention period after which expired Technical PID records are removed.
Requirement · obligation: mandatory · PDF page 27
EXP-5.4-03
The PID Provider shall not remove records that are required for audit or statuspublication purposes before the end of their retention period.
Requirement · obligation: mandatory · PDF page 28
7.1 User-Initiated Deletion
Read section 7.1 in the full text
DEL-6.1-01 — The Wallet Unit shall allow the Wallet User to delete a PID it holds, on the user's own initiative.
The Wallet Unit shall allow the Wallet User to delete a PID it holds, on the user's own initiative.
Requirement · obligation: mandatory · PDF page 29
DEL-6.1-02
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.
Requirement · obligation: mandatory · PDF page 29
DEL-6.1-03 — The Wallet Unit shall obtain confirmation from the Wallet User before deleting a PID.
The Wallet Unit shall obtain confirmation from the Wallet User before deleting a PID.
Requirement · obligation: mandatory · PDF page 29
7.2 PID Provider Notification
Read section 7.2 in the full text
DEL-6.2-01 — The Wallet Unit shall not notify the PID Provider of a user-initiated deletion of a PID.
The Wallet Unit shall not notify the PID Provider of a user-initiated deletion of a PID.
Requirement · obligation: mandatory · PDF page 30
7.3 PID Revocation
Read section 7.3 in the full text
DEL-6.3-01
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.
Requirement · obligation: mandatory · PDF page 30