Quest Technology Pte Ltd
bd_30b2d3ede84ac8ff · schema v1 · pii pii-v1
Full breach record for Quest Technology 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 6 December 2023, the Personal Data Protection Commission (the “ Commission ”) was notified by Quest Technology Pte Ltd (the “ Organisation ”) of a ransomware attack on its servers, resulting in its former and current employees’ personal data to be encrypted and subsequently deleted (the “ Incident ”). The Incident was first discovered on 4 December 2023 when employees found that their shared drives were all empty, containing only a readme file from the ransomware. Additionally, the backup systems had also failed and were compromised. As a result of the Incident, the personal data of approximately 75 individuals, including their names, residential addresses, contact number, NRIC number, date of birth, and salary was affected. The Commission found the Organisation to be wanting in its cybersecurity and data protection practices. First, the Organisation lacked personal data policy and internal guidelines for the employees. Second, there were no documented IT-related policies such as patch management policies and access control policies. Finally, there was a lack of reasonable password policy or management. Remedial Actions After the incident, the Organisation implemented the following: (a) Strengthened passwords to at least 8 characters with a 90-day aging for its Gmail, ERP, domain accounts, and the CCTV account; and (b) Provided cybersecurity courses to all staff to enhance awareness. Voluntary Undertaking Having considered the circumstances of the case and the lack of knowledge by the Organisation in cybersecurity and data protection practices, the Commission accepted a voluntary undertaking (the “ Undertaking ”), which was executed on 24 June 2024, from the Organisation to engage an external service provider to improve its cybersecurity set-up and its data protection practices and policies. As part of the Undertaking, after the initial set-up, the exter
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Aug 28, 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.