.png?sv=2019-07-07&sig=HM9b6CtsfpD3HwlPZ2U8tuUhF%2BUJt7edZh0c0wTeSBU%3D&spr=https%2Chttp&st=2023-03-25T10%3A46%3A51Z&se=2023-03-25T10%3A56%3A51Z&srt=o&ss=b&sp=r){kind=logo}
HTTP Server - Send to Webhook
- 16 Mar 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
HTTP Server - Send to Webhook
- Updated on 16 Mar 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
NOTE
This Enforcement Action was formerly named Web Server Information - Send to Webhook.
HTTP Server - Send to Webhook serializes the entities retrieved from the saved query supplied as a trigger (or entities selected in the asset table) as JSON. This JSON data will be sent to a configured webhook. When used with a saved query as a trigger, only the fields configured in the saved query are added to the JSON.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
- Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
- Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.
Required Fields
These fields must be configured to run the Enforcement Set.
Click to view Required Fields
- Webhook URL (required) - Specify the webhook URL.
- Custom format for body (use {$BODY} as keyword) (required, default: {"entities": {$BODY}}) - You can custom the webhook body. Specify {$BODY} to include the entities found in the saved query supplied as a trigger (or entities that have been selected in the asset table) data,
- Connection timeout (seconds) (required, default: 10 seconds) - Define the number of seconds before the attempt to connect to the webhook is considered to be timed out. As a result, the enforcement action execution will fail.
- Writing data to webhook timeout (seconds) (required, default: 1200 seconds) - Define the maximum number of seconds before the attempt of completing sending the data to the webhook is considered to be timed out. As a result, the enforcement action execution will fail.
Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
Click to view Additional Fields
- Authorization header user name and authorization header password (optional, default: empty) - Specify authorization header user name and password, if required.
- If supplied, Axonius will pass the specified authorization header information along with the Webhook URL.
- If not supplied, Axonius will not pass any additional information along with the Webhook URL.
Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTP proxy (optional, default: empty) - A proxy to use when connecting to a HTTP Webhook URL.
- If supplied, Axonius will utilize the proxy when connecting to the specified URL.
- If not supplied, Axonius will connect directly to the URL.
- Additional headers (optional, default: {"Content-type": "application/json"}) - You can configure additional headers, if required.
- If supplied Axonius will pass additional information with the HTTP/S request.
- If not supplied, Axonius will not pass additional information with the HTTP/S request.
Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.
For more details about other Enforcement Actions available, see Action Library.