Generic HTTPS

📷

Requires an upgraded subscription

This feature is exclusive to our Enterprise Plan. Book a demo to see it in action.

There are countless Log Aggregator and SIEM solutions, so having a specific integration for each of them isn't always possible. Most of those solutions have some ability to ingest logs over HTTPS webhooks though. This integration is designed to take advantage of just such a solution.

Limitations

• The URL being used to send logs to must be HTTPS.
• The only (optional) authentication method supported is a Bearer authentication header.
• Only one Generic HTTPS logging integration can be configured currently, so make sure you configure this to send logs to your primary log aggregator or SIEM.

📘

If your Log Aggregator or SIEM only provides you with a HTTP URL, try changing the protocol to HTTPS anyways. Many solutions support HTTPS even if they only provide a HTTP URL.

Configuration

To setup activity log forwarding to a generic HTTPS webhook, browse to the workplace Settings page and scroll down to the Logging Services section. Then, click on the Connect button.

Next, paste in the HTTPS URL you'd like to send logs to. You can optionally provide a bearer token for authentication.

🚧

The only authentication method supported is an Authentication header with a Bearer token. Basic Auth or other authentication types are not currently available.

Editing an Existing Configuration

To edit an existing configuration, click on the 3 dot menu to the right side of the service and choose Edit.

Disconnecting a Configuration

To remove your configuration, click on the 3 dot menu to the right side of the service and choose Disconnect.