Safeguard Docs
Compliance FrameworksEurope

Moldova Law No. 133 on Personal Data Protection

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 nameMD L133
RegionEurope
Country or scopeMoldova
SectorPrivacy
In your workspaceOff until you switch it on in Compliance โ€บ Manage.

How Safeguard covers MD L133

  • Scan requirements: 5, 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 5 requirements against what the scan found, including the product's software inventory (SBOM).

RequirementWhat Safeguard checksDecided by
MD-133-30 Security and Confidentiality of ProcessingControllers must apply organizational and technical measures protecting personal data against destruction, alteration and unauthorized access; verifiable integrity hashes on the software components processing data evidence this control (Law 133 Art. 30)Scan
MD-133-30-PROC Processor GuaranteesWhen processing is carried out on the controller's behalf, the processor must provide sufficient guarantees of technical security measures, requiring knowledge of the suppliers behind the processing software (Law 133 Art. 30 processor provisions)Scan
MD-133-REG Registration of Processing OperationsControllers must notify and register their processing operations with the National Center, which presupposes an inventory of the software systems performing the processing (Law 133 notification/registration provisions)Scan
MD-133-VER Currency of Processing SystemsMaintaining adequate security over time requires knowing the exact versions of deployed software components so that weaknesses can be assessed and corrected (Law 133 Art. 30 ongoing-security obligation)Scan
MD-133-DOC Documented AccountabilityControllers must be able to demonstrate the measures taken to protect processing, supported by a formally identified and timestamped record of the software in use (Law 133 accountability obligations)Scan

Policy templates

All 22 from the standard set, adapted to MD L133.

On this page