Security Logs Clause Samples
The Security Logs clause requires parties to maintain detailed records of security-related events and activities within their systems. Typically, this involves logging access attempts, system changes, and incidents that could affect data integrity or confidentiality, and may specify retention periods or access controls for these logs. Its core function is to provide a reliable audit trail that supports investigations, compliance, and accountability in the event of a security breach or dispute.
POPULAR SAMPLE Copied 1 times
Security Logs. Logs are generated for security-relevant activities on operating systems. Systems are configured to log default security activities, access to information or programs, system events such as alerts, console messages, and system errors. Oracle reviews logs for forensic purposes and incidents; identified anomalous activities feed into the incident management process. Security logs are stored within the Security Information and Event Management system in a native, unaltered format and retained in accordance with Oracle's internal policies. Such logs are retained online for a minimum of ninety (90) days, or as otherwise required by an applicable regulatory framework.
Security Logs. All Braze systems used in the provision of the Braze Services, including firewalls, routers, network switches, and operating systems log information to their respective system log facility or a centralized syslog server (for network systems) in order to enable security reviews and analysis. Braze has automated alerts and searches on these logs.
Security Logs. Maximl Labs Pvt Ltd’s systems have logging enabled to their respective system log facility in order to support the security audits, and monitor and detect actual and attempted attacks on, or intrusions into, Maximl Labs Pvt Ltd’s systems.
Security Logs. FF shall ensure that all FF or Sub-processor systems used to store Customer Data, including firewalls, routers, network switches and operating systems, log information to their respective system log facility or a centralised syslog server (for network systems).
Security Logs. As it relates to any Cloud Services, the CSP and Vendor Contractors shall provide security logs and reports to a Governmental Entity or its Authorized Contractors in a mutually agreeable format upon request. Such reports shall include at least latency statistics, user access summaries, user access IP address summaries, user access history and security logs for all Customer Data.
Security Logs. Processor’s systems have logging enabled to their respective system log facility in order to support the security audits, and monitor and detect actual and attempted attacks on, or intrusions into, Processor’s systems.
Security Logs. Company’s systems have logging enabled to their respective system log facility in order to support the security audits, and monitor and detect actual and attempted attacks on, or intrusions into, Company’s systems.
Security Logs. All Insider systems used in the provision of the Insider Services, including firewalls, routers, network switches, and operating systems log information to their respective system log facility in order to enable security reviews and analysis.
Security Logs. All PassKit systems used in the provision of the PassKit Services, including firewalls, routers, network switches, and operating systems log information to their respective system log facility or a centralized logging service (for cloud systems) in order to enable security reviews and analysis. PassKit has automated alerts and searches on these logs.
Security Logs. All Inkit systems used in the provision of the Services, including firewalls, routers, network switches, and operating systems, log information to their respective system log facility or a centralized syslog server (for network systems) in order to enable security reviews and analysis. Inkit has automated alerts and searches for such logs.