Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Orthanc
Cyber Security

Orthanc

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Cyber Security

Orthanc is an open source DICOM server and medical imaging archive. It stores, retrieves, and serves DICOM studies through a REST API and plugin ecosystem, often acting as a lightweight Picture Archiving and Communication System gateway or embedded imaging back end.

What Orthanc Actually Is

Orthanc is best understood as a lightweight DICOM server that sits between imaging devices, clinical applications, and long-term storage. Its main value is that it centralises DICOM studies, exposes them through a REST API, and can be extended with plugins, which makes it useful as a gateway or embedded imaging back end rather than only as a passive archive.

How Orthanc Fits Into Medical Imaging Workflows

In practice, Orthanc often becomes the integration layer for PACS-like workflows. It receives studies from scanners or upstream systems, stores them in a structured archive, and makes them available to viewers, analytics tools, or other services through standard interfaces. That makes it attractive in small deployments and embedded products where full enterprise imaging platforms would be too heavy.

Because it is API-driven and extensible, Orthanc can also become the place where imaging data is transformed, routed, or forwarded to other systems. That flexibility is useful, but it also means the server can sit on a critical trust boundary: if it is misconfigured, exposed too broadly, or poorly governed, it can become both a clinical integration point and a security choke point.

Security Characteristics That Matter

The security profile of Orthanc is shaped by two things: the sensitivity of medical imaging data and the fact that it is usually integrated into larger clinical environments. DICOM studies may include highly sensitive personal information, and the server often needs to talk to devices, workstations, and downstream applications that are not all equally trusted.

That means operators should think about authentication, access control, encryption, logging, and network placement as core design choices, not optional hardening. A REST API that is convenient for integration can also expand the attack surface if it is reachable from the wrong networks or if privileged functions are not tightly restricted.

Its plugin ecosystem is another important security dimension. Extensions can add valuable functionality, but they also increase supply-chain and maintenance risk because the security of the platform depends on the trustworthiness and upkeep of additional code paths.

Operational Context and Where It Is Used

Orthanc is especially useful where teams need a compact imaging backend that can be embedded into a larger product or deployed as a bridge between scanners, PACS, and custom workflows. That can include research environments, specialty clinics, imaging middleware, and software products that need DICOM handling without the overhead of a large enterprise stack.

Its lightweight design is part of the appeal, but it also means administrators may underestimate the governance burden. A smaller footprint does not reduce the need for asset inventory, backup planning, access review, or retention decisions when the system stores regulated clinical data.

Risk and Threat Considerations

Orthanc concentrates valuable medical images, so a compromise can expose sensitive data, disrupt imaging workflows, or create a foothold into connected clinical systems. Its REST interface and extensibility also increase the chance that exposure comes from configuration or integration mistakes rather than from the core DICOM functionality itself.

Failure mechanism: Overexposed APIs, weak access control, or unsafe plugins can let an attacker enumerate studies, alter stored content, exfiltrate imaging data, or pivot through the imaging environment.

Impact: The result can be confidentiality loss, workflow interruption, tampering with clinical records, and broader trust damage if downstream systems consume compromised studies.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP API Security Top 10API8 — Security MisconfigurationOrthanc exposes a REST API, so API exposure and hardening are central to the term.
Recommendation — Harden Orthanc API exposure and restrict reachable endpoints to trusted networks.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeOrthanc roles, services, and integrations should only get the access they need.
AU-2 — Audit EventsLogging is material because Orthanc handles sensitive imaging data and API activity.
SC-8 — Transmission Confidentiality and IntegrityOrthanc commonly moves sensitive DICOM studies across networks and integrations.
Recommendation — Apply least privilege to Orthanc administration, API access, and connected services. Log Orthanc access and administrative actions to support investigation and review. Protect Orthanc data flows with encrypted, integrity-protected transport.
CIS Controls v8CIS-6 — Access Control ManagementOrthanc needs controlled access to studies, APIs, and administrative functions.
Recommendation — Restrict Orthanc access paths and remove unnecessary access permissions.

Practitioner Guidance

Why practitioners should care: Treat Orthanc like a production data service, not just a convenience layer. The system often sits on a path where clinical availability, data sensitivity, and integration trust all meet, so its configuration decisions have outsized operational consequences.

What to watch for: Review how the REST API is exposed, who can reach plugin functionality, and whether DICOM traffic is separated from general-purpose networks. Pay particular attention to logging, authorization boundaries, and whether the deployment model matches the sensitivity of the studies it stores.

Practitioner takeaway: The safest Orthanc deployments are the ones that limit exposure first and add integration flexibility second, not the other way around.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org