| ATNA | ATNA-1 | | Testable |
2
|
4
| I think this is redundant to ATNA-11. This is just a generic statement about the ITI-19 transaction. > No, the use of bi-directionnal certificate authentication is implicit in ITI19-1, this assertion makes it explicit. | 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.dedede | 72 | Section 9.4 | 3/18/24 7:30:37 AM by testAuto |
|
| ATNA | ATNA-11 | | Testable |
3
|
2
| Are we going to duplicate the assertions for SN or SA, or just link these assertions to both actors. I think we should link to both. | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall support the Authentication Node [ITI-19] transaction | 69 | Table 9.1-1 | 3/18/24 7:40:36 AM by testAuto |
|
| ATNA | ATNA-13 | | Testable |
1
|
2
| This is a grouping requirement. ITI-1 is not required by the ATNA profile. > According to 2nd Review group, the TF is the reference. | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall perform the Maintain Time [ITI-1] transaction | 72 | Table 9.3-1 | 5/22/23 5:01:36 PM by testAuto |
|
| ATNA | ATNA-14 | | Testable |
2
|
2
| I disagree with this assertion. Section 9.7 reads "If the product claims only to include the Secure Application Actor, that indicates that only those security features that apply to the application features are provided by the product." I expect SAs to support ITI-19 for its IHE transactions that carry PHI. > Yes, this is the philosophy of the SA actor in the TF : "required only for transactions containing PHI". According to 2nd Review group, the TF is the reference, so we won't delete this assertion. | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Authentication Node [ITI-19] transaction | 69 | Table 9.1-1 | 8/26/19 5:25:26 PM by ceoche |
|
| ATNA | ATNA-17 | | Testable |
1
|
2
| | The Secure Node Actor shall include the Authenticate Node [ITI-19] transaction for all network connections that may expose private information. | 69 | Table 9.1-1 | 8/26/19 5:25:26 PM by ceoche |
|
| ATNA | ATNA-18 | | Testable |
4
|
2
| | The Secure Node Actor shall ensure all local user activity (login, logout, etc.) protected to ensure only authorized users. | 69 | Section 9.1.1.1 | 3/15/24 2:32:26 PM by testAuto |
|
| ATNA | ATNA-19 | | Testable |
1
|
2
| I think this is redundant with assertion ATNA-12 | The Secure Node Actor shall include the record Audit Event as specified in ITI TF-2a: 3.20 | 69 | Section 9.1.1.1 | 7/11/19 7:02:45 PM by ceoche |
|
| ATNA | ATNA-2 | | Testable |
2
|
3
| probably not a testable assertion | Secure Nodes shall either prohibit, or be designed and verified to prevent access to PHI, whenever connections are not bi-directionally node-authenticated . | 69 | Section 9.1.1 | 3/8/24 9:20:47 AM by vhofman |
|
| ATNA | ATNA-23 | | Testable |
1
|
2
| | Secure Node actor may support the Radiology Audit Trail option | 71 | Table 9.2-1 | 6/29/22 2:30:45 PM by testAuto |
|
| ATNA | ATNA-24 | | Testable |
1
|
2
| | Secure Application actors may support the Radiology Audit Trail option | 71 | Table 9.2-1 | 5/23/23 9:33:12 AM by testAuto |
|
| ATNA | ATNA-25 | | Testable |
1
|
1
| | 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. | 83 | Section 9.5.2 | 5/23/23 9:31:52 AM by testAuto |
|
| ATNA | ATNA-28 | reviewed | Testable |
1
|
1
| | The Secure Application shall use the Authenticate Node transaction for all network connections to or from the application that may expose private information as specified in ITI TF-2a: 3.19 | 70 | Section 9.1.1.2 | 7/11/19 7:31:05 PM by ceoche |
|
| ATNA | ATNA-29 | reviewed | Testable |
1
|
1
| | The Secure Application shall provide sufficient authentication methods to ensure that only authorized users access the Secure Application | 70 | Section 9.1.1.2 | 7/11/19 7:26:24 PM by ceoche |
|
| ATNA | ATNA-9 | | Testable |
2
|
2
| | When an implementation chooses to support this Integration Profile for an actor, non-IHE applications that process PHI shall detect and report auditable events, and protect access. | 72 | Section 9.4 | 7/11/19 7:25:04 PM by ceoche |
|
| CH-ADR | CH-ADR-001 | reviewed | Testable |
14
|
2
| See also: Section 3.1.6.3 Page 17 | This transaction is based on SOAP v1.2 exchange protocol and Synchronous Web services (see Section 3.1.1 Scope) | 8 | Section 3.1.1 | 3/8/24 10:58:39 AM by vhofman |
|
| CH-ADR | CH-ADR-002 | reviewed | Testable |
15
|
3
| - | The Authorization Decision Consumercan ask for authorization regarding a number of Resources in one query as the request message complies with the Multiple Resource Profile of XACML v2.0 (see Section 3.1.4 XACMLAuthzDecisionQuery Request) | 9 | Section 3.1.4 | 3/8/24 10:58:41 AM by vhofman |
|
| CH-ADR | CH-ADR-003 | reviewed | Testable |
15
|
2
| Checking only the BODY part of the message | The WS-Addressing Action header SHALL have this value:urn:e-health-suisse:2015:policy-enforcement:AuthorizationDecisionRequest (see Section 3.1.6.5 Semantics) | 14 | Section 3.1.6.5 | 3/8/24 10:58:42 AM by vhofman |
|
| CH-ADR | CH-ADR-004 | reviewed | Testable |
15
|
2
| Checking only the BODY part of the message | The recipient of the Authorization Decision Query SHALL be identified by the WS-Addressing <wsa:To>element in the header (URL of the endpoint) (see Section 3.1.6.5 Semantics) | 14 | Section 3.1.6.5 | 3/8/24 10:58:45 AM by vhofman |
|
| CH-ADR | CH-ADR-005 | reviewed | Testable |
15
|
2
| Checking only the BODY part of the message | The value of the WS-Addressing To header (see Req. 4) SHALL be a URL, specifically the recipient's endpoint (see Section 3.1.6.5 Semantics) | 14 | Section 3.1.6.5 | 3/8/24 10:58:47 AM by vhofman |
|
| CH-ADR | CH-ADR-006 | reviewed | Testable |
14
|
3
| Checking only the BODY part of the message | A SAML 2.0 Identity Assertion SHALL be conveyed within the WS-Security Security header (see Section 3.1.6.5 Semantics) | 14 | Section 3.1.6.5 | 3/8/24 10:58:49 AM by vhofman |
|