1200: SEC List Audit Messages

This is a documentation procedure where you list all of the audit messages that your system is required to produce. The purpose of the test is for you to provide that list to the Project Manager so that the manager can determine if your system is producing the proper set of messages. This test result is due 3 weeks in advance of the normal test deadlines. This will give you time to recover in the event that you are missing audit events required of your system.

Create a text file named: grade_1200.txt. Content of the file should be as listed below.

• Line 1: Company Name
• Line 2: System Name
• Line 3 and following: List of all Integration Profile/Actor combinations for this system.
• Following lines: List all audit events for which your system produces an audit message.

Submit the text file to the Project Manager for evaluation.

1201: Actor Start

This sequence tests your ability to send an audit record to the MESA Audit Record Repository. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The Actor Start message is chosen as that is required of all actors and is independent of other IHE transactions. This can be run using the IETF or INTERIM audit record format.

If not already done, start the MESA servers according to the directions in section 1.5.

By whatever means you use, “start” your actor such that it generates the actor-start-stop audit record message. This should be sent to the MESA Audit Record Repository.

Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Actor-start-stop and it should verify the content of that record against the IHE XML schema:

perl 1201/eval_client_1201.pl <log> <INTERIM or IETF>

<log> is a log level (1 – 4). The results file 1201/grade_client_1201.txt) should show 0 failures.

Run the evaluation at log level 4 and submit the test results to the Project Manager.

1202: System Configuration

This sequence tests your ability to send an audit record to the MESA Audit Record Repository. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The Actor-config message is chosen.

If not already done, start the MESA servers according to the directions in section 1.5.

By whatever means you use, configure or reconfigure your actor such that it generates the IHE Actor-config audit record message. This should be sent to the MESA Audit Record Repository. For example, you might change the host name.

Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Actor-config and it should verify the content of that record against the IHE XML schema:

perl 1202/eval_client_1202.pl

The results file (1202/grade_client_1202.txt) should show 0 failures.

Submit the test results to the Project Manager.

1203: User Authenticated

This sequence tests your ability to send an audit record to the MESA Audit Record Repository. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The User-Authenticated message is chosen.

If not already done, start the MESA servers according to the directions in section 1.5.

By whatever means you use, configure or reconfigure your actor such that it generates the IHE User-Authenticated audit record message. This should be sent to the MESA Audit Record Repository. For example, you might change the host name.

Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Actor-config and it should verify the content of that record against the IHE XML schema:

perl 1203/eval_client_1203.pl

The results file (1203/grade_client_1203.txt) should show 0 failures.

Submit the test results to the Project Manager.

1205: Unspecified Records

Tests 1201 through 1204 cover specific events that defined by the MESA documentation. For test 1205, the system under test is asked to send three or more Audit Record messages to the MESA Audit Record Repository. These messages are evaluated by the MESA software, and the user collects the messages and sends them to the Project Manager for distribution to other systems.

You are welcome to use the events that are specified for tests 1201 through 1204. You might want to use other events so that your software is more fully tested.

If not already done, start the MESA servers according to the directions in section 1.5.

By whatever means you use, configure or reconfigure your actor such that it generates the IHE User-Authenticated audit record message. This should be sent to the MESA Audit Record Repository. For example, you might change the host name.

Clear the MESA Audit Record Repository of existing messages:

    perl scripts/clear_db.pl

Generate three (3) or more Audit Record messages and send these to the MESA Audit Record Repository.

Run the evaluation script to examine all audit records sent during this test:

  perl 1205/eval_client_1205.pl

perl 1203/eval_client_1203.pl

Collect all of the files (tar/zip) in $MESA_TARGET/logs/syslog and submit these to the Project Manager.

1211: Time Synchronization

Refer to the tests for Consistent Time/Time Client

11100: ATNA: List Audit Messages

This is a documentation procedure where you list all of the audit messages that your system is required to produce. The purpose of the test is for you to provide that list to the Project Manager so that the manager can determine if your system is producing the proper set of messages. This test result is due 3 weeks in advance of the normal test deadlines. This will give you time to recover in the event that you are missing audit events required of your system.

