26 controls
0 frameworks share controls with it
Senegal
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
No measured overlap with another framework in the corpus.
Every control
| Code | Control | Also in |
|---|
SENEGAL-1 | Scope, Lawful Basis (Senegal Law 2008-12) | 0 |
SENEGAL-2 | Consent, Notice, Sensitive Data | 0 |
SENEGAL-3 | Data Subject Rights | 0 |
SENEGAL-4 | Security and Cross-Border | 0 |
SENEGAL-5 | CDP Notification, DPO, Governance | 0 |
SENEGAL-6 | Breach and Enforcement | 0 |
SN-DPL-1.1 | Scope and Application | 0 |
SN-DPL-10.1 | Direct Marketing Restrictions | 0 |
SN-DPL-11.1 | Personal Data Correspondent Function | 0 |
SN-DPL-12.1 | Records of Processing | 0 |
SN-DPL-13.1 | Automated Decision Making | 0 |
SN-DPL-14.1 | Cooperation with CDP Investigations | 0 |
SN-DPL-15.1 | Sanctions and Penalties Awareness | 0 |
SN-DPL-16.1 | Health Data Specific Rules | 0 |
SN-DPL-17.1 | Data Breach Awareness and Response | 0 |
SN-DPL-2.1 | CDP Registration of Processing | 0 |
SN-DPL-3.1 | Lawful Basis for Processing | 0 |
SN-DPL-3.2 | Consent Requirements | 0 |
SN-DPL-4.1 | Information to Data Subjects | 0 |
SN-DPL-5.1 | Data Subject Rights | 0 |
SN-DPL-5.2 | Right of Access | 0 |
SN-DPL-6.1 | Sensitive Data Processing | 0 |
SN-DPL-7.1 | Data Security Measures | 0 |
SN-DPL-7.2 | Confidentiality of Processors | 0 |
SN-DPL-8.1 | Cross-Border Transfer Restrictions | 0 |
SN-DPL-9.1 | Data Retention Limits | 0 |
Tell me when Senegal Law on Personal Data Protection (Law No. 2008-12) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Incident response plan
- Incident response plan and playbooks
- Tabletop and functional exercise records
- Incident reporting metrics
- SOC operating procedures
- Post-incident reports with corrective actions
- Lawful basis register per processing
- Consent records (granular and withdrawable)
- Direct collection notification evidence
- Arabic + French privacy notices
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for Senegal Law on Personal Data Protection (Law No. 2008-12), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition