Safeguard Docs
Compliance FrameworksEurope

Luxembourg Data Protection Law of 1 August 2018

National data-protection law: technical safeguards, records of processing software, third-party/processor accountability, and integrity controls.

National data-protection law: technical safeguards, records of processing software, third-party/processor accountability, and integrity controls.

Short nameLU DPA
RegionEurope
Country or scopeLuxembourg
SectorPrivacy
In your workspaceOff until you switch it on in Compliance โ€บ Manage.

How Safeguard covers LU DPA

  • Scan requirements: 6, all decided by a scan.
  • Controls: the scan requirements below.
  • Automated tests: none map to it directly. You can link any automated test to its controls yourself (how).
  • Policy templates: 22 from the standard set.

How each kind of coverage works, and what the readiness score counts: Compliance frameworks.

What a scan checks

Each scan of a product checks these 6 requirements against what the scan found, including the product's software inventory (SBOM).

RequirementWhat Safeguard checksDecided by
LU-DPA-A32 Security of ProcessingTechnical and organisational measures appropriate to the risk must safeguard systems that process personal data; verifiable integrity hashes on deployed software components evidence this control (GDPR Art. 32, as given effect in Luxembourg by the Law of 1 August 2018).Scan
LU-DPA-A5F Integrity and Confidentiality PrinciplePersonal data must be processed in a manner ensuring its security and integrity, which requires the processing software stack to consist of components with known, assessable versions (GDPR Art. 5(1)(f), applied alongside the Law of 1 August 2018).Scan
LU-DPA-A30 Records of Processing SystemsControllers and processors must maintain records of processing activities, which presupposes an inventory of the software systems and components through which personal data flows (GDPR Art. 30; the Law of 1 August 2018).Scan
LU-DPA-A28 Processor and Vendor AccountabilityProcessing carried out on behalf of a controller may only use processors offering sufficient guarantees, so third-party software components in the processing chain must have identifiable suppliers (GDPR Art. 28; the Law of 1 August 2018).Scan
LU-DPA-A33 Breach-Notification ReadinessPersonal data breaches must be notified to the supervisory authority without undue delay and where feasible within 72 hours, which requires affected software components to be rapidly and unambiguously identifiable (GDPR Art. 33; the Law of 1 August 2018).Scan
LU-DPA-A24 Accountability of the ControllerResponsibility for processing operations must be demonstrable, which includes documented provenance of who produced the record of the software estate that processes personal data (GDPR Art. 24 and Art. 5(2); the Law of 1 August 2018).Scan

Policy templates

All 22 from the standard set, adapted to LU DPA.

On this page