References

Instructions

Create a text file named: grade_11100.txt. Content of the file should be as listed below

Evaluation

Supplemental Information

11101: ATNA Audit: Actor Start BSD

This sequence tests your ability to send an audit record to a “BSD” Audit Record Repository. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The Actor Start message is chosen as that is required of all actors and is independent of other IHE transactions.

References

Instructions

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. By whatever means you use, “start” your actor such that it generates the Start/Stop audit record message. Send this message to the MESA “BSD” Audit Record Repository.
4. Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Actor-start-stop and it should verify the content of that record against the IHE XML schema:

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/rad/actors/secure_node directory, run the evaluation script

   perl 11101/eval_11101.pl <log level> INTERIM (or)

   perl 11101/eval_11101.pl <log level> IETF

   where INTERIM or IETF indicate which schema is to be used.
2. The output file is 11101/grade_11101.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

11102: ATNA Audit: Actor Start Reliable Syslog

Do not run this test for the 2006-2007 cycle. Reliable Syslog has been placed on hold.

11103: ATNA Audit: Actor Specific Audit Message

In this test, the actor generates a log message that is specific to the actor. The Actor Start/Stop or User Authentication messages are general in nature.

References

Instructions

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. By whatever means you use, generate an audit record message that is specific to one or more of the actors in your system. Send this message to the appropriate repository.
4. Extract the log message from the server. Copy $MESA_TARGET/logs/syslog/last_log.xml to the file name of your choice.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/rad/actors/secure_node directory, run the evaluation script

   perl 11103/eval_11103.pl <log level> INTERIM FILE(or)

   perl 11103/eval_11103.pl <log level> IETF FILE

   where INTERIM or IETF indicate which schema is to be used.
2. The output file is 11103/grade_11103.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

11104: ATNA Audit: User Authentication

In this test, the system generates a User Authentication log message and evaluates it using the MESA tools.

References

Instructions

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for a User Authentication event. Send this message to the appropriate MESA audit record repository.
4. Extract the log message from the server. Copy $MESA_TARGET/logs/syslog/last_log.xml to the file name of your choice.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/rad/actors/secure_node directory, run the evaluation script

   perl 11104/eval_11104.pl <log level> INTERIM FILE(or)

   perl 11104/eval_11104.pl <log level> IETF FILE

   where INTERIM or IETF indicate which schema is to be used.
2. The output file is 11104/grade_11104.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

11121: ATNA Audit: Patient Records

For test 11121, the system under test is asked to generate three or more audit messages. The user collects the messages and sends them to the Project Manager for distribution to other systems.

References

Instructions

1. Generate three (3) or more Audit Record messages containing at least one record for:
   • User Authentication
   • Patient Record Access
   If the Patient Record Access is not pertinet, substitute a different event (PHI export). The third record is of your choosing.
2. Place each message in a separate XML file and tar/zip the collection together. Name the tar/zip file using the system name found in the Kudu web tool.
3. Submit the tar/zip file to the Project Manager. The Project Manager will distribute to other vendors for testing.
4. Please submt the records 2 weeks in advance of the normal deadline to allow distribution to other systems.

1221: Client Certificate Exchange with Valid Certificate

In this test, your client application requests a network connection with a MESA server using the standard X.509 (unexpired) certificates. The MESA server will complete the TLS handshake, read data from the socket and then disconnect after 2 seconds. Therefore, this test demonstrates your ability to implement the basic TLS handshake with the cyphersuite:

TLS_RSA_WITH_NULL_SHA

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Open a network connection with the MESA TLS server listening at port 4100. We assume this means you have to initiate an IHE transaction; this transaction will fail because the MESA TLS server does not respond beyond the TLS handshake.
5. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_server.txt. This should indicate a successful TLS handshake.
6. Cut/paste the entry from the MESA log file. Create a file named SYSTEM_1221.log, enter the log information and submit that file to the Project Manager.

1222: Client Certificate Exchange with Unregistered Certificate

