Auditing page
Last updated
Last updated
Access Manager always logs events to the Windows event log, but you can also have it deliver notifications via email, web hooks, or even PowerShell.
Audit events are always logged to the Windows event log. Access Manager allows you to customize the content of the log message using the Edit Template button.
Access Manager can be configured to forward all audit events to Splunk via HEC (HTTP Event Collector).
You can configure connectivity to a Splunk instance using the Splunk Settings button.
You can configure HEC endpoints and tokens for use with Access Manager for both Splunk Cloud and Splunk Enterprise.
Indicates if Splunk audit log forwarding is currently enabled. If it is not enabled, audit events will not be sent to Splunk.
This setting needs very careful consideration before turning this flag on. When enabled, AMS will wait to grant access to the user until the audit log is delivered to Splunk. If Splunk takes a long time to process the audit log, or connectivity to Splunk is lost, this will result in the user will be denied access to the resource they requested. Only enable this setting if auditing to the notification channel is critical.
This is the fully-qualified domain name (FQDN) to use for connecting to the Splunk HEC endpoint.
The protocol to use when connecting to the Splunk HEC endpoint. Defaults to HTTPS.
Optionally, you can disable certificate verification for the HEC endpoint's certificate, if required.
The port to use when connecting to the Splunk HEC endpoint.
The HEC token used to authenticate to the Splunk HEC endpoint.
For more information on creating HEC tokens for use with Access Manager, refer to the relevant documentation for either Splunk Cloud or Splunk Enterprise.
This token should have the correct permissions to write to the index (with the designated sourcetype) configured below.
All audit messages delivered to Splunk will be sent to this index.
All audit messages delivered to Splunk will include this value as the sourcetype field. This field defaults to lithnet:accessmanager
The global settings section defines which channels should be always notified of a success or failure event. This is in addition to any notification channels defined on a specific authorization rule.
If you want to make sure a channel is notified on every success or failure, then add those channels to this list.
Access Manager uses the concept of a notification channel to define what event information should be sent to where, and how it should be delivered. Notification channels are attached to authorization rules and are sent when access to a computer or role is granted or denied.
SMTP channels allow for the delivery of audit events via an HTML formatted email.
Webhooks are a convenient way to send notifications to 3rd party systems. Using a simple JSON payload, you're able to push audit information to systems that support webhooks such as Microsoft Teams and Slack.
Finally, PowerShell can be used to perform custom audit actions and send notifications to any system you can connect to from PowerShell.
The following settings apply to all channel types
Indicates if the notification channel is currently enabled. If it is not enabled, audit events will not be sent to this channel.
This setting needs very careful consideration before turning this flag on. When enabled, AMS will wait to grant access to the user until the notification is sent. If the notification channel takes a long time to process, this will result in the user waiting a long time for their access request to process on the web page. Only enable this setting if auditing to the notification channel is critical. It is important to note that events are always logged to the Windows event log. If the request fails to log to the event log, the request is denied. So there will always be at least one record of a successful access attempt.
A friendly name that is used through the configuration tool to refer to this notification channel.
Edits the HTML file used as a template for an audit event.
AMS comes with a sample HTML template that you can customize to suit your requirements. See the page on audit variables for a list of the fields that are valid to use inside the email template.
A list of email recipients that the audit notification should be sent to
This is the webhook URL provided by the target application.
Specifies the type of HTTP request to make. This will almost always be POST, but in the event that your web hook target requires another value you can specify that here.
Specifies the Content-Type header used in the HTTP request. This will almost always be application/json for a JSON payload. If your web hook target requires a different value, then specify that here.
Specifies any additional HTTP headers to be included in the HTTP request. All header values are securely encrypted within the Access Manager database.
Clicking the Add... button will allow you to add additional headers for this webhook.
Edits the JSON file used as a template for an audit event.
AMS comes with sample JSON templates for Microsoft Teams and Slack that you can customize to suit your requirements. See the page on audit variables for a list of the fields that are valid to use inside the JSON template.
Edit or import a PowerShell script file to execute
All notification channel types populate notification templates by replacing placeholder variables with data from the event. The audit variables page contains a full list of all valid variables that you can use throughout your templates and scripts.
