Activity Logging Clause Samples
The Activity Logging clause requires parties to systematically record actions, events, or transactions related to the agreement. This typically involves maintaining logs of user access, system changes, or data modifications, often specifying the format, retention period, and access controls for these records. By mandating detailed documentation, the clause ensures accountability, supports audits, and helps resolve disputes by providing a verifiable history of relevant activities.
Activity Logging. Where technically available, IBM maintains logs of access to systems and applications in order to detect and prevent unauthorized activity.
Activity Logging. Where technically available, for systems, applications, data repositories, middleware and network infrastructure devices, IBM’s team maintains logs of its activity. To minimize the possibility of tampering and to enable central analysis, alerting and reporting, activity logging is done in real-time to central log repositories. Data is signed to prevent tampering. Logs are analyzed in real-time and via periodic analysis reports to look for anomalous behavior. Operations staff is alerted to anomalies and contacts a 24x7 on-call security specialist when needed.
Activity Logging. Where technically available, for systems, applications, data repositories, middleware and network infrastructure devices, IBM maintains logs for recording: i) successful and unsuccessful logon access attempts, ii) successful and unsuccessful attempts to gain access to the infrastructure from an external location, iii) update access attempts to OSRs, and iv) activities performed using system or security administrative authority.