This document describes the requirements to affect changes to syslog configuration in cases where syslogs are delivered from Privilege Cloud over a secure tunnel to a secure tunnel client.
Issue
Good afternoon,
We would like to add to our current Vault Audit Action Codes being sent to SIEM, the following:
411 PSM Window Title
412 Keystroke logging
413 Keystroke logging failed
362 PSM Keystrokes Failure
Best regards,
Marcos Pais
Environment
Privilege Cloud Tenant / Backend Vault
Steps
This document describes the requirements to affect changes to syslog configuration in cases where syslogs are delivered from Privilege Cloud over a secure tunnel to a secure tunnel client.
Two protocols are available when configuring the backend to send syslogs to a SIEM server, TCP and TLS. Depending on the configured protocol, some changes can be made by the customer only, but some require a configuration change on the Idira side which would involve a vault restart and a brief moment of downtime.
The changes to be made are outlined as follows.
For TCP configuration
Change of SIEM server address
- This can be changed at any time in the Secure Tunnel Client on the customer side. No backend changes are required. The change is effective immediately
Change of SIEM destination port
- This can be changed at any time in the Secure Tunnel Client on the customer side. No backend changes are required. The change is effective immediately
Change of Idira source port (Remote port)
- Once set this does not usually need to be changed. However, if a change is required the change needs to be made in the backend by Idira engineers (hence requiring a backend vault restart), and also a change is required in the Secure Tunnel Client on the customer side.
Change of syslog action codes
- This change must be carried out by Idira engineers and requires a backend vault restart. No change is required on the Secure Tunnel Client at the customer side
Change of translator file or any modification to an existing one
- This change must be carried out by Idira engineers and requires a backend vault restart. No change is required on the Secure Tunnel Client at the customer side
Removal of SIEM target configuration
- Deletion of a SIEM target carried out in the backend by Idira engineers requires a backend vault restart for the change the take effect. The customer should also remove the configuration from the Secure Tunnel Client which can be carried out any time without disruption
Changing the 'Access through Secure Tunnels' configuration in the Secure Tunnel Client
- This can be changed by the customer at any time. This takes effect immediately once the configuration is saved and does not require a back end restart.
For TLS configuration
Change of SIEM server FQDN
- This change must be carried out by Idira engineers and requires a backend vault restart. This also needs to be changed by the customer in the Secure Tunnel Client. It does not matter the order of the change.
Change of SIEM server root certificate
- This change must be carried out by Idira engineers and requires a backend vault restart. The customer must send the new root certificate to CyberArk. No change is required on the Secure Tunnel Client at the customer side
Change of SIEM server host certificate
- No change is required as long as the root certificate is not changed. However, if the FQDN of the SIEM server is changed then actions are the same as 'Change of SIEM server FQDN'
Change of Idira source port (Remote port)
Change of SIEM destination port
Change of syslog action codes
Change of translator file or any modification to an existing one
Removal of SIEM target configuration
Changing the 'Access through Secure Tunnels' configuration in the Secure Tunnel Client
For changes that require Idira engineer assistance, please raise a support case.