Insights · Data breaches

How do investigators trace who leaked data from a system that contractors can access?

In April 2026 Hong Kong police arrested a man after personal data on more than 56,000 Hospital Authority patients was taken from an operating-theatre system and leaked online. Police said they identified him as a suspect after analysing the system’s logs, and the Hospital Authority said its own monitoring had detected the access. Many organisations give outside developers and support companies deep access to their systems; the points below are general and are not a comment on how the Authority’s or any contractor’s systems were set up.

In short

Mainly through logs and devices. System, database and remote-access logs can show which accounts connected, from where and when, and what they queried or downloaded, as far as the logs record it. Those accounts are then linked to people through access records, shared or generic logins being the usual weak point. Seized computers, servers and storage devices may show copies of the data, tools used to extract it and traces of uploading it. The leaked files themselves can sometimes be matched to a particular extract by their content, structure and timing. Organisations can make this possible in advance by giving every contractor named accounts, limiting what each can reach, and keeping logs long enough to investigate.

What was reported

RTHK and The Standard reported on 8 April 2026 that police had arrested a 30-year-old man on suspicion of access to a computer with dishonest intent, after data on more than 56,000 patients in the Kowloon East Cluster was “taken without authorisation and leaked on a third-party platform”. The Hospital Authority said the system “contained the personal data of patients requiring surgery and details of surgical procedures, among other information”, and was not connected with its clinical management system. It said its monitoring had detected suspected unauthorised access on 3 April, and that it had suspended all contractors from accessing its systems. Police said they identified him as a suspect after analysing the system’s logs, raided a contractor’s office and seized more than 60 digital devices, and urged the public not to download or repost the data.

No charges had been reported. We do not identify him and draw no conclusions about him. Police did not describe the method beyond the log analysis.

How a leak is traced

  • System and database logs. Which accounts ran which queries or exports, and when.
  • Remote access. VPN, jump-server and support-tool records showing where connections came from.
  • Accounts to people. Linking each account to an individual, which is hard when logins are shared or generic.
  • Devices. Copies of the data, extraction scripts and upload traces on computers, servers and storage media, examined under proper authority.
  • The leaked files. Matching their fields, order and timestamps to a particular extract.

Each strand needs to be preserved and documented so that the findings can be tested later.

Preparing before it happens

Give every contractor and support engineer a named account, not a shared one. Limit each to the systems and data they need, and require approval for bulk exports. Record remote sessions and keep logs long enough to investigate, preferably somewhere the people being logged cannot alter. Check contracts for audit rights and cooperation duties in an investigation. If a leak is suspected, preserve the logs and affected systems together while containing access, and take advice on notifying the PCPD and those affected; as at November 2026 there is no general legal duty under the PDPO to notify, although the PCPD encourages it.

If you come across leaked personal data online, do not download or share it.

See what access logs show after a breach and identifying whose data was taken.

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 trace who leaked data from a system that contractors can access?

Through system, database and remote-access logs showing which accounts accessed or exported the data, linking those accounts to people, and examining seized devices and the leaked files themselves. Shared logins make this much harder.

Why are shared contractor logins a problem?

Because logs then show only that the shared account was used, not which person used it. Even with named accounts, logs show an account, not a person, so attribution needs corroborating evidence.

How long should access logs be kept?

Long enough to investigate incidents that may be found weeks or months later, and somewhere the people being logged cannot alter them. The right period depends on the system and the risk.

Should I download leaked personal data to check if mine is included?

No. Downloading or sharing leaked personal data can cause further harm and, depending on how it is used, may be an offence. Contact the organisation or the PCPD instead.

Do Hong Kong organisations have to report a data leak?

As at November 2026 there is no general legal duty under the PDPO to notify the PCPD, although it encourages notification; under Cap. 653 only designated critical infrastructure operators 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 any other incident, and 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.