Event Logging Sample Clauses
Event Logging. For Computershare’s systems directly utilized for providing services to Customer and/or processing or storing Customer Confidential Information, Computershare shall maintain logs of key events that may affect the confidentiality, integrity, and/or availability of the Service to Customer and that may assist in the identification or investigation of material incidents and/or security breaches occurring in relation to Computershare systems. Computershare shall retain the log for at least 12 months and protect the log against unauthorized changes (including, unauthorized amending or deleting a log). Computershare shall regularly review the logs of all key events within Computershare systems (preferably using automated tools) and notify Customer upon identification of any Incidents in accordance with Section (ii)(a) of this Schedule.
Event Logging. The Data Importer logs the use of our data-processing systems. We maintain logs for at least 10 days.
Event Logging a. Acuity logs the use of our dataprocessing systems.
b. Acuity logs access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity.
Event Logging. A. Microsoft logs the use of our data-processing systems.
B. Microsoft logs access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity.
Event Logging. For systems directly providing the Service Offering to Customer, NetWitness shall maintain logs of key events that may affect the confidentiality, integrity, and/or availability of the Service Offering to Customer and that may assist in the identification or investigation of material incidents and/or security breaches occurring in relation to NetWitness systems. The logs shall be retained for at least 90 days and protected against unauthorized changes (including, amending or deleting a log).
Event Logging. Provider logs the use of data-processing systems. Logs are maintained for at least 10 days.
Event Logging. OneNeck shall collect a log of all loss of connectivity events within the monitoring tool.
Event Logging. In performance of the services in the RSA, Enom collects logs. Logs may include access ID, time, authorization granted or denied, diagnostic data, and other relevant activity. Logs are used (i) for providing, securing, managing, measuring and improving the Enom services, (ii) as directed or instructed by Customer and its Users, and/or (iii) for compliance with Enom policies, applicable law, regulation, or governmental request. This may include monitoring the performance, stability, usage and security of the Enom’ services.
Event Logging. Data importer has and will log all key security-related events, including user activities, exceptions, faults, and information security events, which will be produced, kept and regularly reviewed.
Event Logging a. Log files should be activated for each system/application used for the processing of personal data. They should include all types of access to data (view, modification, deletion).
b. Log files should be timestamped and adequately protected against tampering and unauthorized access. Clocks should be synchronized to a single reference time source.
c. Actions of the system administrators and system operators, including addition/deletion/change of user rights should be logged.
d. There should be no possibility of deletion or modification of log files content. Access to the log files should also be logged in addition to monitoring for detecting unusual activity.
e. A monitoring system should process the log files and produce reports on the status of the system and notify for potential alerts.