Преминаване към основното съдържание

Security

Data stays on-premises​

All DICOM processing happens locally. No patient data leaves your network. De-identification still occurs internally between the Gateway and Nuclarity containers as a defense-in-depth measure.

The only outgoing traffic is authentication (auth.nuclivision.com) and operational telemetry (api.nuclivision.com).

What telemetry is sent?

The on-premises deployment sends operational telemetry via OpenTelemetry to Nuclivision for monitoring and support. This data contains no patient information — only system and application health data.

  • Logs — Application log events from the Gateway and Nuclarity services, such as errors, warnings, and processing status updates.
  • Metrics — System and application performance data, such as CPU and memory usage, GPU utilization, job queue lengths, and processing durations.
  • Traces — Request-level timing data that tracks how studies flow through the processing pipeline, used for diagnosing performance issues.

Physical Access Controls and Disk Encryption​

The Nuclivision license agreement requires physical access restrictions limiting physical access to the server to authorized personnel with a legitimate need to access the equipment and/or the use of whole disk encryption (e.g. LUKS).

Secure Local Network​

The Gateway is configured to receive DICOM images from a local PACS or imaging modalities on a secure local area network (LAN). It is not recommended to receive images on an untrusted network unless TLS is enabled on the DICOM listener.

Docker Security​

  • Run Docker in rootless mode or ensure only authorized users have Docker group membership.
  • Keep Docker Engine, NVIDIA drivers, and container images up to date.
  • Do not expose the configuration UI (port 5000) outside your trusted network.

Segregation of Data​

The Nuclivision on-premises deployment should not be configured to support storage of DICOM images from multiple unrelated organizations.