How do investigators work out which records were changed in a cyber attack?
In March 2026 MediMap, a New Zealand platform used to manage medication charts in aged care and pharmacies, was being brought back online after a cyber attack in which, it said, patient information had been altered. Much breach coverage is about data being stolen. When records are changed instead, the questions are different: which records, what did they say before, and can they be trusted now?
By comparing what the records say now with trustworthy earlier versions and with the system’s own history. Audit trails and database transaction logs can show which records changed, when, and under which account or session, as far as they were kept. Clean backups taken before the attack allow record-by-record comparison. Where logs are incomplete, investigators may combine several sources, such as application logs, exports, reports and paper records, to rebuild what each record should say. Until that work is done, an organisation may need to treat affected data as unreliable and check critical entries by hand.
What was reported
Insurance Business reported on 5 March 2026 that MediMap had been taken offline on 22 February after patient information was “altered” in a cyber attack, and was being brought back online. The company said it had “identified the specific demographic records that were altered”. A court had granted an injunction against “accessing, using, copying, sharing or publishing any of the affected data”, and the Health Minister had commissioned a review prompted by an earlier health platform breach; his office said MediMap would not be named in it, but the systemic lessons would likely apply.
We draw no conclusions about the company beyond its reported statements.
How changed records are traced
- Audit trails. Application records of who edited what and when, if auditing was enabled.
- Transaction logs. Database logs of changes, which can sometimes be replayed to show earlier values.
- Backups. Clean copies from before the attack, compared record by record.
- Sessions and accounts. Linking changes to the accounts, sessions or network addresses used.
- Outside copies. Reports, exports, messages and paper records that show what a record used to say.
The hardest part is often establishing when the attacker first got in, because backups taken after that point may already contain altered data.
Preparing for an integrity attack
Turn on audit logging for critical records and keep it somewhere the application’s own users cannot alter. Keep backups that cannot be overwritten, test restoring them, and keep enough history to go back before an attacker’s first access. Plan how critical work, such as medication, will continue if records cannot be trusted.
If you suspect records were altered, isolate affected systems rather than switching them off where possible, and preserve the systems, logs and backups together while containing access. As at November 2026 there is no general legal duty under the PDPO to notify the PCPD of a data breach, although the PCPD encourages notification. Under Cap. 653, only designated critical infrastructure operators (designated organisations are notified in writing; the list is not published) must report computer security incidents affecting their critical computer systems: within 12 hours of becoming aware of a serious incident, and within 48 hours of becoming aware of any other incident. Other laws may apply. Take advice.
See identifying whose data was affected and cyber investigations.
Sources
General commentary on public reports, not legal advice and not a finding about any organisation or person named in those reports. Facts are as reported at the time of writing.
Frequently asked questions
How do investigators work out which records were changed in a cyber attack?
By comparing current records with clean backups and with audit trails and database transaction logs, which can show which records changed, when and under which account, as far as they were kept.
Why is altered data sometimes worse than stolen data?
Because people may rely on it without knowing it is wrong. In healthcare or finance, a changed record can cause harm until it is found and corrected.
Can backups be trusted after an attack?
Treat any backup as something to check, not as trusted. Those taken before the attacker first got in are the best starting point, but should still be checked for tampering and malware. Later backups can help show when records changed. Establishing the first access date is often the hardest part.
What logs help prove records were altered?
Application audit trails, database transaction logs and sign-in records, kept somewhere the attacker could not change them.
Do Hong Kong organisations have to report altered personal data?
As at November 2026 there is no general legal duty under the PDPO to notify the PCPD of a data breach, although the PCPD encourages notification. Under Cap. 653, only designated critical infrastructure operators (designated organisations are notified in writing; the list is not published) must report computer security incidents affecting their critical computer systems: within 12 hours of becoming aware of a serious incident, and within 48 hours of becoming aware of any other incident. Other laws may apply. Take advice.
Facing something like this?
The first discussion is confidential and free, and usually changes what you decide to do next. Call +852 5808 1071 or use the case review form.