ATNA-1 | The Audit Trail and Node Authentication Integration Profile requires the use of bi-directional certificate-based node authentication for connections to and from each node. |
ATNA-10 | Audit Record Repository actor which claims support of the Audit Trail and Node Authentication (ATNA) integration profile shall support the Record Audit Event [ITI-20] transaction. |
ATNA-11 | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall support the Authentication Node [ITI-19] transaction |
ATNA-12 | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall support the Record Audit Event [ITI-20] transaction |
ATNA-13 | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall perform the Maintain Time [ITI-1] transaction |
ATNA-14 | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Authentication Node [ITI-19] transaction |
ATNA-15 | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Maitain Time [ITI-1] transaction |
ATNA-16 | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Record Audit Event [ITI-20] transaction |
ATNA-17 | The Secure Node Actor shall include the Authenticate Node [ITI-19] transaction for all network connections that may expose private information. |
ATNA-18 | The Secure Node Actor shall ensure all local user activity (login, logout, etc.) protected to ensure only authorized users. |
ATNA-19 | The Secure Node Actor shall include the record Audit Event as specified in ITI TF-2a: 3.20 |
ATNA-2 | Secure Nodes shall either prohibit, or be designed and verified to prevent access to PHI, whenever connections are not bi-directionally node-authenticated . |
ATNA-20 | The Audit Repository shall support both audit transport mechanisms
|
ATNA-21 | The Audit Repository shall support any IHE-specified audit message format, when sent over one of those transport mechanisms. Note that new applications domains may have their own extended vocabularies in addition to the DICOM and IHE vocabularies. This also means that an ATNA Audit Repository is also automatically a Radiology Basic Security Profile Audit Repository because it must support the IHE Provisional Message format and it must support the BSD syslog protocol |
ATNA-22 | The Audit Repository shall support self protections and user access controls |
ATNA-23 | Secure Node actor may support the Radiology Audit Trail option |
ATNA-24 | Secure Application actors may support the Radiology Audit Trail option |
ATNA-25 | Actors in the IHE Radiology domain Profiles which claim support of the Audit Trail and Node Authentication (ATNA) integration profile are required to implement the Radiology Audit Trail option. |
ATNA-3 | A Secure Node Actor shall be configurable to support both connection authentication and physically secured networks |
ATNA-4 | The mechanism for logging audit record messages to the audit record repository shall be either Transmission of Syslog Messages over UDP (RFC5426) with The Syslog Protocol (RFC5424) which formalizes and obsoletes Syslog (RFC-3164), either 2) Transmission of Syslog Messages over TLS (RFC5425) with The Syslog Protocol (RFC5424) which formalizes sending syslog messages over a streaming protocol protectable by TLS. |