One entry per configuration from TM (as receiver) One entry per configuration in TM (as sender) list the events which must be audited and give the user the possibility to attach the link to the EVSClient report of audit trail message validation In the former questionnaire, user was asked to describe the authentication process of local users One entry per inbound/outbound network communication type : Will help the user to know which TLS tests to perform and the monitor to check that all tests were performed and OK comes from 3b in former questionnaire, needs to determine what we expect here in the new questionnaire who created the questionnaire which company owns the SUT system keyword in TM status of the questionnaire monitor who reviewed the questionnaire is the SUT secure application or secure node unique identifier of the questionnaire URL of the validation report in EVSClient OID of the validator to use validation status retrieve from EVSClient or given by the monitor if there is no validator defined for this event URL of the test in TLS simulator available tests in TLS Simulators are for HL7v2 (MLLP), DICOM, Syslog and HTTP this the SUT acting as Client or Server for this test : client test is requested for outbound connections and server test for inbound connections status of the test in TLS Simulator (extracted thanks to the URL of the test)