Is real personal data sitting in your test and development environments?

By Alan Jeffries, Principal Consultant · Published · Covers the news of the week of 29 June 2026

In early July 2026 the Singapore Land Authority said a test environment run by its vendor IBM had been accessed without authorisation, and that a data set meant to hold only anonymised test data in fact held the names, NRIC numbers and property addresses of about 70,000 people. Across many organisations, test and development systems are treated as unimportant. The data in them may not be.

In short

Quite possibly. Copies of live data are often taken into test, development and training systems to make them realistic, and are then forgotten, or anonymisation is assumed rather than checked. Those systems usually have weaker controls and more people with access. Find out what each non-production environment actually holds, replace real data with genuinely anonymised or synthetic data, check vendors’ environments too, and delete old copies.

What was reported

In a press release on 3 July 2026, the Singapore Land Authority said IBM had informed it of “unauthorised access to an IBM-managed cloud environment”, used for development and system integration testing of two SLA systems. The data set, created in 1998 and updated periodically, was meant to contain only mock, anonymised test data but held the names, NRIC numbers and property addresses of about 70,000 people. SLA said the data should have been anonymised and that how this failed was under investigation. It said the environment was separate from its live systems, which were not compromised; IBM had revoked access; and SLA had made a police report, notified the PDPC and was working with GovTech and the Cyber Security Agency.

We draw no conclusions about SLA or its vendor beyond their published statements.

Why test data is a blind spot

  • Copies multiply. Each new project, vendor or training exercise can take another copy of live data.
  • Weaker controls. Test systems often have broader access, simpler passwords and less monitoring.
  • Assumed anonymisation. Data labelled as anonymised may not be, or may become identifiable again when updated from live systems. (SLA has not said how its own data set failed.)
  • Vendors. Environments run by suppliers may be outside your own monitoring, but the data generally remains your responsibility.

A practical check

List every non-production environment, including those run by vendors, and find out what each one actually holds by sampling the data or scanning it with data-discovery tools, rather than relying on its label. Replace real personal data with synthetic or properly anonymised data, delete old copies once you have checked they are not needed for an investigation or legal hold, and put test systems that must hold real data under the same controls as live systems. If one is breached, the forensic questions are the same as for any breach: how the attacker got in, what was reached, and whether data was taken.

See what a forensic investigation establishes.

Sources

Singapore Land Authority press release, 3 Jul 2026

This article is general commentary on public reports, not legal advice and not a finding about any organisation named in those reports. Facts are as reported at the time of writing.

Frequently asked questions

Is real personal data sitting in our test and development environments?

Quite possibly. Live data is often copied into test, development and training systems and forgotten, or assumed to be anonymised without checking. Sample or scan what each environment actually holds.

Is a breach of a test system a real data breach?

If the system holds real personal data, yes. The risk to the people concerned is the same whichever system the data was taken from.

How do we make test data safe?

Use synthetic data or data that has been properly anonymised and checked, delete old copies, and apply live-system controls to any test environment that must hold real data.

Are we responsible for data held by our IT vendor?

Generally the organisation that collected the data remains responsible for it. In Hong Kong, a data user must take contractual or other measures to protect personal data passed to a data processor. Take legal advice on your contracts.

Do we have to report a breach of a test system in Hong Kong?

As at November 2026 there is no general duty under the Personal Data (Privacy) Ordinance to notify the PCPD of a data breach, but other duties may apply; see our article on what happens if a company does not report a breach. Take legal advice.

Talk to us before anything is changed.

A short, confidential call is usually enough to tell you what to preserve, what it will cost and whether a forensic examination is worthwhile. We take instructions from solicitors, companies and individuals in Hong Kong and across the Asia-Pacific region.

Telephone +852 5808 1071 · Signal or WhatsApp +852 9103 1852 · Email enquiries@d3forensics.com · Enquiry form