System Logs Clause Samples

The System Logs clause establishes requirements for the creation, maintenance, and access to records of system activity within an organization or between contracting parties. Typically, this clause specifies what types of events must be logged, how long logs should be retained, and who is permitted to review or audit these records. By mandating systematic logging, the clause helps ensure accountability, supports security investigations, and provides a reliable audit trail to detect or resolve operational issues.
System Logs. SpiralFrog will keep track of all download data by user in an SQL database. The database is organized in such a way that it is easy to generate reports on a daily, weekly or monthly basis by record label, artist, genre or user demographic group. SpiralFrog will also record play counts for all content – this is reported to SpiralFrog by Windows Media Player Manager. All play count data is recorded in the SQL database. SpiralFrog will keep records of all database information related to licensed content for as long as it is required to do so by terms specified elsewhere in this agreement.
System Logs. For all systems that access, transmit or store Covered Information of the other Party, system logs shall be in place to uniquely identify individual users and their access to associated systems and to identify, record and clearly depict all attempted or executed activities of any one or more such users. All systems creating system logs shall be synchronized to a central time source. Reasonable processes shall be in place to review privileged access and identify, investigate and respond to suspicious or malicious activity. System log trails shall be secured in a manner to prevent unauthorized access, modification, and accidental or deliberate destruction. These logs shall be maintained in accordance with the retention requirements set forth in the Agreement. If not specified elsewhere, logs shall be maintained in accordance with the following: Security devices, perimeter devices and policy enforcement points e.g. firewalls, VPN servers, intrusion detection systems 13 months Network logon records e.g. domain controllers, Active Directory logs 120 days All other systems and applications 60 days The requirements listed above do not supersede, or otherwise limit the applicability of or the need to comply with, retention requirements that are governed by law, regulations or industry requirements, such as PCI DSS.
System Logs. For all systems that access, transmit or store Covered Information of the other Party, system logs shall be in place to uniquely identify individual users and their access to associated systems and to identify, record and clearly depict all attempted or executed activities of any one or more such users. All systems creating system logs shall be synchronized to a central time source. Reasonable processes shall be in place to review privileged access and identify, investigate and respond to suspicious or malicious activity. System log trails shall be secured in a manner to prevent unauthorized access, modification, and accidental or deliberate destruction. These logs shall be maintained in accordance with the retention requirements set forth in the Agreement. If not specified elsewhere, logs shall be maintained in accordance with the following: System Category Log Retention Period Security devices, perimeter devices and policy enforcement points e.g. firewalls, VPN servers, intrusion detection systems 13 months Network logon records e.g. domain controllers, Active Directory logs 120 days All other systems and applications 60 days The requirements listed above do not supersede, or otherwise limit the applicability of or the need to comply with, retention requirements that are governed by law, regulations or industry requirements, such as PCI DSS.
System Logs. All deliveries shall be made in accordance with the Parties' schedules which are in effect 30 minutes prior to each hour of delivery, except deliveries associated with Load Following service which shall reflect the integrated amount accumulated over the hour and shall be deemed to be made during the hours and in the amounts as accounted for in LEM's and Big Rivers' system logs. If scheduled deliveries are interrupted due to an Uncontrollable Force as defined in Section 12, such schedules shall be adjusted to reflect actual deliveries.

Related to System Logs

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Use (a) An electronic site access system may be used on site, subject to the requirements of this statement. (b) The system operates via: (i) a facial recognition device; and (ii) an electronic gate. (c) The system will be installed at the access and egress point/s of the site and will only be utilised to identify presence on site. (d) The purpose for which the electronic site access system will be implemented is to ensure: (i) avoiding unauthorised access to site; (ii) confirmation and co-ordination of effort in emergency situations; and (iii) confirmation that all entrants to site have received a site specific induction; (e) The only personal data collected by the system is a site entrant’s: (i) image; (ii) first & last name; (iii) mobile phone number; (iv) email address; and (v) employer’s name. (the Collected Data) (f) The Collected Data will only be held or used for the purposes specified above, unless otherwise by consent or required by law. (g) The Employer will not use the electronic site access control system to verify who was on a site at a particular time for the purpose of: (i) evaluating whether a variation claim regarding labour costs made by a subcontractor can be substantiated; (ii) taking disciplinary action against an Employee, or assisting a subcontractor to take disciplinary action against its own employees, regarding their start and finish times; or (iii) otherwise generally tracking a worker’s movements whilst on the site.

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the ISO OATT.