Audit Logs. The Subscriber may use, in combination with the SORACOM Air Global Service, the Audit Logs, which allows Subscriber to check the history of logins and API calls.
Audit Logs. Company will comply with all laws and regulations regulating record retention policies and recording how and by whom records were modified as well as historical views of Saint Luke’s Data, that are in effect during the term of the Agreement. Company shall ensure audit trails are maintained with regard to access to all Saint Luke’s Data. Company shall investigate any security breach resulting in unauthorized access to such Saint Luke’s Data, and provide additional security protections, at no additional charge to Saint Luke’s, to correct any security deficiencies identified by Saint Luke’s. Company will retain the system and security logs generated by the operating system and security software for twelve (12) months.
Audit Logs. Each Participant will maintain a system for its Research Repository to maintain an audit log process whereby access to the system is logged and recorded in accordance with the requirements of the Security Rule. The Audit Log process will be subject to approval of the GPC Governing Council. The GPC through its GPC Infrastructure and Software Development Core will maintain corresponding Audit Log processes for GPC Hosted Services.
Audit Logs. 7.2.1. Participant Participant shall log the following information: (i) date and time Message Content was accessed and the identity (e.g., unique identifier) of the individual or system, as applicable, accessing the Message Content; (ii) date and time Message Content was sent to the Services and the identity of the individual or system, as applicable, sending the Message Content; (iii) date and time a Notice was sent or received from or to the Services; (iv) the unique message identifier for the Message Content accessed, sent, or received; (v) the Message Content accessed; and (vi) any Notices, failures, or network events.
Audit Logs. Audit logs shall capture, at a minimum, the information for each security-related event defined below:
Audit Logs. The Supplier will maintain audit logs of all access to Reserve Bank PII and will actively monitor them for unauthorized access.
Audit Logs. Vendor shall generate audit logs periodically for actual or attempted unauthorized use, access, disclosure, theft, manipulation, reproduction or possible compromise of any application or system associated with the access, processing, storage, communication and/or transmission of The Hartford Data. Vendor shall review the audit logs on a periodic basis and maintain adequate evidence of its review for the purposes of an audit. Vendor shall maintain the audit logs in accordance with the terms and conditions of the Agreement for no less than twelve (12) months and provide summaries to The Hartford upon request. Any instance in which an audit log reveals evidence of any unauthorized use, access, disclosure, theft, manipulation, reproduction and/or possible compromise of The Hartford Data shall be deemed a Security Breach (as defined below).
Audit Logs. 7.2.1. PO PO shall log the following information: (i) date and time Message Content was accessed and the identity (e.g., unique identifier) of the individual or system, as applicable, accessing the Message Content; (ii) date and time Message Content was sent to the HIN Services and the identity of the individual or system, as applicable, sending the Message Content; (iii) date and time a Notice was sent or received from or to the HIN Services; (iv) the unique message identifier for the Message Content accessed, sent, or received; (v) the Message Content accessed; and (vi) any Notices, failures, or network events.
Audit Logs. Bluemix performs period audits of access logs to enable visibility into who logged into various systems, failed authentications, etc. to detect potentially unauthorized access or network attacks.
Audit Logs
