Audit Logging and Monitoring Sample Clauses

Audit Logging and Monitoring. Box shall implement the following controls for audit logging and monitoring:
Sample 1Sample 2Sample 3See All (6)
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.
Sample 1Sample 2
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
Sample 1
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.
Sample 1
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.
Sample 1
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.
Sample 1

Related to Audit Logging and Monitoring

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards. 2. Grantee agrees to cooperate fully and provide the System Agency and its representatives timely access to Products, records, and other items and information needed to conduct such review, evaluation, testing, and monitoring.

  • Reporting and Monitoring Please provide a brief description of the mechanisms proposed for this project for reporting to the UNDP and partners, including a reporting schedule.

  • ANALYSIS AND MONITORING The Custodian shall (a) provide the Fund (or its duly-authorized investment manager or investment adviser) with an analysis of the custody risks associated with maintaining assets with the Eligible Securities Depositories set forth on Schedule B hereto in accordance with section (a)(1)(i)(A) of Rule 17f-7, and (b) monitor such risks on a continuing basis, and promptly notify the Fund (or its duly-authorized investment manager or investment adviser) of any material change in such risks, in accordance with section (a)(1)(i)(B) of Rule 17f-7.

  • EVALUATION AND MONITORING The ORGANIZATION agrees to maintain books, records and other documents and evidence, and to use accounting procedures and practices that sufficiently and properly support the complete performance of and the full compliance with this Agreement. The ORGANIZATION will retain these supporting books, records, documents and other materials for at least three (3) calendar years following the year in which the Agreement expires. The COUNTY and/or the State Auditor and any of their representatives shall have full and complete access to these books, records and other documents and evidence retained by the ORGANIZATION respecting all matters covered in and under this Agreement, and shall have the right to examine such during normal business hours as often as the COUNTY and/or the State Auditor may deem necessary. Such representatives shall be permitted to audit, examine and make excerpts or transcripts from such records, and to make audits of all contracts, invoices, materials, and records of matters covered by this Agreement. These access and examination rights shall last for three calendar years following the year in which the Agreement expires. The COUNTY intends without guarantee for its agents to use reasonable security procedures and protections to assure that related records and documents provided by the ORGANIZATION are not erroneously disclosed to third parties. The COUNTY will, however, disclose or make this material available to those authorized by/in the above paragraph or permitted under the provisions of Chapter 42.56 RCW without notice to the ORGANIZATION. The ORGANIZATION shall cooperate with and freely participate in any other monitoring or evaluation activities pertinent to this Agreement that the COUNTY finds needing to be conducted.

  • Program Monitoring and Evaluation The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Monitoring and Review The Provider agrees to allow access to the Department for purposes of monitoring and review. This access includes but is not limited to client records, fiscal records, staffing records, policy and procedural manuals, facilities, staff, and children in care of the Department. The Department will conduct quality reviews, which may include site-based quality review visits.

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee: a. Grantee must maintain a financial tracking system provided by Florida Housing that ensures that CRF funds are Expended in accordance with the requirements in this Agreement. b. Grantee must maintain records on all awards to Eligible Persons or Households. These records must include, but are not limited to: i. Proof of income compliance (documentation from submission month, including but not limited to paystub, Florida unemployment statement, social security and/or disability statement, etc.); ii. Lease; and iii. Documentation of rental assistance payments made.

Most Referenced Clauses

Most Referenced Definitions