2018 · South Africa · J - Information and communication · Data exposure via publicly accessible server backup
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data exposure via publicly accessible server backup
Expertise to Execution
Evidence coverage: 3/6 stages, weight 19/60
Decisive stage: egress (clearest evidence) · Alternative: Strategy to Execution
(1) ViewFines, the traffic-fines website of Aggregated Payment Systems, held national ID numbers, cell numbers, e-mail addresses and login credentials for roughly 934,000 South African drivers, and its own site publicly promised that registration provides absolute security - the expectation of reasonable technical protection of that data was also the duty the Information Regulator spelled out under POPIA section 19. (2) In practice a database backup containing all of it sat on the company's public web server in a directory with listing/browsing enabled, the passwords in it were plaintext, the exposure was found by an anonymous tipster working with iAfrikan and Troy Hunt rather than by APS itself, and the operations manager explained that when the website was designed in 2006, the security was sufficient - passwords were reset and encryption started only after the leak was reported. (3) The classification rests on the egress stage: the remedies - hashing or encrypting stored credentials, and not serving backups from a browsable public directory - sat squarely in the material column as universally known technical practice, and the chain broke in operations and architecture (the 2006 design was never re-engineered); no source documents a policy, standard or leadership decision that was deferred or miscommunicated, so this is not a doctrinal gap, and no expert warning reaching deaf leadership is documented, so not Expertise to Leadership either. The entry gap is an exposed, misconfigured directory rather than an attributed intrusion, and the detection gap (external discovery, contributing, partly inferred) points the same way. (4) RM26 (Expertise to Execution lens): passwords stayed in plaintext from the 2006 legacy design and hashing/encryption was introduced only after the leak, a cryptographic protection known but never realised in the architecture, which made the exposed database far more damaging through password reuse (causal role: Amplifying). RM27 (Expertise to Execution lens): directory listing was left enabled on the backup directory of the public web server, a known hardening step not maintained in operations, which made the entire dataset downloadable (causal role: Enabling). RM34 (Expertise to Execution lens): nothing internal flagged the publicly browsable data or the certificate revoked weeks earlier; detection came from outside researchers, so the exposure stayed invisible to APS (causal role: Obscuring). RM44 (Expertise to Execution lens): the site's specific public claim that registration provides absolute security was contradicted by the plaintext storage, the browsable backups and the revoked certificate in the period before the leak (causal role: Obscuring).
RM26 — Data-protection / cryptographic weaknessRM27 — Configuration hardening / external exposureRM34 — Monitoring / detection / alert-handling gapRM44 — Public security-claim discrepancyRow's source_url (iafrikan.com 2018-05-23 article) returns 404; the live iAfrikan article on the same leak is cited instead. The Information Regulator's 25 May 2018 media statement is explicitly about an alleged breach and POPIA was not yet fully in force, so RM03 (regulatory obligation) was not coded: the section 19 duty the Regulator invoked was not yet enforceable at incident time. No intrusion is attributed - reporting describes negligent exposure of the company's own backup, so Actor is Unattributed and the entry stage is coded as configuration exposure, not attack. Sector J follows the method-spec rule that IT/web services companies fall under Information and communication; APS itself stated via News24 that ViewFines stores no card or bank details and performs no payments itself (payments run through contracted banks/retailers), so K was not chosen. Victim as written in the case file is ViewFines; the site is owned by Aggregated Payment Systems (Pty) Ltd.