Digital Imaging and Communications in Medicine Security Standards
· About Digital Imaging and Communications in Medicine Security Standards
Key Takeaways
- DICOM PS3.15 applies to implementations that claim conformance to DICOM security and system management profiles, and it is the part of the standard that covers security mechanisms for medical imaging interchange.[1][2]
- The standard is not a law or regulator-issued mandate; it is an international technical standard maintained through NEMA’s DICOM Standards Committee, so penalties come from contract, procurement, accreditation, or local law rather than from DICOM itself.[1][2]
- The current official DICOM publication available in late 2026 is PS3.15 2026d, and the DICOM site shows active editorial and change activity in 2025–2026, including security-related change proposals and updates to TLS support.[2][4][11]
- DICOM security profiles cover encrypted transport, media security, audit trail exchange, and system management controls, but the standard states that local security policy still determines how access control and other computer-security measures are implemented.[5][12]
- Healthcare organizations that exchange, store, or transmit DICOM objects should treat the standard as a baseline interoperability and security framework and pair it with enterprise controls such as ISO 27001, NIST CSF 2.0, and ISO 42001 where they map to imaging workflows.[5][12]
What It Is
DICOM PS3.15, titled Security and System Management Profiles, is the security part of the DICOM standard for medical imaging information and related data.[2][3] It specifies profiles to which implementations may claim conformance, including mechanisms for securing DICOM objects in transit and at rest, while leaving much of the underlying security policy to the local environment.[1][5]
The standard is maintained by the DICOM Standards Committee at NEMA, not by a government regulator.[1][2] The official DICOM publication page currently shows PS3.15 2026d, with the latest posted web content updated in October and November 2026.[2][5][9]
For dates, the standard’s current official web release is 2026d; the public change history also shows recent 2025 change proposals and a 2026 update cycle, including a proposal to fix inconsistencies in the Audit Trail Message Format Profile and further work on TLS support.[2][4][11] Because DICOM is a living standard rather than a statute, “adopted” and “in force” are best understood as the date a particular edition is published and available for use by implementers, not as a legal commencement date.[2][4]
Who Must Comply
Entities that implement DICOM systems and claim conformance to PS3.15 must follow the relevant profiles they adopt.[1][2] This includes vendors of imaging modalities, PACS, VNA platforms, teleradiology systems, viewers, gateways, and middleware that exchange DICOM objects or audit messages.[1][5]
DICOM’s security profiles are technically relevant wherever medical images or related data are stored, transmitted, or shared across systems, including cross-institution exchanges.[5][12] The standard’s wording is broad, but compliance is only mandatory in practice where a contract, procurement requirement, accreditation program, or internal policy requires conformance.
There is no DICOM-specific legal extraterritoriality test in the standard itself, and no built-in exemption list comparable to a statute.[1][2] Instead, applicability is determined by whether a product or organization asserts conformance, whether a customer requires a named profile, and whether local law or sector rules require stronger safeguards for health data.
Core Requirements
- Use defined security profiles for DICOM interchange. PS3.15 provides security and system management profiles for implementations to claim conformance, so organizations should identify which profile applies to each modality, archive, viewer, or gateway.[1][2]
- Protect data in transit. DICOM security guidance explicitly covers encrypted transport, including TLS-based protection for DICOM traffic.[12] Where imaging crosses networks, the transport profile should be selected and tested as part of deployment.
- Protect data at rest and in media workflows. The standard supports security for stored objects and media interchange, including mechanisms for whole-object or attribute-level protection in the DICOM security ecosystem.[8][12] This is critical where images move through removable media, export workflows, or long-term archives.
- Implement audit logging and audit trail exchange. DICOM expects audit trails and activity monitoring to be part of the local security system, and it defines structured audit message formats and exchange profiles for centralized repositories.[8][12] Audit controls should cover user activity and system events relevant to imaging access and export.
- Apply local access control policy. DICOM does not mandate a single access-control model; it states that local security policies determine what is handled by access control versus audit controls.[8][12] That means identity, authorization, and privilege design must be implemented by the healthcare environment, not assumed from DICOM alone.
- Maintain system management and operational consistency. PS3.15 includes system management profiles and security-related conformance claims, so organizations should document which controls are implemented, where, and by which component.[1][2]
Deadlines and Penalties
| milestone | date | what applies | |---|---:|---| | Current official web publication | 31 October 2026 | PS3.15 2026d is the current posted DICOM security and system management profile edition.[2] | | Recent security change proposal finalized | 13 November 2025 | CP-2530 addressed inconsistencies in the Audit Trail Message Format Profile.[11] | | Ongoing standards activity on TLS support | 2025–2026 | DICOM work continued on TLS support updates, including post-quantum related drafting activity in committee minutes.[15] |
Maximum fines: DICOM itself sets no fines because it is a technical standard, not a law or enforcement code.[1][2] Other sanctions: Consequences typically arise through contract termination, failed procurement acceptance, product nonconformance, accreditation findings, liability exposure, or failure to meet privacy and security obligations under applicable health-data laws.
How to Comply
- Map DICOM flows and systems. Inventory every modality, archive, viewer, broker, export path, and external exchange that handles DICOM objects or audit events. Tie each flow to the specific PS3.15 profile and to any applicable legal privacy regime.
- Define a security architecture for imaging. Use ISO 27001 as the management-system layer for risk assessment, asset control, supplier governance, incident response, and evidence retention. Treat DICOM profiles as technical controls inside that management system.
- Harden transport and identity controls. Require authenticated, encrypted transfer for DICOM networks and gateways, and align the control set with NIST CSF 2.0 functions for Identify, Protect, Detect, Respond, and Recover. Use strong certificate lifecycle management where TLS is used.
- Build auditability into PACS and VNA operations. Configure centralized logging, time synchronization, event retention, and review procedures for access, export, deletion, and administrative actions. DICOM’s audit trail exchange concept fits well with enterprise SIEM and SOC workflows.
- Control access with least privilege. Separate clinical access, administrative access, service accounts, and vendor support access. Use role-based access, break-glass controls, and periodic recertification because DICOM leaves access control policy to the local environment.[8][12]
- Secure de-identification and sharing workflows. If images are shared for research, AI development, or external consultation, use documented de-identification rules, re-identification governance, and approval workflows. DICOM security guidance supports attribute-level handling, but privacy compliance requires broader policy and legal controls.
- Operationalize product and vendor requirements. Include PS3.15 conformance claims in procurement, integration testing, and acceptance criteria. Where vendors provide security posture evidence, map it to ISO 42001 if AI-assisted imaging tools use patient images, metadata, or automated triage.
- Test, attest, and monitor continuously. Perform periodic configuration reviews, penetration testing for exposed imaging services, and tabletop exercises for image-sharing incidents. Revalidate certificates, logging, and interop after upgrades because DICOM change activity continues across annual releases.[2][11]
Related Regulations
- HIPAA Security Rule: In the United States, HIPAA sets legal safeguards for electronic protected health information, while DICOM PS3.15 provides a technical interoperability framework that can support those safeguards.
- GDPR: In the EU, GDPR governs lawful processing, minimization, and security of personal data; DICOM can secure image exchange, but it does not determine legal bases, retention, or cross-border transfer rules.
- NIS2 Directive: For covered healthcare entities in the EU, NIS2 drives cyber-risk management and incident reporting, while DICOM addresses how imaging systems exchange and protect data.
- FDA cybersecurity expectations for medical devices: Where imaging devices are regulated medical devices, FDA cybersecurity expectations may apply to the device lifecycle, and DICOM security profiles are only one part of the device’s overall security design.
- ISO 27799: This healthcare-security standard overlaps closely with imaging environments and is useful for operational controls around confidentiality, integrity, and availability of health information.
FAQ
Does DICOM security apply to companies outside the healthcare sector?
Yes, if they develop, operate, or integrate systems that exchange DICOM objects or claim conformance to PS3.15.[1][2] The standard is not limited by geography or industry label; it follows the use of DICOM in medical imaging workflows. The legal obligations around the data may still come from healthcare, privacy, or device laws in the relevant jurisdiction.
Is DICOM security mandatory by law?
No. DICOM PS3.15 is a technical standard, not a statute or regulation, so it does not itself create fines or criminal penalties.[1][2] It becomes effectively mandatory only when a contract, procurement rule, certification scheme, or local policy requires conformance.
Does DICOM require encryption for all medical images?
DICOM provides security profiles that support encrypted transport and protection for data at rest, but the standard also says local security policy governs implementation choices.[5][12] In practice, organizations should expect encryption to be required for sensitive clinical networks, especially over untrusted channels. The exact profile selected depends on the deployment and the conformance statement.
Does DICOM define access control rules?
Not in a fixed, universal way. DICOM explicitly leaves access control policy to the local security system and focuses on the profiles and interfaces used to secure interchange.[8][12] That means identity governance, privilege management, and approval workflows must come from the hospital, vendor, or hosting environment.
What changed in 2025–2026?
The DICOM standards process remained active in 2025–2026, including a finalized change proposal to clean up the Audit Trail Message Format Profile and committee work on TLS support updates, including post-quantum discussion.[11][15] The current public DICOM release shows PS3.15 2026d.[2] No published delay or suspension of PS3.15 was identified in the available sources.
Sources
- DICOM PS3.15 2026d — Security and System Management Profiles (NEMA)
- DICOM PS3.15 scope and field of application (NEMA)
- DICOM standard overview: Security and System Management Profiles (dicomstandard.org)
- DICOM 2026d page and recent content updates (NEMA)
- DICOM PS3.1 6.15 overview of PS3.15 (NEMA)
- DICOM Change Proposal CP-2530: Audit Trail Message Format Profile fixes
- DICOM WG-14 meeting minutes, December 2025
- DICOM Security 101 presentation, DICOM standards materials
Put it into practice
- Generate the policy: NIST CSF policy generator (generatepolicy.com)
- Buy the policy pack: Telecom Communications Security Policy Bundle (cyberpolicy.shop)
- Build it yourself: Build Series Vol. 08 — Network Segmentation & Zero Trust (ciso.diy)