Skip to content
Cloud Security Breaches

Crawfort Pte. Ltd. (2022): what the sources say about the cloud incident

Crawfort Pte. Ltd. disclosed the incident on 14 Jul 2022. What was exposed, as the sources state it: The PDPC decision states the personal data of 5,421 customers was affected: images of identity cards, PDF loan contracts and income documents.

Open the ledger · Report a correction

Disclosed
14 Jul 2022
Incident window
about 15 April 2020 (one-week migration window); dark web sale notified 9 June 2021
Cloud or provider
AWS
What was exposed
The PDPC decision states the personal data of 5,421 customers was affected: images of identity cards, PDF loan contracts and income documents.
How access was gained
The decision says the company opened an S3 server port in its AWS environment for one week during a data migration, and that the S3 bucket holding the data was publicly accessible due to a misconfiguration. It states the threat actor gained access to the public bucket in that period.
Access path
Public storage, databases and services; also Exposed network services and request paths
Kind of control that addresses it
require a risk review before temporary changes to cloud storage, block public access on buckets, and alert on any opened ports or public buckets

In the words of the source

“The investigation identified an opened S3 server port in the Organisation’s AWS environment as the cause of the Incident.” (regulator filing, PDPC decision: Crawfort Pte. Ltd. (7 June 2022))

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. PDPC decision: Crawfort Pte. Ltd. (7 June 2022), read 16 Nov 2026

Last reviewed 16 Nov 2026.