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), syslog, graylog.

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.

Web Hook Destination

For each web hook 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

Syslog Destination

You may choose to send your logs to a syslog receiver. This can either be directly accessible from each connector, or, accessible from one connector that the others use as a gateway (this allows multi-site routing).

Create a destination. Set the type to ‘syslog’. Enter a URI for the destination in the format

transport://path?param

The transport would be one of unix, udp, tcp. So to send to a syslog server on the same machine it might be unix:///dev/log. To send to a syslog server via UDP on a remote, it might be udp://10.11.12.13:514.

Optional parameters might be:

  • severity (Default: 6 / LogInfo); Range: 0 (Emergency) to 7 (Debug)
  • facility (Default: 16 / LogLocal0); Range: 0 (Kernel) to 23 (Local7)
  • max_message_size (Default: 10240) – The maximum size (in bytes) of a log message before it is truncated.