Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Log in to RSA security console with admin level privilegesas administrator.

  2. Navigate to tab Set Up and then select System Settings

  3. Under section In Basic Settings please , select Logging

  4. Click on Select Instance first, 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 please click on Next

  5. Now in 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 level levels assigned. For analysis, Administrative Audit and Runtime Audit are of most importance.

Please note that we 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.

Please note that syslog Syslog messages are pushed over port 514 UDP only. So, we need not to explicitly define port anywhereNo 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 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 “How Help section How does masking work” work label defined. Security Event Scenarios to be monitored on Product

...