DICOM PS3.15 2018d - Security and System Management Profiles

A.2 Basic Digital Signatures Secure Use Profile (Current)
Prev | A Secure Use Profiles (Normative) | Next

## A.2 Basic Digital Signatures Secure Use Profile

An implementation that validates and generates Digital Signatures may claim conformance to the Basic Digital Signatures Secure Use Profile. Any implementation that claims conformance to this Security Profile shall obey the following rules in handling Digital Signatures:

1. The implementation shall store any SOP Instances that it receives in such a way that it guards against any unauthorized tampering of the SOP Instance.

2. Wherever possible, the implementation shall validate the Digital Signatures within any SOP Instance that it receives.

3. If the implementation sends the SOP Instance to another Application Entity, it shall do the following:

   1. remove any Digital Signatures that may have become invalid due to any allowed variations to the format of Attribute Values (e.g., trimming of padding, alternate representations of numbers),

   2. generate one or more new Digital Signatures covering the Data Elements that the implementation was able to verify when the SOP Instance was received.

Prev | Up | Next
A Secure Use Profiles (Normative) | Home | A.3 Bit-preserving Digital Signatures Secure Use Profile

DICOM PS3.15 2018d - Security and System Management Profiles