About the Device
RSA Authentication Manager: The central two-factor authentication software that provides capabilities to manage security tokens, users, multiple applications, agents, and resources across physical sites. Authentication Manager verifies authentication requests and centrally administers authentication policies for enterprise networks. RSA AM leverages RSA Secure ID for 2 factor authentication, On Demand authentication which sends authentication credentials over email and SMS, Risk Based Authentication which silently observes user behavior of authentication and bind devices accordingly with a specific user. Any deviation, result into an extra level of authentication which can be Security questions or on demand authentication.
Device Information
Entity | Particulars |
|---|---|
Vendor Name | RSA |
Product Name | Authentication Manager |
Type of Device | Hosted |
Collection Method
Log Type | Ingestion label | Preferred Logging Protocol - Format | Log collection method |
|---|---|---|---|
RSA | RSA_AUTH_MANAGER | Syslog-CSV | CyberHub |
Port Requirements
Source | Destination | Port |
|---|---|---|
RSA Authentication Manager | CyberHub | 514 (UDP) |
Device Configuration
Log in to RSA security console as administrator.
Navigate to Set Up and select System Settings
In Basic Settings, select Logging
Click Select Instance, select the Primary instance type configured in your environment. There can be replica instances available for failover but need to select primary for log collection. Once done click Next
In Configure settings, you will find 3 sections to configure logs.
a) Log Levels Section: Please find below the default setting for log levels as per defined by RSA. We recommend configuring the same level of logging. Changing the settings might block some important logs to be sent to Chronicle for security analysis.
Log | Default Setting |
|---|---|
Trace Log | Fatal |
Administrative Audit Log | Success |
Runtime Audit Log | Success |
System Log | Warning |
To understand the level of logging defined please refer Help section on the same page and check section Log Configuration Parameters. It contains the meaning of all levels assigned. For analysis, Administrative Audit and Runtime Audit are of most importance.
We are not supporting Trace Logs as these are logs which are used by RSA Support in case of any device crash or any other application specific issue. It is recommended to never use Verbose as logging level as it consumes a lot of device space.
b) Log Data Destination: For all the three types of log level data select Save to Internal database and Remote Syslog in the following Hostname or IP Address. Specify the IP address of Cyberhub machine.
Syslog messages are pushed over port 514 UDP only. No explicit port definition is required. We can collect logs just by configuring Syslog sensor listening on port 514. Please do not select first 2 options for any if the Logs as it would not send the data to the configured Cyberhub box, rather stores the data internally.
c) Log Data Masking: There is an option that allows administrators to mask the serial number in the log line if they prefer not to reveal it. We would recommend displaying all digits. In “Mask Token Serial Number: Number of digits of the token serial number to display: Please select max value, which can be equal to the number of digits which appear in available tokens. To check please navigate to Authentication > Secure ID Tokens > Assigned/Unassigned on security console home page.
Recommended: Please put in value at least equal to 6, so that token serial number can be identified. Otherwise enter the max value. For more information, please hover over Help section How does masking work label defined. Security Event Scenarios to be monitored on Product
Integration Parameters
Parameters required from customer for Integration.
Property | Default Value | Description |
|---|---|---|
IP Address | RSA Authentication Manager interface IP address | Hostname or IP address of the device which forwards logs to the CyberHub |