In this test, your client application requests a network connection with a MESA server using the standard X.509 certificates. The MESA server will attempt the TLS handshake by offering an unregistered certificate. You are expected to abort the network connection and log an audit record message with the MESA Audit Record Repository (at port 4000 on the MESA system).

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Open a network connection with the MESA TLS server listening at port 4101. We assume this means you have to initiate an IHE transaction; the server will attempt the TLS handshake with an unregistered certificate.
5. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_server.txt. This should indicate a connection attempt from your system and an aborted connection.
6. Cut/paste the entry from the MESA log file. Create a file named SYSTEM_1221.log, enter the log information and submit that file to the Project Manager.
7. Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Node-Authentication failure and it should verify the content of that record against the IHE XML schema:

     perl 1222/eval_client_1222.pl  IETF (or)

     perl 1222/eval_client_1222.pl  INTERIM

8. The results file 1222/grade_client_1222.txt should show 0 failures.
9. Submit the grade file to the Project Manager.

1223: Client Certificate Exchange with Expired Certificate

In this test, your client application requests a network connection with a MESA server using the standard X.509 certificates. The MESA server will attempt the TLS handshake by offering an unregistered certificate. You are expected to abort the network connection and log an audit record message with the MESA Audit Record Repository (at port 4000 on the MESA system).

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Open a network connection with the MESA TLS server listening at port 4102. We assume this means you have to initiate an IHE transaction; the server will attempt the TLS handshake with an unregistered certificate.
5. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_server.txt. This should indicate a connection attempt from your system and an aborted connection.
6. Cut/paste the entry from the MESA log file. Create a file named SYSTEM_1221.log, enter the log information and submit that file to the Project Manager.
7. Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Node-Authentication failure and it should verify the content of that record against the IHE XML schema:

     perl 1223/eval_client_1223.pl IETF (or)

     perl 1223/eval_client_1223.pl INTERIM

8. The results file 1223/grade_client_1223.txt should show 0 failures.
9. Submit the grade file to the Project Manager.

1224: Client TLS Handshake for 3DES

Do not run this test for the 2006-2007 cycle

1226: DICOM Verification with TLS

This test is for DICOM client applications that are lacking a fully integrated MESA test sending data with TLS. In this test, your actor establishes a TLS connection with a MESA server and sends a DICOM C-Echo command (Verification class). If your actor has a fully integrated MESA test that exercises TLS and DICOM, you can skip this test.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Establish a DICOM/TLS connection with the MESA server running on port 2350. DICOM AE titles are ignored. Send a C-Echo request to that server.
5. This should run to completion with no errors. If you encounter an error, you will need to correct the communication problem and rerun the test.
6. When you have successfully completed the C-Echo request, there will be log information stored in the MESA Image Manager log: $MESA_TARGET/logs/imgmgr.log. Submit that log file to the Project Manager as the output of this test.
7. The most typical problem is using the wrong certificate. Start the MESA servers with the highest log level. If you cannot get a C-Echo command to work, examine the MESA Image Manager log file.

1226: DICOM Verification with TLS: Unregistered Certificate

In this test, your actor establishes a TLS connection with a MESA server that has a certificate that is not registered with your system. That is, your system should attempt to establish a DICOM connection, determine that the MESA system is using a certificate that is not known to you, and abort/terminate the network connection.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Establish a DICOM/TLS connection with the MESA server running on port 2351. DICOM AE titles are ignored. Send a C-Echo request to that server.
5. Your system should not complete the DICOM association negotiation.
6. When you have successfully completed the test, there will be log information stored in the MESA Image Manager log: $MESA_TARGET/logs/imgmgr.log. Submit that file to the Project Manager.
7. This is a rather difficult test as it is designed to make something fail on purpose. Whether your system closes the connection gracefully or merely exits depends on your design and software.

1226: DICOM Verification with TLS: Expired Certificate

In this test, your actor establishes a TLS connection with a MESA server that has a certificate that is expired. That is, your system should attempt to establish a DICOM connection, determine that the MESA system is using a certificate that is expired, and abort/terminate the network connection.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

