LogZilla

Update Logzilla

1. Identify or create credentials to access integration with read access, at minimum.
2. Generate a new authorization token in the LogZilla command line:
   1. logzilla authtoken

API Calls

The following API calls are used by the Validation Platform.

Update the Validation Platform

Prerequisites

Information to gather before you start:

• Identify the hostname/IP used to access LogZilla.
• Identify the Port used for Graylog communication (this defaults to 443).
• Identify whether the protocol is HTTP or HTTPS for connections to the LogZilla port.
• Obtain the Auth Token of a LogZilla account with appropriate access permissions.

Configuration

To add the LogZilla integration

1. Go to Settings > Integrations.

2. Click Add Integration > LogZilla.

   You can add this as either a Local or Remote Inetgration.

3. Enter information for the Host, Port, and Protocol.

4. Review and update the Query.
   The %ACTOR_IPS% variable can be used in all queries. This improves event matching.
   

   LogZilla Integration

5. Expand Advanced options.

6. (Optional) Update Query time and Delay time.

   The Query time is the amount of time (minutes) before and after the query runs that the platform looks for events, while the Delay time is the amount of time (minutes) that the platform waits to run the first query after a Job Action starts. For example, you configure your integration with the following values: Query time = 5, Query interval = 30 seconds, and Delay time = 0. When a Job Actions starts at 12:00:00, the first time the query runs, the platform looks for events from 11:55:00 to 12:00:00. Then 30 seconds later, it looks for events from 11:55:30 to 12:00:30. This interval continues, with the last query looking from 12:00:00 to 12:05:00. If you instead configured the Delay time to equal 10, it would run the same query, but it wouldn't start that query until 12:10:00.
   If your monitors are set to run more frequently than the query time, this configuration impacts the pass/fail results for AEDA monitors.

7. (Optional) Select Enable query for Malicious DNS Actions and configure the Query. This query will only be used when you run Malicious DNS Actions or Captive DNS Actions.

8. (Optional) Select Enable query for Email Actions and configure the Query. This query will be only be used when you run Email Actions.

9. (Optional) Select Enable query for Host CLI Actions and configure the Query. This query will only be used when you run Host CLI Actions.

   If you enable the Host CLI Actions query and use the %HOST_CLI_ACTOR_HOSTNAMES% variable, the platform will substitute the plain hostname and the information from the Alternate Hostname field on the Actor configuration page.
   

   LogZilla Integration (Advanced Options)

10. Identify the field name mappings for the following (there could be multiple of each, depending on log sources and configuration):

    • Source IP
    • Destination IP
    • Source Port
    • Destination Port
    • Event Source Host
    • Event Start Time (timestamp)
    • LogZilla Unique ID
    • Event Signature ID
    • Event Description
    • Email Sender
    • Email Recipient
    • Email Subject
    • URL
    • Username

11. Modify the Query Interval and Event Time Adjustment, if necessary.

12. (Optional) Assign a Name.

13. (Optional) Choose Yes to save suspicious events.

14. Click Submit.

LogZilla Integration (Advanced Options)

Set up Proxy Assignment

If all outbound connections go through a proxy, you may want to set up a proxy definition and assignment for your integration. For information on setting up your proxy rules, see Proxy Rules.

Verify connectivity

To verify connectivity to LogZilla

Click Test to verify that:

• The Director can communicate with the integration host on the port and protocol specified.
• The integration credentials are valid and working.