Forward Logs to an HTTP(S) Destination

The firewall and Panorama can forward logs to an HTTP server. You can choose to forward all logs or selectively forward logs to trigger an action on an external HTTP-based service when an event occurs. When forwarding logs to an HTTP server, you can choose the following options:
  • Configure the firewall to send an HTTP-based API request directly to a third-party service to trigger an action based on the attributes in a firewall log. You can configure the firewall to work with any HTTP-based service that exposes an API, and modify the URL, HTTP header, parameters, and the payload in the HTTP request to meet your integration needs.
  • Tag the source or destination IP address in a log entry automatically and register the IP address and tag mapping to a User-ID agent on the firewall or Panorama, or to a remote User-ID agent so that you can respond to an event and dynamically enforce security policy. To enforce policy, you must Use Dynamic Address Groups in Policy .
  1. Create an HTTP server profile to forward logs to an HTTP(S) destination.
    The HTTP server profile allows you to specify how to access the server and define the format in which to forward logs to the HTTP(S) destination. By default, the firewall uses the management port to forward these logs. You can however, assign a different source interface and IP address in DeviceSetupServicesService Route Configuration.
    1. Select DeviceServer ProfilesHTTP, add a Name for the server profile, and select the Location. The profile can be Shared across all virtual systems or can belong to a specific virtual system.
    2. Click Add to provide the details for each server. Each profile can have a maximum of 4 servers.
    3. Enter a Name and IP Address.
    4. Select the Protocol (HTTP or HTTPS). The default Port is 80 or 443 respectively; you can modify the port number to match the port on which your HTTP server listens.
    5. Select the HTTP Method that the third-party service supports—PUT, POST (default), GET and DELETE.
    6. Enter the Username and Password for authenticating to the server, if needed. Click OK.
    7. Select Test Server Connection to verify network connectivity between the firewall and the HTTP(S) server.
      http_server_profile.PNG
  2. Select the Payload Format for the HTTP request.
    1. Select the Log Type link for each log type for which you want to define the HTTP request format.
    2. Select the Pre-defined Formats drop-down to view the formats available through content updates, or create a custom format.
      If you create a custom format, the URI is the resource endpoint on the HTTP service. The firewall appends the URI to the IP address you defined earlier to construct the URL for the HTTP request. Ensure that the URI and payload format matches the syntax that your third-party vendor requires. You can use any attribute supported on the selected log type within the HTTP Header, Parameter and Value pairs, and in the request payload.
      http_server_profile_SNow.PNG
    3. Send Test Log to verify that the HTTP server receives the request. When you interactively send a test log, the firewall uses the format as is and does not replace the variable with a value from a firewall log. If your HTTP server sends a 404 response, provide values for the parameters so that the server can process the request successfully.
  3. Define the match criteria for when the firewall will forward logs to the HTTP server, and attach the HTTP server profile to use.
    1. Select the log types for which you want to trigger a workflow:
      • Add a Log Forwarding Profile (ObjectsLog Forwarding Profile) for logs that pertain to user activity. For example, Traffic, Threat, or Authentication logs.
      • Select DeviceLog Settings for logs that pertain to system events, such as Configuration or System logs.
    2. Select the Log Type and use the new Filter Builder to define the match criteria.
    3. Add the HTTP server profile for forwarding logs to the HTTP destination.
      log-forwarding_filter.PNG
    4. Add a tag to the source or destination IP address in the log entry. This capability allows you to use dynamic address groups and security policy rules to limit network access or isolate the IP address until you can triage the affected user device.
      Select Add in the Built-in Actions section and select the Target, Action: Add Tag, and Registration to register the tag to the local User-ID on a firewall or to the Panorama that is managing the firewall.
      If you want to register the tag to a remote User-ID agent, see Step 4 .
      log-forwarding_auto_tag.PNG
  4. Register or unregister a tag on a source or destination IP address in a log entry to a remote User-ID agent.
    1. Select DeviceServer ProfilesHTTP, add a Name for the server profile, and select the Location. The profile can be Shared across all virtual systems or can belong to a specific virtual system.
    2. Select Tag Registration to enable the firewall to register the IP address and tag mapping with the User-ID agent on a remote firewall. With tag registration enabled, you cannot specify the payload format.
    3. Add the connection details to access the remote User-ID agent.
      http_server_profile_tag.PNG
    4. Select the log type (ObjectsLog Forwarding Profile or DeviceLog Settings) for which you want to add a tag to the source or destination IP address in the log entry.
    5. Select Add in the Built-in Actions section and Name the action. Select the following options to register the tag on the remote User-ID agent:
      • Target: Select source or destination IP address.
      • Action: Add Tag or Remove Tag.
      • Registration: Remote User-ID agent.
      • HTTP Profile: Select the profile you created with Tag Registration enabled.
      • Tag: Enter a new tag or select from the drop-down.
    For dynamic policy enforcement, Use Dynamic Address Groups in Policy .

Related Documentation