RSA Authentications Test
Using the unique multi-factor authentication, the RSA Authentication Manager verifies security pins, security tokens and the user’s identity for servicing authentication requests. This way, the RSA Authentication Manager guarantees that only authorized users are granted permission to access the enterprise's network.
If the RSA Authentication Manager is rendered unavailable for a while or is unable to process authentications owing to an overload condition or network malfunction, then, the authentication failure may increase rapidly. This may in turn may stall operations of the RSA Authentication Manager and lead to unauthorized user access on the enterprise's network exposing critical data. Added to this, valid users may also be denied access. Authentication failures may directly impact the security of the enterprise's network which leads to data loss and may pave way for malicious attacks on the enterprise's network. To avert such issues, administrators should continuously track the authentications processed by the RSA Authentication Manager, and capture abnormalities before users start complaining. The RSA Authentications test helps the administrators in this regard!
This test accurately pinpoints the total number of authentications processed by the RSA Authentication Manager, and the number of authentications that were processed successfully and those that failed. In addition, this test also reports the number of new PIN authentications and security token authentications that were processed.
Target of the test : A RSA Authentication Manager
Agent deploying the test : An external agent
Outputs of the test : One set of results for the RSA Authentication Manager being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the specified host listens. By default, this is NULL. |
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; The default value 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 the 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. |
Engine ID |
This parameter appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Total authentication |
Indicates the total number of authentications that were processed during the last measurement period. |
Number |
A high value of this measure could indicate a potential overload condition. |
Successful authentication |
Indicates the number of authentications that were processed successfully during the last measurement period. |
Number |
A high value is desired for this measure. |
Failed authentication |
Indicates the number of authentications that failed during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. A non-zero value for this measure is a cause of concern and requires further investigation. |
Failure authentication pct |
Indicates the percentage of authentications that failed on the target RSA Authentication Manager. |
Percent |
|
New pin authentication |
Indicates the number of new PIN authentications that were processed during the last measurement period. |
Number |
|
Next token code authentication |
Indicates the number of token code authentications that were processed during the last measurement period. |
Number |
|