Wizvision Pte Ltd
bd_00b722e3cea3d0a7 · schema v1 · pii pii-v1
Full breach record for Wizvision Pte Ltd →Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
Background On 7 July 2023, Personal Data Protection Commission (the “ Commission ”) received a data breach notification from Wizvision Pte Ltd (the “ Organisation ”) of a ransomware attack by “Faust” on their servers that encrypted the data files and internal backup data on their file servers with a “.faust” extension and left behind a ransom note (the “Incident ”). As a result of the Incident, the personal data of 795 individuals including their names, phone numbers, addresses, email addresses, NRIC numbers, date of birth, financial information and employment history was affected. 2.9GB of outbound traffic from the Organisation’s network to Mega.nz was detected from firewall logs dated 20 June 2023. However, the source and content of the outbound traffic could not be determined due to the lack of available logs. Investigation revealed that the threat actor had either gained access through one of the 25 publicly accessible endpoints via brute force attack or exploiting a system vulnerability. The Organisation had poor security configurations for its VPN connections and the Organisation’s use of the default port for its Fortinet SSL-VPN facilitated the threat actor’s activities. Remedial Actions Upon discovering the Incident, the Organisation immediately took the following actions: (a) Changed the default port for VPN and all active directory and admin credentials; (b) Disabled VPN web mode access and the VPN option to allow client to connect automatically and keep connections alive; (c) Conducted a full review of the network architecture and enhanced the design of the entire network with proper network segregation and access control; (d) Replaced hardware firewall with latest patches and implemented strict configuration according to best practices; (e) Implemented a centralized logging solution to preserve logs and monitor system assets; (f) Maintained an updated inve
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 4, 2024
Filed
—
No linked breach filing · watching
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- outcome + obligations
- fine (SGD) and affected count where a grounds document states them
- discovery date
- notification clock
See the underlying breach notice, if any.