The invention relates generally to computer networking, and more specifically, to an access point that also performs surveillance on a network.
Wireless computing technologies provide untethered access to the Internet and other networks. One of the most critical technologies for wireless networking (or Wi-Fi) is the IEEE 802.11 family of protocols promulgated by the Institute of Electrical and Electronics Engineers. Currently, the protocols are widely adopted in wireless devices such as laptop computers, tablet computers, smart phones, and network appliances.
Typically, access points provide a port for wireless devices to access a network. At a business, several access points can be spread around a geographical region so that employees have Internet access as they travel around to different meeting rooms and even different buildings on a campus. Sometimes, rogue access points are placed in the network by unscrupulous people, or even an employee without any intent for harm. The rogue access points present vulnerabilities to the network because the access points may not be in conformity with a security policy of the network. For example, the access point may not require a password for connections, thereby allowing undesirable accesses to the network.
Currently, network administrators have difficulty in monitoring against rogue devices. One solution is to physically walk around the geographical region checking for signals from rogue access points. However, rogue access points can be powered up for malicious activity, and then powered down until needed again. This makes random walk-throughs ineffective in consistent monitoring. Another solution is to deploy a dedicated device for constant monitoring of rogue access points. Problematically, the dedicated device can only monitor a portion of large geographical areas. Effective monitoring can drastically increase costs because multiple stationary monitors may be needed to cover the entire geographical area.
What is needed is a robust technique to monitor for rogue access points and other anomalous devices without the physical effort or expense drawbacks, as described.
To meet the above-described needs, methods, computer program products, and systems for channel surveillance of anomalous devices in an access point.
An access point switches between an access point mode and a surveillance mode. In the access point mode, the access point provides network access for end stations using a BSSID (Basic Service Set Identifier) while in the access point mode. In surveillance mode, the access point scans one or more channels of the wireless network to identify one or more anomalous devices. A group of access points can take turns leaving an RF blanket of connectivity for mobile stations to temporarily perform scanning.
In one embodiment, the access point switches from the access point to the surveillance mode responsive to a first condition, and switches back responsive to a second condition. The conditions can be predetermined time intervals, network loads and the like. In preparation to leave access point mode, the access mode hands-off one or more connected end stations to a second access point as directed by a controller. The mobile stations can maintain the same BSSID at the second access point, thereby making the mobile stations unaware of the hand-off.
Advantageously, an access point can protect a wireless network against anomalous devices without disturbing continuous access to an RF blanket.
In the following drawings, like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.
Methods, computer program products, and systems for surveillance of anomalous devices in an access point are disclosed.
The managed access points 110A-N can be any computing devices, such as a personal computer, a server blade, or any computing environment as shown in
A rogue access point 120 can be a similar device to the managed access points 110A-N. One main difference is that the rogue access point 120 is not authorized for a wireless network by, for example, a network administrator. Consequentially, the rogue access point 120 may be operating out of conformity with the managed access points 110A-N and network security policies enforced on and by them. For example, the rogue access point 120 may not require the same login credentials or may not limit bandwidth usage in conformity with network policy. In
The mobile stations 130A-B can be, for example, a personal computer, laptop computer, tablet computer, smart phone, mobile computing device, Internet appliance, end station or any other computing device as described in
As an option, controller 140 in the network architecture is in communication with each of multiple access points 120A-C (e.g., the Meru MC6000 Controller by Meru Networks of Sunnyvale, Calif.). As a result, the controller 140 can manage the access point and assist in network services such as virtual cell and virtual port while access points are in access point mode, as described below. The controller 140 can also assist in identifying anomalous devices while access points are in surveillance mode.
The access point module 112 provides access point services to mobile stations. In some embodiments, the access point module 112 can maintain a list of BSSIDs (Basic Service Set Identifiers) and corresponding mobile stations. When the mobile stations transmit information to and receive information from the wireless network, the access point module 112 handles the retransmission of packets. The access point module 112 can operate in conjunction with a controller with respect to BSSID assignments for virtual cell and/or virtual port services.
The surveillance module 114 scans an RF blanket for anomalous devices. Exemplary anomalous devices include rogue devices and non-mobile stations. The surveillance module 114 can operate in conjunction with a controller to identify anomalous devices.
The mode switch 115 executes switches between the access point module 112 and the surveillance module 114. The access point mode can be a default mode. Responsive to a first condition, the mode switch 112 reconfigures control of radios, and responsive to a second condition, returns to the default mode. The conditions are implementation-specific, but can trigger a change due to a preconfigured period of time, a rolling sequence of access points, an command from a network administrator, and the like.
The operating system 116 can be a general operating system, or a streamlined operating system for access pint such as System Director OS by Meru Networks of Sunnyvale, Calif. The operating system 116 generally interfaces between the software and hardware of the access point 110. The operating system 116 can also include integrated applications, such as the access point module 112, the surveillance module 114 and the mode switch 115.
The radio array/connection ports 118 represent physical access to communication channels or mediums. A radio array can include one or more transmit (Tx) and receive (Rx) antennas for communication with the physical layer. Some mobile stations 110 include separate antennae for IEEE 802.11a, IEEE 802.11b, IEEE 802.11n, and IEEE 802.11 ac. Other mobile stations 110 include several antenna dedicated for separate transmit and receive paths using the MIMO functionality of IEEE 802.11ac. Antennae can be tuned for IEEE 802.11 transmissions. An Ethernet port can allow plug-in connections to a wired medium using a RJ-45 jack, or the like.
At step 210, in an access point mode, the access point provides network services to mobile stations. In some embodiments, the access point provides virtual cell and virtual port services. In general, the virtual cell service maintains a BSSID assigned to a mobile statin across different access points in an RF blanket. Meanwhile, the virtual port service assigns a unique BSSID to a mobile station to allow a controller to manage the mobile station. While performing surveillance, it is the virtual cell and virtual port architectures allow a wireless network to continue providing services to mobile stations that remain substantially unaware of any change. These network services are described in more detail in association with
At step 220, the process waits until a first condition is detected. The first condition can be one or more conditions, and is implementation-specific. In a first embodiment, scans can occur periodically after a predetermined duration of time. In another embodiment, a specific threat detection, or evidence that suggestive anomalous device connections triggers the scan. In yet another embodiment, an access point determines that a switch can be made without disruption (or with minimal disruption) to the RF blanket used by mobile stations.
At step 230, in response to detecting a first condition, the access point hands-off mobile stations that are currently connected. The technique is sometimes referred to as a ‘soft’ hand-off because mobile stations may be unaware of any change. Specifically, the BSSID associated with an access point that is switching to surveillance mode can be reassigned to another access point within range, for example, by a controller. Without the soft hand-off, a mobile station that has been dropped by an access point has to respond to a beacon, with a new BSSID, to configure a new connection.
At step 240, the access point switches from the access point mode to a surveillance mode. Once the access point has redistributed a load for the access point mode, it is free to change modes without disruption of services. To switch, control of the access point radios are associated with the surveillance module for its purposes.
At step 250, the access point scans channels of the network for anomalous devices. The radios can be tuned to the same channels utilized in the access point mode, in addition to others. In a preferred embodiment, the access point scans for rogue devices and for non-mobile stations. Of course, any type of anomalous device can be searched, depending on the implementation. Remediation action can be taken against detected anomalous devices. In some embodiments, remediation can occur while still in surveillance mode. If the anomalous device is harmful to the wireless network as a whole, it can be eradicated by removing an associated connection. If the anomalous device is not appropriate for the connected access point, the device can be handed-off to another access point. For example, a stationary station can be moved to an access point having a shorter flight time, or be reassigned to a different BBSID.
At step 260, responsive to detecting a second condition, the access point switches back from the surveillance mode to an access point mode at step 270. The second condition triggers the end of scanning. Example conditions include the end of a preconfigured time period for scanning, successful identification and eradication of all anomalous devices, notification that a neighboring access point is entering surveillance mode and needs to hand-off mobile station, and the like. Ultimately, control of the radios is changed back to an access point module from a surveillance module.
At step 280, the access point mode switches from the surveillance mode to the access point mode. As such, control of the access point radios is switched back to the access point module.
At step 310, a group of access points provide an RF blanket for connection by mobile stations. A collective range of radios from the access points not only allow connections, but maintain continuous connections as mobile stations are in transit across the RF blanket.
At step 320, assigning a BSSID to a mobile point that is persistent across different access points a virtual cell of the RF blanket. The BSSID can be shared among one or more mobile stations, and more importantly, is shared among access points. As a result, a mobile station moving out-of-range for a first access point and in-range for a second access point can be handed-off between the access points. To do so, a controller pulls the BSSID from the first access point and reassigns the BSSID to the second access points. Although more than one access point may receive transmissions to a BSSID, only the access point assigned to the BSSID by the controller will respond.
At step 330, assigning a BSSID to an end point that is unique to the end point in virtual port of the RF blanket. The BSSIDs are managed by a controller, as far as the type of services offered. For example, a controller can allow unlimited uplink access for one BSSID and minimal uplink access for a second BSSID. As with virtual cell, the virtual port is transported around the RF blanked through updated assignments to access points.
At step 410, an access point listens for beacons from rogue access points for comparison against known access points. In accordance with IEEE 802.11 standards, an access point advertises its presence with beacon frames broadcast at periodic intervals. The beacon frames include a BSSID associated with an access point. The BSSID can be compared against a list of BSSIDs from managed access points that are trusted to operate in a wireless network. In one embodiment, a controller in communication with access points on the wireless network provides a list of valid access points to an access point for comparison, or performs the comparison at the controller.
At step 420, the access point sends probe requests over different channels. Rather than passive listening, the access point actively elicits a probe response from rogue access points. In response to probe requests, access points within range send a probe response frame which includes a BSSID. As described above, the BSSID can be compared against a list of known BSSID for the wireless network.
At step 430, the access point listens to transmission traffic from rogue access points. By scanning channels across the spectrum, the access point can listen to communication exchanges taking place by rogue access point and rogue mobile stations connected thereto. Although wireless packets have a specific destination, as indicated by a destination address field, the packet is propagated among an entire range of a transmitting radio. As a result, any receiving radio within range of the transmitting radio can pick up the transmission for analysis. As with the beacon comparison, source and destination addresses of observed communication packets can be compared against known source and destination addresses.
At step 440, the access point determines which stations are non-mobile. Some services provided to mobile station, such as virtual cell and virtual port, can cost additional overhead that is not necessary for a non-mobile station. The station can be temporarily non-mobile (e.g., a mobile station that is stationary for some time), or permanently mobile (e.g., a desktop personal computer). Various techniques can analyze mobility. For example, RSSI can be measured for communications to determine whether flight time remains the same.
The computing device 500, of the present embodiment, includes a memory 510, a processor 520, a storage device 530, and an I/O port 540. Each of the components is coupled for electronic communication via a bus 599. Communication can be digital and/or analog, and use any suitable protocol.
The memory 510 further comprises network applications 512 and an operating system 514. The network applications 520 can include the programs that use network services, a web browser, a mobile application, an application that uses networking, a remote application executing locally, a network protocol application, a network management application, a network routing application, or the like.
The operating system 514 can be one of the Microsoft Windows® family of operating systems (e.g., Windows 95, 98, Me, Windows NT, Windows 2000, Windows XP, Windows XP x64 Edition, Windows Vista, Windows CE, Windows Mobile), Linux, HP-UX, UNIX, Sun OS, Solaris, Mac OS X, Alpha OS, AIX, IRIX32, or IRIX64. Other operating systems may be used. Microsoft Windows is a trademark of Microsoft Corporation.
The processor 520 can be a network processor (e.g., optimized for IEEE 802.11), a general purpose processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a reduced instruction set controller (RISC) processor, an integrated circuit, or the like. Qualcomm Atheros, Broadcom Corporation, and Marvell Semiconductors manufacture processors that are optimized for IEEE 802.11 devices. The processor 520 can be single core, multiple core, or include more than one processing elements. The processor 520 can be disposed on silicon or any other suitable material. The processor 520 can receive and execute instructions and data stored in the memory 510 or the hard drive 530.
The storage device 530 can be any non-volatile type of storage such as a magnetic disc, EEPROM, Flash, or the like. The storage device 530 stores code and data for applications, firmware, and the like.
The I/O port 540 further comprises a user interface 542 and a network interface 544. The user interface 542 can output to a display device and receive input from, for example, a keyboard. The network interface5 connects to a medium such as Ethernet or Wi-Fi for data input and output. In one embodiment, the network interface 544 includes IEEE 802.11 antennae.
Many of the functionalities described herein can be implemented with computer software, computer hardware, or a combination.
Computer software products (e.g., non-transitory computer products storing source code) may be written in any of various suitable programming languages, such as C, C++, C#, Java, JavaScript, PHP, Python, Perl, Ruby, and AJAX. The computer software product may be an independent application with data input and data display modules. Alternatively, the computer software products may be classes that are instantiated as distributed objects. The computer software products may also be component software such as Java Beans (from Sun Microsystems) or Enterprise Java Beans (EJB from Sun Microsystems).
Furthermore, the computer that is running the previously mentioned computer software may be connected to a network and may interface to other computers using this network. The network may be on an intranet or the Internet, among others. The network may be a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system of the invention using a wireless network using a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11n, and 802.ac, just to name a few examples). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.
In an embodiment, with a Web browser executing on a computer workstation system, a user accesses a system on the World Wide Web (WWW) through a network such as the Internet. The Web browser is used to download web pages or other content in various formats including HTML, XML, text, PDF, and postscript, and may be used to upload information to other parts of the system. The Web browser may use uniform resource identifiers (URLs) to identify resources on the Web and hypertext transfer protocol (HTTP) in transferring files on the Web.
This description of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form described, and many modifications and variations are possible in light of the teaching above. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications. This description will enable others skilled in the art to best utilize and practice the invention in various embodiments and with various modifications as are suited to a particular use. The scope of the invention is defined by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
20060153138 | Asoh et al. | Jul 2006 | A1 |
20070049323 | Wang et al. | Mar 2007 | A1 |
20070298720 | Wolman et al. | Dec 2007 | A1 |
20080002651 | Nakano | Jan 2008 | A1 |
20080151844 | Tiwari | Jun 2008 | A1 |
20080186932 | Do et al. | Aug 2008 | A1 |
20090235354 | Gray et al. | Sep 2009 | A1 |
20110083165 | Gopinath et al. | Apr 2011 | A1 |
20110131651 | Shanmugavadivel et al. | Jun 2011 | A1 |
20110258681 | Iyer et al. | Oct 2011 | A1 |
20120052876 | Anderson et al. | Mar 2012 | A1 |
20120134272 | Vempati et al. | May 2012 | A1 |
20140118113 | Kaushik et al. | May 2014 | A1 |
Number | Date | Country | |
---|---|---|---|
20140301363 A1 | Oct 2014 | US |