The SBC supports JITC Audit Log Capture and Hashing. JITC Audit Log Capture and Hashing improves security monitoring by cryptographically hashing the log files at rest using a private key. Hashing of event logs is enabled/disabled for different log types through the log type's Type Admin configuration. Refer to Event Log - Type Admin.
Use this window to to manage the SBC's default key and optionally submit a key to use for cryptographical hashing when it is enabled.
From the SBC main window, go to Configuration > System Provisioning > Security Configuration > Event Log Valdation. The Event Log Validation window opens.
Figure 1: Event Log Validation Window
The Event Log Validation table lists the keys configured in the SBC. The first row in the table is the Default key generated by the system or one requested by the user. The default private key is used for hashing unless there is a user-submitted key. Any user-submitted keys provided through the CLI or added using the Set User Private Key button appear in any rows that follow. If there are no additional keys, the table has only one row and the default key is used for hashing.
The following options are available on this window:
| Window Option | Description |
|---|---|
| Set User Private Key | Click this button to open the Set User Private Key pop-up window where you can enter a private key name and private key value and then save the key. A user-submitted private key must be from a RSA key pair with a bit strength between 2,048 - 8,192. |
| Generate Default Key | Click this button to open the Generate Default Key pop-up window where you can confirm that you want to generate a new default key to replace the current default key. |
| Show Public Key | Click the red magnifying glass icon to view the public key value for the adjacent private key. The private key is always hidden. |
| Delete (X) | Click the X at the end of a row to delete any user-submitted keys. You can delete the default key. |
Overview
Content Tools