4. Establish a DICOM/TLS connection with the MESA server running on port 2352. DICOM AE titles are ignored. Send a C-Echo request to that server.
5. Your system should not complete the DICOM association negotiation.
6. When you have successfully completed the test, there will be log information stored in the MESA Image Manager log: $MESA_TARGET/logs/imgmgr.log. Submit that file to the Project Manager.
7. This is a rather difficult test as it is designed to make something fail on purpose. Whether your system closes the connection gracefully or merely exits depends on your design and software.

Supplemental Information

The certificate used by the Image Manager for this test is located in $MESA_TARGET/runtime/certificates/expired.cert. You should try to configure your system to know that this is the peer certificate. This is to make sure you are testing for expired certificates rather than unregistered certificates.

1221: Server Certificate Exchange with Valid Certificate

In this test, a MESA client application requests a network connection with your server using the standard X.509 (unexpired) certificates. The MESA client will complete the TLS handshake and then disconnect after 2 seconds. Therefore, this test demonstrates your ability to implement the basic TLS handshake with the cyphersuite:

    TLS_RSA_WITH_NULL_SHA

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1221/1221_server_test.pl

6. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_client.txt. This should indicate a successful TLS handshake.
7. Cut/paste the entry from the MESA log file. Create a file named SYSTEM_1221.log, enter the log information and submit that file to the Project Manager.

1222: Server Certificate Exchange with Unregistered Certificate

In this test, a MESA client application requests a network connection with your server using the standard X.509 certificates. The MESA server will attempt the TLS handshake by offering an unregistered certificate. You are expected to abort the network connection and log an audit record message with the MESA Audit Record Repository (at port 4000 on the MESA system).

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA servers are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1222/1222_server_test.pl

6. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_client.txt This should indicate the aborted network connection.
7. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_client.txt. This should indicate a successful TLS handshake.
8. Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Node-Authentication failure and it should verify the content of that record against the IHE XML schema:.

     perl 1222/eval_server_1222.pl  IETF (or)

     perl 1222/eval_server_1222.pl  INTERIM

9. The results file 1222/grade_server_1222.txt should show 0 failures.

1223: Server Certificate Exchange with Expired Certificate

In this test, a MESA client application requests a network connection with your server using the standard X.509 certificates. The MESA server will attempt the TLS handshake by offering an expired certificate. You are expected to abort the network connection and log an audit record message with the MESA Audit Record Repository (at port 4000 on the MESA system).

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA applications are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1223/1223_server_test.pl

6. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_client.txt This should indicate the aborted network connection.
7. After the TLS handshake and aborted message sequence, examine the MESA log file in $MESA_TARGET/logs/tls_client.txt. This should indicate a successful TLS handshake.
8. Run the evaluation script to examine the last audit record sent by your system to the MESA Audit Record Repository. It should find the last audit record was for Node-Authentication failure and it should verify the content of that record against the IHE XML schema:.

      perl 1223/eval_server_1223.pl

9. The results file 1223/grade_server_1223.txt should show 0 failures.

1224: Server TLS Handshake for 3DES

Do not perform this test for the 2006-2007 cycle.

1226: Server DICOM Verification with TLS

This test establishes a TLS connection with your server and sends a DICOM C-Echo command (Verification class) to your system.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA applications are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1226/1226_server_test.pl

6. This should run to completion with no errors. If you encounter an error, you will need to correct the communication problem and rerun the test
7. When the test is working successfully, run the test and redirect the output to a file. Submit that file to the Project Manager for evaluation.

1227: Server DICOM Verification with TLS: Unregistered Certificate

This test attempts to establish a TLS connection with your server using an unregistered certificate. Should you accept the connection, the MESA application sends a DICOM C-Echo command (Verification class) to your system. The proper behavior is that your system refuses the TLS connection.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA applications are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1227/1227_server_test.pl

6. This should run to completion and indicate that a connection was not completed. If the script completes a DICOM verification this indicates an error that should be corrected.
7. When the test is working successfully, run the test and redirect the output to a file. Submit that file to the Project Manager for evaluation.

1228: Server DICOM Verification with TLS: Expired Certificate

