US 8,196,199 B2Grant
Personal wireless monitoring agent
Issue Date:2012-06-05
•22 Claims
•23 Drawing Sheets
Abstract
An agent for monitoring a wireless device is provided. The agent compares communications against policy guidelines and determines whether a violation of the policy guidelines has been committed, and communicates information about the violation to an authorized user.
Metadata
Assignee
- AirDefense, Inc.
Inventors
- Scott E. Hrastar
- Subra Viswanathan
Application Information
Application Number:US 11/253,316
Filing Date:2005-10-19
Priority Date:2004-10-19
Art Unit:2436
Classifications
IPC:
H04L29/06
Patent Drawings (23 sheets)
Description
Cross-Reference to Related Patent Applications
[0001] This application claims priority to U.S. patent application Ser. No. 60/620,197 filed Oct. 19, 2004, and incorporates by reference in their entirety for all purposes commonly assigned Provisional U.S. Patent Application Ser. No. 60/381,829, filed May 20, 2002, entitled “SYSTEMS AND METHODS FOR NETWORK SECURITY,” provisional U.S. Patent Application Ser. No. 60/464,464, filed Apr. 21, 2003, entitled “SYSTEM AND METHOD FOR MANAGING WIRELESS NETWORK ACTIVITY,” and U.S. patent application Ser. No. 10/360,587, filed Feb. 6, 2003, entitled “SYSTEM AND METHOD FOR SENSING WIRELESS LAN ACTIVITY”.
[0002] This application further incorporates by this reference in their entirety for all purposes commonly assigned U.S. patent applications filed Jun. 3, 2002:
[0003]
| Application | |
|---|---|
| No. | Title |
| 10/161,142 | “SYSTEMS AND METHODS FOR NETWORK |
| SECURITY” | |
| 10/161,440 | “SYSTEM AND METHOD FOR WIRELESS LAN |
| DYNAMIC CHANNEL CHANGE WITH | |
| HONEYPOT TRAP” | |
| 10/161,443 | “METHOD AND SYSTEM FOR ACTIVELY |
| DEFENDING A WIRELESS LAN AGAINST ATTACKS” | |
| 10/160,904 | “METHODS AND SYSTEMS FOR IDENTIFYING |
| NODES AND MAPPING THEIR LOCATIONS” | |
| 10/161,137 | “METHOD AND SYSTEM FOR ENCRYPTED |
| NETWORK MANAGEMENT AND INTRUSION | |
| DETECTION” | |
[0004] Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent applications filed Nov. 4, 2003:
[0005]
| Application | |
|---|---|
| No. | Title |
| 10/700,842 | “SYSTEMS AND METHODS FOR AUTOMATED |
| NETWORK POLICY EXCEPTION DETECTION AND | |
| CORRECTION” | |
| 10/700,914 | “SYSTEMS AND METHOD FOR DETERMINING |
| WIRELESS NETWORK TOPOLOGY” | |
| 10/700,844 | “SYSTEMS AND METHODS FOR ADAPTIVELY |
| SCANNING FOR WIRELESS COMMUNICATIONS” | |
[0006] Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent applications filed Feb. 6, 2004:
[0007]
| Application | |
|---|---|
| No. | Title |
| 10/774,034 | “SYSTEMS AND METHODS FOR ADAPTIVE |
| LOCATION TRACKING” | |
| 10/774,111 | “WIRELESS NETWORK SURVEY SYSTEMS AND |
| METHODS” | |
| 10/774,896 | “SYSTEMS AND METHODS FOR ADAPTIVE |
| MONITORING WITH BANDWIDTH CONSTRAINTS” | |
| 10/774,915 | “DYNAMIC SENSOR DISCOVERY AND SELECTION |
| SYSTEMS AND METHODS” | |
Background
[0008] The present invention is directed to systems and methods for enhancing security associated with electronic communications. More specifically, without limitation, the present invention relates to computer-based systems and methods for assessing security risks and identifying and responding to threats in wireless network environments.
[0009] The Internet is a global network of connected computer networks. Over the last several years, the Internet has grown in significant measure. A large number of computers on the Internet provide information in various forms. Anyone with a computer connected to the Internet can potentially tap into this vast pool of information.
[0010] The information available via the Internet encompasses information available via a variety of types of application layer information servers such as SMTP (simple mail transfer protocol), POP3 (Post Office Protocol), GOPHER (RFC 1436), WAIS, HTTP (Hypertext Transfer Protocol, RFC 2616) and FTP (file transfer protocol, RFC 1123).
[0011] One of the most wide spread methods of providing information over the Internet is via the World Wide Web (the Web). The Web consists of a subset of the computers connected to the Internet; the computers in this subset run Hypertext Transfer Protocol (HTTP) servers (Web servers). Several extensions and modifications to HTTP have been proposed including, for example, an extension framework (RFC 2774) and authentication (RFC 2617). Information on the Internet can be accessed through the use of a Uniform Resource Identifier (URI, RFC 2396). A URI uniquely specifies the location of a particular piece of information on the Internet. A URI will typically be composed of several components. The first component typically designates the protocol by which the address piece of information is accessed (e.g., HTTP, GOPHER, etc.). This first component is separated from the remainder of the URI by a colon (‘:’). The remainder of the URI will depend upon the protocol component. Typically, the remainder designates a computer on the Internet by name, or by IP number, as well as a more specific designation of the location of the resource on the designated computer. For instance, a typical URI for an HTTP resource might be:
[0012] http://www.server.com/dir1/dir2/resource.htm
[0013] where http is the protocol, www.server.com is the designated computer and /dir1/dir2/resouce.htm designates the location of the resource on the designated computer. The term URI includes Uniform Resource Names (URN's) including URN's as defined according to RFC 2141.
[0014] Web servers host information in the form of Web pages; collectively the server and the information hosted are referred to as a Web site. A significant number of Web pages are encoded using the Hypertext Markup Language (HTML) although other encodings using SGML, eXtensible Markup Language (XML), DHMTL or XHTML are possible. The published specifications for these languages are incorporated by reference herein; such specifications are available from the World Wide Web Consortium and its Web site (http://www.w3c.org). Web pages in these formatting languages may include links to other Web pages on the same Web site or another. As will be known to those skilled in the art, Web pages may be generated dynamically by a server by integrating a variety of elements into a formatted page prior to transmission to a Web client. Web servers, and information servers of other types, await requests for the information from Internet clients.
[0015] Client software has evolved that allows users of computers connected to the Internet to access this information. Advanced clients such as Netscape's Navigator and Microsoft's Internet Explorer allow users to access software provided via a variety of information servers in a unified client environment. Typically, such client software is referred to as browser software.
[0016] Electronic mail (e-mail) is another wide spread application using the Internet. A variety of protocols are often used for e-mail transmission, delivery and processing including SMTP and POP3 as discussed above. These protocols refer, respectively, to standards for communicating e-mail messages between servers and for server-client communication related to e-mail messages. These protocols are defined respectively in particular RFC's (Request for Comments) promulgated by the IETF (Internet Engineering Task Force). The SMTP protocol is defined in RFC 821, and the POP3 protocol is defined in RFC 1939.
[0017] Since the inception of these standards, various needs have evolved in the field of e-mail leading to the development of further standards including enhancements or additional protocols. For instance, various enhancements have evolved to the SMTP standards leading to the evolution of extended SMTP. Examples of extensions may be seen in (1) RFC 1869 that defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports and in (2) RFC 1891 that defines an extension to the SMTP service, which allows an SMTP client to specify (a) that delivery status notifications (DSNs) should be generated under certain conditions, (b) whether such notifications should return the contents of the message, and (c) additional information, to be returned with a DSN, that allows the sender to identify both the recipient(s) for which the DSN was issued, and the transaction in which the original message was sent.
[0018] In addition, the IMAP protocol has evolved as an alternative to POP3 that supports more advanced interactions between e-mail servers and clients. This protocol is described in RFC 2060.
[0019] The various standards discussed herein by reference to particular RFC's are hereby incorporated by reference herein for all purposes. These RFC's are available to the public through the Internet Engineering Task Force (IETF) and can be retrieved from its Web site (http://www.ietf.org/rfc.html). The specified protocols are not intended to be limited to the specific RFC's quoted herein above but are intended to include extensions and revisions thereto. Such extensions and/or revisions may or may not be encompassed by current and/or future RFC's.
[0020] A host of e-mail server and client products have been developed in order to foster e-mail communication over the Internet. E-mail server software includes such products as sendmail-based servers, Microsoft Exchange, Lotus Notes Server, and Novell GroupWise; sendmail-based servers refer to a number of variations of servers originally based upon the sendmail program developed for the UNIX operating systems. A large number of e-mail clients have also been developed that allow a user to retrieve and view e-mail messages from a server; example products include Microsoft Outlook, Microsoft Outlook Express, Netscape Messenger, and Eudora. In addition, some e-mail servers, or e-mail servers in conjunction with a Web server, allow a Web browser to act as an e-mail client using the HTTP standard.
[0021] As the Internet has become more widely used, it has also created new risks for corporations. Breaches of computer security by hackers and intruders and the potential for compromising sensitive corporate information are a very real and serious threat.
[0022] Wireless Local Area Networks (WLANs) offer a quick and effective extension of a wired network or standard local area network (LAN). FIG. 1 depicts a typical LAN 190 including both wired and wireless components. The wired component depicted in FIG. 1 includes a variety of connected systems including local servers 120, local clients 130 and network accessible data storage components 110. By simply installing access points 180A, 180B to the wired network (e.g., Ethernet 150 and router 140), personal computers and laptops equipped with WLAN cards 170A, 170B can connect with the wired network at broadband speeds.
[0023] Over the last few years, most deployments of WLANs have conformed to the Institute of Electrical and Electronics Engineers (IEEE) 802.11b standard that operates over the unregulated 2.4 GHz frequency spectrum. The 802.11b standard offers connectivity of up to 11 Mbps—fast enough to handle large e-mail attachments and run bandwidth-intensive applications like video conferencing. While the 802.11b standard now dominates the WLAN market, other variations of the 802.11 standard, such as 802.11a, 802.11g, and supporting standards such as 802.1X, are being developed to handle increased speeds and enhanced functionality. WLAN vendors have committed to supporting a variety of standards. The various 802.11 standards developed by the IEEE are available for download via URL: http://standards.ieee.org/getieee802/802.11.html; these various standards are hereby incorporated by this reference herein.
[0024] As businesses connected their LANs to the Internet 160, they installed firewalls 145 to protect their local networks and act as security gates to fend off unauthorized traffic coming from the Internet's information highway such as potential hacker 135. The mobility of air-bound, wireless networks creates security concerns where threats can come from any direction and are not limited to the wired infrastructure. Established security practices of guarding a few wired entry points to the network are no longer effective. A firewall 145 may effectively deter an attack from a wired hacker 135 via the Internet 160; however, wireless hackers 195A, 195B typically enter the LAN 190 through access points 180A, 180B that are already behind the firewall 145. Companies must constantly monitor their airwaves to survey wireless activity and guard against intruders.
[0025] Because wireless communication is broadcast over radio waves, eavesdroppers 195A, 195B who merely listen to the airwaves can easily pick up unencrypted messages. Additionally, messages encrypted with the Wired Equivalent Privacy (WEP) security protocol can be decrypted with a little time and easily available hacking tools. These passive intruders put businesses at risk of exposing sensitive information to corporate espionage.
[0026] The theft of an authorized user's identity poses one the greatest threats. Service Set Identifiers (SSIDs) that act as crude passwords and Media Access Control (MAC) addresses that act as personal identification numbers are often used to verify that clients are authorized to connect with an access point. However, existing encryption standards are not foolproof and allow knowledgeable intruders to pick up approved SSIDs and MAC addresses to connect to a WLAN as an authorized user with the ability to steal bandwidth, corrupt or download files, and wreak havoc on the entire network.
[0027] Outsiders who cannot gain access to a WLAN can none-the-less pose security threats by jamming or flooding the airwaves with static noise that causes WLAN signals to collide and produce CRC errors. These Denial-of-Service (DoS) attacks effectively shut down the wireless network in a similar way that DoS attacks affect wired networks.
[0028] Careless and deceitful actions by both loyal and disgruntled employees also present security risks and performance issues to wireless networks with unauthorized access points, improper security measures, and network abuses. Because a simple WLAN can be easily installed by attaching a $150 access point to a wired network and a $100 WLAN card to a laptop, employees are deploying unauthorized WLANs or peer-to-peer wireless connections 175 when IT departments are slow to adopt the new technology.
[0029] Incorrectly configured access points are an avoidable but significant hole in WLAN security. Many access points are initially configured to broadcast unencrypted SSIDs of authorized users. While SSIDs are intended to be passwords to verify authorized users, intruders can easily steal an unencrypted SSID to assume the identity of an authorized user.
[0030] Authorized users can also threaten the integrity of the network with abuses that drain connection speeds, consume bandwidth, and hinder a WLAN's overall performance. A few users who clog the network by trading large files such as MP3 audio or MPEG video files can affect the productivity of everyone on the wireless network.
[0031] The systems and methods according to the present invention provide solutions to these and other security and/or management issues associated with WLANs and/or encrypted computer networks.
Summary
[0032] The present invention is directed to systems and methods for enhancing network security. One preferred embodiment according to the present invention includes a system data store (SDS), a system processor and one or more interfaces to one or more communications channels which may include one or more interfaces to wireless and/or encrypted communications network over which electronic communications are transmitted and received. The SDS stores data needed to provide the desired security tracking and/or assessment functionality and may include, for example, received communications, data associated with such communications, information related to known security risks and predetermined responses to the identification of particular security risks and situations. The SDS may include multiple physical and/or logical data stores for storing the various types of information. Data storage and retrieval functionality may be provided by either the system processor or data storage processors associated with, or included within, the SDS.
[0033] The system processor is in communication with the SDS via any suitable communication channel(s); the system processor is in communication with the one or more interfaces via the same, or differing, communication channel(s). The system processor may include one or more processing elements that provide electronic communication reception, transmission, interrogation, analysis and/or other functionality. In some embodiments, the system processor can include local, central and/or peer processing elements depending upon equipment and the configuration thereof.
[0034] Each interface to a wireless network includes at least one receiver adapted to receive wireless communications; each interface can also include one or more transmitters adapted to transmit wireless communications. Each interface to a wired network, if any, include a receiver, a transmitter, both or a plurality of one and/or both; such receivers and/or transmitters adapted to receive or transmit communication over the wired network to which the interface connects. In one preferred embodiment, the communication interface includes at least one wireless receiver.
[0035] Network sensors according to the present invention can include at least one wireless receiver, the SDS (or a portion thereof) and the system processor (or a portion thereof). The system processor, or portion thereof, in the network sensor extracts data into one or more logical units such as frames from received wireless signals according a selected wireless protocol such as a variant of 802.11. These logical units are inspected for a variety of information (e.g., frame type, source, destination, etc.). Information derived from the inspection is stored in the SDS, or the portion thereof, in the network sensor.
[0036] Information from one or more further network sensors can be received via the wireless receiver or an additional communication interface, stored the SDS and processed by the system processor along with the locally derived information. Such storage and processing can occur in the network sensor, one or more peer network sensor or one or more central servers. The stored information is analyzed in the aggregate to generate a security rating which is then output to a user or a further data processing system.
[0037] Accordingly, one preferred method of security enhancement includes a variety of steps that may, in certain embodiments, be executed by the environment summarized above and more fully described below or be stored as computer executable instructions in and/or on any suitable combination of computer-readable media. Configuration data associated with an access point on a wireless computer network potentially compromised by an intruder is received. Information contained within and/or derived from the received configuration data is stored. Communication with the intruder is continued by emulating the identification characteristics of the potentially compromised access point. In some embodiments, communication may appear to come from an access point that appears less secure than the potentially compromised access point. A channel change request is transmitted to the potentially compromised access point to reroute communication between the potentially compromised access point and authorized stations such that communications may continue on a different channel.
[0038] In some embodiments, the configuration data associated with the potentially compromised access point is received from an intrusion detection system such as described in greater detail below. In such embodiments, the configuration data may be included as part of a generated security violation alarm. In other instances, an alarm signal is received that triggers the generation and transmission of a request for information regarding the potentially compromised access point. Some embodiments involving an intrusion detection system may include the intrusion detection system while other respond to input from such a system.
[0039] Some embodiments further include the mapping of the identification of the intruder's node and/or the mapping of the location of the intruder's node within the wireless network. In some instances, a notification of the triggering of the honeypot trap can be sent to an administrator; some such notifications may include an identification and/or location of the node associated with the intruder in embodiments that include node identification and location mapping.
[0040] In some embodiments, the configuration data includes one or more risk criteria, network default data, network policy, performance and/or usage data. This configuration information may be received from one or more of a variety of sources including from a configuration file, an interactive data entry interface or a command line or from monitoring the wireless computer network.
[0041] Some embodiments may further include updating of various types of stored information; different embodiment may update all, none or any combination of the various types of stored information. For instance, some embodiments can update station information associated with the various stations in the wireless computer network based upon the received data. Further, some embodiments can update state information regarding the security of the wireless computer network based upon the received data. In addition, some embodiments can update statistics based upon the received data. Such updates can occur each time data is received, in response to reaching a fixed amount of such update data, in response to reaching a fixed time or the end of a predetermined duration, or some combination of these approaches.
[0042] Additional advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out herein. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention.
Brief Description of the Drawings
[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
[0044] FIG. 1 graphically depicts a typical LAN with both wired and wireless components.
[0045] FIGS. 2A-E graphically depicts LANs incorporating various preferred embodiments according to the present invention.
[0046] FIG. 3 is a flow chart of a multi-dimensional wireless intrusion detection process according to one preferred embodiment of the present invention.
[0047] FIG. 4 is a flow chart of an example multiple input wireless intrusion detection process including multiple input correlation and long-term data fusion.
[0048] FIG. 5 is a flow chart of an exemplary dynamic channel change active defense process that includes a honeypot trap.
[0049] FIGS. 6A-B are flow charts of example station identification and location mapping processes.
[0050] FIGS. 7A-C are diagram depicting exemplary architectures for sensor devices.
[0051] FIGS. 8A-B are flow charts depicting an exemplary security data collection process performed according to the present invention.
[0052] FIG. 9 is a flow chart depicting steps in an exemplary wireless network topology tracking process.
[0053] FIG. 10 is a flow chart depicting an automated wireless network policy enforcement process.
[0054] FIG. 11 is a flow chart depicting an adaptive scanning process.
[0055] FIG. 12 is a figure depicting a sample visualization of a wireless network topology.
[0056] FIGS. 13A-B depict sample screens providing interfaces for configuration of automated policy enforcement.
[0057] FIG. 14 depicts an exemplary interface for configuring a default or baseline scan pattern.
[0058] FIG. 15 depicts a flowchart illustrating a process associated with a personal wireless monitoring agent of the present disclosure.
[0059] FIG. 16 depicts a flowchart illustrating a process associated with the multi-dimensional wireless intrusion detection process of FIG. 3 .
Detailed Description
[0060] Exemplary embodiments of the present invention are now described in detail. Referring to the drawings, like numbers indicate like parts throughout the views. As used in the description herein, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. Finally, as used in the description herein, the meanings of “and” and “or” include both the conjunctive and disjunctive and may be used interchangeably unless the context clearly dictates otherwise; the phrase “exclusive or” may be used to indicate situation where only the disjunctive meaning may apply.
[0061] Ranges may be expressed herein as from “about” one particular value, and/or to “about” another particular value. When such a range is expressed, another embodiment includes from the one particular value and/or to the other particular value. Similarly, when values are expressed as approximations, by use of the antecedent “about,” it will be understood that the particular value forms another embodiment. It will be further understood that the endpoints of each of the ranges are significant both in relation to the other endpoint, and independently of the other endpoint.
[0062] The term “Wi-Fi” is short for wireless fidelity and is another name for IEEE 802.11b. The foregoing discussion of exemplary embodiments may use terminology or make reference to the IEEE 802.11b standard, or other 802.11 variant; however, those skilled in the art will appreciate that systems and methods of the present invention may be applied to WLANs meeting these standards as well as WLANs developed according to competing WLAN standards. The phrase “frame” as used herein shall mean broadly any discretely defined communication transmitted via a computer network and shall not be limited to those specific frame types (control, management, data and error) defined according to 802.11X standards.
[0063] FIGS. 2A-E depicts several LAN environments including several preferred embodiments according to the present invention. These figures depict a typical LAN environment as depicted in FIG. 1 having wired and wireless components. In contrast to FIG. 1 , FIGS. 2A-E include one or more hardware components supporting preferred embodiments according to the present invention. The depicted hardware components include a system processor, an SDS and one or more interfaces to one or more wireless and/or encrypted communications network over which electronic communications are transmitted and received.
[0064] The hardware components depicted in these figures are outlined as follows:
-
- [0065] In
FIG. 2A , the hardware components include a single device 210A that includes a local processor serving as the system processor, or at least a portion thereof, and the one or more interfaces to the wireless network. The device 210A is preferably a mobile computer system such as a notebook computer. The local primary and/or secondary storage of device 210A may serve as the SDS; alternatively, portions of the SDS may be provided by other systems capable of communicating with the device 210A such as network addressable data storage 110, local servers 120 and/or wireless stations 170A, 170B. In some embodiments, the device's interfaces to the wireless network may be limited to one or more wireless receivers. In other embodiments, the interfaces may include one or more wireless transmitters as well as one or more transmitters. If wireless transmitters are included, the device 210 may communicate over LAN 190 using a wireless access point 180A, 180B. In addition, included wireless transmitters may be used to support one or more of the active defense measures described in greater detail below. In some embodiments, the device 210A may further include a wired connection (not shown) to Ethernet 150 allowing direct communication between it and systems connected to the wired portion of LAN 190. - [0066] In
FIG. 2B , the hardware components include multiple devices 210A, 210B, 210C, 210D. Each device 210A-D includes a local processor and one or more interfaces to the wireless network and is preferably a mobile computer system such as a notebook computer. The individual local processors in the aggregate serve as the system processor. The SDS may include a combination of storage local to each of the devices and/or external storage accessible via the LAN 190. As described above with respect toFIG. 2A , each device includes at least a wireless receiver but may also include additional wireless receivers and/or wireless transmitters. Each device may also include a wired connection (not shown) to Ethernet 150. Finally, the devices 210A-D may further use existing interfaces and/or incorporate additional interfaces to allow peer-to-peer communication among themselves. - [0067] In
FIG. 2C , the hardware components include multiple devices 210A, 210B, 210C, 210D, 220. Each device 210A-D may include the various components as described above with respect toFIG. 2B . Device 220 includes a local processor and one or more communication interfaces; this device may be referred to hereinafter as the host system. Device 220's communication interfaces may include only a wired communication interface and may receive data related to wireless communications as forwarded by devices 210A-D over the wire Ethernet 150. In addition to, or instead of, the wired communication interface, device 220 may include a one or more wireless communication interfaces each of which may include a wireless receiver, a wireless transmitter or both. In embodiment where devices 210A-D support peer-to-peer communication, device 220 may in some of such embodiments participate in the peer-to-peer communication and, in such instances, its communication interfaces would include the appropriate communication interface to support this participation. The system processor functionality in the depicted embodiment may be provided by the host system alone and/or by some combination of the devices 210A-D. The host system may in some embodiments provide the SDS for the environment; alternatively, the SDS may be supported by some combination of the local storage among the devices 210A-D, the local storage in the host system and external storage available through LAN 190. - [0068] In
FIG. 2D , the hardware components include multiple devices 210A, 210B, 210C, 210D, 220, 230A, 230B. Devices 210A-D, 220 support the same functionality and include the same range of components as provided above with respect toFIG. 2C . In addition, devices 230A, 230B are sensor devices that monitor wireless traffic over the wireless network. These sensor devices at least include a wireless receiver for monitoring the traffic and a communication interface wired (as depicted) or wireless (not shown) allowing communication with one or more of the devices 210A-D and/or the host system 220. In some embodiments, the sensor devices 230A, 230B may include a wireless transmitter for supporting communication with the other hardware components and/or for supporting various active wireless network defensive measures as discussed below. In some embodiments, the sensor device 230A, 230B may further include local processing capability and or local storage capability; in some such embodiments, the system processor and/or the SDS may incorporate these local capabilities of the sensor devices 230A, 230B. - [0069] In
FIG. 2E , the hardware components include multiple devices 220, 230A, 230B. In this embodiment, the host system 220 and sensor devices 230A, 230B include the same functionality and range of components as discussed above with respect toFIGS. 2D and 2E respectively. In such embodiments, the host system 220 will typically provide a significant portion of the system processor functionality and will only have limited capacity to directly receive wireless network communication. In some of these embodiments, the host system 220 may have no wireless communication interface.
- [0065] In
[0070] The depicted hardware components include a system processor potentially including multiple processing elements, that may be distributed across the depicted hardware components, where each processing element may be supported via Intel-compatible processor platforms preferably using at least one PENTIUM III or CELERON (Intel Corp., Santa Clara, Calif.) class processor; alternative processors such as UltraSPARC (Sun Microsystems, Palo Alto, Calif.) could be used in other embodiments. In some embodiments, security enhancement functionality, as further described below, may be distributed across multiple processing elements. The term processing element may refer to (1) a process running on a particular piece, or across particular pieces, of hardware, (2) a particular piece of hardware, or either (1) or (2) as the context allows. The sensor devices 230A, 230B depicted in FIGS. 2D-E may in some preferred embodiments include more limited optimized local processors such as a digital signal processor (DSP). Other embodiment can use application specific integrated circuits (ASIC) or a field programmable gate arrays (FPGA).
[0071] The depicted hardware components include an SDS that could include a variety of primary and secondary storage elements. In one preferred embodiment, the SDS would include RAM as part of the primary storage; the amount of RAM might range from 64 MB to 4 GB in each individual hardware device although these amounts could vary and represent overlapping use such as where the host system 220 supports additional functionality such as integrated with firewall system 145 for providing unified wired and wireless security. The primary storage may in some embodiments include other forms of memory such as cache memory, registers, non-volatile memory (e.g., FLASH, ROM, EPROM, etc.), etc. The sensor devices 230A, 230B depicted in FIGS. 2D-E may in some preferred embodiments include more limited amounts and kinds of primary storage. In one preferred embodiments, the primary storage in the sensor devices includes FLASH memory.
[0072] The SDS may also include secondary storage including single, multiple and/or varied servers and storage elements. For example, the SDS may use internal storage devices connected to the system processor. In embodiments where a single processing element supports all of the security analysis functionality, such as seen in FIGS. 2A and 2E , a local hard disk drive may serve as the secondary storage of the SDS, and a disk operating system executing on such a single processing element may act as a data server receiving and servicing data requests.
[0073] It will be understood by those skilled in the art that the different information used in the security enhancement processes and systems according to the present invention may be logically or physically segregated within a single device serving as secondary storage for the SDS; multiple related data stores accessible through a unified management system, which together serve as the SDS; or multiple independent data stores individually accessible through disparate management systems, which may in some embodiments be collectively viewed as the SDS. The various storage elements that comprise the physical architecture of the SDS may be centrally located, or distributed across a variety of diverse locations.
[0074] The architecture of the secondary storage of the system data store may vary significantly in different embodiments. In several embodiments, database(s) are used to store and manipulate the data; in some such embodiments, one or more relational database management systems, such as DB2 (IBM, White Plains, N.Y.), SQL Server (Microsoft, Redmond, Wash.), ACCESS (Microsoft, Redmond, Wash.), ORACLE 8i (Oracle Corp., Redwood Shores, Calif.), Ingres (Computer Associates, Islandia, N.Y.), MySQL (MySQL AB, Sweden) or Adaptive Server Enterprise (Sybase Inc., Emeryville, Calif.), may be used in connection with a variety of storage devices/file servers that may include one or more standard magnetic and/or optical disk drives using any appropriate interface including, without limitation, IDE and SCSI. In some embodiments, a tape library such as Exabyte X80 (Exabyte Corporation, Boulder, Colo.), a storage attached network (SAN) solution such as available from (EMC, Inc., Hopkinton, Mass.), a network attached storage (NAS) solution such as a NetApp Filer 740 (Network Appliances, Sunnyvale, Calif.), or combinations thereof may be used. In other embodiments, the data store may use database systems with other architectures such as object-oriented, spatial, object-relational or hierarchical.
[0075] Instead of, or in addition to, those organization approaches discussed above, certain embodiments may use other storage implementations such as hash tables or flat files or combinations of such architectures. Such alternative approaches may use data servers other than database management systems such as a hash table look-up server, procedure and/or process and/or a flat file retrieval server, procedure and/or process. Further, the SDS may use a combination of any of such approaches in organizing its secondary storage architecture.
[0076] The hardware components may each have an appropriate operating system such as WINDOWS/NT, WINDOWS 2000 or WINDOWS/XP Server (Microsoft, Redmond, Wash.), Solaris (Sun Microsystems, Palo Alto, Calif.), or LINUX (or other UNIX variant). In one preferred embodiment, the devices 210A-D and/or host system 220 include a LINUX (or other UNIX variant) operating system; although other embodiments may include a WINDOWS/XP (or other WINDOWS family) operating system.
[0077] Depending upon the hardware/operating system platform of the overall environment, appropriate server software may be included to support the desired access for the purpose of configuration, monitoring and/or reporting. Web server functionality may be provided via an Internet Information Server (Microsoft, Redmond, Wash.), an Apache HTTP Server (Apache Software Foundation, Forest Hill, Md.), an iPlanet Web Server (iplanet E-Commerce Solutions—A Sun—Netscape Alliance, Mountain View, Calif.) or other suitable Web server platform. The e-mail services may be supported via an Exchange Server (Microsoft, Redmond, Wash.), sendmail or other suitable e-mail server. Some embodiments may include one or more automated voice response (AVR) systems that are in addition to, or instead of, the aforementioned access servers. Such an AVR system could support a purely voice/telephone driven interface to the environment with hard copy output delivered electronically to suitable hard copy output device (e.g., printer, facsimile, etc.), and forward as necessary through regular mail, courier, inter-office mail, facsimile or other suitable forwarding approach.
[0078] Some preferred embodiments of the present invention include sensor devices 230A, 230B of a form such as depicted in FIGS. 7A-C . FIG. 7A depicts a sensing device having combined functionality of an access point and sensor. The device includes a transceiver antenna 705 and a sensing antenna 710. The transceiver antenna 705 allows receipt and transmission of wireless signals according to a predetermined protocol such as a variant of IEEE 802.11. Wireless stations associate with the active radio (transceiver antenna) which connects through port 720 to a wired network such as a network interface to a local Ethernet and/or to a further wireless network (transceiver not shown), a modem allowing connection to a network or direct connection to a host system or peer system or combinations thereof. The sensing antenna 710 allows reception of wireless signals according to the protocol without impacting performance of transceiver. The sensing antenna 710 receives all wireless signals in parallel with the transceiver antenna 705. The sensor can further include local data storage 715 that serves as the SDS, or a portion thereof. This local storage 715 contains any necessary operating code and/or data such as accumulated security data, network configuration data, sensor identification information and/or network communication related data. This local storage typically include DRAM, FLASH memory or combinations thereof. The sensor can further include a local processor 725 that serves as the system processor, or a portion thereof. This local processor 725 supports communication management and security collection, and in some embodiment security analysis, functionality. The local processor can be any microprocessor, ASIC, FPGA or combination thereof that has the computing power capable of managing the two wireless components 705 and 710 and the auxiliary components of the device (e.g., local storage 715, network interface 720, etc.); for example, a Pentium I Class microprocessor (Intel) or faster is capable of managing the computing needs. The device will also include a connection to a power source such as depicted alternating current (AC) interface 730 although other embodiments could in addition, or instead, include a power over Ethernet compatible interface or a repository for one or more disposable and/or rechargeable batteries.
[0079] FIG. 7B depicts a stand-alone sensor embodiment. In this embodiment, a wireless transceiver for supporting access point functionality is not included. The description above with respect to FIG. 7A provides description of the like numbered components in FIG. 7B . This embodiment includes a further communication interface 735. This additional interface can be used to connect further devices such as a standard access point. This would be useful for installing a sensor at a location with an existing access point without having to run another network line. Any data sent outbound from the device connected to interface 735 would be forwarded via network interface 720. Any data received at network interface 720 directed to the device would be forwarded via interface 735.
[0080] FIG. 7C depicts a modified access point embodiment. In this embodiment, a separate antenna is not provided for parallel monitoring of wireless signals. Instead, wireless transceiver 705 is responsible for both access point and signal monitor functionality. This functionality can be implemented in software or hardware of the local processor 725, or as a modified logic within the transceiver itself. This embodiment has the advantage that existing access points with sufficient local processing capability can be modified through either a hardware addition or a software upgrade to support the monitoring capability. One disadvantage is that the original access point may not have been intended to support both functionality and, therefore, access point functionality may be degraded in some instances.
[0081] As previously described, the sensors 230A-B and/or devices 210A-D in some embodiments collect and forward security related data to a host system 220 for further processing and analysis. Some such embodiments provide for local processing of security data. FIGS. 8A-B are flow charts depicting an exemplary security data collection process performed according to the present invention. In some embodiments, this process can be executed by sensors 230A-B and/or devices 210A-D.
[0082] In some particular embodiments using an 802.11 compatible network, the hardware sensors read 802.11 radio waves and strip management and control frames, aggregate statistics and send collected information to a backend server. A hardware sensor can have several embodiments. Three embodiments such as depicted in FIGS. 7A-7C would be a stand-alone hardware sensor (FIG. 7B ), a combination 802.11 Access Point/hardware sensor (FIG. 7A ), and a modified 802.11 Access Point capable of stripping management and control frames and sending them back to a central server for analysis (FIG. 7C ).
[0083] A hardware sensor will typically include at least one 802.11 radio capable of reading 802.11 radio waves. To provide functionality for securing a wireless network, the hardware sensor strips 802.11 management and control frames off of wireless data transmissions and sends real-time or batched data back to a centralized server (e.g., host system 220) for analysis and processing to determine intrusions or other network activity such as health or performance monitoring or performing such analysis and processing locally in peer-to-peer configurations.
[0084] In the three above mentioned embodiments, the stand-alone hardware sensor would have an 802.11 radio operating in “promiscuous mode” in order to be undetectable from the airwaves and still read all 802.11 network traffic. In operating in promiscuous mode, the hardware sensor would not be able to transmit data such as beacon management and would be in a read-only operation mode. The sensor software embedded on the device would read 802.11 frames from the wireless network and interrogate them to strip the management and control frames from the data frames, collect the data and send it to the back-end server. The process to collect the data in one preferred approach is as follows:
[0085] The physical hardware powers up and loads the operating system (preferred OS: Real-Time Linux or RTOS) to an operational state, step 800. The first-time execution of the sensor process after power up (step 805), a timer is initialized for management and control frames buffering (step 810). The timer allows the management and control frames to be buffered until the timer reaches a predetermined elapsed time, at which point they will be forwarded to a server or peer for processing or processed locally. Although other embodiments can forward unbuffered management and control frames and would therefore not require a timer, or any process steps involving the timer.
[0086] A wireless packet frame is then read from the wireless network, step 820. Frames are read so that the frame content can be interrogated in down-stream processes. This is also the entry point 815 in the process for retrieving the next frame after interrogation of the present frame.
[0087] The packet frame read off the wireless network is interrogated to determine if the frame is of a redundant type such as management or control frames, step 825. If the frame is of a redundant type, processing continues at entry point 830 in FIG. 8B . Management and control frames are broadcast more frequently than data frames and are protocol specific. Further interrogation of a management or control frame is performed to determine whether the frame is a redundant type frame (i.e., Beacon Frame), step 855. If not, control passes back to entry point 815 in FIG. 8A . Management and control frames such as beacon frames are broadcast more frequently than data frames and can be buffered as one record with a frame count and to reduce the traffic on the network as frames are transmitted to the server or to a peer or to reduce overhead of local processing. The buffering can be accomplished by maintaining a frame count for the particular type of redundant frame (step 860) and populating an appropriate data structure based upon the redundant frame type (step 865). If an appropriate time interval has elapsed or if a particular time has been reached (step 870), or if no buffering is intended, processing proceeds to entry point 845 in FIG. 8A for forwarding of the redundant frame information to the central server or peer or for local processing depending upon the particular embodiment. If the timer does not trigger transmission or processing, processing continues at entry point 815 for retrieval of the next frame in FIG. 8A .
[0088] If the frame is not of a redundant type, processing continues at step 835 where the header data is stripped from the wireless packet frame. The header data is used to get origin/destination data as well as for maintaining state.
[0089] In step 840, a data structure is populated with pertinent information concerning wireless station state and protocol activity as well as origin and destination information for later down-line processing by a backend analysis server, by a peer or a local processor.
[0090] Once data is accumulated and preprocessed by the remote sensor, the resulting data structures are passed back to the central server or a peer over IP or locally processed for intrusion detection analysis (step 850). The process continues at entry point 815 with the retrieval of the next frame.
[0091] The embodiment of a combination hardware sensor and access point, one 802.11 radio would operate as a normal 802.11 access point operating in infrastructure mode that would allow wireless stations to associate and pass data through to the wired network. The additional 802.11 radio would operate in promiscuous mode just as a stand-alone hardware sensor would operate. This would give the device the ability to send and receive data as a normal 802.11 access point while utilizing the additional radio to monitor the airwaves against intrusions and monitor the wireless network for performance and health monitoring.
[0092] The embodiment of an access point modified to provide monitoring capability would utilize a single 802.11 radio to send and receive data with wireless stations but would utilize an SNMP mechanism to send traps back to a back end server when events occur such as intrusions or attacks against the access point. This method is not as effective as the previously mentioned embodiments but can provide additional information that is not collected by standard operating access points.
[0093] In one preferred embodiment, devices 210A-D and host system 220 can be configured locally or remotely, and configuration can occur through an interactive interface and/or through a command line interface. The interactive interface is accessible locally whereas the command line interface is accessible either locally or remotely. Remote access is preferably granted through the use of a secure shell (SSH) client communicating with an SSH server running on the device or host system.
[0094] Management of a wireless network differs in many ways from the management of a wired network. One important difference is the more dynamic nature of nodes (computers, PDAs, 802.11 cell phones, etc) in the network. In a wired network, connections to the network occur only at fixed locations. In a wireless network, nodes are not tied to physical connectivity to the network; a wireless network has no traditional boundaries and its topology can change at a fairly high rate.
[0095] This dynamic change is due to the ability of wireless network users to roam across multiple networks as well as the ability of modern wireless protocols to support instantaneous creation of ad hoc networks. Given these features, the connectivity patterns and network topology can change from moment to moment.
[0096] FIG. 9 depicts a process that supports the capture, and in some embodiments visualization, of a wireless network topology over time. This mechanism utilizes the stateful analysis capabilities of the network behavior engine to capture and track the connectivity patterns of users and the networks that are established over time.
[0097] Network data is accumulated over a defined time period (an epoch). This epoch may vary in length depending upon the depth of analysis and state accumulation desired. In any case, at the end of an epoch, statistical and state analysis is performed on the accumulated data to generate a network topology. For analysis purposes, this topology can then be represented mathematically as a graph, with a set of nodes and edges interconnecting the nodes per the observed pattern. This generated topology can also be further processed to generate a visualization or to compare with a prior network topology to evaluate potential security and/or policy violations. The topology comparison in some embodiments could include rules-based comparison for potential security and/or policy violations. In addition, or instead, the topology could be subject to a pattern matching-based comparison to identify a topology state that violates security and/or policy constraints. Any suitable pattern matching approach could be used; in some instances, neural networks, lexical analysis and/or bit masking could be included as part of such pattern matching. Through collection of state information related to activity, usage and connectivity patterns, the topology can be constructed and updated over time as new state information is collected by the system. Additional information also includes device identity and classification, allowing each node in the network to be represented in terms of its capabilities, its state and its usage patterns. Further, these patterns can also be analyzed via a number of mechanisms including pattern matching to discriminate between normal and anomalous activity.
[0098] This topology information can be visualized in some embodiments through the use of graphical representations with encodings for state, traffic, security; and connectivity. FIG. 12 depicts an example visualization interface showing a tracked topology.
[0099] In some preferred embodiments of the present invention, an interactive interface is provided for configuring the access point and various hardware components and supplying a variety of configuration data including thresholds values of various kinds. In one preferred embodiment, an administration program area provides such an interface and allows:
-
- [0100] definition and configuration of access point settings and policies;
- [0101] definition of authorized user identities and authorized types or modes of behavior
- [0102] creation and/or designation of thresholds used to trigger intrusion/detection alarms for authorized access points;
- [0103] creation and/or designation of default thresholds used to trigger intrusion/detection alarms for non-authorized access points; and
- [0104] configuration of settings for the various hardware/software components.
[0105] The administration program area, in one preferred embodiment, offers standard windowing interface featuring tabbed pages for easy navigation between configuration functions. From within each of the tabbed pages, an Edit button allows modification of the values. After editing the data, Accept temporarily saves the changes. Commit permanently saves and applies edits (until edited again). Accepted changes persist until the system is restarted whereas committed changes persist until across restarts.
[0106] One preferred embodiment automatically attempts to detect and record all the configured properties for all access points it observes. The settings constitute access point “policies”—when access point properties deviate from those recorded, one or more alarms can be generated. The values for an access point can be modified manually to alter the generation of specific alarms. Policies for off-line access points can also be created in some embodiments using an Add feature.
[0107] The table below provides a summary of several access point properties displayable and/or configurable in some preferred embodiments of the present invention.
[0108]
| Values | Description |
|---|---|
| Access | The MAC address of the access point. |
| Point ID | |
| Access | The user-defined name of the access point. |
| Point | |
| Name | |
| Extended | The name of the Extended Service Set indicating the |
| Service | wireless network to which the access point belongs. |
| Set ID | |
| Access | The manufacturer of the access point. In some embodiments, |
| Point | this is detected by comparing the first three bytes of its |
| Vendor | MAC address with a database of OUI numbers. |
| Supported | The data transfer rates the access point supports. In some |
| Rates | embodiments, this value (or these values) can be edited to |
| specify the supported rates. | |
| Authenti- | Whether the access point accepts non-authenticated network |
| cation | connections and/or also accepts shared key authentication. (If |
| Modes | connections are detected that deviate from either of these |
| settings, an alarm can be generated.) | |
| Configured | Whether or not the access point is configured to require |
| to Run | WEP encryption. |
| WEP | |
| AP Mgmt | Whether the access point is configured to allow users to |
| From | directly administer its settings over the wireless network. |
| Wireless | |
| Network | |
| Authorized | Whether this access point is authorized to be present in |
| Access | the air space. Unauthorized access points, when detected, |
| Point | can generate alarms. (In some embodiment, a change |
| in this value will not take effect until the system is restarted.) | |
[0109] For each access point, a station maintenance screen or menu may allow the specification of the stations that are authorized to use it. One preferred embodiment of such a screen or menu, automatically detects all stations within the footprint of the access point's Basic Service Set (BSS) and enters their MAC addresses in an Observed column. Such stations can be indicated as an authorized member of the BSS by selecting them in the Observed column and designating them as Valid. Designated stations are moved to a Valid column. (Stations can, in some embodiments, be designated as invalid by selecting and marking them in the Valid column.) Stations not auto-detected can be manually entered by specifying its MAC address in a Enter New Station input field and triggering an Add Station feature. Authorization of stations can also be done via file import, access control server export or via direct configuration through a typical access point configuration and management port.
[0110] Systems and methods according to the present invention generate alerts if network traffic that exceeds thresholds is detected. In one preferred embodiment, all detected or manually configured off-line access points are listed in a Select AP pick list. Thresholds associated with each access point in the pick list can be edited by selecting the particular access point. Such threshold values can be either temporary (until the next restart) or persistent across restarts (until a further edit designated as persistent).
[0111]
| Values | Description |
|---|---|
| Signal Strength | If the signal strength for any station in the BSS is |
| Threshold | lower than this value, an alarm can be generated. |
| # of Associations | Enter the maximum number of associations per minute |
| per Minute | to allow with all stations combined. (Preferably, this |
| value is not higher than twice the number of | |
| stations in the BSS.) | |
| # of Associated | Enter the maximum number of stations allowed to |
| Stations | associate at any one time with this access point. The |
| number should reflect the actual number of stations. | |
| If a greater number is detected, an alarm can | |
| be generated. | |
[0112] The following table outlines a set of thresholds used in one preferred embodiment that refer to the network characteristics encompassing all stations and traffic in the BSS. In one preferred embodiment, special care must be taken when creating the “byte thresholds” that immediately follow. Several factors govern the values entered for each:
-
- [0113] The “transmission rate” of the access point—how much data it can transmit—is the first consideration. If the transmission rate is only 1 megabyte per second, the thresholds will be much lower than if the transmission rate is 11 megabytes per second.
- [0114] All four “directions” of traffic (wired to wired, wired to wireless, wireless to wired, and wireless to wireless) must add up to less than 100% of available bandwidth. Many administrators will set the individual thresholds such that their combined value is less than 80% of available bandwidth.
[0115]
| Value | Description |
|---|---|
| # Bytes into | Enter the maximum number of bytes of data per minute |
| BSS from | allowed into the BSS from the wired portion of your |
| Wired Net | network. If a greater number is detected, an alarm |
| can be generated. | |
| # Bytes from | Enter the maximum number of bytes of data per minute |
| BSS to Wired | allowed out of the BSS to a wired portion of your network. |
| Net | If a greater number is detected, an alarm can be generated. |
| # Bytes | Enter the maximum number of bytes of data per minute |
| between | allowed to be transmitted within the BSS from all stations. |
| Stations in BSS | If a greater number is detected, an alarm can be generated. |
| # Bytes from | Enter the maximum number of bytes of data per minute |
| Wired Net to | allowed to be transmitted from a wired portion of the |
| Wired Net | network to another wired portion of the network, using |
| the access point as a bridge. If a greater number is detected, | |
| an alarm can be generated. | |
| Total Data | Enter the maximum number of data frames per minute |
| Frames Seen | from all stations combined allowed to be transmitted. If a |
| greater number is detected, an alarm can be generated. | |
| Total Mgmt | Enter the maximum number of management frames per |
| Frames Seen | minute from all stations combined allowed to be |
| transmitted. If a greater number is detected, an alarm | |
| can be generated. | |
| Total Ctrl | Enter the maximum number of control frames per minute |
| Frames Seen | from all stations combined allowed to be transmitted. |
| If a greater number is detected, an alarm can be generated. | |
| Total Ad hoc | Enter the maximum number of ad hoc frames per minute |
| Frames Seen | from all stations combined allowed to be transmitted. |
| If a greater number is detected, an alarm can be generated. | |
[0116] The following table outlines a set of potential thresholds applied to any individual station in one preferred embodiment. If any single station reaches one of these thresholds, an alarm can be generated.
[0117]
| Column | Description |
|---|---|
| Signal | If the signal strength for any station in the BSS is lower |
| Strength | than this value, an alarm can be generated. |
| Threshold | |
| # of | Enter the maximum number of associations per minute |
| Associations | any station is allowed to make with an access point. If a |
| per Minute | greater number is detected, an alarm can be generated. |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Transmitted | any station is allowed transmit. If a greater number is |
| detected, an alarm can be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Received | any station is allowed to receive. If a greater number is |
| detected, an alarm can be generated. | |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | any station is allowed to transmit. If a greater number is |
| Transmitted | detected, an alarm can be generated. |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | any station is allowed to receive. If a greater number is |
| Received | detected, an alarm can be generated. |
| # of Mgmt | Enter the maximum number of management frames |
| Frames | per minute any station is allowed to transmit. If a |
| Transmitted | greater number is detected, an alarm can be generated. |
| # of Mgmt | Enter the maximum number of management frames per |
| Frames | minute any station is allowed to receive. If a greater |
| Received | number is detected, an alarm can be generated. |
| # of Ctrl | Enter the maximum number of control frames per |
| Frames | minute any station is allowed to transmit. If a greater |
| Transmitted | number is detected, an alarm can be generated. |
| # of Ctrl | Enter the maximum number of control frames per |
| Frames | minute any station is allowed to receive. If a greater |
| Received | number is detected, an alarm can be generated. |
| # of Fragment | Enter the maximum number of fragment frames |
| Frames Seen | per minute from any station that are allowed. If a |
| greater number is detected, an alarm can be generated. | |
| # of Decrypt | Enter the maximum number of decrypt error frames |
| Error | per minute from any station that are allowed. If a |
| Frames Seen | greater number is detected, an alarm can be generated. |
[0118] The following table outlines a set of thresholds, in one preferred embodiment, applied to the access point itself, and will typically be somewhat more than the Aggregate Station thresholds.
[0119]
| Column | Description |
|---|---|
| Signal | If the signal strength for any frame is lower than this value, |
| Strength | an alarm can be generated. |
| Threshold | |
| # of | Whereas stations must associate with an access point, |
| Associations | access points do not associate with themselves. Therefore, |
| per Minute | this value should be zero, indicating that it does not |
| associate. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Transmitted | this access point is allowed to transmit. If a greater |
| number is detected, an alarm can be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Received | this access point is allowed to receive. If a greater |
| number is detected, an alarm can be generated. | |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | this access point is allowed to transmit. If a greater |
| Transmitted | number is detected, an alarm can be generated. |
| # of Data | Enter the maximum number of data frames per |
| Frames | minute this access point is allowed to receive. If a |
| Received | greater number is detected, an alarm can be generated. |
| # of Mgmt | Enter the maximum number of management frames |
| Frames | per minute this access point is allowed to transmit. |
| Transmitted | If a greater number is detected, an alarm can be |
| generated. | |
| # of Mgmt | Enter the maximum number of management frames |
| Frames | per minute this access point is allowed to receive. If a |
| Received | greater number is detected, an alarm can be generated. |
| # of Ctrl | Enter the maximum number of control frames per |
| Frames | minute this access point is allowed to transmit. If a |
| Transmitted | greater number is detected, an alarm can be |
| generated. | |
| # of Ctrl | Enter the maximum number of control frames per |
| Frames | minute this access point is allowed to receive. If a |
| Received | greater number is detected, an alarm can be |
| generated. | |
| # of Fragment | Enter the maximum number of fragment frames |
| Frames Seen | per minute this access point can see before |
| generating an alarm. | |
| # of | Enter the maximum number of decrypt error frames |
| Decrypt Error | per minute this access point can see before |
| Frames Seen | generating an alarm. |
[0120] In one preferred embodiment, whenever a new access point is detected or manually entered, the specified default settings are applied until it is manually customized. It is assumed that new or unauthorized access points are potential hackers, so it is preferable to set the default thresholds fairly low.
[0121] The table below outlines a set of thresholds that refer to the combined statistics for all stations in one preferred embodiment.
[0122]
| Column | Description |
|---|---|
| Signal | If the signal strength for any station in the BSS associated |
| Strength | with an unknown access point is lower than this value, an |
| Threshold | alarm can be generated. |
| # of | Whereas stations must associate with an access point, |
| Associations | access points do not associate with themselves. Therefore, |
| per Minute | this value should be zero, indicating that it does not |
| associate. | |
| # of | Enter the maximum number of stations allowed to |
| Associated | associate with unknown access points. The number should |
| Stations | reflect your actual stations. If a greater number is detected, |
| an alarm can be generated. | |
| # Bytes | Enter the maximum number of bytes of data per minute |
| into BSS | allowed into the BSS through unknown access points |
| from | from the wired portion of your network. If a greater |
| Wired Net | number is detected, an alarm can be generated. |
| # Bytes | Enter the maximum number of bytes of data per minute |
| from BSS to | allowed out of the BSS through unknown access points |
| Wired Net | to a wired portion of your network. If a greater number |
| is detected, an alarm can be generated. | |
| # Bytes | Enter the maximum number of bytes of data per minute |
| between | allowed to be transmitted within the BSS from all stations |
| Stations | through unknown access points. If a greater number is |
| in BSS | detected, an alarm can be generated. |
| # Bytes from | Enter the maximum number of bytes of data per minute |
| Wired Net to | allowed to be transmitted through unknown access |
| Wired Net | points from a wired portion of the network to another |
| wired portion of the network, using the access point | |
| as a bridge. If a greater number is detected, an | |
| alarm can be generated. | |
| Total Data | Enter the maximum number of data frames per |
| Frames | minute for all stations combined allowed to be transmitted |
| Seen | through unknown access points. If a greater number is |
| detected, an alarm can be generated. | |
| Total Mgmt | Enter the maximum number of management frames per |
| Frames Seen | minute for all stations combined allowed to be transmitted |
| through unknown access points. If a greater number is | |
| detected, an alarm can be generated. | |
| Total Ctrl | Enter the maximum number of control frames per |
| Frames | minute for all stations combined allowed to be transmitted |
| Seen | through unknown access points. If a greater number is |
| detected, an alarm can be generated. | |
| Total Ad hoc | Enter the maximum number of ad hoc frames per minute |
| Frames Seen | for all stations combined allowed to be transmitted |
| through unknown access points. If a greater number is | |
| detected, an alarm can be generated. | |
[0123] The set of thresholds outlined in the table below apply to any individual station in one preferred embodiment, and will typically be lower than the Aggregate Station thresholds.
[0124]
| Column | Description |
|---|---|
| Signal | If the signal strength for any station associated with an |
| Strength | unknown access point is lower than this value, an |
| Threshold | alarm can be generated. |
| # of | Enter the maximum number of associations per minute |
| Associations | any station is allowed to make with an unknown access |
| per Minute | point. If a greater number is detected, an alarm can |
| be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Transmitted | any station is allowed transmit through unknown access |
| points. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Received | any station is allowed to receive through unknown access |
| points. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | any station is allowed to transmit through unknown access |
| Transmitted | points. If a greater number is detected, an alarm can |
| be generated. | |
| # of Data | Enter the maximum number of data frames per minute any |
| Frames | station is allowed to receive through unknown access |
| Received | points. If a greater number is detected, an alarm can |
| be generated. | |
| # of Mgmt | Enter the maximum number of management frames per |
| Frames | minute any station is allowed to transmit through unknown |
| Transmitted | access points. If a greater number is detected, an alarm can |
| be generated. | |
| # of Mgmt | Enter the maximum number of management frames per |
| Frames | minute any station is allowed to receive through unknown |
| Received | access points. If a greater number is detected, an alarm can |
| be generated. | |
| # of Ctrl | Enter the maximum number of control frames per minute |
| Frames | any station is allowed to transmit through unknown access |
| Transmitted | points. If a greater number is detected, an alarm can |
| be generated. | |
| # of Ctrl | Enter the maximum number of control frames per minute |
| Frames | any station is allowed to receive through unknown access |
| Received | points. If a greater number is detected, an alarm can |
| be generated. | |
| # of | Enter the maximum number of fragment frames per |
| Fragment | minute from any station that are allowed. If a greater |
| Frames | number is detected, an alarm can be generated. |
| Seen | |
| # of | Enter the maximum number of decrypt error frames per |
| Decrypt | minute from any station that are allowed. If a greater |
| Error | number is detected, an alarm can be generated. |
| Frames | |
| Seen | |
| Signal | If the signal strength for any access point is lower than |
| Strength | this value, an alarm can be generated. |
| Threshold | |
| # of | Enter the maximum number of associations per minute |
| Associations | between any access point and stations. (It is recommended |
| per Minute | that this value not be higher than twice the number of |
| stations in your BSS.) | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Transmitted | allowed to be transmitted from any access point. If a |
| greater number is detected, an alarm can be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per minute |
| Received | allowed to be received by any access point. If a greater |
| number is detected, an alarm can be generated. | |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | allowed to be transmitted by any Access point. If a greater |
| Transmitted | number is detected, an alarm can be generated. |
| # of Data | Enter the maximum number of data frames per minute |
| Frames | allowed to be received by any access point. If a greater |
| Received | number is detected, an alarm can be generated. |
| # of Mgmt | Enter the maximum number of management frames |
| Frames | per minute allowed to be transmitted by any access point. |
| Transmitted | If a greater number is detected, an alarm can be generated. |
| # of Mgmt | Enter the maximum number of management frames per |
| Frames | minute allowed to be received by any access point. If a |
| Received | greater number is detected, an alarm can be generated. |
| # of Ctrl | Enter the maximum number of control frames per |
| Frames | minute allowed to be transmitted by any access point. |
| Transmitted | If a greater number is detected, an alarm can be generated. |
| # of Ctrl | Enter the maximum number of control frames per minute |
| Frames | allowed to be received by any access point. If a greater |
| Received | number is detected, an alarm can be generated. |
| # of | Enter the maximum number of fragment frames per |
| Fragment | minute allowed for any access point. If a greater |
| Frames | number is detected, an alarm can be generated. |
| Seen | |
| # of Decrypt | Enter the maximum number of decrypt error frames |
| Error | per minute allowed for any access point. If a greater |
| Frames | number is detected, an alarm can be generated. |
| Seen | |
[0125] The set of thresholds in the table below applies to all unauthorized access points in one preferred embodiment.
[0126]
| Column | Description |
|---|---|
| Signal Strength | If the signal strength for any access point is lower |
| Threshold | than this value, an alarm can be generated. |
| # of Associations | Enter the maximum number of associations per |
| per Minute | minute between any access point and stations. (It is |
| recommended that this value not be higher than | |
| twice the number of stations in your BSS.) | |
| # of Bytes | Enter the maximum number of bytes of data per |
| Transmitted | minute allowed to be transmitted from any access |
| point. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Bytes | Enter the maximum number of bytes of data per |
| Received | minute allowed to be received by any access point. |
| If a greater number is detected, an alarm can be | |
| generated. | |
| # of Data Frames | Enter the maximum number of data frames per |
| Transmitted | minute allowed to be transmitted by any Access |
| point. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Data Frames | Enter the maximum number of data frames per |
| Received | minute allowed to be received by any access point. |
| If a greater number is detected, an alarm can be | |
| generated. | |
| # of Mgmt Frames | Enter the maximum number of management frames |
| Transmitted | per minute allowed to be transmitted by any access |
| point. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Mgmt Frames | Enter the maximum number of management frames |
| Received | per minute allowed to be received by any access |
| point. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Ctrl Frames | Enter the maximum number of control frames per |
| Transmitted | minute allowed to be transmitted by any access |
| point. If a greater number is detected, an alarm can | |
| be generated. | |
| # of Ctrl Frames | Enter the maximum number of control frames per |
| Received | minute allowed to be received by any access point. |
| If a greater number is detected, an alarm can be | |
| generated. | |
| # of Fragment | Enter the maximum number of fragment frames per |
| Frames Seen | minute allowed for any access point. If a greater |
| number is detected, an alarm can be generated. | |
| # of Decrypt Error | Enter the maximum number of decrypt error frames |
| Frames Seen | per minute allowed for any access point, if a greater |
| number is detected, an alarm can be generated. | |
[0127] Some embodiments may allow for self-configuration of some or all of the thresholds discussed above. Such self-configuration could occur through a learning mode in which the systems and methods according to the present invention monitor traffic on the wireless computer network for the first several hours or days after installation. In such a learning mode, alarm notifications can be disabled. It is expected that, in the beginning, the generation of alarms will be very high—hundreds or thousands per day depending on actual network traffic—until thresholds in accordance with the network's normal activity are determined. Once an accurate picture of normal network traffic has been captured, and thresholds are reflective of normal activity, a switch to normal operations mode enables alarm notifications.
[0128] In one preferred embodiment, a command line interface is provided to configure settings that are not available within the graphical user interface. For example, the IP address of a hardware component can be changed, its system clock reset or set to “sync” with a network time server. In other embodiments, the graphical user interface and/or the command line interface can allow significant overlap of configuration capability. Further, some embodiments have only one or the other interface type.
[0129] Finally, some embodiments provide no interactive interface for configuration and are limited to reading configuration data from a file, deriving configuration data from past monitoring of the wireless computer network or otherwise receiving this data. The command line interface in one preferred embodiment can be accessed either on the hardware component such as through a command shell such as the Linux Gnome Terminal or over the network using an SSH (preferably, version 2) client.
[0130] In one preferred embodiment, a command shell automatically opens on the hardware component after booting. A terminal icon can appear on the task bar at the bottom of the display; clicking the icon opens additional terminal windows. At the command line prompt, a command is entered to launch the command line interface.
[0131] An SSH client is launched and connected to the hardware component's IP address. The identity of the user making the connection is verified. At the command line prompt, enter the following command to launch the command line interface:
[0132] In one preferred embodiment, the screen displays in the terminal window provide five “program areas”:
-
- [0133] Network—offering options to change IP address, DNS servers, hostname, domain name, mail server, ARP, and create “allow” and “deny” lists.
- [0134] Date—allowing time and date editing, time zone setting, and configuration of an NTP server.
- [0135] Service—providing tools to fine-tune the hardware component parameters, configure data management, and reboot and shut down the component.
- [0136] Users—allowing creation, editing, and deletion of user accounts allowed access to the graphical user interface.
- [0137] Help—tips on using the application, and detailed help topics.
[0138] Opening the network settings program area, the following commands are available in one preferred embodiment:
[0139]
| Command | Description |
|---|---|
| IP | IP address config |
| Allows modification of the IP address, Subnet mask, and | |
| default gateway for the hardware component logged onto. | |
| The “IP configuration” screen opens, displaying the | |
| current network configuration and allows modification. | |
| DNS | Define DNS servers |
| Adding or deleting a DNS nameserver. | |
| The “Nameserver screen” opens, displaying your current | |
| DNS server's IP address and allows addition, deletion | |
| and modification. | |
| Note: Multiple DNS servers can in some embodiments have | |
| an “order” for processing DNS requests. The first server on the | |
| list (identified by the numeral 1) is the first to offer name | |
| resolution; the second server on the list (identified by the | |
| numeral 2) is the second to process the request if the first | |
| is unable to do so. In order to change the order preference | |
| of multiple servers, all must be deleted and re-entered in the | |
| desired order for them to process DNS requests. | |
| HNAME | Set hostname |
| Changing the name of the hardware component. The | |
| Hostname screen displays your current hostname and | |
| allows modification. | |
| Bear in mind that whenever the hostname is changed, its | |
| name must also be modified in all devices that refer to it | |
| (e.g., DNS servers). | |
| DNAME | Set domain name |
| Changing the domain to which the hardware component | |
| belongs. The Domain name screen displays your current | |
| domain name and allows modification. | |
| Bear in mind that whenever the domain name is changed, | |
| it must also be modified in all devices that refer to it | |
| (e.g., DNS servers). | |
| MRELAY | Config mail relay host |
| Configuring a hardware component to send alarms by email. | |
| The Mail relay host screen appears and allows entry of | |
| qualified hostnames. | |
| In one embodiment, mail relay hosts may be referred to by | |
| IP address or fully qualified hostname (e.g., | |
| myhostname.mydomainname.com) of a mail server to | |
| process email alarm messages. | |
| Note: the mail server must be configured to allow this | |
| appliance to relay email through it, or at least to direct its | |
| mail to another mail server that will relay it. | |
| ARP | Config permanent ARP table |
| Creating a permanent ARP table. The ARP table screen | |
| displays your current ARP records and allows modification. | |
| In order to protect connections between this hardware | |
| component and remote administrators from being hijacked by | |
| man-in-the-middle ARP “blasts” (that redirect traffic for this | |
| IP address to an alternate MAC address), it is preferable | |
| to create permanent ARP records for gateways and | |
| other important machines. | |
| HALLOW | Configure/etc/hosts.allow file |
| Specifying which machines are allowed to connect to the | |
| hardware component. The Allow list screen displays your | |
| current list of allowed machines and allows modification. | |
| Machines allowed to connect to this hardware components | |
| can be specified. | |
| Only those whose IP address, subnet, fully qualified | |
| hostname, or domain name match an entry in this list are | |
| allowed to connect to this hardware component to run the | |
| available administrative programs and routines. | |
| HDENY | Config/etc/host.deny file |
| Identifying machines that may not connect to the hardware | |
| component. The Deny list screen displays your current list | |
| of denied machines and allows modification. | |
| Machines not allowed to connect to this hardware | |
| component can be specified. Anyone whose IP address, | |
| subnet, fully qualified hostname, or domain name matches | |
| an entry in this list are not allowed to connect to this | |
| hardware component | |
| Note: HALLOW, in one preferred embodiment, takes | |
| precedence over HDENY. For example, if 123.456.789.963 | |
| is on the allow list, yet the subnet 123.456.789. is on the deny | |
| list, the individual machine above is allowed to connect to | |
| the appliance. | |
[0140] Opening the date settings program area, the following commands are available in one preferred embodiment:
[0141]
| Command | Description | |
|---|---|---|
| TIME | Time/Date config | |
| Allows configuration of the time/date | ||
| for the hardware component. | ||
| TZ | Set time zone | |
| Allows configuration of the time | ||
| zone for the hardware component. | ||
| NTP | Enable/disable NTP | |
| Allows configuration of the hardware | ||
| component to use a network time | ||
| server. | ||
[0142] Note: If you change the system time because, for example, you move the appliance's location from the east to west coast of the United States, you must also locate a new network time server in the same time zone.
[0143] Opening the set appliance parameters, configure data management, and restart or shutdown the system area, the following commands are available in one preferred embodiment:
[0144]
| Command | Description |
|---|---|
| TUNE | Tune appliance parameters |
| Allows users to modify some of the core | |
| values related to the environment's | |
| functionality. | |
| DMGT | Data management |
| Allows users to modify how the environment stores its data. | |
| REBOOT | Reboot system |
| Allows graceful restart of the hardware component. | |
| HALT | Halt system |
| Allows graceful shutdown of the hardware component. | |
[0145] Opening the Users program area, the following commands are available in one preferred embodiment:
[0146]
| Command | Description | |
|---|---|---|
| NEWU | Create user | |
| EDITU | Edit user | |
| DELU | Delete user | |
[0147] The functionality of these features can in one preferred embodiment match with like functionality provided in a standard LINUX user management facility.
[0148] Various methods and functions as exhibited in various embodiments according to the present invention are described above and below with respect to network security enhancement. In some embodiments, one or more processors within architectures of the environments as described above may execute the steps in such methods and provide such functionality. The functionality may spread across multiple processing elements. In other embodiments, any suitable computer readable storage device, media or combination of devices and/or media, including primary storage such as RAM, ROM, cache memory, etc. or secondary storage such as magnetic media including fixed and removable disks and tapes; optical media including fixed and removable disks whether read-only or read-write; paper media including punch cards and paper tape; or other secondary storage as would be known to those skilled in the art, may store instruction that upon execution by one or more processors cause the one or more processors to execute the steps in such methods and to provide such functionality.
[0149] Vulnerability assessment is accomplished by analyzing WLAN traffic, and discovering access points and workstations. The system determines how many bytes of data stations are sending and receiving, the mean signal strength for an entire day or the hi/low signal strength for each minute. It can distinguish between network traffic internal to the wireless network and traffic originating from or destined to the physical, wired-network and which stations are the largest senders and receivers of data. The system produces broad summaries of data that report high, low, and mean values for a variety of traffic parameters, and detailed views that show minute-by-minute snapshots of your traffic. Traffic parameters include the breakdown of frame traffic (control, management, data, and error frames) and network routing information. The system determines if any traffic has not been encrypted, users are authenticated, and all hardware is properly configured. The system detects rogue deployments by identifying and locating unauthorized WLANs and ad hoc networks (peer-to-peer networks) that violate company policy and jeopardize security. The system identifies suspicious WLAN traffic across unauthorized channels and frequencies, which can be a common sign of intruders accessing your WLAN or employees abusing their network privileges.
[0150] The systems and methods according to one preferred embodiment use an audit of existing wireless hardware and perform a survey the air space surrounding the wireless network prior to activating intrusion detection. In this way, a baseline activity level can be determined.
[0151] Identify every access point in the wireless computer network. Obtain or determine for each its MAC address, Extended Service Set name, manufacturer, supported transmission rates, authentication modes, and whether or not it is configured to run Wired Equivalent Privacy (WEP) and wireless administrative management. In addition, identify every workstation equipped with a wireless network interface card, and record the MAC address of each device. Take note of any physical features in the environment (walls, competing electronic devices such as microwave ovens, cordless phones, etc.) that might interfere with wireless signals.
[0152] The hardware audit serves as the baseline against which the systems and methods according to the present invention can compare. That is, all access points and wireless stations should be detected by the various embodiments of the present invention. (If an access point or station is not detected, follow logical troubleshooting steps.) On the other hand, it is likely that more devices than expected will be detected. Some of these may be stations or access points not identified or of which no one was aware. Others may be “rogue” devices—surreptitious or unauthorized installations in the network—or harmless equipment belonging to nearby companies, and others may be actual hackers. Once the systems and methods according to the present invention are in intrusion detection mode, all detected access points and stations can be reported.
[0153] Preferably a mobile hardware component according to the present invention is walked around the perimeter of the wireless computer network in a powered up state (allowing it to collect data as it is moved), or placed in a central location for 12 to 24 hours to collect a larger amount of data. The benefit of a “walk-around” survey is that it generates a nearly immediate picture of the existing wireless “air space.” The benefit of a “stationary” survey is that over a longer period of time, is greater certainty of detecting devices that only operate intermittently or hackers attempting to penetrate the network off-hours. Repetition of the survey, whether walking or stationary, should occur on all 11 channels.
[0154] Depending on the size of the wireless network, a hardware component can be placed at the four corners or at intermediate points in the Extended Service Set footprint. At each location, the component should be allowed to passively monitor network traffic for 12-24 hours. Hard copy of network data should be preserved prior to each move.
[0155] Simply walk around the perimeter of the wireless network with the hardware component powered on and open to an overview screen. The various access points and stations within the wireless computer network can be detected. Compare this information with the hardware audit made prior to collecting this data. Repeat this walk-around survey for each of the eleven channels.
[0156] Each access point detected should be designated as authorized or unauthorized. Each observed station should be designated as valid or not.
[0157] Leave a component in each location from 1-3 days. Each day, print reports to preserve captured information. Based upon this information, specific access point and station related thresholds can be tuned to distinguish between normal and abnormal traffic patterns.
[0158] The intrusion detection system (IDS) engine listens to wireless network traffic. FIG. 3 depicts one preferred process the IDS follows in evaluating data associated with received traffic. In the depicted exemplary process, all packets pass through four detections systems: signature-based testing, protocol-based testing, anomaly-based testing, and policy deviation-based testing; other embodiments may use one or more of these tests, or other tests, in varying combinations.
[0159] Initially, configuration information is received in step 305, typically including network default data and risk criteria. This information can be retrieved from a file, derived or obtained from monitoring the network and/or entered interactively at the outset of the process. The system reads or receives frames from the wireless network instep 310. The received frames are interrogated as follows.
[0160] The information within the frame is interrogated to determine if a known attack signature has been identified in step 325. Signatures encode datalink layer attack patters as combinations of packet sequences and state. For example, active probing emits a pattern or sequence of network requests. This sequence can be recognized by its packet sequence signature. If the attack signature is identified, the intrusion detection system signals an alarm manager to deliver an alert to the administrator in step 345.
[0161] If no attack signature is identified, the frame information is passed through a protocol violation engine to determine if the protocol used in the frame is authorized in step 330. Protocol analysis examines whether or not protocol usage is legitimate. For example, emitting a large number of association or disassociation requests in a short interval is not a legitimate use of the protocol. If the protocol used in the frame is outside of the authorized protocol set, the intrusion detection system signals an alarm manager to deliver an alert to the administrator in step 345.
[0162] If the protocol test passes, in step 335, the IDS checks the frame data for statistical anomalies against the SDS, or a statistics database maintained therein. Anomaly based detection computes such values as the mean, non-zero mean, standard deviation, autocorrelation and peak for each time slice throughout the day. This can be used to create a normalized statistics database for each time slice and user. Current activity is then monitored and compared with the recorded statistics vector. If the difference is larger than a configurable threshold, an alert is generated. Instead of, or in addition to, this approach, a Bayes test can be applied to deduce the probability that the current statistics vector is an attack as opposed to a legitimate sequence. If an anomaly exists, the intrusion detection system signals an alarm manager to deliver an alert to the administrator in step 345.
[0163] If no anomaly is detected, the system interrogates the frame to determine if a pre-defined policy has been violated in step 340. Policy testing compares the observed activity with a configurable set of activity rules stored in the SDS. For example, a rule can declare that only specific hosts with specific addresses and specific network cards can access the network. If a pre-defined policy has been violated, the intrusion detection system signals an alarm manager to deliver an alert to the administrator in step 345.
[0164] If no policy has been violated, the system determines whether a rogue or unauthorized user has gained access to an access point physically connected to the network, as shown in step 342. An example of the test used to determine whether a rogue exists on the network is shown with reference to FIG. 16 . As described above, through analysis of traffic patterns observed directly over the air, a determination of all wireless devices that are communicating with one or more wired network devices can be made. Further, by comparing the patterns associated with authorized and unauthorized wireless devices, a list of all unauthorized wireless devices attached to an authorized wired network can be derived.
[0165] As those skilled in the art should recognized, the 802.11 MAC layer frame format includes up to four address fields. These fields are used to specify the wireless receiver, wireless transmitter, originating source and targeted destination address of the frame. All addresses are specified per IEEE 802 MAC address specifications. These addresses are formatted as a six-byte hexadecimal number and are uniquely assigned to each device.
[0166] Devices communicating using 802.11 populate the various address fields with their own address, destination address, and minimally a third address representing the Basic Service Set Identifier (BSSID) of the wireless LAN being used. The position of the addresses in the 802.11 frame depends on the direction of communication and whether or not the communication is part of a BSS, IBSS, or wireless bridging configuration.
[0167] As communications occur over time by each device, the position of the addresses naturally changes. By observing these changes, a pattern of activity can be logged for each device and each address represented in the frame transmissions.
[0168] After observing these patterns for a period of time, a list of wireless and wired devices can be derived, as described above. This is done by noting the addresses that have populated the wireless transmitter or receiver positions versus the addresses that have not. With regard to an embodiment of the present disclosure, those addresses that have been observed in the transmitter or receiver frame positions are characterized as wireless, while those addresses observed only in the source or destination frame positions are characterized as wired devices. The wired devices by definition include no transmitter or receiver, and therefore their addresses are not seen in the transmitter or receiver frame positions. Otherwise, the device is considered a wireless device, if the device address has been noted in the transmitter or receiver field of the frame.
[0169] Once this determination is made, the system in various embodiments, is further enabled to examine the patterns of authorized and unauthorized wireless devices and determine whether or not any wired-side devices are present in these patterns. If common wired-side addresses are present in both sets of patterns, an elevated level of threat can be assigned to those unauthorized wireless devices communicating with wired devices present in both lists. Otherwise, the system issues an alarm indicating an unauthorized device is operating in the vicinity of the wireless network.
[0170] The elevated threat issued is assigned due to the fact that the above analysis has determined that an unauthorized wireless device has been observed and is physically attached to a protected wired network (e.g. a rogue on the network). Those skilled in the art should recognize that such a situation could potentially represent a more dangerous situation to the network's security than a wireless device operating in the general vicinity of the network.
[0171] Referring to FIG. 16 , shown is a flowchart illustrating a process associated with the multi-dimensional wireless intrusion detection process of FIG. 3 . The process begins at step 1600. In step 1605, the intrusion detection process reads the wireless frame. In step 1610, the intrusion detection process parses the wireless frame to determine the addresses that exist within the wireless frame. The intrusion detection process then updates the source/destination list with those addresses which were identified as either a source or a destination in the wireless frame, as shown in step 1615. The intrusion detection process also updates the transmitter and receiver list with those addresses which were identified as either a transmitter or a receiver, as shown in step 1620. The lists are then compared to each other, as shown in step 1625. Through this comparison, it is determined whether addresses are present in both lists. If so, these are marked for removal from the source/destination list. The intrusion detection process continues for a period of time and until a number of frames have been received, such than an adequate sampling of frames has been received. Those skilled in the art should recognize that there exist numerous algorithms to determine proper sampling from a statistical standpoint. Each of these algorithms is intended to be included within the scope of the present disclosure. Moreover, in various alternative embodiments of the present disclosure, an administrator sets up the sample size (number of frames and length of time), such that the thresholds shown in steps 1630 and 1635 are customizable by the administrator.
[0172] After capturing an adequate sampling of the network traffic, the source/destination and the transmit/receive lists are then compared to each other, as shown in step 1640, and the addresses which are common to both lists are removed from the source/destination list. Thus, all of the device addresses remaining on the source/destination list are wired devices, and a wired device list is updated with the device addresses from the source/destination list as shown in step 1645.
[0173] The intrusion detection process then determines, as shown in step 1650, whether each of the wireless transmissions include authorized transmitter/receiver addresses. If the transmitter/receiver addresses on the transmitter/receiver list are authorized, then the wireless transmission was an authorized transmission. However, if there exists a transmitter/receiver address on the transmitter/receiver list which is not authorized, the intrusion detection process determines whether the wireless transmission includes a source or destination address which is on an authorized wired list, as shown in step 1655. If the wireless transmission was not to/from an authorized wired device, an unauthorized device alarm is issued, as shown in step 1660. Such a transmission is typically a wireless device operating in conjunction with another wireless network in the same vicinity.
[0174] However, if the source or destination address of the wireless transmission was to a device on the authorized wired list, the intrusion detection process issues a rogue on network alarm, as shown in step 1665. Such a situation can mean that a hacker has gained access to a network access point and has access to the wired network behind the access point. Those skilled in the art should also recognize that such a situation could occur when an employee buys an access point, and fails to register the access point with the network administrators. However, it should also be noted that even in such innocent instances where an employee uses an unapproved access point, the access point could leave the wireless (and wired) network open to hackers.
[0175] The tests outlined above and depicted in FIG. 3 are performed serially. In other embodiments, one or more of these tests may occur in parallel. Further, subsequent tests only occur if a prior test was passed. In a further preferred embodiment, all tests occur irrespective of the outcome of a prior test; consequently, a single read frame could potentially generate an alarm for every test performed on it.
[0176] Alerts can be in the any suitable form delivered to any suitable platform including, without limitation, a screen display to a monitor, a page to a pager, an outgoing voice call to telephone, a SMS message to a mobile telephone, an e-mail message to a valid address, posted to a Web page available via an appropriate Web server or WAP alert to a WAP enabled device. Various types of screen displays and reports may be used to provide information regarding generated alarms.
[0177] In one preferred embodiment referred to as AirDefense Mobile in U.S. Provisional Patent Application Ser. No. 60/381,829 entitled “SYSTEMS AND METHODS FOR NETWORK SECURITY” filed May 20, 2002, preferred interfaces for reviewing and reporting alarms are described in detail. The contents of this application are hereby incorporated by this reference herein for all purposes.
[0178] In some embodiment, the outputs of all IDS test are then compared and a confidence level computed in step 345. In one such embodiment, in the case where only a statistical anomaly is detected, it is flagged as a lower level performance alert. In the case where one or more other violations are detected, the alarm is elevated to an intrusion alarm.
[0179] Some embodiments may use a variety of data stores in implementing the above process to track data across multiple iterations of the process; such data stores can in one preferred embodiment be part of an SDS as described above. Some such embodiments can include a statistics database, a station database and/or a state data store. In such embodiments, some or all of the following steps depicted in FIG. 3 can occur.
[0180] In step 315, a station database is updated. This database contains, in one preferred embodiment, per station and per access point records with information describing device address, communications state, timestamps of first and last activity, counts of byte transmissions and local policy information describing whether device is authorized or not for usage in the monitored network.
[0181] In step 320 state information is updated. State refers to whether or not the device has been seen before and whether or not the station is unauthenticated and unassociated, authenticated, authenticated and associated or unknown state information associated with the wireless computer network.
[0182] In step 350, a determination is made as to whether a particular statistics interval has been complete. If so, statistics in an SDS are updated in step 355, and processing continues with the next frame in step 310. Otherwise, processing simply continues in step 310 with the next reading or receiving of a frame.
[0183] A modified and enhance version of the above approach is used where network traffic is monitored from multiple input devices such as with the embodiments depicted in FIGS. 2B-E . FIG. 4 depicts this enhanced process starting at step 405.
[0184] Step 410 is analogous to step 305 from the process of FIG. 3 . In step 410, configuration information is received. As before, this is typically done through reading system configuration files, monitoring the network and/or interactive entry at the outset of the process. This information typically includes network default data and risk criteria such as access point configuration data (MAC Address of the access point, Access Point Name, etc.), station configuration data and various thresholds values.
[0185] In step 430, a wireless packet frame is received from each input device (e.g., hardware components 210A-D, host system 220 and/or sensors 230A, 230B). Frames are read so that the frame content can be interrogated.
[0186] Each read frame is interrogated by a multi-dimensional intrusion detection system (IDS) such as detailed above with respect to FIG. 3 , and the outputs of all IDS tests are then compared and a confidence level computed in step 435. As with the process above, other tests in either alone, in combination with each other or in combination with one or more of those described above may be used in other embodiments.
[0187] In step 440, in the case where only a statistical anomaly is detected, it is flagged as a lower level performance alert. In the case where, in addition to the statistical anomaly, one of the other violations has been detected, the alarm is elevated to an intrusion alarm and an alarm manager is alerted in step 444. Other embodiments do not rely on aggregate test outcome but determine alarm status on single test outcomes. Further, some embodiments can use other test types and outcome combinations to determine type and severity of alarms generated.
[0188] If an alarm is not detected in step 440, a test to see if a predetermined interval for gathering statistics has been reached occurs in step 460. If the end of the pre-configured statistics gathering interval has occurred, the SDS is updated in step 470 to reflect the statistics gathered from the received frames over the interval. Statistics are gathered by monitoring traffic between network nodes, minute-by-minute statistics about BSS frame types and traffic volumes, summaries of transmission statistics for all stations associated with access points, current-minute transmission statistics for all Stations, and detailed minute-by-minute transmission statistics for any individual station in the wireless computer network.
[0189] Data fusion occurs on a batch basis by aggregating data from multiple databases. This process begins at step 414. The process integrates statistical data from multiple databases that is generated through frame monitoring and intrusion detection engines. This approach provides a methodology for managing data received from input devices such as hardware devices 210A-D and/or sensors 230A, 230B deployed at multiple sites and for aggregating enterprise data at a single central system such as host 220.
[0190] The Attack and Station Profile database is read at step 418 to begin a processing loop to integrate databases from separate sources. Correlation and pattern recognition is performed at step 420 to update the attack and station profiles in step 424. The processing loop then sleeps at step 428 until the next processing loop interval is to take place based on the pre-configured time interval or trigger.
[0191] After the alarm manager is signaled in step 444, the attack and station profile database is read in step 448; in this step, existing attacks are queried and existing station security state is queried. In step 450, this data is compared to the newly generated alarm. If it is sufficiently similar, no new external notification occurs in step 454. If it is not, a new notification message is generated in step 454 and console display and/or external messaging of the alarm occurs in step 458.
[0192] In some embodiments, the scanning of air waves for network activity can be adaptive in nature. In a typical configuration, wireless network channels are scanned for activity according to a predefined pattern. According to an adaptive approach, the predefined pattern can serve as an initial and/or baseline pattern. This pattern can then be adapted based upon actual activity in the scanned channels. FIG. 11 depicts a flow chart of a process for performing adaptive scanning.
[0193] This mechanism allows the system to deterministically scan all wireless channels through time-based multiplexing while also allowing the system to adaptively adjust the time spent on a given channel based on current and past activity. A typical scenario would be to monitor a fixed set of channels and periodically perform a background scan of the remaining channels; FIG. 14 depicts an example interface for configuring such a baseline or default scan pattern. If any activity is observed on a channel expected to be idle or unauthorized activity is discovered, the system adapts by adding this channel to its primary scanning pattern. If activity then diminishes, this channel will be removed from the primary scanning pattern and then scanned next during the background scanning mode. The system can utilize either pre-configured thresholds or user-entered thresholds to determine the trigger point at which to start or stop dynamic monitoring of the channel. Additionally, automated controls can be included that will lock onto the channel if a security violation has been detected per the underlying multi-dimensional analysis engine.
[0194] Further, enhanced embodiments may utilize multi-channel receivers in which adaptive scanning may occur uniquely per receiver. This allows, for example, multiple channels or multiple frequency bands to be scanned and monitored in parallel.
[0195] As described above, systems and methods according to the present invention can automatically generate alarms whenever certain events or conditions occur within your wireless network. In some embodiments, an alarm manager providing an interface for viewing can be provided; such an interface is described in greater detail in co-pending “SYSTEMS AND METHODS FOR NETWORK SECURITY” filed May 20, 2002 60/381,829 The following table identifies the alarms, alarm subtypes and severities available in one preferred embodiment referred to as AirDefense Mobile.
[0196]
| Alarm | ||
|---|---|---|
| Alarm Type | Alarm Subtype | Level |
| DoS Attack | De-authenticate | Critical |
| AirDefense Mobile detects when a hacker | ||
| pretends to be an Access point and broadcasts | ||
| a “de-authenticate” message. This forces all | ||
| Stations to re-authenticate themselves, generating | ||
| excessive network traffic, and causing | ||
| inconsistent connectivity and data transfer. | ||
| Disassociate | Critical | |
| AirDefense Mobile detects when a hacker | ||
| pretends to be an Access point and broadcasts | ||
| a “disassociate” message. This forces all | ||
| Stations to re-associate themselves with the | ||
| Access Point, generating excessive network | ||
| traffic, and causing inconsistent connectivity | ||
| and data transfer. | ||
| Unauthorized | Not on allow list | Critical |
| Station | AirDefense Mobile detects a Station whose | |
| MAC address is not on its Valid list. | ||
| (A Valid list is maintained by the system.) | ||
| Threshold | GLB CRC errors | Major |
| AirDefense Mobile detects if CRC errors | ||
| exceeded configured limits (CRC errors are | ||
| generated when checksums fail on | ||
| individual frames.) | ||
| BSS assoc count | Major | |
| AirDefense Mobile detects when the number | ||
| of associations within an entire BSS, in any | ||
| given minute, exceed the number specified in | ||
| configuration information | ||
| BSS signal strength | Critical | |
| AirDefense Mobile detects when the signal | ||
| strength in any access point falls below a | ||
| specified threshold. | ||
| BSS fragments | Minor | |
| AirDefense Mobile detects when the number | ||
| of fragmented frames within any minute exceed a | ||
| specified threshold. | ||
| BSS decrypt errors | Major | |
| AirDefense Mobile detects when the number of | ||
| decrypt error frames within any minute exceed a | ||
| specified threshold. | ||
| BSS assoc stations | Minor | |
| AirDefense Mobile detects when the total number | ||
| of associated Stations within an entire BSS, in any | ||
| given minute, exceed a specified number. | ||
| BSS tbw in | Minor | |
| AirDefense Mobile detects when, during any | ||
| minute, the number of bytes of data entering the | ||
| BSS from the wired portion of your network | ||
| exceed a set threshold. | ||
| BSS tbw out | Minor | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of bytes of data going | ||
| from the BSS to a wired portion of your network | ||
| exceed a set threshold. | ||
| BSS tbw intra | Minor | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of bytes of data | ||
| originating from and destined for the BSS | ||
| exceed a specified threshold. | ||
| BSS tbw thru | Minor | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of bytes of data | ||
| originating from a wired portion of the network | ||
| hop through the BSS to another wired portion | ||
| of the network exceed a set threshold. | ||
| BSS data | Major | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of data frames in the | ||
| BSS exceed a specified threshold. | ||
| BSS mgt | Major | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of management frames | ||
| in the BSS exceed a specified threshold. | ||
| BSS ctl | Major | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of control frames in | ||
| the BSS exceed a set threshold. | ||
| BSS ad hoc | Critical | |
| AirDefense Mobile detects when, during any | ||
| minute, the total number of Ad Hoc frames in | ||
| the BSS exceed a specified threshold. | ||
| Note: Wireless network adaptor cards of lesser | ||
| quality will randomly generate Ad Hoc frames. | ||
| AirDefense Mobile's default threshold (1) may | ||
| cause all of these spurious frames to generate an | ||
| alarm. After monitoring the network for a week | ||
| or two, it may be advisable to set the threshold | ||
| to a number at or a little higher than what the | ||
| network normally generates. | ||
| STA assoc count | Major | |
| AirDefense Mobile detects, during any | ||
| minute, when any Station associates with | ||
| an access point more times than provided | ||
| by a specified threshold. | ||
| STA signal strength | Critical | |
| AirDefense Mobile detects, during any | ||
| minute, when any station's signal strength | ||
| falls below a value specified. | ||
| STA fragments | Minor | |
| AirDefense Mobile detects, during any | ||
| minute, when any station generates more | ||
| fragmented frames than a specified value. | ||
| STA decrypt errors | Major | |
| AirDefense Mobile detects, during any | ||
| minute, when any station generates more | ||
| decrypt errors than a set threshold. | ||
| STA tbw received | Minor | |
| AirDefense Mobile detects, within any | ||
| minute, when any station receives more | ||
| bytes of data than a predetermined threshold. | ||
| STA tbw transmitted | Minor | |
| AirDefense Mobile detects, within any | ||
| minute, when any station transmits more | ||
| bytes of data than specified in a set threshold. | ||
| STA data received | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station receives more data | ||
| frames than a specified threshold. | ||
| STA data transmitted | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station transmits more | ||
| data frames than a specified threshold. | ||
| STA mgt received | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station receives more | ||
| management frames than a specified threshold. | ||
| STA mgt transmitted | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station transmits more | ||
| management frames than a set threshold. | ||
| STA ctl receive | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station receives more | ||
| control frames than a specified threshold. | ||
| STA ctl transmit | Major | |
| AirDefense Mobile detects, within any | ||
| minute, when any station transmits more | ||
| control frames than a set threshold. | ||
| ID Theft | Out of sequence | Critical |
| AirDefense Mobile detects when frames are | ||
| transmitted out of sequence. This suggests | ||
| that someone has spoofed a Station and is | ||
| sending data at the same time as the | ||
| legitimate Station. | ||
| Vendor out of character | Critical | |
| AirDefense Mobile compares every | ||
| Station's transmissions against an internal | ||
| database of known vendor “transmission | ||
| profiles” or “signatures.” If the actual | ||
| network traffic does not match the | ||
| vendor-profile associated with the | ||
| Station's Wireless NIC, AirDefense | ||
| Mobile assumes that the traffic | ||
| originates from an unauthorized station | ||
| using a spoofed NIC. | ||
| Anomalous signal strength | Critical | |
| AirDefense Mobile tracks the high, low, | ||
| and mean signal strength of each station | ||
| many times a minute throughout the day. | ||
| Whenever it detects that the Station's | ||
| signal strength deviates from the norm, | ||
| it generates an alarm. | ||
| Access Point | WEP mode changed | Critical |
| Mode | AirDefense Mobile detects when the | |
| WEP value in an access point's beacon | ||
| differs from the value it is supposed to be. | ||
| (AirDefense Mobile auto-detected the | ||
| WEP property, or it was manually entered.) | ||
| Rate changed | Critical | |
| AirDefense Mobile detects when the | ||
| supported transmission rate values in | ||
| an access point's beacon differs from the | ||
| value it is supposed to be. (AirDefense | ||
| Mobile auto-detected the rate property, or | ||
| it was manually entered.) | ||
| Channel changed | Critical | |
| AirDefense Mobile detects whenever an | ||
| access point changes channels. (The | ||
| channel is identified in configuration | ||
| information.) | ||
| Cf changed | ||
| AirDefense Mobile detects when the | ||
| Point Coordination value in an AP's | ||
| beacon changes. A change in this field | ||
| may indicate that the access point was | ||
| reconfigured, though this is not necessarily | ||
| a problem. (The Point Coordination field | ||
| refers to the access point's mode of | ||
| collision avoidance.) | ||
| Essid changed | ||
| AirDefense Mobile detects when the | ||
| access point's broadcast of its Extended | ||
| BSS ID changes. The ESSID information | ||
| is stored as configuration information. | ||
| Unauthorized | AirDefense Mobile detects when | Critical |
| AP Admin | administration sessions are being | |
| conducted directly with the access point. | ||
| Odd Mgt. | Sta tx ap mgt fr | Critical |
| Frame | AirDefense Mobile detects when a | |
| Station is transmitting a management | ||
| frame reserved for access point's use. | ||
| Ap tx illegal mgt fr | Critical | |
| AirDefense Mobile detects when an | ||
| access point transmits an illegal | ||
| management frame. | ||
| Out of spec frame | Critical | |
| AirDefense Mobile detects when an | ||
| access point transmits a frame that | ||
| does not follow 802.11b standards. | ||
| Other bogus frame | Critical | |
| AirDefense Mobile detects when an | ||
| access point transmits any frame it | ||
| does not understand. | ||
| Ad Hoc Net | AirDefense Mobile detects when | Critical |
| Detected | Stations are directly transmitting and | |
| receiving to and from each other without | ||
| using an authorized access point. | ||
| Note: Unlike all other alarms that are | ||
| generated every time the network event | ||
| is detected within a minute, AirDefense | ||
| Mobile will only generate an Ad Hoc | ||
| Network alarm once in the current 24 | ||
| hour period for each MAC address. | ||
| AP Beacon | AirDefense Mobile detects when an | Critical |
| Rate | access point's beacon rate changed. | |
[0197] The present systems and methods allow an end-user to specify and implement the security and policy constraints associated with a particular wireless network deployment. Once configured with such information, the network activity is monitored on a continuous basis to determine if the activity is within the guidelines specified by the established constraints.
[0198] If the activity is found to not be in compliance with the established constraints, a real-time alarm is generated and reported to the user through a number of mechanisms. These mechanisms can include Web, Email, SNMP and Syslog notification. In some embodiments, the response is not limited to notification. These embodiments can include automated enforcement and/or active defensive measures as discussed below.
[0199] Some embodiments support automated enforcement of constraints. In such embodiments, attempts to rectify the policy deviation through re-configuration of the affected device or devices can occur automatically upon detection of the deviation. This reconfiguration attempts to implement the specified policy within the relevant devices.
[0200] This process can be viewed as a form of a feedback control loop. In many cases, such a loop operates by comparing a reference input to a measured output, computing their difference, and using this difference to adjust the desired output. This continues to drive the desired output to compliance with the reference input.
[0201] FIG. 10 depicts an exemplary process that includes automated policy enforcement. Normal monitoring of network activity occurs. The monitored activity is checked for compliance with established constraints. If a constraint is violated, a notification (alert) is generated and forwarded to a user and/or other systems. A procedure associated with the alert is triggered that attempts to manually or automatically rectify the underlying cause of the violation. If the procedure successfully rectifies the cause of the violation, the triggered alert can be cancelled, updated or otherwise modified to indicate the present status of the violation.
[0202] Automatic resolution of the policy violation can employ a management and control interface on the monitored equipment to effect the desired change. This interface may be in the form of an HTTP, HTTPS, SNMP or vendor-specific command line interface reachable via Telnet, SSH or another remote login interface; in addition, or instead, alternative interfaces could be provided via automated voice and/or tone recognition systems for handling telephone based configuration of the environment. Multiple such interfaces could be simultaneously available. An example Web-based interface is depicted in FIGS. 13A-B .
[0203] Various embodiments of the present disclosure further include a personal wireless monitoring agent on one of the devices 210A-D, which, as described above, are typically mobile computer systems or notebook computers. In various embodiments of the present disclosure, thee personal wireless monitoring agent is a software package installed on the devices 210A-D, and executed by the notebook computer.
[0204] The personal wireless monitoring agent is designed to examine the behavior of the wireless networking activity and operational modes observed on a particular device (e.g. the notebook computer). Thus, whereas the various embodiments of this disclosure capture, assess and examine the activities of multiple device at a central host, the current embodiment creates a more distributed system for examining the activities of a single device upon which the agent is installed. This examination is done periodically and is used to compare the recorded behavior, as documented in the registry and audit files of the wireless computer system, to an authorized operational policy, as described above. This comparison provides an assessment of policy compliance and assignment of risk and threat levels. The personal wireless monitoring agent will alert the user regarding any non-compliant behaviors which are detected and will further log the non-compliant behaviors for further analysis, such as to modify policies, create new policies, disable the mobile computer system from accessing the wireless network, etc.
[0205] Once the personal wireless monitoring agent has detected network connectivity, the agent will upload alert logs periodically to a centralized management server. This server will catalog all alerts as well as offer updates to agent policy rules and agent executable software. Additionally, the devices 210A-D (FIGS. 2A-E ) can also be specified for special handling when observed by an IDS monitoring engine. For example, such a device 210A-D can be automatically placed on a watch list within a centralized server having an enterprise monitoring solution. When the device 210A-D is observed operating over the air by a sensor device 230A-B (FIGS. 2A-E ), an alert will be automatically generated. Additional customized handling procedures can be specified via policy administration, whereby a policy to automatically terminate the device 210A-D based upon observed behavior can be implemented as described herein.
[0206] The monitoring and detection of suspicious or risky wireless network behavior can be performed using a number of methods. In a passive mode, through examination of the host platform's configuration files and activity logs, decisions regarding the health of the platform can be made without any active network monitoring. This technique utilizes rules and the logged behavior to assess operational security health.
[0207] Another embodiment of the present disclosure includes a mode of operation that utilizes a networking driver to allow monitoring and network communications filtering and blocking. By combining the two modes in a feedback loop, the agent can be used to not only detect but also proactively prevent risky or unauthorized wireless network communications.
[0208] A further embodiment of the present disclosure includes a mode which enables the agent to utilize a network driver to also function as a roaming sensor in a streaming or store-and-forward mode of operation, as discussed with reference to vulnerability assessment and threat identification above and with reference to FIG. 3 . In this case, captured wireless data is transmitted back to a centralized server for multi-dimensional intrusion detection analysis and operational performance characterization.
[0209] In an embodiment of the present disclosure, rules defining acceptable or unacceptable configuration modes and wireless behavior are defined using an extensible format, such as extensible markup language (XML). The use of XML enables the rules to be dynamically modified by uploading new rules during an agent-to-server communications session. This format can also be used to control and configure the actual operating modes of the agent and also assign rules for its centralized communication sessions.
[0210] With reference to FIG. 15 , shown is a flowchart detailing the operation of an embodiment of a wireless personal monitoring agent. The process begins at step 1500. The wireless personal monitoring agent loads the policies in step 1505. The policies are typically stored in non-volatile memory on the device 210A-D (FIGS. 2A-E ), however, it should also be recognized that the policies could be downloaded from a centralized server (enterprise host) on startup.
[0211] The personal wireless monitoring agent then scans the registry, audit, log and/or configuration files on the device 210A-D, as shown in step 1510. The registry, log, audit, configuration files include information about communications being sent to or from the device as requested by the user. The scan compares these files to the policies loaded in step 1505. The results of the scan are logged by the personal wireless monitoring agent, as shown in step 1515.
[0212] The personal wireless monitoring agent then determines whether an alert should be sent to the screen of the device. This determination in various embodiments of the present disclosure can be based upon various considerations. The considerations can include, among others: whether the user of the device is an administrator; what level of policy violation is being committed; the configuration of the agent by the user of the device. If the agent determines that an alert should be sent to the screen, the agent instructs the graphics driver of the device 210A-D to display an alert, as shown in step 1525. Alternatively, if the agent determines that an alert should not be sent to the screen, the agent returns to step 1505. As should be understood, the process can include a delay between scanning such that the agent scans the registry, log, audit and/or configuration files at an interval. The interval in some embodiments of the present disclosure is set up by the user. However, it should be understood that the interval is not required to be regular/periodic.
[0213] As shown in the flowchart, the process branches at step 1515. While the agent determines whether any alerts should be sent to the screen/display, the agent also determines whether it should connect to the centralized server having the enterprise monitoring solution, as shown in step 1530. Again, the agent can be set up to connect with the central server at intervals. However, it should be recognized that in various embodiments of the present disclosure, the agent could generate its own determination of when to connect to the central server. For example, the agent could be set up to connect to the central server any time that the device is within range of accessing any of the wireless access points 180A-B (FIGS. 2A-E ) connected to the local network 190 (FIGS. 2A-E ). If there is no connection available, the agent would return to step 1505 of the process.
[0214] Upon connecting to the server, in step 1535 the agent in various embodiments of the present disclosure uploads alerts generated by the scanning step 1510, and logged in the logging step 1515. These alerts may be acted on by the central server in accordance with any of the response mechanisms provided herein. The agent further updates the policies stored on the device 210A-D, as shown in step 1540. The agent then returns to step 1505 of the process.
[0215] In some embodiments of the present invention, one or more active defense mechanisms may be triggered in response to alarm conditions, in addition to, or instead of, the notification process described above. The system may provide active defense from attacks by broadcasting data into the wireless network as well as being able to trap and/or map an intruder's workstation by triangulating the position of the intruder's workstation relative to the wireless network access points. It also may attempt alter the access point configuration in a manner that makes it difficult or impossible for the targeted attacker to continue communications.
[0216] By introducing CRC errors into the wireless stream, the system can actively defeat an attacker that is monitoring the stream for patterns to crack the encryption. CRC errors are introduced by transmitting at the same time as the detected intruder. Due the shared medium nature of the wireless computer network, the cause the packet transmission to be corrupted, preventing the intruder from successfully communicating with the network.
[0217] By introducing chaf, the system can actively defeat the attacker by placing random frames into the stream so that the encryption pattern becomes undetectable. Chaf is a form of randomized packet transmission that is designed to reduce the probability that a statistical analysis of the packet sequence would result in breaking of the encryption key. This is done by emitting a low-rate background transmission of packets that are emitted using the same characteristics (e.g., address, initialization vector, etc.) of legitimately observed traffic but with a randomized payload.
[0218] The system can lock-down a wireless network by jamming, a technique to prevent any unauthorized access to the wireless access point by introducing enough noise into the wireless network that workstations cannot physically connect to the wireless network. Jamming is a physical layer transmission that is performed to disrupt all unwanted wireless communications. It is equivalent to introducing a noise signal on top of the unwanted signal transmission such that any receiver would not be able to successfully receive the transmission.
[0219] In a Physical Device approach, one embodiment would utilize a standalone sensor to implement any of the Active Defense mechanisms. Dynamic channel change can be used to reroute authorized traffic to a different communication channel to avoid an intruder detected on a particular channel. In this approach, a channel change request is transmitted to the access point believed to be compromised and authorized stations use the new channel to communicate with the access point. This approach can also be used to avoid interference causing problems in communication between an access point and its authorized stations.
[0220] Some embodiments including dynamic channel change may further use a honeypot trap that tricks the attacker into thinking the original channel is still valid and provides the necessary forensic information to identify the attacker. FIG. 5 depicts a flow chart of a process starting at step 510 used in some such embodiment incorporating the honeypot trap.
[0221] In step 520, configuration information is received. This step is much the same as previously described steps 305 and 410 in FIGS. 3 and 4 respectively. Step 530 represents a waiting loop that waits until an attack has been detected. Typically, an intrusion detection system generates a signal that triggers departure from this loop; in some preferred embodiments, the intrusion detection system contains the hardware and/or executes the process described above. The signal from the intrusion detection system typically includes an indicator of the access point believed to be under attack.
[0222] In the case that an attack has been detected in 530, processing is passed to step 540 to activate the honeypot trap. A trap thread is started in step 580; the thread initializes itself with the identity of the monitored access point believed to be attacked. This identity typically includes the MAC address, Service Set Identifier, encryption mode, network mode and transmission modes. Once initialized, the thread moves to step 590, the Trap Intruder process. This process is designed to logically fool the identifier attacker into believing communication is still occurring with the original access point. This is accomplished through complete emulation of the original access point's identity and behavior. By maintaining communication with the attacker, a trap is created such that the attacker's physical proximity is assured as long as communication continues. Optionally, a new identity may be assumed such that a weaker or more vulnerable appearing access point can be presented to the attacker. This is done by again emulating access point functionality, but in this case with an identity and set of characteristics that appear vulnerable. This vulnerability appearance may be created through the use of no or weak encryption modes or the appearance of default manufacturing modes with known passwords and user IDs.
[0223] In step 550 a control packet is sent to the original access point to change channels or suspend transmission while the trap is engaged. This packet encapsulates a message indicating the above request and may be sent in or out-of-band to the access point. In-band refers to over-the-air transmission to the access point's wireless network interface whereas out-of-band transmission refers to transmission to the wired side interface of the access point.
[0224] Processing in the main loop then returns to attack detection in 530.
[0225] Triangulation determines the location of an attacker by mapping her relative position within the deployed wireless access points. The mapping and location detection process according to one or more preferred embodiments of the present invention as depicted in FIGS. 6A-B are discussed in greater detail below.
[0226] The process of FIG. 6A is used to create an internal database of IP addresses and/or names mapped to corresponding MAC addresses. Every Address Resolution Protocol (ARP) transaction is detected in step 605. In step 610, the information in the detected transaction is used to update the internal database. Some embodiments can perform the identification and location processing such as depicted in FIG. 6B without reference to such an internal database. This database is created and maintained in one preferred embodiment to make the station identification and location process easier and more efficient.
[0227] FIG. 6B depicts a process for identifying and locating a station within the wireless network. In some embodiments, this process can be used to pinpoint the location of a potential attacker; in some such embodiments, activation of the process is triggered by an intrusion detection system. In a preferred embodiment, the process is triggered by one of the intrusion detections systems and methods described in detail above.
[0228] In step 620, a lookup occurs in the internal database, such as created via the process depicted in FIG. 6A , on the current MAC address to determine if an IP or name mapping is already available. If found, the internal database is updated in step 640 and execution proceeds to step 645 to query the wireless sensor array—to begin position or location resolution. As indicated above, the internal database is one approach to acquiring the desired information. Some embodiments may skip this step and use either the wired network sensor or the reverse address resolution protocol (RARP) approach discussed below.
[0229] Otherwise, an optional wired network sensor can be queried for the name mapping in step 625. This sensor is preferably deployed within the wired network at a location convenient to sniffing DHCP, LDAP, DNS or other service/name mapping protocols. If found, the internal database is updated in step 640 and execution proceeds to step 645 to query the wireless sensor array—to begin position or location resolution. Some embodiments may not include such a wired network sensor; in which case this step is skipped.
[0230] If name is still not found, execution proceeds to step 630 where a RARP request is issued. This request asks the receiver population for the IP address of the MAC address in question. If found, the internal database is updated in step 640 and execution proceeds to step 645 to query the wireless sensor array—to begin position or location resolution.
[0231] If not found, name/IP mapping is not available at current time for this MAC address. In some embodiments, name/IP mapping may not be desired but location or position information is in which case the process can begin in such embodiments at step 645.
[0232] Step 645 begins the position or location resolution with a query to the wireless sensor array. Each sensor is queried for tracking information on the current MAC address in question. This tracking information identifies whether the MAC is currently observable by a given sensor, the sensor ID, and the signal strength associated with the MAC in question. The sensor array may include not only sensor devices (e.g., 230A, 230B) but also other wireless nodes accessible from this process such as devices 210A-D and/or host system 220.
[0233] From the data received via the query, the position relative to grid of sensors is calculated in step 650 by computing the “signal strength” distance to each sensor. This distance is computed as the square root of the sum of squares of three sensor signal strength values. The position is then estimated to be within the proximity of the sensors determined to have the smallest signal strength distance to the MAC address in question per the above computation. Once the set of sensors is selected, the position is further refined by selected the position as within the proximity of the sensor within above set with the strongest signal strength. In some embodiments, the process ends at this point with the position information being returned.
[0234] In embodiments maintaining a position database, this database is updated in step 660 with the position of the MAC address in question. The process then ends at step 670.
[0235] The techniques utilized to monitor WLANs can apply in general to monitoring and analyzing any network link using encryption of the payload or at the IP layer and above rather than just WLANs. In this case, Layer 1 and Layer 2 are observed and decisions made at these layers in terms of signature, protocol, policy and statistical anomaly analysis to assess network health and security. This technique is thus applicable to any network (wired or wireless) exhibiting the above encryption characteristics of the network traffic. In other words, the multi-dimensional IDS implemented per our framework is more broadly applicable to managing and securing any encrypted network. In this case, a WLAN running WEP is one particular instance of an encrypted network.
[0236] Throughout this application, various publications may have been referenced. The disclosures of these publications in their entireties are hereby incorporated by reference into this application in order to more fully describe the state of the art to which this invention pertains.
[0237] The embodiments described above are given as illustrative examples only. It will be readily appreciated by those skilled in the art that many deviations may be made from the specific embodiments disclosed in this specification without departing from the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
The invention claimed is:
1. A processor based method for monitoring use of a wireless device with respect to communications that are received at a wireless interface, the method comprising the steps of:
loading a personal wireless monitoring agent on the wireless device, wherein the wireless device comprises an authorized device on a wireless network, and wherein the personal wireless monitoring agent is configured to examine behavior on the wireless device on which it is installed;
accessing on the wireless device one or more policy guidelines through the personal wireless monitoring agent;
determining locally on the wireless device through the personal wireless monitoring agent whether a violation exists with respect to the one or more policy guidelines by analysis of the communication attributes based upon the policy guidelines, the analysis comprises using the personal wireless monitoring agent in a combination of passive monitoring and active monitoring of a wireless local area network driver of the wireless device, wherein the active monitoring comprises monitoring data, management, and control frames associated with the wireless local area network driver, the policy guidelines comprising a configurable set of activity rules related to the wireless device and authorized activity on the wireless network for the wireless device, and the determining based on wireless communication associated with the wireless device, wherein the violation comprises a deviation in communications being sent to or from the wireless device from the one or more policy guidelines;
logging any policy violations from the scanning step to a log file; and
sending the log file to a server responsive to the wireless device having an available connection to the server.
2. The method of claim 1, further comprising the step of:
sending an alert to a display associated with the wireless device responsive to a policy violation.
3. The method of claim 1, wherein the plurality of policies are defined using an extensible markup language format.
4. The method of claim 3, further comprising the step of periodically updating the plurality of policies by receiving from the server a plurality of updated policies for use in the scanning step;
wherein the plurality of updated policies are pushed from the server to a plurality of wireless devices.
5. The method of claim 1, wherein the wireless device intercepts a communication sent over the wireless network to which the wireless device is connected;
wherein the intercepted communications are analyzed for policy violations.
6. The method of claim 1, wherein the communications received at the device's wireless interface are communications originated by or provided to the wireless device.
7. The method of claim 1, further comprising the step of filtering the communications via the wireless interface to attempt to prevent a policy violation from occurring due to the communication;
wherein the filtering step comprises blocking communications in violation of the plurality of policies.
8. The method of claim 1, wherein policy violations comprise unauthorized access of the wireless network, attempts to send sensitive information, or detection of a wireless attack;
wherein an alarm is sent to the server responsive to determining that a policy violation has occurred.
9. The method of claim 1, wherein the wireless interface comprises a wireless network interface card configured to operate using one of the 802.11 standards.
10. The method of claim 1, wherein the availability of the connection to the server comprises one of the server having enough bandwidth to handle the connection to the wireless device and the wireless interface having an available wireless network to transmit the log file to the server.
11. One or more non-transitory computer readable media storing instructions that upon execution by a computer cause the computer to monitor the use of a wireless device with respect to communications that are received at a wireless interface by performing the steps of claim 1.
12. The method of claim 1, wherein the personal wireless monitoring agent on the wireless device is utilized with a plurality of additional personal wireless monitoring agent to form a distributed system.
13. The method of claim 1, further comprising:
utilizing the personal wireless monitoring agent to analyze historical wireless activity of the wireless device through checking audit files and log files on the wireless device; and
utilizing the personal wireless monitoring agent to analyze current wireless activity of the wireless device through checking registry files and configuration files on the wireless device.
14. The method of claim 1, further comprising:
operating as one of a roaming sensor and a store-and-forward sensor in a wireless intrusion detection system using the personal wireless monitoring agent.
15. A computer system having a wireless monitoring agent, the system comprising:
a wireless communication interface operable to receive and transmit communications on a wireless network on which the computer system is an authorized device;
a data store operable to store policy guidelines associated with the computer system and a log file associated with analysis of the communication attributes; and
a system processor comprising one or more processing elements, wherein the system processor is in communication with the system data store and the wireless communication interface and wherein the system processor is programmed or adapted to:
load a personal wireless monitoring agent, wherein the computer system comprises an authorized device on the wireless network, and wherein the personal wireless monitoring agent is configured to examine behavior on the computer system on which it is installed;
execute via the personal wireless monitoring agent policy analysis instructions configured to analyze communication attributes both passively and actively to determine whether a violation has occurred at the computer system based upon the policy guidelines, wherein active analysis comprises monitoring data, management, and control frames associated with an IEEE 802.11 network driver associated with the wireless communication interface;
check locally via the personal wireless monitoring agent registry, audit, log, or configuration files in the data store regarding compliance to the policy guidelines for wireless communications of the computer system; and
alert a centralized server via the wireless network based upon the analysis of communication attributes with respect to the policy guidelines;
wherein the computer system comprises one of a mobile computer system or a notebook computer.
16. The system of claim 15, wherein the log file stored in the data store;
wherein the log file that is stored in the data store is sent to the server responsive to the wireless device having an available connection to the server.
17. The system of claim 15, further comprising a display operable to communicate information to a user of the computer system, wherein the system processor is further programmed or adapted to:
determine whether an alarm should be sent to the display; and send an alarm to the display responsive to the determining step.
18. The system of claim 15, wherein the wireless device intercepts a communication sent over a wireless network to which the wireless device is connected; and
wherein the intercepted communications are analyzed for policy violations.
19. The system of claim 15, wherein the log files contain information associated with activities performed by a user of the computer system.
20. The system of claim 15, wherein the system processor is further programmed or adapted to:
periodically request an updated policy; and
replace the stored policy with the updated policy;
wherein the stored policy is defined using an extensible markup language (XML) format, thereby enabling the policy to be dynamically modified.
21. The system of claim 15, wherein the system processor is further programmed or adapted to:
filter the communications via the wireless interface to attempt to prevent a policy violation from occurring due to the communication.
22. A processor based method for monitoring use of a wireless device with respect to communications that are received at a wireless interface, the method comprising the steps of:
operating the wireless device as an authorized device on a wireless network;
installing a personal wireless monitoring agent on the wireless device, wherein the personal wireless monitoring agent is configured to examine behavior on the wireless device on which it is installed;
receiving on the wireless device for the personal wireless monitoring agent one or more policy guidelines comprising approved wireless communication attributes comprising a configurable set of activity rules for a wireless network;
accessing on the wireless device the one or more policy guidelines for the personal wireless monitoring agent;
monitoring using the personal wireless monitoring agent wireless network behavior of the wireless device through a combination of passive monitoring reviewing various configuration files and activity logs created on the wireless device and monitoring of a network driver on the wireless device to analyze IEEE 802.11 data, management, and control frames, wherein the monitoring is performed locally on the wireless device, and wherein the monitoring is based on data transmitted associated with the wireless device;
determining on the wireless device whether a violation exists with respect to the one or more policy guidelines by analysis of the communication attributes based upon the policy guidelines, wherein the violation comprises a deviation from the approved wireless communication attributes;
logging on the wireless device any policy violations from the scanning step to a log file; and
communicating the log file to an authorized user.
Patent Citations (216)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5077753(A) | 1991-12-01 | Grau, Jr. et al. | Applicant |
| US5231634(A) | 1993-07-01 | Giles et al. | Applicant |
| US5237614(A) | 1993-08-01 | Weiss | Applicant |
| US5339316(A) | 1994-08-01 | Diepstraten | Applicant |
| US5393965(A) | 1995-02-01 | Bravman et al. | Applicant |
| US5487069(A) | 1996-01-01 | O'Sullivan et al. | Applicant |
| US5577209(A) | 1996-11-01 | Boyle et al. | Applicant |
| US5646389(A) | 1997-07-01 | Bravman et al. | Applicant |
| US5666662(A) | 1997-09-01 | Shibuya | Applicant |
| US5737328(A) | 1998-04-01 | Norman et al. | Applicant |
| US5745479(A) | 1998-04-01 | Burns et al. | Applicant |
| US5745483(A) | 1998-04-01 | Nakagawa et al. | Applicant |
| US5768312(A) | 1998-06-01 | Imamura | Applicant |
| US5781857(A) | 1998-07-01 | Hwang et al. | Applicant |
| US5787077(A) | 1998-07-01 | Kuehnel et al. | Applicant |
| US5796942(A) | 1998-08-01 | Esbensen | Applicant |
| US5809060(A) | 1998-09-01 | Cafarella et al. | Applicant |
| US5825817(A) | 1998-10-01 | Tanaka et al. | Applicant |
| US5844900(A) | 1998-12-01 | Hong et al. | Applicant |
| US5866888(A) | 1999-02-01 | Bravman et al. | Applicant |
| US5870666(A) | 1999-02-01 | Tanaka et al. | Applicant |
| US5875179(A) | 1999-02-01 | Tikalsky | Applicant |
| US5896499(A) | 1999-04-01 | McKelvey | Applicant |
| US5903848(A) | 1999-05-01 | Takahashi | Applicant |
| US5913174(A) | 1999-06-01 | Casarez et al. | Applicant |
| US5919258(A) | 1999-07-01 | Kayashima et al. | Applicant |
| US5940591(A) | 1999-08-01 | Boyle et al. | Applicant |
| US5953652(A) | 1999-09-01 | Amin et al. | Applicant |
| US5987609(A) | 1999-11-01 | Hasebe | Applicant |
| US6006090(A) | 1999-12-01 | Coleman et al. | Applicant |
| US6029144(A) | 2000-02-01 | Barrett et al. | Examiner |
| US6058482(A) | 2000-05-01 | Liu | Applicant |
| US6067297(A) | 2000-05-01 | Beach | Applicant |
| US6070244(A) | 2000-05-01 | Orchier et al. | Applicant |
| US6104712(A) | 2000-08-01 | Robert et al. | Applicant |
| US6119230(A) | 2000-09-01 | Carter | Applicant |
| US6141778(A) | 2000-10-01 | Kane et al. | Applicant |
| US6145083(A) | 2000-11-01 | Shaffer et al. | Applicant |
| US6151357(A) | 2000-11-01 | Jawahar et al. | Applicant |
| US6158010(A) | 2000-12-01 | Moriconi et al. | Applicant |
| US6178512(B1) | 2001-01-01 | Fifield | Applicant |
| US6185689(B1) | 2001-02-01 | Todd, Sr. et al. | Applicant |
| US6188681(B1) | 2001-02-01 | Vesuna | Applicant |
| US6202157(B1) | 2001-03-01 | Brownlie et al. | Applicant |
| US6272129(B1) | 2001-08-01 | Dynarski et al. | Applicant |
| US6272172(B1) | 2001-08-01 | Deshpande et al. | Applicant |
| US6282546(B1) | 2001-08-01 | Gleichauf et al. | Applicant |
| US6289214(B1) | 2001-09-01 | Backstrom | Applicant |
| US6292508(B1) | 2001-09-01 | Hong et al. | Applicant |
| US6301668(B1) | 2001-10-01 | Gleichauf et al. | Applicant |
| US6301699(B1) | 2001-10-01 | Hollander et al. | Applicant |
| US6304973(B1) | 2001-10-01 | Williams | Applicant |
| US6317829(B1) | 2001-11-01 | Van Oorschot | Applicant |
| US6320948(B1) | 2001-11-01 | Heilmann et al. | Applicant |
| US6324647(B1) | 2001-11-01 | Bowman-Amuah | Applicant |
| US6324656(B1) | 2001-11-01 | Gleichauf et al. | Applicant |
| US6330244(B1) | 2001-12-01 | Swartz et al. | Applicant |
| US6363477(B1) | 2002-03-01 | Fletcher et al. | Applicant |
| US6400752(B1) | 2002-06-01 | Suzuki et al. | Applicant |
| US6404772(B1) | 2002-06-01 | Beach et al. | Applicant |
| US6411608(B2) | 2002-06-01 | Sharony | Applicant |
| US6453159(B1) | 2002-09-01 | Lewis | Applicant |
| US6453345(B2) | 2002-09-01 | Trcka et al. | Applicant |
| US6466608(B1) | 2002-10-01 | Hong et al. | Applicant |
| US6470384(B1) | 2002-10-01 | O'Brien et al. | Applicant |
| US6473449(B1) | 2002-10-01 | Cafarella et al. | Applicant |
| US6477198(B1) | 2002-11-01 | Gumm | Applicant |
| US6484029(B2) | 2002-11-01 | Hughes et al. | Applicant |
| US6487666(B1) | 2002-11-01 | Shanklin et al. | Applicant |
| US6499107(B1) | 2002-12-01 | Gleichauf et al. | Applicant |
| US6501951(B2) | 2002-12-01 | Moore | Applicant |
| US6507864(B1) | 2003-01-01 | Klein et al. | Applicant |
| US6522689(B1) | 2003-02-01 | Heinrich | Applicant |
| US6539207(B1) | 2003-03-01 | del Castillo et al. | Applicant |
| US6539428(B2) | 2003-03-01 | Davies | Applicant |
| US6567859(B1) | 2003-05-01 | Yang et al. | Applicant |
| US6674403(B2) | 2004-01-01 | Gray et al. | Applicant |
| US6697337(B1) | 2004-02-01 | Cafarelli et al. | Applicant |
| US6735701(B1) | 2004-05-01 | Jacobson | Examiner |
| US6745333(B1) | 2004-06-01 | Thomsen | Applicant |
| US6751752(B1) | 2004-06-01 | Smith | Examiner |
| US6799047(B1) | 2004-09-01 | Bahl et al. | Applicant |
| US6874089(B2) | 2005-03-01 | Dick et al. | Applicant |
| US6910135(B1) | 2005-06-01 | Grainger | Applicant |
| US6934298(B2) | 2005-08-01 | Bentley | Applicant |
| US7356545(B2) | 2008-04-01 | Muralidharan et al. | Examiner |
| US7397770(B2) | 2008-07-01 | Le et al. | Examiner |
| US7702775(B2) | 2010-04-01 | Kuan et al. | Examiner |
| US7778606(B2) | 2010-08-01 | Ammon et al. | Examiner |
| US7839432(B2) | 2010-11-01 | Fernandez et al. | Examiner |
| US7853250(B2) | 2010-12-01 | Harvey et al. | Examiner |
| US7917938(B2) | 2011-03-01 | Jacobson | Examiner |
| US7924717(B2) | 2011-04-01 | Narasimhan | Examiner |
| US8001594(B2) | 2011-08-01 | Heintz et al. | Examiner |
| US8064927(B2) | 2011-11-01 | Hsu et al. | Examiner |
| US8069483(B1) | 2011-11-01 | Matlock | Examiner |
| US8111645(B2) | 2012-02-01 | Proctor et al. | Examiner |
| US2001/0027107(A1) | 2001-10-01 | Shinozaki et al. | Applicant |
| US2001/0030956(A1) | 2001-10-01 | Chillariga et al. | Applicant |
| US2001/0038626(A1) | 2001-11-01 | Dynarski et al. | Applicant |
| US2001/0039579(A1) | 2001-11-01 | Trcka et al. | Applicant |
| US2002/0010798(A1) | 2002-01-01 | Ben-Shaul et al. | Examiner |
| US2002/0021745(A1) | 2002-02-01 | Negus | Applicant |
| US2002/0029288(A1) | 2002-03-01 | Dobbins et al. | Applicant |
| US2002/0032871(A1) | 2002-03-01 | Malan et al. | Applicant |
| US2002/0035699(A1) | 2002-03-01 | Crosbie | Applicant |
| US2002/0044533(A1) | 2002-04-01 | Bahl et al. | Applicant |
| US2002/0059434(A1) | 2002-05-01 | Karaoguz et al. | Applicant |
| US2002/0060994(A1) | 2002-05-01 | Kovacs et al. | Applicant |
| US2002/0060995(A1) | 2002-05-01 | Cervello et al. | Applicant |
| US2002/0061031(A1) | 2002-05-01 | Sugar et al. | Applicant |
| US2002/0066034(A1) | 2002-05-01 | Schlossberg et al. | Applicant |
| US2002/0072329(A1) | 2002-06-01 | Bandeira et al. | Applicant |
| US2002/0083343(A1) | 2002-06-01 | Crosbie et al. | Applicant |
| US2002/0083344(A1) | 2002-06-01 | Vairavan | Examiner |
| US2002/0087882(A1) | 2002-07-01 | Schneier et al. | Applicant |
| US2002/0090089(A1) | 2002-07-01 | Branigan et al. | Applicant |
| US2002/0090952(A1) | 2002-07-01 | Cantwell | Applicant |
| US2002/0094777(A1) | 2002-07-01 | Cannon et al. | Applicant |
| US2002/0101837(A1) | 2002-08-01 | Bender et al. | Applicant |
| US2002/0112047(A1) | 2002-08-01 | Kushwaha et al. | Applicant |
| US2002/0112185(A1) | 2002-08-01 | Hodges | Applicant |
| US2002/0129138(A1) | 2002-09-01 | Carter | Applicant |
| US2002/0138755(A1) | 2002-09-01 | Ko | Applicant |
| US2002/0144135(A1) | 2002-10-01 | Langford et al. | Examiner |
| US2002/0147920(A1) | 2002-10-01 | Mauro | Applicant |
| US2002/0160769(A1) | 2002-10-01 | Gray | Applicant |
| US2002/0161755(A1) | 2002-10-01 | Moriarty | Applicant |
| US2002/0174364(A1) | 2002-11-01 | Nordman et al. | Applicant |
| US2002/0176437(A1) | 2002-11-01 | Busch et al. | Applicant |
| US2002/0178383(A1) | 2002-11-01 | Hrabik et al. | Applicant |
| US2002/0181417(A1) | 2002-12-01 | Malhotra et al. | Applicant |
| US2003/0009696(A1) | 2003-01-01 | Bunker V et al. | Applicant |
| US2003/0021254(A1) | 2003-01-01 | Fukuda | Applicant |
| US2003/0026198(A1) | 2003-02-01 | Diepstraten et al. | Applicant |
| US2003/0027550(A1) | 2003-02-01 | Rockwell | Applicant |
| US2003/0036404(A1) | 2003-02-01 | Adachi et al. | Applicant |
| US2003/0048770(A1) | 2003-03-01 | Proctor, Jr. | Applicant |
| US2003/0060207(A1) | 2003-03-01 | Sugaya et al. | Applicant |
| US2003/0061344(A1) | 2003-03-01 | Monroe | Applicant |
| US2003/0061506(A1) | 2003-03-01 | Cooper et al. | Applicant |
| US2003/0063592(A1) | 2003-04-01 | Seki et al. | Applicant |
| US2003/0064720(A1) | 2003-04-01 | Valins et al. | Applicant |
| US2003/0065934(A1) | 2003-04-01 | Angelo et al. | Applicant |
| US2003/0067884(A1) | 2003-04-01 | Abler et al. | Applicant |
| US2003/0070084(A1) | 2003-04-01 | Satomaa et al. | Applicant |
| US2003/0084323(A1) | 2003-05-01 | Gales | Applicant |
| US2003/0088789(A1) | 2003-05-01 | Fenton et al. | Applicant |
| US2003/0095520(A1) | 2003-05-01 | Aalbers et al. | Applicant |
| US2003/0096577(A1) | 2003-05-01 | Heinonen et al. | Applicant |
| US2003/0096607(A1) | 2003-05-01 | Taylor | Applicant |
| US2003/0100308(A1) | 2003-05-01 | Rusch | Applicant |
| US2003/0105976(A1) | 2003-06-01 | Copeland, III | Applicant |
| US2003/0108016(A1) | 2003-06-01 | Bonta | Applicant |
| US2003/0110398(A1) | 2003-06-01 | Dacier et al. | Applicant |
| US2003/0117966(A1) | 2003-06-01 | Chen | Applicant |
| US2003/0117985(A1) | 2003-06-01 | Fujii et al. | Applicant |
| US2003/0117986(A1) | 2003-06-01 | Thermond et al. | Applicant |
| US2003/0119526(A1) | 2003-06-01 | Edge | Applicant |
| US2003/0120821(A1) | 2003-06-01 | Thermond et al. | Applicant |
| US2003/0123420(A1) | 2003-07-01 | Sherlock | Applicant |
| US2003/0125035(A1) | 2003-07-01 | Khafizov et al. | Applicant |
| US2003/0126258(A1) | 2003-07-01 | Conkright et al. | Applicant |
| US2003/0135638(A1) | 2003-07-01 | Brabson et al. | Examiner |
| US2003/0135762(A1) | 2003-07-01 | Macaulay | Examiner |
| US2003/0140246(A1) | 2003-07-01 | Kammer et al. | Applicant |
| US2003/0149888(A1) | 2003-08-01 | Yadav | Examiner |
| US2003/0161341(A1) | 2003-08-01 | Wu et al. | Applicant |
| US2003/0174680(A1) | 2003-09-01 | Kuan et al. | Applicant |
| US2003/0185244(A1) | 2003-10-01 | Wu et al. | Examiner |
| US2003/0189908(A1) | 2003-10-01 | Kuan et al. | Examiner |
| US2003/0192055(A1) | 2003-10-01 | Aoki et al. | Applicant |
| US2003/0196115(A1) | 2003-10-01 | Karp | Applicant |
| US2003/0200455(A1) | 2003-10-01 | Wu | Applicant |
| US2003/0212812(A1) | 2003-11-01 | Wang et al. | Applicant |
| US2003/0217283(A1) | 2003-11-01 | Hrastar et al. | Examiner |
| US2003/0217289(A1) | 2003-11-01 | Ammon et al. | Examiner |
| US2003/0219008(A1) | 2003-11-01 | Hrastar | Examiner |
| US2003/0221006(A1) | 2003-11-01 | Kuan et al. | Examiner |
| US2003/0224797(A1) | 2003-12-01 | Kuan et al. | Examiner |
| US2003/0229808(A1) | 2003-12-01 | Heintz et al. | Examiner |
| US2003/0233567(A1) | 2003-12-01 | Lynn et al. | Examiner |
| US2003/0236990(A1) | 2003-12-01 | Hrastar et al. | Examiner |
| US2004/0003285(A1) | 2004-01-01 | Whelan et al. | Applicant |
| US2004/0068668(A1) | 2004-04-01 | Lor et al. | Applicant |
| US2004/0078598(A1) | 2004-04-01 | Barber et al. | Applicant |
| US2004/0102192(A1) | 2004-05-01 | Serceki | Applicant |
| US2004/0103307(A1) | 2004-05-01 | Raphaeli et al. | Applicant |
| US2004/0107219(A1) | 2004-06-01 | Rosenberger | Applicant |
| US2004/0111643(A1) | 2004-06-01 | Farmer | Examiner |
| US2004/0136318(A1) | 2004-07-01 | Bentley | Applicant |
| US2004/0162995(A1) | 2004-08-01 | Muaddi et al. | Applicant |
| US2004/0165563(A1) | 2004-08-01 | Hsu et al. | Examiner |
| US2004/0176024(A1) | 2004-09-01 | Hsu et al. | Examiner |
| US2004/0198392(A1) | 2004-10-01 | Harvey et al. | Examiner |
| US2004/0203764(A1) | 2004-10-01 | Hrastar et al. | Examiner |
| US2005/0141447(A1) | 2005-06-01 | Carlton et al. | Examiner |
| US2005/0181785(A1) | 2005-08-01 | Chen et al. | Examiner |
| US2005/0195753(A1) | 2005-09-01 | Chaskar et al. | Examiner |
| US2005/0213553(A1) | 2005-09-01 | Wang | Examiner |
| US2005/0254474(A1) | 2005-11-01 | Iyer et al. | Examiner |
| US2005/0272445(A1) | 2005-12-01 | Zellner | Examiner |
| US2006/0099965(A1) | 2006-05-01 | Aaron | Examiner |
| US2006/0150250(A1) | 2006-07-01 | Lee et al. | Examiner |
| US2006/0236363(A1) | 2006-10-01 | Heard et al. | Examiner |
| WO98/59428 | 1998-12-01 | Applicant | |
| WO1/43467(A1) | 2001-06-01 | Applicant | |
| WO2/058346(A2) | 2002-07-01 | Applicant | |
| WO2/058346(A3) | 2002-07-01 | Applicant | |
| WO2/097560(A2) | 2002-12-01 | Applicant | |
| WO3/021851 | 2003-03-01 | Applicant | |
| WO3/079708(A1) | 2003-09-01 | Applicant | |
| WO3/084255(A1) | 2003-10-01 | Applicant | |
| WO3/085544(A1) | 2003-10-01 | Applicant | |
| WO3/088547(A2) | 2003-10-01 | Applicant | |
| WO3/088687 | 2003-10-01 | Applicant |
Non-Patent Literature (18)
- WildPackets. “AiroPeek Technical Specifications”. Apr. 2004. Available at http://web.archive.org/web/20040405092711/www.wildpackets.com/elements/AiroPeek—TechSpecs.pdf. Downloaded Aug. 28, 2009.Examiner
- Anne Saita. “Hot Pick: AirDefense”. Information Security. Jul. 2002. Available at http://www.airdefense.net/newsandpress/InfoSecMag.pdf. Downloaded Apr. 21, 2011.Examiner
- Distributed Wireless Security Auditor, IBM Research http://www.research.ibm.com/gsal/dwsa/ (Accessed: Apr. 10, 2003).Applicant
- IBM Debuts First Self-Diagnostic Wireless Security Tool on Linux, LWN.NET, (Date Alleged: Jun. 17, 2002) http://www.lwn.net/Articles/2661 (Accessed: Apr. 10, 2003).Applicant
- IBM extends its Wireless Security Auditor with more autonomic features, Serverworld: Online News (Date Alleged: Jun. 2002) http://www.serverworldmagazine.com/newsflash2/2002/06/19—ibmdwsa.shtml (Accessed: Apr. 10, 2003).Applicant
- IBM initiative addresses wireless security, M2 Preswire (Date alleged: Oct. 9, 2001) http://www.lexis.com/research (Accessed: Apr. 10, 2003).Applicant
- IBM Research's Wireless Security Auditor One-Step Ahead of Hackers, MOBILEINFO.COM , Issue 2001-30 (Date Alleged: Jul. 2001) (Alleged Update: Jul. 25, 2001) http://www.mobileinfo.com/News—2001/Issue30/IBM—Auditor.htm (Accessed from Google's cache: Apr. 10, 2003).Applicant
- IBM unlocks wireless security services, IT WORLD.COM (Date Alleged: Oct. 9, 2001) http://www.itworld.com/Net/2629/IDG011009IBMsecurity (Accessed from Google's cache: Apr. 10, 2003.Applicant
- Losi, Stephanie, IBM Steps Up Wireless Security, Newsfactor Network (Date Alleged: Oct. 8, 2001) http://www.newsfactor.com/perl/story/14012.html (Accessed: Apr. 10, 2003).Applicant
- Lough, Daniel et al., “A Short Tutorial on Wireless LANs and IEEE 802.11” printed on May 27, 2002 in the IEEE Computer Society's Student Newsletter, Summer 1997, vol. 5, No. 2.Applicant
- Manecksha, Ferina, IBM to focus on “Think” strategy, News Straits Times—Management Times (Date Alleged: Jan. 30, 2003) http://www.lexis.com/research (Accessed: Apr. 10, 2003).Applicant
- Morochove, Richard, Why Dell lets competitors do the heavy lifting, Toronto Star (Date Alleged: Nov. 11, 2002) http://www.lexis.com/research (Accessed: Apr. 10, 2003).Applicant
- Schwartz, Ephraim, IBM Offers a Peek at Self-Healing PCS: Autonomic computing initiative will lead to self-configuring desktops and notebooks and greater wireless security. (Date Alleged: Nov. 19, 2002) http://www.pcworld.com/resource/printable/article/0,aid,107069.asp (Accessed from Google's cache: Apr. 10, 2003).Applicant
- Schwartz, Ephraim, IBM unveils autonomic computing on notebooks, desktops, Inforworld Daily News (Dated Alleged: Nov. 19, 2002) http://www.lexis.com/research (Accessed: Apr. 10, 2003).Applicant
- Toomgum, Sirvish, “Think” Big Blue, Nation, Worldsources, Inc. (Date Alleged: Nov. 19, 2002) http://www.lexis.com/research (Accessed: Apr. 10, 2003).Applicant
- WhereLAN Location Sensor Locating Access Point, Wherenet U.S.A. (2002).Applicant
- Wireless Security Auditor (WSA), IBM Security Research http://www.research.ibm.com/gsal/wsa/ (Accessed: Apr. 10, 2003).Applicant
- Non Final Office Action for U.S. Appl. No. 11/342,021 mailed Feb. 20, 2009, a continuation-in-part of U.S. Appl. No. 11/253,316.Applicant