Audit Logging and Monitoring. Box shall implement the following controls for audit logging and monitoring:
Audit Logging and Monitoring. 1. Vendor shall develop audit logging and log monitoring policies and procedures, which includes the capturing of finical transaction and security incident audit logs in a central audit logging solution.
2. Vendor audit logs shall consist of all relevant security event logs for the Systems. This includes logs from systems and devices including, but is not limited to: firewalls, IDS/IPS, authentication systems, applications, databases and VPN devices.
3. Audit log monitoring shall include correlation of events and the generation of alerts and escalation to Vendor information security resources in a timely manner, including support twenty-four (24) hours a day, seven (7) days a week, three-hundred and sixty-five (365) days a year, in the event of critical or high severity security alerts.
4. Systems shall maintain synchronized time to ensure adequate support for accurate correlation of events across systems, applications and network devices.
5. Audit log entries should utilize write-once or tamper proof capabilities to ensure logs are not modified.
6. Audit log events shall include sufficient level required to support forensics investigations. Such detail may include, but is not limited to: timestamp, source IP address, destination IP address, system name, user name, system or application process ID, description of error and activity or function performed.
7. Financial transaction audit logs should be designed to reconstruct material financial transactions sufficient to support normal operations and obligations of Renaissance. Financial transaction audit logs shall be retained for a minimum of five (5) years.
8. Security Incident audit logs shall be retained for a minimum of three (3) years, or, if involved in an investigation, until such investigation is completed, whichever is later.
9. Vendor shall provide a summary of events and alerts to Renaissance upon request.
Audit Logging and Monitoring. 3.1 The Service Provider should put in place appropriate monitoring tools and processes to support and maintain the key performance indicators and Service Levels to identify any changes in demand or usage of the solution/service.
3.2 The solution/service must maintain logs and records for audit purposes. Audit logs and records must be maintained in a way that facilitates finding or identifying specific items within the log, and which supports a policy of Forensic Readiness capable of supporting the investigation and response to security breaches.
3.3 The solution/service must maintain a log or record of all access to the solution/service. The access log will be maintained such that it is possible to identify all successful and unsuccessful access attempts.
3.4 The solution/service will log or record all operations and changes made to data and information. As a minimum, it should be possible to identify the user that accessed the solution/service, and the time the access or any change was made. This will include changes and uploads made by web users.
3.5 Audit and monitoring logs and records will be available to designated authorised users.
3.6 It will not be possible to amend or delete any audit trail without a separate audit event capturing these changes.
3.7 Audit and log data will be held for the same amount of time as the source data it pertains to (i.e. for the same data retention period).
3.8 When data or information is changed, a record of the original data should be maintained. Note: The exact requirement as to which data this applies to will be normally determined as part of
Audit Logging and Monitoring. 4.1 The Supplier shall put in place appropriate monitoring tools and processes to support and maintain the Key Performance Indicators and to provide management information.
4.2 The System shall maintain logs and records for audit purposes. Audit logs and records shall be maintained in a way that facilitates finding or identifying specific items within the log, and which supports a policy of forensic readiness capable of supporting the investigation and response to security breaches.
4.3 The System shall log or record all operations and changes made to data and information. As a minimum, it should be possible to identify the user that accessed the System, and the time the access or any change was made, including changes and uploads made by web users.
4.4 Audit and monitoring logs and records shall be available to designated authorised users and the Authority if so requested.
4.5 It shall not be possible to amend or delete any audit trail without a separate audit event capturing these changes.
4.6 Audit and log data shall be held for the same amount of time as the source data it pertains to (i.e. for the same data retention period).
4.7 When data or information is changed, a record of the original data must be maintained.
4.8 The System shall not delete from audit and monitoring logs any data relating to users.
4.9 The creation and storage of audit logs shall not impact on the performance of the transcription service.
4.10 In the event of error or component failure, the relevant log files must provide enough information to support investigation and isolation of the point and possible cause of failure.
Audit Logging and Monitoring. 5.1 The Supplier shall put in place appropriate monitoring tools and processes to support and maintain the Key Performance Indicators and Service Levels and to identify any changes in demand or usage of the Booking Service.
5.2 The Booking Service must maintain logs and records for audit purposes. Audit logs and records must be maintained in a way that facilitates finding or identifying specific items within the log, and which supports a policy of forensic readiness capable of supporting the investigation and response to security breaches.
5.3 The Booking Service must maintain a log or record of all access to the Booking Service. The access log will be maintained such that it is possible to identify all successful and unsuccessful access attempts.
5.4 The Booking Service must log or record all operations and changes made to data and information. As a minimum, it should be possible to identify the user that accessed the Booking Service, and the time the access or any change was made, including changes and uploads made by web users.
5.5 Audit and monitoring logs and records must be available to designated authorised users.
5.6 It must not be possible to amend or delete any audit trail without a separate audit event capturing these changes.
5.7 Audit and log data must be held for the same amount of time as the source data it pertains to (i.e. for the same data retention period).
5.8 When data or information is changed, a record of the original data must be maintained.
5.9 The Booking Service must not delete from audit and monitoring logs any data relating to users who have been removed from the Booking Service.
5.10 The creation and storage of audit logs must not impact on the performance of the Booking Service.
5.11 In the event of error or component failure, the relevant log files must provide enough information to support investigation and isolation of the point and possible cause of failure.
Audit Logging and Monitoring. 5.1 The Supplier shall put in place appropriate monitoring tools and processes to support and maintain the Key Performance Indicators and to identify any changes in demand or usage of the Booking Service.
5.2 The Booking Service must maintain logs and records for audit purposes. Audit logs and records must be maintained in a way that facilitates finding or identifying specific items within the log, and which supports a policy of forensic readiness capable of supporting the investigation and response to security breaches.
5.3 The Booking Service must maintain a log or record of all access to the Booking Service. The access log will be maintained such that it is possible to identify all successful and unsuccessful access attempts.
5.4 The Booking Service must log or record all operations and changes made to data and information. As a minimum, it should be possible to identify the user that accessed the Booking Service, and the time the access or any change was made, including changes and uploads made by web users.
5.5 Audit and monitoring logs and records must be available to designated authorised users.
5.6 It must not be possible to amend or delete any audit trail without a separate audit event capturing these changes.
