You do not need to guess what the Information Regulator will fault in your technology estate. It has already told you, in enforcement notice after enforcement notice, and it keeps naming the same handful of failures.
Since POPIA’s enforcement provisions came into force on 1 July 2021, South Africa’s Information Regulator has moved from guidance to action — issuing enforcement notices, an infringement notice with a R5 million administrative fine against a government department, and public statements naming the entities that fell short. Read those actions together and a pattern emerges. The Regulator is not chasing exotic attacks or novel legal theories. It is repeatedly citing the same basic, preventable technical failures. That makes its enforcement record something more useful than a warning: it is a checklist you can work through before you are the subject of one.
Section 19 of POPIA requires you to secure the integrity and confidentiality of personal information through appropriate, reasonable technical and organisational measures. That phrase is doing a lot of work, and the Regulator has been filling it in through the specifics it chooses to act on. Here are six of those specifics.
Free · 4 minutes
Would you survive contact with a determined attacker — or an auditor?
Fourteen questions on access, patching, detection, and recovery — the basics that prevent most real incidents, and the ones most often assumed rather than verified. Banded finding on screen, full sheet by email.
1. Access control that lets weak credentials through
In the Dis-Chem matter, the Regulator’s finding was blunt: the company did not identify the risk of weak passwords and did not prevent their use. In the enforcement notice issued to the Electoral Commission, the finding was that it lacked adequate access control measures to protect the confidentiality of the personal information in its possession. Two very different organisations, the same root cause.
This is the least glamorous control on the list and the one that turns up most often. The technology answer is not complicated — enforced password policy, multi-factor authentication on anything that touches personal data, least-privilege access, and a periodic review of who can reach what. The failure is almost never that the firm did not know these controls existed. It is that nobody owned enforcing them across the estate, so a weak-credential path survived in some corner and that corner was where the breach came from.
2. No means of detecting unlawful access
The Regulator also faulted Dis-Chem for failing to put adequate measures in place to monitor and detect unlawful access to its environment. This is the difference between having a lock and knowing the lock has been forced. A firm can hold every preventive control on the list and still fail POPIA if it has no way to tell that a control was bypassed and personal data was reached.
Detection is where security posture and supervisory evidence meet. If you cannot show logging across the systems that hold personal information, retention long enough to reconstruct what happened, and alerting that fires before the data is already gone, you have a monitoring gap that reads as a compliance gap the moment a breach occurs. This is the same failure mode that GDPR enforcement patterns keep exposing under a different flag.
3. Operators processing your data on a handshake
The Dis-Chem breach originated at Grapevine, a third party processing personal data on its behalf. The Regulator found that Dis-Chem had not entered into an operator agreement obliging that operator to maintain adequate security measures. Section 21 of POPIA is explicit on this: where an operator processes personal information for a responsible party, the processing must be governed by a written contract requiring the operator to establish and maintain the security safeguards referred to in section 19.
For the technology function this is a supplier-oversight problem, not a paperwork one. The contract has to exist, but it also has to be true — the operator must actually run the controls the contract claims, and you need some way of assuring yourself of that. A signed agreement with a supplier whose security you have never assessed is a documented liability, not a defence. Every operator that touches personal data belongs in your supplier inventory with the same rigour you apply to your own perimeter.
4. Reporting the breach to the Regulator but not to the people
Dis-Chem notified the Regulator of the compromise but did not notify the affected data subjects. Section 22 requires notification to both the Regulator and the individuals affected, as soon as reasonably possible after the compromise is discovered. POPIA does not set a fixed hour-count the way some regimes do, but “as soon as reasonably possible” is not a licence to wait — and quietly telling the Regulator while leaving the affected people in the dark is precisely the shortcut the Regulator acted on.
The technology consequence is that you need to be able to answer, quickly and defensibly, whose data was in the compromised set. A breach-response process that cannot identify affected data subjects cannot notify them, which means data mapping and the ability to scope an incident are breach-notification controls, not just good hygiene.
5. Security software left to expire
The R5 million fine against the Department of Justice and Constitutional Development — the first administrative fine issued under POPIA — turned on a mundane operational failure: expired security software licences, including antivirus, SIEM and intrusion-detection licences, and no disciplinary follow-up against the officials responsible for renewing them. Controls that were bought and then allowed to lapse offered no protection at the moment they were needed.
This is a governance failure wearing a licensing badge. Somewhere between procurement and operations, the renewal fell off. The defensible position is a maintained register of the security controls the estate depends on, with ownership and renewal dates that a board can see — the kind of board-visible evidence that South African financial institutions already have to produce under the Joint Standard. A control you cannot prove is current is a control you should assume is not.
6. Treating the enforcement notice itself as optional
The Department of Justice was fined not merely for the lapsed licences but because it did not comply with the enforcement notice that preceded the fine. The Regulator gave it a defined window to submit proof of remediation; the deadline passed without the proof and without a request for an extension or an appeal. The notice was the off-ramp, and the department drove past it.
An enforcement notice is a structured chance to fix the problem before a fine attaches. Missing its deadline converts a remediable finding into a penalty. Whoever owns the regulator relationship needs a process that treats a notice as a hard, dated commitment with named owners and evidence assembled against it — not correspondence to be handled later. The same discipline applies the day your regulator first starts asking about your technology, well before any notice is drafted.
Working the list backwards
None of these six is novel. Access control, detection, supplier oversight, breach notification, control maintenance, and follow-through — this is the ordinary substance of a security programme, and that is exactly the point. The Regulator is not setting a bar few can clear. It is acting on firms that failed the basics and could not show otherwise. Enforcement bodies converge on the same short list because it is where real breaches keep originating; the pattern is visible across jurisdictions, from the ICO’s actions against UK technology functions to the Regulator’s in Pretoria.
Read the enforcement record the way an adversary reads your estate: as a list of the weakest points, already ranked. The Regulator has done the ranking for you. The only question left is whether you close the gaps before it arrives to find them, or after.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Free interactive tool
Interactive deadline calculator
Check which regulations apply to you and when
Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.
Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.
Full Governance by Sixteen Pillars
Govern your business. Prove your compliance.
A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.
See what's coming