Rogue Device Details Test
A rogue device is an unauthorized device that is connected to an organization's network but does not have permission to access and operate in the network. The rogue devices can be broken down into two categories:
- Access point (AP) -based rogue devices - Wireless access points (WAP) installed in the network without authorization
- Computer-based rogue threats, or rogue peers - end user computers that are connected to the network without permission
The rogue device can impose significant threats to the network and is able to create a conduit for theft of confidential system information. The rogue device potentially allows unchallenged access to the network by any wireless user or client in the physical vicinity and also floods the network with useless data. This way, the rogue devices undermine the security of the network, create a denial of service to the authorized users and potentially damage the organization. It is, therefore, vital for administrator to detect and control the rogue devices connected to the network before they cause serious damage to the network. This is where the Rogue Device Details test helps administrator!
For each rogue device connected to the network, this test reveals the radio type, the number of channels associated with it, the type of device, the encryption mode and strength of the signals.
Target of the test : A Ruckus ZoneDirector
Agent deploying the test : An external agent
Outputs of the test : One set of results for each rogue device that accesses the network in an unauthorized way
| Parameters | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The host for which the test is to be configured. |
|
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; the default is 161. |
|
SNMPversion |
By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list. |
|
SNMPCommunity |
The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the snmpversion chosen is v3, then this parameter will not appear. |
|
Username |
This parameter appears only when v3 is selected as the SNMPversion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. |
|
Context |
This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box. By default, this parameter is set to none. |
|
Authpass |
Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3. |
|
Confirm password |
Confirm the Authpass by retyping it here. |
|
Authtype |
This parameter too appears only if v3 is selected as the SNMPversion. From the Authtype list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:
|
|
Encryptflag |
This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. |
|
Encrypttype |
If this Encryptflag is set to Yes, then you will have to mention the encryption type by selecting an option from the Encrypttype list. SNMP v3 supports the following encryption types:
|
|
Encryptpassword |
Specify the encryption password here. |
|
Confirm Password |
Confirm the encryption password by retyping it here. |
|
Timeout |
Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds. |
|
Data Over TCP |
By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Radio type |
Indicates the radio type of this rogue device. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the Radio type of this rogue device. The graph of this measure however, represents the type of a rogue device using the numeric equivalents only - 0 and 3. |
||||||||||
|
Channel |
Indicates the number of channels associated with this rogue device. |
Number |
|
||||||||||
|
Rogue type |
Indicates the type of this rogue device. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the type of this rogue device. The graph of this measure however, represents the type of a rogue device using the numeric equivalents only - 1 and 2. |
||||||||||
|
Encryption mode |
Indicates the encryption mode of this rogue device. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the encryption mode of this rogue device. The graph of this measure however, represents the encryption mode of a rogue device using the numeric equivalents only - 0 and 1. |
||||||||||
|
Signal strength |
Indicates the signal strength of this rogue device. |
dBm_negative |
Ideally, the value of this measure should be low. |
