South Africa's Protection of Personal Information Act (POPIA, Act 4 of 2013) looks like the GDPR from a distance, but it protects companies as well as people, reports every security compromise rather than only risky ones, and gives the Information Regulator criminal as well as administrative tools. Teams that extend a GDPR programme to South Africa without adjusting for those points under-scope their inventories, under-report incidents and miss the information officer registration step. This guide compares the two laws for privacy, security and GRC leads who already run a GDPR programme and need to know what to reuse and what to rebuild. It goes deeper on the differences than the South Africa POPIA Guide, which covers POPIA on its own. Status checked on 14 November 2026 against EUR-Lex, the POPIA text on the Law Library (lawlibrary.org.za) and the Information Regulator.
Key takeaways
- Juristic persons are data subjects: POPIA protects identifiable, existing juristic persons such as companies and trusts as well as living natural persons, while the GDPR's Recital 14 excludes legal persons, so B2B records fall inside POPIA scope.
- Every compromise is reportable: section 22 is triggered by reasonable grounds to believe personal information was accessed or acquired by an unauthorised person, and the Regulator's 2025 fact sheet says every compromise must be reported regardless of risk level.
- No fixed clock, but no waiting either: POPIA requires notice "as soon as reasonably possible" through the Regulator's eServices Portal, against the GDPR's 72 hour rule for the supervisory authority.
- Section 19 is a cycle: identify foreseeable risks, maintain safeguards, verify them regularly and update them, with due regard to generally accepted security practice; GDPR Art. 32 evidence fits, but the verification step needs its own records.
- Different penalty model: administrative fines under section 109 are capped at R10 million, some offences carry imprisonment of up to 10 years under section 107, and section 99 civil claims do not require proof of intent or negligence.
Short answer: what carries over and what does not
A GDPR programme covers most of POPIA's eight conditions for lawful processing. The South African layer is about scope, notification, the information officer and transfers.
| GDPR artefact | Reuse for POPIA? | What to change |
|---|---|---|
| Art. 30 record of processing | Reuse with edits | Add juristic person data (supplier, customer and partner company records) and tag South African processing |
| Art. 32 security programme | Reuse | Add dated evidence for the section 19(2) cycle: risk identification, safeguards, verification, updates |
| Art. 33 and 34 breach runbook | Adapt | Report every compromise to the Regulator via the eServices Portal; no "unlikely to result in a risk" exit; data subject notice unless identity cannot be established |
| DPO appointment | Adapt | Information officer and deputies, registered with the Regulator before taking up duties (s55(2), s56) |
| Art. 28 processor terms | Reuse with edits | Section 21 written contract binding the operator to s19 measures and to notify you immediately of suspected unauthorised access |
| SCCs and transfer assessments | Partly reusable | Map each export from South Africa to a section 72 ground; check s57 prior authorisation for special or children's information to non-adequate countries |
| Legitimate interest assessments | Reuse | Section 11(1)(f) legitimate interests of the responsible party or a third party is close to GDPR Art. 6(1)(f) |
Side-by-side comparison
| Topic | GDPR (Regulation (EU) 2016/679) | POPIA (Act 4 of 2013) |
|---|---|---|
| Territorial reach | EU establishment (Art. 3(1)); offering goods or services to, or monitoring, people in the Union (Art. 3(2)) | Responsible party domiciled in South Africa, or not domiciled but using automated or non-automated means in the Republic, other than only to forward information (s3) |
| Who is protected | Natural persons (Art. 4(1)) | Living natural persons and, where applicable, identifiable existing juristic persons (s1) |
| Roles | Controller, processor | Responsible party, operator (s1) |
| Lawful grounds | Six bases (Art. 6(1)) | Six justifications in s11(1)(a) to (f), including a legitimate interest of the data subject |
| Sensitive data | Art. 9(1) special categories | Special personal information (s26): religious or philosophical beliefs, race or ethnic origin, trade union membership, political persuasion, health or sex life, biometric information, certain criminal behaviour |
| Security duty | Art. 32(1) risk-based measures, naming pseudonymisation, encryption, resilience, restore and testing | s19: appropriate, reasonable measures plus a four-step risk cycle and due regard to generally accepted practice |
| Prior approval | Prior consultation only after a high-risk DPIA (Art. 36) | Prior authorisation from the Regulator for listed processing (s57) |
| Automated decisions | Art. 22 | s71: no decision with legal or substantial effect based solely on automated profiling, unless a contract or law exception applies with protective measures |
| Maximum administrative fine | EUR 20 million or 4% of worldwide annual turnover, whichever is higher (Art. 83(5)); EUR 10 million or 2% (Art. 83(4)) | R10 million (s109(2)(c)), adjustable by the Minister in line with inflation (s109(10)) |
| Criminal sanctions | Left to member state law | s107: up to 10 years' imprisonment, a fine or both for the most serious offences; up to 12 months for others |
| Civil liability | Art. 82 compensation for material or non-material damage | s99 action by the data subject, or the Regulator at their request; intent or negligence need not be shown |
Article references are paraphrased from the official texts; read the provisions themselves before relying on a detail.
Juristic persons: the scope difference that changes inventories
Threat model
The incidents are familiar: a CRM export, a compromised procurement portal, a leaked vendor master file. Under the GDPR a file of company names, registration numbers and bank details may hold little personal data beyond named contacts. Under POPIA the same file relates to identifiable existing juristic persons and is personal information in its own right, so the compromise is a section 22 event even if no individual is named.
Architecture in words
Extend the data inventory with a "juristic person" data subject category for South African processing. Tag supplier, customer, partner and tenant records in ERP, procurement, CRM, billing and credit systems. Apply the same access controls, retention rules and incident triage to those stores as to customer personal data. DLP and data discovery rules tuned only to natural person identifiers will not find these records, so add rules for company registration numbers and bank account fields.
Failure modes
- B2B blind spot: procurement and finance systems are left out of the privacy inventory because "they hold no personal data".
- Under-reporting: an incident affecting only corporate customer records is closed without a section 22 assessment.
- Rights handling: access and correction requests from companies under s23 and s24 are routed to sales or legal rather than the privacy process.
Decision
Organisations with a South African establishment or systems in South Africa should treat juristic person data as in scope by default. Groups that only sell into South Africa from abroad should check the section 3 "means in the Republic" test first, because POPIA's reach depends on domicile or use of means in South Africa rather than on targeting alone.
Section 19 safeguards versus Article 32
Both duties are risk-based and technology-neutral, and one control set can evidence both. The difference is emphasis. GDPR Art. 32(1) names outcomes: pseudonymisation and encryption, ongoing confidentiality, integrity, availability and resilience, timely restoration, and regular testing of effectiveness. POPIA section 19 names a process.
| Step | POPIA source | GDPR closest equivalent | Evidence that satisfies both |
|---|---|---|---|
| Prevent loss, damage, unauthorised destruction and unlawful access | s19(1) | Art. 32(1) and (2) | Control framework mapped to ISO/IEC 27001 or NIST CSF 2.0 |
| Identify reasonably foreseeable internal and external risks | s19(2)(a) | Art. 32(2) risk assessment | Dated risk register naming personal information assets |
| Establish and maintain safeguards | s19(2)(b) | Art. 32(1)(a) and (b) | Control owners, configuration baselines |
| Regularly verify effective implementation | s19(2)(c) | Art. 32(1)(d) testing | Scan results, penetration test reports, tool health checks, licence status |
| Update in response to new risks or deficiencies | s19(2)(d) | Implied by Art. 32(1)(d) | Change log tied to findings and incidents |
| Due regard to generally accepted practice | s19(3) | "State of the art" in Art. 32(1) | Statement of applicability or framework profile |
Why the verify step matters: on 4 July 2023 the Regulator fined the Department of Justice and Constitutional Development R5 million for not complying with an enforcement notice that followed its failure to renew its anti-virus, SIEM and intrusion detection licences. Expired tooling is exactly what a section 19(2)(c) verification should catch. See the GDPR Compliance Guide for Security Teams for the GDPR side.
Notification: section 22 versus Articles 33 and 34
The rules compared
| Question | GDPR | POPIA |
|---|---|---|
| Trigger | Personal data breach, unless unlikely to result in a risk to rights and freedoms (Art. 33(1)) | Reasonable grounds to believe personal information was accessed or acquired by an unauthorised person (s22(1)); the 2025 fact sheet says report every compromise regardless of risk |
| Regulator deadline | Without undue delay and where feasible within 72 hours of awareness | As soon as reasonably possible after discovery, allowing for law enforcement needs and steps to establish scope and restore integrity (s22(2)) |
| Individuals | Without undue delay where high risk is likely, with Art. 34(3) exceptions | Every affected data subject unless identity cannot be established (s22(1)); delay only if a public body or the Regulator says notice would impede a criminal investigation (s22(3)) |
| Channel | Lead or competent supervisory authority | Information Regulator eServices Portal |
| Individual notice contents | Nature of the breach, contact point, likely consequences, measures (Art. 34(2) by reference to Art. 33(3)) | Possible consequences, measures taken or intended, recommended steps, and the identity of the unauthorised person if known (s22(5)) |
| Processor or operator | Notify the controller without undue delay (Art. 33(2)) | Notify the responsible party immediately (s21(2)) |
| Publicity | Public communication where individual notice is disproportionate (Art. 34(3)(c)) | The Regulator may direct publicity where it would protect data subjects (s22(6)) |
Architecture in words
Run one triage with two decision paths. The GDPR path applies the risk test and the 72 hour clock. The POPIA path asks a simpler question: are there reasonable grounds to believe someone unauthorised accessed or acquired the information? If yes, report to the Regulator once reasonably sure, without waiting for the investigation to finish, and update the report as facts emerge. Data subject notices go in writing by post, email, a prominent website notice, news media or as the Regulator directs (s22(4)). The fact sheet gives 30 to 90 days as a rule of thumb for keeping a website notice up.
Failure modes
- Applying the GDPR risk exit: deciding a South African incident is "unlikely to result in a risk" and not reporting it, when POPIA has no such exit.
- Waiting for forensics: treating "as soon as reasonably possible" as "when the investigation is complete"; the fact sheet says confirmation and a finished investigation are not required first.
- No portal access: nobody on the incident team holds working eServices Portal credentials at 2am.
- Soft operator deadlines: contracts that copy GDPR "without undue delay" wording instead of the section 21 "immediately" standard with a measurable number.
Worked scenario
A retailer with operations in Johannesburg and Dublin finds that a service account key for its loyalty platform was used from an unknown IP to read member records, including some business members. The GDPR path assesses risk for Irish members, decides it is likely, notifies the Data Protection Commission within 72 hours and notifies affected Irish members. The POPIA path does not run a risk test: the key's misuse gives reasonable grounds to believe information was accessed, so the information officer files on the eServices Portal as soon as the team is reasonably sure, notifies individual and juristic person members in writing, and updates the Regulator filing when the investigation closes. Both paths revoke and rotate the key and record the root cause. See the Breach Notification Laws by Country Guide.
Information officer versus DPO
| Aspect | GDPR DPO | POPIA information officer |
|---|---|---|
| When required | Public bodies; core large-scale regular and systematic monitoring; core large-scale special category or criminal data (Art. 37(1)) | Every public and private body has one; deputies must be designated as PAIA s17 requires (s56) |
| Registration | Contact details communicated to the supervisory authority | Must be registered with the Regulator before taking up duties (s55(2)), via the Information Officer Portal |
| Duties | Inform, advise, monitor, cooperate with the authority | Encourage compliance, handle requests, work with the Regulator on investigations, ensure compliance (s55(1)) |
| Independence | No instructions on tasks; reports to highest management (Art. 38(3)) | Powers and duties may be delegated to deputy information officers (s56) |
Decision: a group DPO can act as the information officer's deputy or adviser, but the registration has to be in place for the South African entity, and someone in South Africa should hold eServices Portal access. Re-check registration after any leadership change. See DPO vs CPO.
Cross-border transfers
The GDPR has a full toolkit: adequacy decisions under Art. 45, safeguards under Art. 46(2) including standard clauses, BCRs under Art. 47 and derogations under Art. 49. POPIA section 72 has five grounds and no regulator-issued standard clauses:
- (a) Adequate protection: the recipient is subject to a law, binding corporate rules or a binding agreement giving substantially similar protection, including on onward transfers. Most organisations use this ground through contract.
- (b) Consent: workable for narrow consumer cases, weak for employees.
- (c) and (d) Contract necessity: with the data subject, or concluded in their interest with a third party.
- (e) Benefit of the data subject: consent impracticable but likely to be given.
Reusing EU SCCs: EU SCCs can support ground (a) as a binding agreement, but check they extend to juristic person data, which they were not written for, and to onward transfers. Prior authorisation: section 57 requires the Regulator's authorisation before transferring special personal information or children's information to a foreign country without adequate protection under section 72. See the Standard Contractual Clauses (SCCs) Guide and the International Data Transfers Map.
Information Regulator enforcement
The GDPR runs through national supervisory authorities with a one-stop-shop. POPIA has one regulator with assessment, enforcement notice and infringement notice powers. The R5 million fine against the Department of Justice and Constitutional Development in July 2023 followed its failure to comply with an enforcement notice by the deadline, and it did not appeal. The practical lesson is that the enforcement notice is the point of maximum risk: once one arrives, its deadline matters more than the original incident.
- Administrative: fines up to R10 million under section 109.
- Criminal: section 107 penalties, up to 10 years for offences such as those in ss100 and 103(1), and up to 12 months for others.
- Civil: section 99 damages without proof of fault, subject to listed defences.
When to lead with which law
- Lead with the GDPR when South Africa is one market among many: keep the global control set and add the POPIA layer for juristic persons, notification, the information officer and section 72.
- Lead with POPIA when you are a South African group expanding into Europe: your inventory already covers juristic persons; add GDPR items such as the 72 hour clock, the Art. 34 high-risk test and lead authority mapping.
Small versus large organisations: a small business needs a registered information officer, operator contracts with an immediate notice clause and a portal-ready incident process before anything else. A multinational should keep one control set and one incident register, with a South African decision path that cannot be closed on a GDPR risk exit.
Where identity fits
A misused service account, API key or OAuth token that reaches personal information gives reasonable grounds to believe information was accessed, so non-human credential misuse is a section 22 event on its own. List leaked, over-privileged and unrotated machine credentials as foreseeable risks in the section 19(2) register and record when each was verified. See the Service Account Security Guide.
Implementing a dual programme
- Scope: apply the s3 test to each entity and system; tag South African processing, including juristic person records, in the record of processing.
- Register: register the information officer and deputies and record the registration date.
- Run the s19 cycle: one risk register and verification calendar feeding both Art. 32 and s19 evidence.
- Rebuild the runbook: add a POPIA path with no risk exit, eServices Portal access for named staff, and s22(5) notice templates.
- Test: tabletop a compromise affecting only corporate customer records and confirm the POPIA path reports it.
- Fix contracts: s21 immediate notice with a measurable deadline; s72 ground recorded for each export.
- Screen projects: check new processing against s57 before build.
Detection and measurement
- Reporting latency: hours from reasonable grounds to eServices filing, and from awareness to GDPR notice.
- Inventory coverage: share of procurement, finance and CRM systems with juristic person data tagged (target: 100%).
- Verification cadence: safeguards verified within their scheduled interval, including security tool licence status.
- Contract coverage: share of operators with a s21 clause and a measurable notice deadline.
- Credential hygiene: machine credentials reaching personal information with a named owner and rotation date.
Framework mapping
| Requirement (GDPR / POPIA) | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Lawful grounds (Art. 6 / s11) | GV.OC-03 | PT-2, PT-3 | A.5.34 |
| Inventory incl. juristic persons (Art. 30 / s17) | ID.AM-07 | PT-3 | A.5.9, A.5.34 |
| Risk identification and safeguards (Art. 32 / s19) | GV.OC-03, PR.DS-01 | RA-3, AC-6, IA-5 | A.8.2, A.8.24 |
| Notification (Arts. 33, 34 / s22) | RS.CO-02, RS.CO-03 | IR-6, IR-8 | A.5.24, A.5.26 |
| Processors and operators (Art. 28 / ss20, 21) | GV.SC-05 | SA-9 | A.5.19, A.5.20 |
| Transfers (Arts. 44 to 49 / s72) | GV.OC-03 | SA-9 | A.5.14 |
Common failure patterns
- Natural-person-only inventory: juristic person data left out, so B2B compromises are never assessed.
- GDPR risk exit applied to South Africa: compromises judged low risk are not reported to the Regulator.
- Unregistered information officer: the role exists on paper but the s55(2) registration was never made or lapsed with a leadership change.
- Verification without records: controls are tested but there is no dated evidence of the s19(2)(c) step.
- Ignoring enforcement notice deadlines: the 2023 Justice Department fine followed a missed enforcement notice deadline, not the original lapse alone.
Practitioner checklist
- Add juristic person data to the South African record of processing and to discovery rules.
- Register the information officer and deputies and recheck after leadership changes.
- Keep a dated s19(2) risk register with verification evidence, including tool licence status.
- Give a POPIA path in incident triage with no risk exit and named eServices Portal users.
- Pre-approve s22(5) notice templates for individuals and companies.
- Write a measurable "immediately" deadline into every s21 operator contract.
- Record a s72 ground for each export and screen special or children's information against s57.
- Treat machine credential misuse as reasonable grounds for a s22 assessment.
Standards and references
- Law Library (lawlibrary.org.za): Protection of Personal Information Act 4 of 2013
- EUR-Lex: Regulation (EU) 2016/679, General Data Protection Regulation
- Information Regulator (South Africa): official website
- Acts Online: Information Regulator Fact Sheet on Handling of Security Compromises (2025)
- SAnews: Information Regulator fines Justice Department
- NIST: Cybersecurity Framework 2.0
This guide compares the GDPR and South Africa's POPIA as of 14 November 2026 and is not legal advice. Related NHI Mgmt Group resources: South Africa POPIA Guide · GDPR vs LGPD · GDPR Compliance Guide for Security Teams · Global Privacy Regulatory Map