Audit Destinations

Audit Destination: Securely deliver audit logs to your chosen destination with AnyX. Illustration of a delivery truck arriving at a building, representing reliable log transport and address confirmation.

Audit Destinations

Configure your own private log destinations.

Audit Destinations

Four types of auditing information are available:

  1. Authentication: users presenting credentials to obtain an access token
  2. Authorisation: individual transactions with an access token that are checked for allow/deny
  3. Access logs: individual transaction detail information
  4. API access: changes to the state of the system via API

By default, all records except for those generated by an Agilicus Connector are stored inside the Agilicus cloud. In addition, you may send logs to a webhook (or, in the case of the Connector, a file).

You may enable records from the Connector to come back to the Agilicus Cloud by enabling ‘Access’ and ‘Authorisation’ check marks in the Audit Destinations screen.

9ab426ad image

For each webhook destination, optional authentication information may be passed.

The intent of the audit destinations to a webhook is to allow the use of an external SIEM or log collector. Messages are sent in JSON format, an example is shown below:

To test your integration, copy the above text to a file (e.g. logs.json) and use:

curl -X POST -d@logs.json https://my-webhook:port