This test attempts to establish a TLS connection with your server using an expired certificate. Should you accept the connection, the MESA application sends a DICOM C-Echo command (Verification class) to your system. The proper behavior is that your system refuses the TLS connection.

References

Instructions

1. Configure your system using the X.509 certificate assigned to you ($MESA_TARGET/runtime/certificates/test_sys_1). The MESA applications are configured to recognize this certificate.
2. Make sure the configuration file secure_test.cfg accurately describes your system.
3. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
4. (Optional) Clear the log files of prior messages:

   perl scripts/clear_logs.pl

5. Instruct the MESA client to open a connection with your server:

       perl 1228/1228_server_test.pl

6. This should run to completion and indicate that a connection was not completed. If the script completes a DICOM verification this indicates an error that should be corrected.
7. When the test is working successfully, run the test and redirect the output to a file. Submit that file to the Project Manager for evaluation.

Supplemental Information

The certificate used by the Image Manager for this test is located in $MESA_TARGET/runtime/certificates/expired.cert. You should try to configure your system to know that this is the peer certificate. This is to make sure you are testing for expired certificates rather than unregistered certificates.

11141: Client ATNA Certificate Exchange with Valid Certificate

References

Instructions

Run test 1221 described in this document.

Rename the grade file grade_11141.txt.

Submit the grade file to the Project Manager.

11142: Client ATNA Certificate Exchange with Unregistered Certificate

References

Instructions

Run test 1222 described in this document.

Rename the grade file grade_11142.txt.

Submit the grade file to the Project Manager.

11143: Client ATNA Certificate Exchange with Expired Certificate

References

Instructions

Run test 1223 described in this document.

Rename the grade file grade_11143.txt.

Submit the grade file to the Project Manager.

11180: System Audit Event

Test 11180 is a reference to other tests. Your “system” should generate one or more of the audit events listed in ITI TF 2:3.20.6.

Determine which log messages your system should generate in response to user events.

Run one or more of the tests 11181 – 11202 as appropriate for the user events.

Submit the grade message for test 11181 – 11202 as 11180. You may submit a zip file with multiple results

11181: Actor Start

In this test, the system generates an Actor Start log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Start event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11181/eval_11181.pl <log level>

2. The output file is 111181/grade_11181.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Actor Start. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11182: Actor Stop

In this test, the system generates an Actor Stop log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Stop event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11182/eval_11182.pl <log level>

2. The output file is 11182/grade_11182.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Actor Stop. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11183: Begin Storing Instances

In this test, the system generates a Begin Storing Instances log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Stop event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11183/eval_11183.pl <log level>

2. The output file is 11183/grade_11183.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Begin Storing Instances. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11184: Health-service-event

In this test, the system generates a Health Service Event log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Stop event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11184/eval_11184.pl <log level>

2. The output file is 11184/grade_11184.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Health Service Event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11185: Instances-deleted

In this test, the system generates an Instances Deleted log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Instances Deleted event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11185/eval_11185.pl <log level>

2. The output file is 11185/grade_11185.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Instances Deleted. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11186: Instances-Stored

In this test, the system generates an Instances Stored log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Instances Stored event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11186/eval_11186.pl <log level>

2. The output file is 11186/grade_11186.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Instances Stored. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11187: Medication

In this test, the system generates a Medication log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Medication event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11187/eval_11187.pl <log level>

2. The output file is 11187/grade_11187.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Medication event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

Supplemental Information

The trigger event is Health Service Event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11188: Mobile-machine-event/enter

In this test, the system generates a Mobile-Machine-Event (Enter) log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Mobile Machine Event (enter) event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11188/eval_11188.pl <log level>

2. The output file is 11188/grade_11188.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Mobile Machine Event (enter). See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11189: Mobile-machine-event/leave

In this test, the system generates a Mobile-Machine-Event (Leave) log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Mobile Machine Event (leave) event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11189/eval_11189.pl <log level>

2. The output file is 11189/grade_11189.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Mobile Machine Event (leave). See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11190: Node-Authentication-Failure

In this test, the system generates a Node-Authentication-Failure log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Node-Authentication-Failure event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11190/eval_11190.pl <log level>

