Compliance FrameworksEurope
North Macedonia Law on Personal Data Protection 2020
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 name | MK LPDP |
| Region | Europe |
| Country or scope | North Macedonia |
| Sector | Privacy |
| In your workspace | Off until you switch it on in Compliance › Manage. |
How Safeguard covers MK LPDP
- 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).
| Requirement | What Safeguard checks | Decided by |
|---|---|---|
MK-LPDP-SEC Security of Processing | Controllers and processors must implement technical measures ensuring the ongoing confidentiality, integrity and resilience of processing systems; integrity hashes on software components evidence this control (LPDP 2020 GDPR Art. 32-equivalent security obligation) | Scan |
MK-LPDP-ROP Records of Processing Activities | Controllers must keep records of their processing activities, which presupposes an inventory of the software systems and components performing the processing (LPDP 2020 GDPR Art. 30-equivalent records obligation) | Scan |
MK-LPDP-PROC Processor Guarantees | Only processors providing sufficient guarantees of appropriate technical measures may be engaged, requiring visibility into who supplies each component of the processing software (LPDP 2020 GDPR Art. 28-equivalent processor obligation) | Scan |
MK-LPDP-BRE Breach Notification Readiness | Personal data breaches must be notified to the Agency within 72 hours, requiring the ability to identify precisely which software components were affected (LPDP 2020 GDPR Art. 33-equivalent breach obligation) | Scan |
MK-LPDP-DBD Data Protection by Design | State-of-the-art safeguards must be embedded in processing systems from design onward, which requires knowing the exact versions of components in use (LPDP 2020 GDPR Art. 25-equivalent by-design obligation) | Scan |
Policy templates
All 22 from the standard set, adapted to MK LPDP.