Security Event Logs definition

Security Event Logs means any logs (also known as audit records) of events, notifications or alerts that any component of any Device or other device (not limited to security device), or any Systems or other system or software is technically capable of producing in relation to its status, functions and activities that may be used for such purposes as security investigations, auditing, monitoring and determining security incidents (examples of components capable of producing such logs include firewalls, intrusion prevention systems, routers, switches, content filtering, network traffic flow logs, networks, authentication services, directory services, dynamic host configuration protocols, dynamic naming services, hardware platforms, virtualization platforms, servers, operating systems, web servers, databases, applications, application firewalls);
View Source
Security Event Logs means any event, notification or alert that a device, Systems or software is technically capable of producing and is configured to produce in relation to its status, such as a notification of configuration change or notification of log-on/log-off events (also referred to as infrastructure event logs); or any event, notification or alert that a device, Systems or software is technically capable of producing and is configured to produce in relation to its function and activities, such as data/traffic/sessions routed, transmitted, blocked or permitted (also referred to as activity/function event logs). Security Event Logs are not limited to security devices, but are applicable to all devices, Systems and software that are technically capable of producing and are configured to produce event logs that can be used in security investigations, auditing and monitoring. Examples of Systems that can produce security event logs are, but not limited to: routers, switches, content filtering, network traffic flow, network firewalls, intrusion prevention systems, servers, applications, databases, operating systems, virtualization platform, application firewalls, authentication services, directory services, DHCP, DNS, and hardware platforms. Security Event Logs are event logs that can be used in security investigations, auditing or monitoring and can give rise to a security incident or Information Incident;
View Source

Examples of Security Event Logs in a sentence

  • The Contractor must review Security Event Logs regularly to detect potential security incidents, using automated tools or equivalent processes for the monitoring, review, correlating and alerting of Security Event Logs.

  • The Contractor must ensure that Protected Information and Tenancy Security Event Logs on magnetic media are securely wiped by overwriting using procedures and adequate media wiping solutions, degaussing, or other method in line with security best practices for disposal of media.

  • The Contractor must ensure that logging of Security Event Logs is enabled on all applicable Systems components The Contractor must retain Security Event Logs for the Systems online for a minimum of 90 days and either online or off-line for an additional period of time adequate to enable the Contractor to conduct effective security investigations into suspected or actual security incidents.

  • The Contractor must retain Tenancy Security Event Logs online for a minimum of 90 days and either: such additional period of time as the Province may instruct; or ensure that the Tenancy offers the technical capability for the Province to retain the Tenancy Security Event Logs, to enable the Province to comply with an information schedule approved under the Information Management Act or other retention period required by law.

  • At any time after the Issue Date of this Debenture but not after the date which is 180 days after the date of the Purchase Agreement, the Company may, at the option of the Company, redeem all of the outstanding aggregate principal amount of this Debenture at a redemption price (plus accrued and unpaid interest and penalties thereon) equal to 125% of the aggregate principal amount of this Debenture (the "Redemption Price").

  • The Contractor must securely erase: records that contain Protected Information and Tenancy Security Event Logs when instructed in writing by the Province; and any backup, transitory and extra copies of records that contain Protected Information or Tenancy Security Event Logs when no longer needed in relation to this Agreement.

  • The Contractor must retain Tenancy Security Event Logs online for a minimum of 90 days and either: such additional period of time as the Purchaser may instruct; or ensure that the Tenancy offers the technical capability for the Purchaser to retain the Tenancy Security Event Logs, to enable the Purchaser to comply with an information schedule approved under the Information Management Act or other retention period required by law.

  • The Contractor must securely erase: records that contain Protected Information and Tenancy Security Event Logs when instructed in writing by the Purchaser; and any backup, transitory and extra copies of records that contain Protected Information or Tenancy Security Event Logs when no longer needed in relation to this Order.

  • Upon the Purchaser’s request, the Contractor must ensure that the Tenancy offers the technical capability for the Purchaser to enable or configure the forwarding, extraction, backup of Tenancy Security Event Logs from the Tenancy to the Purchaser’s security information and event management system or to an external log storage and retention system.

  • The Contractor must ensure that logging of Security Event Logs is enabled on all applicable Systems components.

Related to Security Event Logs

  • Security Event means an immediately reportable subset of security incidents which incident would include: a. A suspected penetration of Contractor’s information system of which the Contractor becomes aware of but for which it is not able to verify immediately upon becoming aware of the suspected incident that PHI was not accessed, stolen, used, disclosed, modified, or destroyed; b. Any indication, evidence, or other security documentation that the Contractor’s network resources, including, but not limited to, software, network routers, firewalls, database and application servers, intrusion detection systems or other security appliances, may have been damaged, modified, taken over by proxy, or otherwise compromised, for which Contractor cannot refute the indication of the time the Contractor became aware of such indication; c. A breach of the security of the Contractor’s information system(s) by unauthorized acquisition, including, but not limited to, access to or use, disclosure, modification or destruction, of unencrypted computerized data and which incident materially compromises the security, confidentiality, or integrity of the PHI; and or, d. The unauthorized acquisition, including but not limited to access to or use, disclosure, modification or destruction, of unencrypted PHI or other confidential information of the County by an employee or authorized user of Contractor’s system(s) which materially compromises the security, confidentiality, or integrity of PHI or other confidential information of the County. If data acquired (including but not limited to access to or use, disclosure, modification or destruction of such data) is in encrypted format but the decryption key which would allow the decoding of the data is also taken, the parties shall treat the acquisition as a breach for purposes of determining appropriate response.

  • Cybersecurity Event means any act or attempt, successful or, to the extent known by Provider, unsuccessful, to gain unauthorized access to, disrupt or misuse an Information System or Nonpublic Information stored on such Information System. The ongoing existence and occurrence of attempted but Unsuccessful Security Incidents shall not constitute a Cybersecurity Event under this definition. “Unsuccessful Security Incidents” are activities such as pings and other broadcast attacks on Provider’s firewall, port scans, unsuccessful log-on attempts, denials of service and any combination of the above, so long as no such incident results in unauthorized access, use or disclosure of Molina Nonpublic Information or sustained interruption of service obligations to Molina.

  • Switch Event Date means the date recorded in the Registry as being the date on which a trader assumes responsibility for an ICP;