On April 7, 2025, South Africa’s Information Regulator announced a new requirement for organizations to report data breaches—referred to under local law as “security compromises”—via an online eServices Portal. The announcement marks a significant procedural shift in how companies must comply with the Protection of Personal Information Act, 2013 (“POPIA”), South Africa’s data protection framework.
The move to a digital platform aligns South Africa with international trends toward streamlined breach reporting mechanisms. For companies that process personal information using means located in South Africa—whether or not they are headquartered in the country—this development highlights the importance of understanding when and how POPIA may apply. Foreign-based companies that rely on South African infrastructure, service providers, or operations to process data should review whether their activities fall within POPIA’s extraterritorial scope.
POPIA and the Concept of a “Security Compromise”
POPIA defines a “security compromise” broadly as any unauthorised access to, or acquisition of, personal information. While this may sound similar to the concept of a “data breach” in the EU General Data Protection Regulation (“EU GDPR”), the terminology and legal framework in South Africa differ in several key respects.
Under POPIA:
- A “responsible party” (analogous to a data controller in EU or UK data protection law) is the person or entity that determines the purpose and means of processing personal information
- An “operator” (akin to a data processor) is a third party that processes information on behalf of the responsible party under contract
- Both responsible parties and operators must take “appropriate, reasonable technical and organisational measures” to safeguard personal information and prevent unauthorised access, damage, loss or destruction
If a responsible party has reasonable grounds to believe a security compromise has occurred, they are required to notify both the Information Regulator and the affected data subjects as soon as reasonably possible.
The notification to data subjects must include:
- A description of the possible consequences of the breach
- A description of the measures taken or to be taken by the responsible party to address the breach
- Recommendations on how data subjects can mitigate potential adverse effects
- If known, the identity of the unauthorised person who may have accessed or acquired the personal information
There are limited exceptions that allow a delay in notification—for example, where immediate notice would impede a criminal investigation by law enforcement.
New Reporting Mechanism: eServices Portal
The Information Regulator’s new online eServices Portal serves as the official platform for submitting breach notifications. It is still unclear whether reporting via the official platform fully replaces the use of Form SCN1, the Information Regulator’s prescribed form for manually reporting security compromises, first released in 2023, but Information Officers are encouraged to submit their reports digitally via the portal going forward.
According to the Information Regulator’s announcement, the portal aims to:
- Simplify the submission process for Information Officers, a statutory role under POPIA assigned to a senior individual within an organization and functionally comparable to a Data Protection Officer under the EU GDPR and similar global frameworks
- Improve the Regulator’s ability to monitor and respond to breach notifications
- Standardize the quality of information submitted in response to security incidents
Does POPIA Apply to Foreign-Based Organizations?
Although POPIA does not explicitly provide that it has extraterritorial application, its reach extends beyond South African borders in certain instances. A company that is not domiciled in South Africa may still be subject to POPIA if it makes use of automated or non-automated means in the country to process personal information, unless those means are used solely for transit through the country.
The potential extraterritorial scope means that foreign-headquartered companies may fall within POPIA’s regulatory ambit in scenarios such as:
- Using South African-based vendors or IT infrastructure to store or process data
- Outsourcing HR, payroll, or customer support functions to South African service providers
In these situations, such companies may be required to inter alia:
- Comply with POPIA’s principles, including security safeguards and breach notification requirements
- Designate an Information Officer to inter alia serve as a point of contact for the Information Regulator and affected data subjects
While POPIA shares similarities with frameworks such as the GDPR, including in its extraterritorial reach and underlying privacy principles, it also contains South Africa-specific obligations and enforcement mechanisms. Multinational organizations should therefore assess their exposure under POPIA independently and avoid relying solely on global privacy programs.
Implications and Next Steps
The rollout of the eServices Portal signals the Information Regulator’s continued efforts to operationalise POPIA and strengthen its enforcement infrastructure. It also underscores the expectation that organizations subject to POPIA take a proactive and structured approach to managing data breach responses.
For international organizations—particularly those without a physical presence in South Africa—this development is an opportunity to revisit how personal information from or about South African individuals is processed, stored, and secured. It may also be a trigger to assess whether POPIA compliance obligations apply, and whether existing incident response plans account for the nuances of local law.
If you have questions about the applicability of POPIA to your operations, breach notification obligations under South African law, or broader data governance strategies, Covington’s global privacy and cybersecurity team is available to assist.
* * *
If you have questions about the application of POPIA or broader privacy regulation across Africa, please contact Dan Cooper at dcooper@cov.com, Ben Haley at bhaley@cov.com, Deon Govender at dgovender@cov.com, Ahmed Mokdad at amokdad@cov.com, and Mosa Mkhize at mmkhize@cov.com. This article is intended to provide general information. It does not constitute legal advice.