web client only
You can configure audit event logs to send to syslog server (cluster-wide). Audit events include connection, closure, and failures. Failures include the reason, the initiator, and the target. For example, a certificate validation failure will include the initiator and the target.
Debug logging to syslog server is available and is appliance specific (see Debug).
To configure audit event logs to send to a syslog server
- You will need a configured syslog server. If you have not configured a syslog server, you will see a message like this: To configure additional debut logging options, you need to configure a syslog server. Click Configure a syslog server. For more information, see Configuring and verifying a syslog server.
- Navigate to Settings| External Integration | Syslog Events.
- The Syslog Events pane displays the following.
Table 166: Syslog server: Properties
The name of the syslog server
||The type of program being used to create syslog messages (for example, User or Mail)|
The format which can be CEF or JSON
||The description of the syslog event|
|# of Events
||The number of events selected to be logged to the syslog server|
Use these toolbar buttons to manage the syslog server configurations
Add a syslog event subscriber
web client only
It is the responsibility of the Appliance Administrator to add an event subscriber.
To add an event subscriber
- Navigate to Settings| External Integration | Syslog Event.
- Click Add to display the Syslog Events dialog.
In the Syslog Events dialog, enter the following:
Syslog Server: Select the server to which you want to send the events.
- Description: Enter the description of the syslog event.
- Subscribe to All Events: Select this check box to subscribe to all events, including new events that may be added in the future. If unselected, select specific events.
If you left Subscribe to All Events unselected, click Browse then select the check boxes of the Events to which you want to subscribe You can enter characters then click Search to limit the events that are displayed. Click OK.
- Facility: Select which syslog facility to send, for example User or Mail.
- If you select JSON, enter the Attribute Prefix which is text that will be prepended to the JSON attributes.
- Click OK.
ServiceNow ticketing system integration
ServiceNow is a cloud-based issue tracking system. Safeguard for Privileged Passwords can exchange the following ticket types with ServiceNow:
- CHG (change) tickets
- RITM (request) tickets
- PRB (problem) tickets
The data items specific to ServiceNow may be optional based on your configuration.
To use ServiceNow, the root CA Certificate required for ServiceNow must be installed in Safeguard for Privileged Passwords. For more information, see Trusted CA Certificates. To add a trusted certificate, see Adding a trusted certificate.
Tickets can be viewed in the Activity Center, Ticket # column.
Setting up the integration
- Go to Ticket Systems:
- web client: Navigate to Settings | External Integration | Ticket Systems.
- desktop client: Navigate to Administrative Tools | Settings | External Integration | Ticket Systems.
- Click Add to add a ticket system.
- Do the following:
- web client: Select ServiceNow.
- desktop client: On the Ticket System dialog, select the Type as ServiceNow.
- Complete the authorization information based on your installation:
- Name: Enter the name of your ticketing system
- URL: Enter the web site address to the ticketing system.
- Username: Enter an account for Safeguard for Privileged Passwords to use to access the ticketing system.
- Password: Enter the user account's password.
- Client Identifier: Enter the ServiceNow Client ID.
- Client Secret: Enter the ServiceNow secret key.
- Click Test Connection to test the connection to ServiceNow.
- The Security Policy Administrator creates an access request policy that requires the requester to provide a ticket number when creating an access request. For more information, see Creating an access request policy
- When the requester makes a request, they must enter the existing ServiceNow ticket number on the New Access Request dialog, Request Details tab, Ticket Number field. See:
- Safeguard for Privileged Passwords queries all configured ticket systems to see if that ticket number represents a ticket that exists and is in an open state. For ServiceNow, Safeguard checks the Active property of the identified ticket returned from the ServiceNow API and considers the ticket number valid if the Active property is not false for that incident.
- If the ticket is not active, the request is denied.
- If the ticket is active, the access workflow continues.