Enforcement
UK ICO reprimands IT provider and client over dormant account breach
The UK Information Commission issued reprimands to an IT provider and its client after a twelve-year-old test account enabled a ransomware attack.
On October 20, 2026, the UK Information Commission's Office (opens in a new tab) issued formal reprimands to an IT service provider and its client following a ransomware attack. The breach exposed the personal data of 3,300 people, the majority of whom were children, after attackers accessed the network through a test account that had existed for more than twelve years. The compromised information related to two projects supporting children and families.
The ransomware attack took place on November 1, 2024. The incident resulted in the encryption of 182.7 gigabytes of data, with 42 gigabytes exfiltrated from the client systems. The root cause was a single dormant account secured by a weak password. The regulatory decision outlines how authorities view the shared responsibility between managed service providers and the organisations that hire them to maintain their technical infrastructure.
Who it applies to
The enforcement action directly concerns data controllers and their IT service providers, categorised as data processors under the UK General Data Protection Regulation.
The regulator issued the reprimands to Ogi Networks Limited, the IT service provider, and the Local Government Data Unit in Wales, known as Data Cymru. The client organisation retained overall control of its network, including the authority to instruct the service provider to create or remove user accounts.
The decision applies the standard of shared accountability to network security. The regulator found that both the company providing the Active Directory services and the client receiving them failed to meet their legal obligations. Regulators expect both parties to maintain active oversight of the environment and to document exactly who is responsible for routine security audits. The responsibility for the failures did not sit with one organisation alone.
What it requires
The UK GDPR requires organisations to implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk. The text specifically demands the ability to ensure the ongoing confidentiality and integrity of processing systems under Article 32(1)(b). It also requires a process for regularly testing, assessing, and evaluating the effectiveness of these measures under Article 32(1)(d).
The regulator found that Ogi Networks Limited infringed these articles by failing to implement appropriate measures and failing to evaluate its security controls. The provider created the test account in January 2012 with the password 'Password1' and did not apply appropriate password strength or complexity requirements. When checked against a password strength tool, this credential was classified as very weak and could be compromised in less than a second.
The provider also failed to conduct regular audits of the accounts it had created within the client network. This failure allowed the operationally unnecessary account to remain active for over twelve years, including over six years after the obligations under the GDPR came into effect. Furthermore, local administrator accounts on three affected systems retained the exact same password for the entire twelve-year period.
Data Cymru infringed the same security articles, along with Article 28(4) regarding processor contracts. The client did not have a contract in place with the IT provider containing the legally mandated data protection terms required when appointing a sub-processor. The organisation also failed to document how the Active Directory services provided by the IT firm would be delivered, monitored, or audited. This created a critical gap in the allocation of responsibilities between the two entities.
The regulator noted that the client did conduct some account reviews. However, these reviews were not scheduled, were not routine, and did not cover the full contents of the Active Directory. This incomplete auditing allowed the dormant test account to remain active and bypass enhanced password requirements that the client introduced at a later date.
The decision establishes that basic cyber security controls are mandatory under the law. The regulator explicitly expects organisations to remove test and dormant accounts, block easily guessed credentials, and apply multi-factor authentication to remote access services by default. The regulator stated that the password was "a wide-open door to nefarious actors."
Organisations are also expected to avoid shared administrative credentials. The enforcement notice specifies that privileged accounts must use unique credentials so that one compromised system does not automatically provide access to others. Finally, agreements with IT providers must clearly explain how security controls will be delivered, monitored, and audited.
The dates
The IT service provider created the vulnerable test account in January 2012.
The ransomware attack exploiting this account occurred on November 1, 2024.
The client and the IT provider entered into a legally compliant data processing contract on April 30, 2025. Following the incident, both organisations introduced periodic account reviews and multi-factor authentication.
The Information Commission's Office issued the formal reprimands on October 20, 2026.
The enforcement text notes that on September 30, 2026, provisions within the Data (Use and Access) Act 2025 came into force. This abolished the office of the Information Commissioner and transferred its powers to the Information Commission, which operates through a collective board.
What to check now
- Review the active directory and identity management systems to identify and deactivate dormant, test, and former user accounts.
- Verify that password complexity rules block commonly used credentials across all accounts, including legacy administrative profiles.
- Confirm that multi-factor authentication is active by default for all remote access services and privileged accounts.
- Audit the entire account environment routinely, ensuring reviews cover all relevant accounts, permissions, and security groups rather than a limited subset.
- Examine the service agreements with IT providers and sub-processors to ensure they contain all legally mandated data protection clauses.
- Document the exact allocation of responsibilities between the internal team and the external IT provider for delivering, monitoring, and auditing security controls.
Outsourcing IT operations does not outsource the legal responsibility for data security. The reprimands demonstrate that regulators expect both the service provider and the client to actively monitor the network environment and maintain formal, documented oversight of their shared systems. A failure to define these boundaries in a contract leaves both organisations liable when legacy infrastructure is compromised.
Sources
This article is general information, not legal advice. For your company's situation, talk to a qualified lawyer.
This article was written with AI and checked, sentence by sentence, against the sources linked above.