Difference between revisions of "Audit Trail and Node Authentication"

From IHE Wiki
Jump to navigation Jump to search
Line 95: Line 95:
  
 
===Additional Supplements:===
 
===Additional Supplements:===
−
* [https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_RESTful-ATNA.pdf Add RESTful Query and Feed to ATNA] - Trial Implementation
+
* [[Add RESTful Query and Feed to ATNA]] - Trial Implementation
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''

Revision as of 20:42, 12 November 2019


Summary

The Audit Trail and Node Authentication (ATNA) Integration Profile establishes security measures which, together with the Security Policy and Procedures, provide patient information confidentiality, data integrity and user accountability.

Note Trial Implementation addition of FHIR support in Add RESTful Query and Feed to ATNA

Benefits

Assistance to sites in implementing security and confidentiality policies

  • This model is partially driven by the underlying assumption that there will be situations where documents are being exchanged between machines and stored on the recipient. This is partly driven by the need for healthcare systems to operate in disasters and overload situations, where the network operation is limited or destroyed. It is not safe to assume that clients are display only. So there will be semi-permanent copies of most information kept. Even in normal operation, healthcare providers may have only 15 minutes per patient. Good healthcare system design recognizes the need to not waste any of those seconds searching and transferring documents over a network. The documents are transferred in advance, and are kept locally until it is determined that they are no longer needed. There are thin client display only applications in healthcare, but they are limited to uses that can fail without introducing risks to safety or patient health, but a complete security/privacy design requires handling situations where data is stored after retrieval.

Details

The Audit Trail and Node Authentication (ATNA) Integration Profile: contributes to access control by limiting network access between nodes and limiting access to each node to authorized users. Network communications between secure nodes in a secure domain are restricted to only other secure nodes in that domain. Secure nodes limit access to authorized users as specified by the local authentication and access control policy.

  • User Authentication

The Audit Trail and Node Authentication Integration Profile requires only local user authentication. The profile allows each secure node to use the access control technology of its choice to authenticate users. The use of Enterprise User Authentication is one such choice, but it is not necessary to use this profile.

  • Connection Authentication

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. The DICOM, HL7, and HTML protocols all have certificate-based authentication mechanisms defined. These authenticate the nodes, rather than the user. Connections to these machines that are not bi-directionally node-authenticated shall either be prohibited, or be designed and verified to prevent access to PHI.

  • Audit Trails

User Accountability is provided through Audit Trail. The Audit Trail needs to allow a security officer in an institution to audit activities, to assess compliance with a secure domain’s policies, to detect instances of non-compliant behavior, and to facilitate detection of improper creation, access, modification and deletion of Protected Health Information (PHI).

Options

Secure Transport Options

Update in 2019 by CP-ITI-1151 adds a set of comprehensive secure transport (STX) options :

  • STX: No Secure Transport Option
  • STX: TLS 1.0 Floor with AES Option
  • STX: TLS 1.0 Floor using BCP195 Option
  • STX: TLS 1.2 Floor using BCP195 Option
  • STX: S/MIME
  • STX: WS-Security

a 'system' must choose at least one of the "STX" options, but is expected to declare in the Integration Statement as many configurations as the system can support. The specific configuration used in a deployed environment will be a policy choice.

Historically these alternatives have not been clear. A system could have had no secure transport as they expected it to be used on a secure network (a configuration often found in Imaging devices), however many Cross-Enterprise systems were expected to support TLS 1.0 with AES. Thus now an Integration Statement must declare transparently what it can support.

Audit Record Options

In the Add RESTful Query and Feed to ATNA supplement has options for the Secure Node, Secure Application, Audit Record Repository, and Audit Record Forwarded to enable those actors to more precisely specify the Audit Transport (ie "ATX") that they use to send audit messages. These actors must support one or more of these options:

  • ATX: FHIR Feed Option
  • ATX: TLS Syslog Option
  • ATX: UDP Syslog Option

Other

  • FQDN Validation of Server Certificate Option

Systems Affected

Systems involved in this profile are:

  • Any local or enterprise-wide healthcare information systems that manage or process Protected Health Information


Actors & Transactions:

ATNA-Actors.png

Specification

Profile Status: Final Text

Formal Specification: IHE IT Infrastructure Technical Framework Version 2 or later


Underlying Standards:

Additional Supplements:

Underlying Standards:

See Also

This profile supports the security/privacy model discussed in IHE Security and Privacy for HIE white paper.

See ATNA FAQ for implementation assistance, and ATNA Profile FAQ for other random help.

For information related to testing the ATNA profile at IHE Connectathons, read this[

NEMA White Paper on Management of Machine Authentication Certificates

Related Profiles

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.

Retrieved from "http://wiki.ihe.net/index.php?title=Audit_Trail_and_Node_Authentication&oldid=118608"