- 14 Oct 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
HTTP Server - Send to Webhook per Asset
- Updated on 14 Oct 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
HTTP Server - Send to Webhook per Asset serializes each asset as JSON and sends its JSON data to a configured webhook for:
- Assets returned by the selected query or assets selected on the relevant asset page.
When run on a query, only the fields configured in the query are added to the JSON.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Webhook URL - Specify the webhook URL.
- Custom format for body (use {$BODY} as keyword) (default: {"entities": {$BODY}}) - You can customize the webhook body.
- Use {$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.
- Use {$BODY_ESCAPED} instead of {$BODY} if you want to escape JSON characters so that the JSON is sent as a string instead of an object.
- Connection timeout (seconds) (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) (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.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Authorization header user name and Authorization header password - Specify the authorization header user name and password, if required. Axonius will pass the specified authorization header information along with the Webhook URL.
- Verify SSL (optional) - 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 (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTP proxy - When a proxy is supplied, Axonius will use the proxy, instead of the direct URL, when connecting to the HTTP Webhook URL.
Additional headers (default: {"Content-type": "application/json"}) - Add Customized Headers to be Sent with Request. For Example:
{"Content-type":"application/json","Accept":"application/json","Authorization":"Bearer <TOKEN>"}
- Gateway Name - Select the Gateway through which to connect to perform the action.
For more details about other Enforcement Actions available, see Action Library.