Auditing and Logging Sample Clauses

Auditing and Logging. Matterport will maintain system audit or event logging and related monitoring procedures to proactively record user access and system activity for routine review. Matterport will create, protect and retain such log records to the extent needed to enable monitoring, analysis, investigation and reporting of unlawful, unauthorized or inappropriate information system activity, including successful and unsuccessful account logon events, account management, events, security events, object access, policy change, privileged functions, administrator account creation/deletion and other administrator activity, data deletions, data access and changes, firewall logs, and permission changes.
AutoNDA by SimpleDocs
Auditing and Logging. Remote User agrees that his/her remote access is subject to review and/or audit by Children’s. Upon notice, Remote User agrees to return any Children’s-owned portable device for purposes of ensuring compliance with this Agreement and the policies described herein.
Auditing and Logging. With respect to system auditing and logging, DocuSign will do the following:
Auditing and Logging. Application must support interoperability with, and stream logs to the City’s centralized Sumo Logic Security Information and Event Management (SIEM) platform for, at a minimum, all security related events including logon, logoff, data modification, data deletion, change in rights or permission levels, and the addition of data/information to the application. Logs must include user ID generating the transaction, time of the transaction and details regarding the activity (e.g., logon, logoff, or data details). Partially Compliant 1.7 Compliance with Organization’s Security Policy, Standards and Procedures. Solution Proposer working directly on City-owned applications or from City facilities are subject to, and required to follow, all City policies, standards, and guidelines. Proposer must also follow FIPS 140-2 standards which can be viewed at xxxx://xxxx.xxxx.xxx/groups/STM/cmvp/standards.html For FIPS-140-2 the City requires Level 2 compliance; the City requires at least role based authentication for access to this application. N/A 1.8

Related to Auditing and Logging

  • 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.

  • REPORTING AND EVALUATION The Provider agrees to comply with 7 AAC 81.120, Confidentiality and 7 AAC 81.150, Reports, and other applicable state or federal law regarding the submission of information, including the provisions of Section VI of this Agreement. The Provider agrees to submit any reporting information required under this Agreement and to make available information deemed necessary by DHSS to evaluate the efficacy of service delivery or compliance with applicable state or federal statutes or regulations. The Provider agrees to provide state officials and their representatives access to facilities, systems, books and records, for the purpose of monitoring compliance with this Agreement and evaluating services provided under this Agreement. On-site Quality Assurance Reviews may be conducted by DHSS staff to ensure compliance with service protocols. The Provider will ensure that DHSS staff has access to program files for the purposes of follow-up, quality assurance monitoring and fiscal administration of the program.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!