ATNA | ATNA-1 | reviewed | Testable |
1
|
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. | 76 | Section 9.1.2 | 3/16/17 4:42:08 PM by aberge |
|
ATNA | ATNA-10 | validated | Testable |
0
|
2
| | 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. | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-11 | validated | Testable |
0
|
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 | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-12 | validated | Testable |
1
|
2
| | 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 | 80 | Table 9.4-4 | 10/20/22 2:34:14 PM by testAuto |
|
ATNA | ATNA-13 | reviewed | Testable |
0
|
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 | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-14 | reviewed | Testable |
1
|
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 | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-15 | reviewed | Testable |
0
|
2
| | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Maitain Time [ITI-1] transaction | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-16 | reviewed | Testable |
0
|
2
| see previous comment on ITI-19 | 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 | 80 | Table 9.4-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-17 | validated | Testable |
1
|
2
| | The Secure Node Actor shall include the Authenticate Node [ITI-19] transaction for all network connections that may expose private information. | 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-18 | validated | Testable |
1
|
2
| | The Secure Node Actor shall ensure all local user activity (login, logout, etc.) protected to ensure only authorized users. | 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-19 | to delete | Testable |
0
|
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 | 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-2 | validated | Testable |
1
|
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 . | 76 | Section 9.1.2 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-20 | reviewed | Testable |
0
|
2
| | The Audit Repository shall support both audit transport mechanisms
| 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-21 | reviewed | Testable |
0
|
2
| | 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 | 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-22 | to be reviewed | Testable |
0
|
2
| | The Audit Repository shall support self protections and user access controls | 80 | Section 9.4 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-23 | reviewed | Testable |
0
|
2
| | Secure Node actor may support the Radiology Audit Trail option | 82 | Table 9.5-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-24 | reviewed | Testable |
0
|
2
| | Secure Application actors may support the Radiology Audit Trail option | 82 | Table 9.5-1 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-25 | reviewed | Testable |
0
|
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 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-3 | reviewed | Testable |
0
|
2
| | A Secure Node Actor shall be configurable to support both connection authentication and physically secured networks | 76 | Section 9.1.2 | 2/5/16 12:27:23 PM by aboufahj |
|
ATNA | ATNA-4 | reviewed | Testable |
0
|
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. | 80 | Section 9.3 | 2/5/16 12:27:23 PM by aboufahj |
|