Types of Events Detected Sample Clauses

Types of Events Detected. The types of events most commonly detected by network-based IDPS sensors include the following: Application layer reconnaissance and attacks (E.g. banner grabbing, buffer overflows, format string attacks, password guessing, malware transmission). Most network-based IDPSs analyse several dozen application protocols. Commonly analysed ones include Dynamic Host Configuration Protocol (DHCP), DNS, Finger, FTP, HTTP, Internet Message Access Protocol (IMAP), Internet Relay Chat (IRC), Network File System (NFS), Post Office Protocol (POP), rlogin/rsh, Remote Procedure Call (RPC), Session Initiation Protocol (SIP), Server Message Block (SMB), SMTP, SNMP, Telnet, and Trivial File Transfer Protocol (TFTP), as well as database protocols, instant messaging applications, and peer-to-peer file sharing software. Transport layer reconnaissance and attacks (E.g. port scanning, unusual packet fragmentation, SYN floods). The most frequently analysed transport layer protocols are TCP and UDP. Network layer reconnaissance and attacks (E.g. spoofed IP addresses, illegal IP header values). The most frequently analysed network layer protocols are IPv4, ICMP, and IGMP. Many products are also adding support for IPv6 analysis. The level of IPv6 analysis that network-based IDPSs can perform varies considerably among products. Some products provide no IPv6 support or can simply alert administrators that IPv6 activity is present. Other products can do basic processing of IPv6 and tunneled IPv6 traffic, such as recording source and destination IP addresses, and extracting payloads (e.g., HTTP, SMTP) for in-depth analysis. Some products can do a full analysis of the IPv6 protocol, such as confirming the validity of IPv6 options, to identify anomalous use of the protocol. Organisations with a current or future need to monitor IPv6 activity should carefully evaluate the IPv6 analysis capabilities of network-based IDPS products.23 Unexpected application services (E.g. tunneled protocols, backdoors, hosts running unauthorised application services). These are usually detected through stateful protocol analysis methods, which can determine if the activity in a connection is consistent with the expected application protocol, or through anomaly detection methods, which can identify changes in network flows and open ports on hosts. Policy violations
Sample 1
AutoNDA by SimpleDocs

Related to Types of Events Detected

  • NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business.

  • Notice of Events of Default The Issuer shall give a Responsible Officer of the Indenture Trustee and each Rating Agency prompt written notice of each Event of Default hereunder and each default on the part of the Servicer or the Seller of its obligations under the Sale and Servicing Agreement.

  • Train Operator Events of Default The following are Train Operator Events of Default:

  • Emergency Action on Imports of Particular Products Where any product is being imported in such increased quantities and under such conditions as to cause, or threaten to cause:

  • Consequences of Events of Default and Corrective Action If an Event of Default occurs, the Province may, at any time, take one or more of the following actions:

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Events of Default Any of the following shall constitute an Event of Default:

  • Events of Default Defined The following shall each constitute an "Event of Default" hereunder:

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Events of Default and Remedies Section 8.01

Time is Money Join Law Insider Premium to draft better contracts faster.