Summary
- UK policing is developing central infrastructure to improve access to data held by separate forces and government bodies.
- Planned capabilities include national datasets, analytical tooling, device data, and cloud-hosted services.
- Proportional access, auditability, supplier oversight, data retention, and incident containment will determine the programme’s resilience.
UK policing is developing central data infrastructure intended to connect intelligence and operational records across forces, creating a national capability whose security will depend on precise control over access, purpose, suppliers, and recovery.
The National Police Chiefs’ Council says the National Data Integration and Exploitation Service, or NDIES, will allow authorised officers and staff to use information held in separate systems without repeatedly searching individual force platforms. The programme is being led by the National Data and Analytics Office in collaboration with the Home Office.
NDIES is intended to provide centralised infrastructure rather than one database containing every police record. The NPCC says national datasets will be made available when required for public protection, while analytical tools judged safe, reliable, and compliant will be able to work with that information.
Documents obtained by Computer Weekly describe a broader programme of data integration involving intelligence, digital forensics, mobile-device analysis, and cloud services. The material refers to a national “police data factory”, connections involving more than 50 policing and government bodies, and a National Police Capability Environment hosted on Microsoft Azure.
Palantir software has been used in pilot activity, including a platform known as Nectar, although the final supplier arrangements have not been settled publicly. Procurement notices have placed the potential five-year value of the wider programme between £75 million and £250 million.
Connecting data across force boundaries can reduce delays caused by incompatible systems and fragmented intelligence. Investigators may be able to identify relationships or risks that remain hidden when records are held locally, while officers could spend less time moving between applications to assemble information.
Access at national scale
The same integration concentrates personal information, technical authority, and operational dependency. Data may include intelligence reports, device extractions, location records, personal identifiers, and material concerning victims, witnesses, suspects, or people who have never been charged.
An internal assessment cited in the document-based investigation reportedly identified a medium risk that personal information could be processed for purposes that were not necessary or proportionate. Controls will need to distinguish not only between user roles but also between the legal and operational purposes for which particular records were collected.
A user authorised to access one category of police information does not automatically require access to every connected dataset. Search results may need to be filtered according to the source of the information, the status of an investigation, handling restrictions, the user’s force, and the reason for the query.
Audit records will need to show which searches were made, which records were returned, whether information was exported, and how an analytical result influenced a decision. Those logs must remain protected from alteration while being available to investigators, data-protection officers, professional standards teams, and external oversight bodies.
Central infrastructure can improve security by replacing inconsistent local platforms with common controls, although compromise of a privileged identity, cloud-management service, or widely deployed analytical component could affect multiple forces at once. The programme will need mechanisms for isolating one force, supplier, account group, or data source without disabling the whole environment.
Supplier dependence extends beyond hosting. Analytical platforms, identity systems, integration tools, device-processing services, and specialist support may each hold administrative access or operational knowledge. Contracts need to preserve police authority over logging, access approval, security testing, incident evidence, and migration away from a supplier.
Retention policies must work across the integrated environment as well as within the original source system. Data deleted or restricted by one force should not remain indefinitely in an analytical copy, search index, backup, or exported workspace maintained elsewhere.
NDIES is intended to remove friction between fragmented systems, but its security model cannot inherit every local privilege and data copy without increasing national exposure. Its success will rest on whether access remains proportionate, activity remains traceable, and compromised components can be contained before an incident spreads through the shared service.
