Commonwealth Capital Pte Ltd
bd_501d772e2f4bf1ff · schema v1 · pii pii-v1
Full breach record for Commonwealth Capital 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 Commonwealth Capital Pte. Ltd. (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 4 January 2024 of a personal data breach involving the unauthorised exfiltration of personal data (the “ Incident ”). Investigation revealed that a threat actor had gained unauthorised access to the Organisation’s servers through Remote Desktop Protocol (“ RDP ”) brute force of two local administrator accounts. The local administrator accounts were created by the Organisation to allow its vendor to assist in the migration of the Organisation’s on-premise servers to cloud servers. A malicious actor exfiltrated the personal data of 2,951 individuals who were the Organisation’s and its related companies’ former and current employees, tenants and contractors. For 1,675 individuals, the personal data affected is limited to their name, NRIC/FIN /passport number, address, telephone number, email address, photo, and date of birth/age. For the remaining 1,276 individuals, the affected personal data included their salary and/or bank account details. Upon discovering the Incident, the Organisation took prompt remedial actions including engaging a vendor to investigate, implement containment and recovery measures, and improved its existing security measures. Voluntary Undertaking H aving considered the circumstances of the case, the Commission accepted a voluntary undertaking (the “ Undertaking ”) from the Organisation to improve its compliance with the Personal Data Protection Act 2012 (the “ PDPA ”). The Undertaking was executed on 17 April 2024. As part of the Undertaking, the Organisation will be implementing the following: (a) Measures to detect and alert the Organisation on unusually large volume of outgoing traffic; (b) A backup solution for key data stores and servers that is safe from ransomware deployments; (c) Network segmentation an
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Aug 2, 2024
Filed
—
Corroborated · see linked filings
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.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitebianlianbd_6e088ab71c1cda692023-12-14 · +232dCandidate
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.