South Africa South Africa cybersecurity Bill SAPS

Gauteng's e-Panic Button Exposure Shows South Africa's Breach Rules Lack a Single Reporting Route, Not a Missing Cyber Commissioner

An unsecured safety-app database exposed crime victims' data. The Information Regulator says it received no section 22 notice, and the Cybercrimes Act reporting duty does not cover provincial departments.

e-Panic Button breach: the reporting gap People of Internet Research · South Africa 288,307 Active e-Panic users Department figure for the app's ac… 72 hrs SAPS reporting deadline Section 54 outer limit where feasi… 544 Cyber-fraud cases on SAPS register DA's 2025 figure against over 100,… R50,000 Section 54 maximum fine Penalty for covered providers that… peopleofinternet.com
e-Panic Button breach: the reporting g… People of Internet Research · South Africa 288,307 Active e-Panic users 72 hrs SAPS reporting deadline 544 Cyber-fraud cases on SAPS register R50,000 Section 54 maximum fine peopleofinternet.com

Key Takeaways

In late September 2026 the Gauteng Department of e-Government said it had detected and addressed "an attempted security breach involving the e-Panic Button environment". It added that it had "established that no citizens' personal information was compromised" (SAnews, 29 September 2026). GroundUp's reporting, republished by AllAfrica on 28 September, described something different. It found an unsecured database behind the app holding crime-report text, photos, contact details and GPS coordinates of the people who reported crimes (AllAfrica/GroundUp). The department's account and the journalists' account have not been reconciled in public.

The episode matters beyond Gauteng. It shows how South Africa's overlapping reporting duties can leave a public body with no clear incentive to tell anyone anything.

What the record shows

The DA's Gauteng e-Government spokesperson, Michael Waters, said the party would report the incident to the Information Regulator and asked whether affected residents had been told. The Regulator confirmed it had not received a section 22 security-compromise notification from the department. It said it would assess the matter once a notification arrived, and would otherwise engage the department, citing the "severity and sensitivity" of the alleged compromise (ITWeb, 1 October 2026).

The Gauteng Legislature's e-Government committee said it was "deeply alarmed". It said the flaw allegedly dates back to the app's 2024 launch, and it would not accept assurances without evidence. It ordered a written report on the incident timeline and security audits. The department says the app has 288,307 active users, so the stakes are not small (SAnews; ITWeb).

Two caveats apply. The 2024 date is the committee's claim, not an established fact. Press accounts also differ on which data fields were exposed.

The legal gap

Section 22 of the Protection of Personal Information Act (POPIA) requires a responsible party to notify both the Regulator and the affected data subjects when there are "reasonable grounds to believe" personal information has been accessed or acquired by an unauthorised person. The notice must come "as soon as reasonably possible after the discovery of the compromise" (POPIA s 22). The trigger is a reasonable belief, not a finished forensic conclusion. A department that has asserted "no personal information was compromised" while an exposed database is in the press is in an awkward position under that test.

The Cybercrimes Act 2020 points elsewhere. Section 54 obliges electronic communications service providers and financial institutions to report offences to the South African Police Service "without undue delay and, where feasible, not later than 72 hours". It also requires them to preserve information useful to an investigation. Failure carries a fine of up to R50,000. The offences covered, and the form of reporting, are fixed by a ministerial Gazette notice (Cybercrimes Act s 54). I could not confirm from the statute page that this notice has been published. The duty is aimed at providers and financial institutions, not provincial departments. The result is two regimes with different recipients, different triggers and different clocks. Neither is clearly built for a government app that leaks citizens' data.

The strongest case for a Cyber Commissioner

The DA's Cyber Commissioner Bill, formally the Constitution Twentieth Amendment Bill, would create a Chapter 9 institution with a mandate over cyber security capabilities. That includes a reporting and monitoring hub and compliance oversight across state bodies (DA, 18 July 2023). The case for it is serious. Responsibility is fragmented, and SAPS is stretched. In 2025 the DA cited banking-sector figures of over 100,000 cyber-attacks in 2024 against only 544 cyber-fraud cases on police registers, and called the Information Regulator under-resourced (DA, 16 September 2025). A body with independence and a single mandate could, in principle, close the gaps between those agencies.

Why the fix should be narrower

The e-Panic Button case does not show that the missing piece is a new constitutional office. By the Regulator's own account, the failure was an overdue or absent section 22 notification, and an existing regulator was waiting for it. A constitutional amendment is the slowest and most contested way to fix that. It needs a supermajority, and the DA's own 2025 statement conceded the proposal was received less warmly in government than elsewhere. Another institution does not guarantee compliance either. A new commissioner would also have to compete for the same scarce skills and budget that the Regulator is said to lack.

A proportionate package would start with what already exists:

What to watch

The test is simple. Either the department files a section 22 notice and tells affected users, or the Regulator compels it to. If the Regulator must compel it, South Africa has a compliance and resourcing problem that a new Chapter 9 body would not solve. If a notice is filed and the system still fails to coordinate with SAPS, the DA's fragmentation argument gains real force. Either way, the evidence should come from the incident record, not from assurances.

Sources & Citations

  1. SAnews: Gauteng e-Panic Button attempted security breach thwarted
  2. POPIA section 22: Notification of security compromises
  3. Cybercrimes Act 2020, section 54
  4. ITWeb: e-Panic Button security flaw sparks legislature probe
  5. AllAfrica/GroundUp: DA to report e-Panic data breach
  6. DA: 100,000 cyber-attacks, SAPS records 544 cases