Compliance FrameworksAsia-Pacific
Tajikistan Law on Protection of Personal Data
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 | TJ PDPL |
| Region | Asia-Pacific |
| Country or scope | Tajikistan |
| Sector | Privacy |
| In your workspace | Off until you switch it on in Compliance โบ Manage. |
How Safeguard covers TJ PDPL
- 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 |
|---|---|---|
TJ-PDPL-SEC Protection of Personal Data | Owners and operators must take measures preventing unlawful access to, destruction, modification, blocking or copying of personal data; verifiable integrity hashes on software components evidence protection against modification (Law No. 1537 protection obligations) | Scan |
TJ-PDPL-INV Database and System Inventory | Protection duties attach to personal data databases and the systems operating them, which presupposes an inventory of the software components those systems comprise (Law No. 1537 owner/operator obligations) | Scan |
TJ-PDPL-THIRD Delegated Processing Accountability | Delegating processing to third persons does not relieve the owner of protection responsibility, requiring visibility into the suppliers behind the software used for processing (Law No. 1537 delegated-processing provisions) | Scan |
TJ-PDPL-VER Maintained Security of Systems | Protection measures must remain effective throughout processing, which requires knowing exact versions of deployed components so weaknesses can be assessed and corrected (Law No. 1537 ongoing-protection duty) | Scan |
TJ-PDPL-DOC Documented Protection Measures | Owners and operators must be able to demonstrate the protective measures adopted, supported by a formally identified, timestamped record of the software in use (Law No. 1537 accountability duties) | Scan |
Policy templates
All 22 from the standard set, adapted to TJ PDPL.