Malabo Convention (AU) - Comoros
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 | KM Malabo |
| Region | Middle East & Africa |
| Country or scope | Comoros |
| Sector | Privacy |
| In your workspace | Off until you switch it on in Compliance › Manage. |
How Safeguard covers KM Malabo
- 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).
| Requirement | What Safeguard checks | Decided by |
|---|---|---|
KM-MAL-13 Transparent and Accurate Processing Records | Personal-data processing must be lawful, transparent and accurate, which presupposes a maintained record of the software components that perform the processing (Malabo Convention Art. 13). | Scan |
KM-MAL-13-6 Confidentiality Principle: Identifiable Components | The confidentiality principle requires knowing precisely which software handles personal data, so components must carry standard identifiers such as PURL or CPE that tie safeguards to specific packages (Malabo Convention Art. 13, Principle 6). | Scan |
KM-MAL-20 Processor and Third-Party Accountability | Processing performed on a controller's behalf must remain under the controller's authority and instructions, so third-party components need named, accountable suppliers (Malabo Convention Art. 20). | Scan |
KM-MAL-21 Security of Processing Systems | Controllers must take all appropriate precautions to keep data from being altered, destroyed or accessed by unauthorised third parties; integrity hashes on components let tampering be detected (Malabo Convention Art. 21). | Scan |
KM-MAL-21-V Incident and Breach-Impact Readiness | Judging whether processing systems remain secure after an incident requires knowing the exact versions of the components in operation (Malabo Convention Art. 21). | Scan |
KM-MAL-10 Declared and Documented Processing | Preliminary formalities require processing operations to be declared to the supervisory authority, which presupposes dated, identifiable documentation of the systems used (Malabo Convention Art. 10, preliminary formalities). | Scan |
Policy templates
All 22 from the standard set, adapted to KM Malabo.
Malabo Convention (AU) - Central African Republic
National data-protection law: technical safeguards, records of processing software, third-party/processor accountability, and integrity controls.
Malabo Convention (AU) - Djibouti
National data-protection law: technical safeguards, records of processing software, third-party/processor accountability, and integrity controls.