2. The output file is 11190/grade_11190.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Node-Authentication-Failure. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11191: Order-record-event

In this test, the system generates an Order-record-event log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Order-record-event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11191/eval_11191.pl <log level>

2. The output file is 11191/grade_11191.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Order-record-event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11192: Patient-care-assignment

In this test, the system generates a Patient-Care-Assignment log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Patient-care-assignment event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11192/eval_11192.pl <log level>

2. The output file is 11192/grade_11192.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Patient-care-assignment. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11193: Patient-care-episode

In this test, the system generates a Patient-care-episode log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Patient-care-episode event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11193/eval_11193.pl <log level>

2. The output file is 11193/grade_11193.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Patient-care-episode. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11194: Patient-care-protocol

In this test, the system generates a Patient-care-protocol log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Patient-care-protocol event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11194/eval_11194.pl <log level>

2. The output file is 11194/grade_11194.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Patient-care-protocol. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11195: Patient-record-event

In this test, the system generates a Patient-record-event log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Patient-care-protocol event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11195/eval_11195.pl <log level>

2. The output file is 11195/grade_11195.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Patient-record-event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11196: PHI-export

In this test, the system generates a PHI Export log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Stop event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11196/eval_11196.pl <log level>

2. The output file is 11196/grade_11196.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is PHI Export. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11197: PHI-import

In this test, the system generates a PHI Import log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Actor Stop event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11197/eval_11197.pl <log level>

2. The output file is 11197/grade_11197.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is PHI-Import. See DICOM Supplement 95 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11198: Procedure-record-event

In this test, the system generates a Procedure-record-event log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Procedure-care-protocol event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11198/eval_11198.pl <log level>

2. The output file is 11198/grade_11198.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Procedure-record-event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11199: Query Information

In this test, the system generates a Query Information log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Query Information event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11199/eval_11199.pl <log level>

2. The output file is 11199/grade_11199.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Query Information event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11200: Security Administration

In this test, the system generates a Security Administration log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Security Administration event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11200/eval_11200.pl <log level>

2. The output file is 11200/grade_11200.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Query Information event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11201: Study-Object-Event

In this test, the system generates a Security Administration log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Security Administration event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11201/eval_11201.pl <log level>

2. The output file is 11201/grade_11201.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Security Administration event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11202: Study-used

In this test, the system generates a Study-used log message and evaluates it using the MESA tools.

References

Instructions

Perform these instructions using a DOS/Command prompt window or terminal emulator.

1. Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/secure_node.
2. Make sure the MESA servers have been started. See Starting the MESA Servers for details.
3. Generate an audit record message for the Study-used event. Send this message to the MESA syslog server (Syslog UDP protocol, port 4000).
4. Examine the file $MESA_TARGET/logs/syslog/last_log.xml. This should contain your ATNA log message. If not, the BSD syslog communication failed.

Evaluation

To evaluate your response to this test:

1. From the $MESA_TARGET/mesa_tests/iti/actors/secure_node directory, run the evaluation script

   perl 11202/eval_11202.pl <log level>

2. The output file is 11202/grade_11202.txt. This test is successfully completed when the last line in the output file indicates 0 errors.
3. Submit the grade file to the Project Manager.

Supplemental Information

The trigger event is Study-used event. See ITI TF-2 for details. This section defines the values expected/required by this test. If your interpretation of the values for these fields differs from ours, please contact us.

11141: ATNA Certificate Exchange with Valid Certificate

References

Instructions

Run test 1221 described in this document. Rename the grade file grade_11141.txt. Submit the grade file to the Project Manager.

Supplemental Information

11142: ATNA Certificate Exchange with Unregistered Certificate

References

Instructions

Run test 1222 described in this document. Rename the grade file grade_11142.txt. Submit the grade file to the Project Manager. Submit the grade file to the Project Manager.

Supplemental Information

11143: ATNA Certificate Exchange with Expired Certificate

References

Instructions

Run test 1223 described in this document. Rename the grade file grade_11143.txt. Submit the grade file to the Project Manager. Submit the grade file to the Project Manager.

Supplemental Information