Intrusion Detection and Prevention Clause Samples

Intrusion Detection and Prevention. State Street shall maintain software, hardware, intrusion detection system, personnel and other resources designed to ascertain whether a penetration attempt is being made against any part of State Street’s network, mainframe, server or other infrastructure used by State Street to process, store or transport Client Data. This may include deploying intrusion detection /intrusion prevention controls to block, monitor, and alert State Street of security incidents that may require escalation to, and response from, State Street’s incident response personnel on a 24 hours per day, 7 days per week, 365 days per year basis.
Intrusion Detection and Prevention. DST shall maintain software, hardware, intrusion detection system, personnel and other resources to ascertain whether a penetration attempt is being made against any part of DST’s network, mainframe, server or other infrastructure or facilities used by DST to process, store or transport Fund Confidential Information. This includes deploying intrusion detection /intrusion prevention controls to block, monitor, and alert DST’s incident response team of security incidents that may require escalation to, and response from, DST’s incident response personnel on a 24 hour per day, 7 days per week, 365 days per year basis.
Intrusion Detection and Prevention. All systems that are accessible via the internet must actively use a network based intrusion detection and prevention solution.
Intrusion Detection and Prevention. Convercent will deploy intrusion detection or preferably prevention systems (NIDS/NIPS) in order to generate, monitor, and respond to alerts which could indicate potential compromise of the network and/or host.
Intrusion Detection and Prevention a) Intrusion detection and prevention systems must be implemented for critical components of the network.
Intrusion Detection and Prevention. Illumina shall employ risk-appropriate security measures, such as network intrusion detection systems and intrusion prevention systems, to protect telecommunications systems and any networked computer systems or devices that store, process, transmit Customer Data. Illumina shall actively monitor network intrusion detection and intrusion prevention systems.
Intrusion Detection and Prevention. You will deploy intrusion detection or preferably prevention systems (NIDS/NIPS) in order to generate, monitor, and respond to alerts which could indicate potential compromise of the network and/or host.
Intrusion Detection and Prevention. RingCentral deploys network intrusion detection and/or intrusion prevention systems that monitor all non-VoIP traffic entering or leaving the Data Centres.
Intrusion Detection and Prevention. Market Logic will deploy intrusion detection or preferably prevention systems (NIDS/NIPS) in order to generate, monitor, and respond to alerts which could indicate potential compromise of the network and/or host.
Intrusion Detection and Prevention. (i) The network intrusion detection and prevention features of the Service (“IDS/IPS”) monitor Customer’s network traffic on 24x7 basis for a list of attack and misuse signatures according to a pre-defined security policy specific to Customer’s network environment. The policy may have an option to block and report on misused traffic. (ii) The security policy is submitted by Customer to CenturyLink on a standard CenturyLink template and is subject to CenturyLink’s approval. The security policy categorizes intrusion Events as either “low priority level,” “medium priority level,” or “high priority level.” An “Event” means any security occurrence detected and reported by the IDS/IPS feature. An Event does not necessarily constitute an actual security incident. CenturyLink may update the security policy from time-to-time in order to address industry-wide changes in security needs. Customer may view the Event detail (including timestamp, attack type) on the NBS Web portal. Such reports contain information relating to low, medium, and high priority Events, including the time of the Event, the Event name, and a summary of attack statistics. Low, medium, and high priority Events are described below:  Low Priority. A low priority Event identifies activity on a network that is not necessarily suspicious or malicious in nature, but may indicate a need for a more secure means of network implementation. An example of a low priority Event includes poor security practices.  Medium Priority. A medium priority Event identifies activity that is suspicious in nature and may warrant investigation. An example of a medium priority Event includes network reconnaissance by an unknown source.  High Priority. A high priority Event identifies activity that is potentially malicious in nature and requires immediate attention. An example of a high priority Event includes attempts to compromise Customer’s network or attempts to gain privileged access to Customer’s network. (iii) CenturyLink will analyze high priority Events to determine if an Incident has occurred. An “Incident” means any single Event or collection of Events that have been determined by a CenturyLink IDS/IPS analyst reviewing the data to potentially be of security consequence. Incidents may include Events that are currently being investigated and actual attacks that may be in progress. If, upon investigation, an Event or series of Events is determined to be a high priority level Incident, CenturyLink will attempt to n...