Send to HTTPS Log Server
  • 25 May 2022
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Send to HTTPS Log Server

  • Dark
    Light
  • PDF

The Send to HTTPS Log Server action creates a log message with custom description and/or the action results summary (incident description) in HTTPS log server. It also creates optional JSON messages with the asset data (device or user) for each of the assets in the query results or a JSON file with data about the system entity queried, for queries created on Activity logs and Fetch History using filters.

To use this action, you must enable the Use HTTPS logs setting and configure the HTTPS Logs host and port. For more details, see Global Settings.

To configure the Send to HTTPS Log Server action, from the Action Library, click Notify, and then click Send to HTTPS Log Server.

The incident description message includes the Enforcement Set name, the triggered query, the condition for executing the Enforcement (if it exists), and number of current and previous results.

Message Example

Click to view Message Example

Alert - "test" for the following query has been triggered: Missing Sophos

Alert Details
The alert was triggered because: The number of entities is above 0
The number of devices returned by the query:4
The previous number of devices was:4

You can view the query and its results here: https://demo-latest.axonius.com/devices?view=Missing Sophos


Connection Settings

Click to view Connection Settings


  1. Authorization Header (optional, default: empty) - If the HTTPS log server message requires user authentication, specify the required HTTP authorization request in the field.
    • If supplied, Axonius will pass the specified authorization header information with the HTTP request.
    • If not supplied, Axonius will not pass any additional information with the HTTP request.

Action Settings

Click to view Connection Settings


  1. Description (optional, default: empty) - Specify an optional description.
    • If supplied, Axonius will include the specified description in HTTPS log server message.
    • If not supplied, Axonius will not include any custom description in HTTPS log server message.
  2. Send result details (required, default: False) - Select whether to send additional messages to the HTTPS log server with the details of the results.
    • If enabled, Axonius will send a JSON file with details of the results.
    • If disabled, Axonius will not send details of the results.
  3. Add default incident description (required, default: False) - Select whether to send the incident description to the HTTPS log server.
    • If enabled, Axonius will include the default incident description (mentioned above) in HTTPS log server message.
    • If disabled, Axonius will not include the default incident description (mentioned above) in HTTPS log server message.
  4. Send CSV data (required, default: False) - Select whether to send the ran query data in a CSV format to the HTTPS log server.
    • If enabled, Axonius will include the query data in a CSV format in HTTPS log server message.
    • If disabled, Axonius will not include the query data in HTTPS log server message.
  5. Extra headers around message (JSON format) (optional, default: empty) - Use this setting to add a JSON formatted string that can be added to the HTTPS Log JSON thus enabling efficient integration with tools that accept input of JSON. The input should appear as follows:
     {"index": 12345, "sourcetype": "_json"}
    
  6. Export CSV delimiter to use for multi-value fields - set the delimiter to use in fields in cells that contain multiple values (for instance IP addresses).

To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


What's Next
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.