Auditing and Logging Sample Clauses

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

Auditing and Logging. With respect to system auditing and logging, DocuSign will do the following: (a) DocuSign will use and maintain an auditing and logging mechanism that, at a minimum, captures and records successful and failed user logons and logoffs (with a date and time stamp, user ID, application name, and pass/fail indicator). User access activities will be logged and audited periodically by DocuSign to identify unauthorized access and to determine possible flaws in DocuSign’s access control system. (b) All application components that have logging capabilities (such as operating systems, databases, web servers, and applications) will be configured to produce a security audit log. (c) Audit logs will be configured for sufficient log storage capacity. (d) Each log will be configured so that it cannot be disabled without proper authorization and will send alerts for the success or failure of each auditable event. (e) Access to security log files will be limited to authorized Personnel, and to Customer upon request. (f) In regard to DocuSign’s development, access to source code by team members must be reviewed at least every ninety (90) days. (g) In regard to DocuSign’s support, DocuSign will maintain a process to help assure that any individual leaving DocuSign’s team that provides support to Customer will lose access to Customer’s accounts and data upon termination of employment or as soon as reasonably possible after moving to another position within DocuSign.

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