Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is PACS and DICOM Security?

PACS and DICOM security protects medical imaging archives and the protocol that moves images between scanners, workstations, and hospitals, a stack that was built with no authentication in mind.

Illustration for the cybersecurity term PACS and DICOM Security
Home / Blog / Cybersecurity Terms / What Is PACS and DICOM Security?
17 November 2026

What Is PACS and DICOM Security?

What Is PACS and DICOM Security?

A picture archiving and communication system, universally shortened to PACS, stores and distributes medical images: radiographs, CT and MRI series, ultrasound, nuclear medicine, and increasingly digital pathology. The images travel in DICOM format and over the DICOM protocol, a standard that dates to the 1980s and was designed for a world in which the imaging department network was a closed room with a cable in it. PACS and DICOM security is the work of defending that stack now that it sits on a hospital network with internet connectivity attached.

What makes imaging distinctive is the payload. A DICOM file carries the image and, embedded in its header, the patient’s name, date of birth, hospital number, referring clinician, study reason, and sometimes free-text clinical history. One stolen study is a complete identity record with a diagnosis attached.

What the Protocol Does Not Do

The Exposure Is Documented, Not Theoretical

In September 2019 Greenbone Networks published a survey of internet-reachable PACS systems and reported tens of millions of patient records accessible without authentication across dozens of countries, with images retrievable in many cases. Follow-up surveys over the following years found the number falling slowly rather than sharply. The cause is almost always the same: a system connected for teleradiology or for a sharing arrangement, exposed directly instead of through a gateway, and then forgotten.

Beyond disclosure, integrity deserves attention. Researchers have demonstrated that nodules can be added to or removed from CT volumes convincingly enough to mislead radiologists, which places image integrity on the same footing as laboratory result integrity, discussed under laboratory information system security.

Controls That Apply

  1. Never expose DICOM services to the internet. External sharing goes through an exchange portal or a brokered gateway with its own authentication, not through a port forward.
  2. Enable TLS on DICOM associations where the equipment supports it, and plan replacement of the equipment that does not.
  3. Use user identity negotiation and strict application entity allow lists, with a defined title per device and a record of what each is permitted to query.
  4. Segment imaging. Modalities, the archive, and reading workstations belong on their own VLANs, reachable only from the systems that need them.
  5. Log and review retrievals. Query and retrieve activity should be auditable per user and per device, with alerts on bulk retrieval, which is the signature of both exfiltration and curiosity browsing.
  6. De-identify for research and teaching using the standard’s own confidentiality profiles, remembering that burnt-in annotation on the image pixels survives header scrubbing.
  7. Treat imaging workstations as clinical endpoints: patched, hardened, no shared logins, and no general web browsing.

The UK Position

Images and their headers are health data, and therefore special category personal data under the UK GDPR, requiring an Article 9 condition and a corresponding condition in the Data Protection Act 2018. NHS organisations also operate under the Data Security and Protection Toolkit, which NHS England has been aligning with the NCSC Cyber Assessment Framework, and under the common law duty of confidentiality with the Caldicott Principles governing how patient information is used and shared.

Image sharing between trusts in England generally runs through the Image Exchange Portal rather than through direct DICOM connections between hospitals, which is the right pattern: a single accountable intermediary with authentication and audit, instead of a mesh of trusted associations whose history nobody can reconstruct. Where a trust holds imaging on a cloud platform, the usual data residency and processor obligations follow.

Our infrastructure and architecture review services examine imaging networks, archive exposure, and modality segmentation without active probing of clinical equipment.

FAQ – Frequently Asked Questions

Why Is DICOM Still Unencrypted in So Many Hospitals?

Because the installed base is old and the change is disruptive. Enabling the secure transport profile requires every modality, workstation, and archive in the association to support and be configured for it, and some equipment predates the option entirely. The usual interim answer is network isolation and strict allow lists, with encryption required at procurement for anything new.

Can Medical Images Be Altered Convincingly?

Yes. Published research has shown that lesions can be inserted into or removed from CT volumes with enough fidelity to deceive experienced radiologists and automated analysis. The practical defences are integrity controls on the archive, strict write access, audit of modifications, and treating any unexplained change to a stored study as a clinical safety incident rather than an IT fault.

Does Anonymisation Remove All Identifiers from a Study?

Header de-identification using the standard confidentiality profiles removes the structured identifiers, but not text burnt into the image pixels, which is common on ultrasound and some older modalities. Private tags added by manufacturers can also carry identifying data. Any research export should include pixel-level checks and a review of private tags, not only header scrubbing.

What Should a Hospital Check First?

Whether any DICOM service is reachable from outside the clinical network. An external scan for the common DICOM ports, a review of firewall rules and any port forwarding set up for teleradiology, and a check of which application entity titles are permitted will usually surface the serious problems within a day, long before a full architecture review is complete.

Related Terms

You May Be Interested In These

What Is Mimikatz?

Cybersecurity Terms

17 November 2026

What Is Mimikatz?

Read More
What Is DOM-Based XSS?

Cybersecurity Terms

17 November 2026

What Is DOM-Based XSS?

Read More
What Is the EU AI Act?

Cybersecurity Terms

17 November 2026

What Is the EU AI Act?

Read More