Juniper Secure Analytics (JSA)

This document applies to Classic/Legacy Integrations. You may continue to use these integration configurations. While no active development is happening for these integrations, we continue to provide Classic/Legacy Integrations in the product. You do not have to move to MSI Integrations. If your support engineer or TSC recommends or you choose to move to MSI Integrations, you can take advantage of the latest features and functionality. For more information, see the MSI Integration documentation in the Integrations Overview.

This integration is remote capable.

Update Juniper JSA

Set up the credentials that will be used with the Validation Platform.

  • Username and password or authentication token.
  • Admin permissions are required, at minimum .

Update the Validation Platform

Prerequisites

Information to gather before you start:

  1. Identify the IP address.
  2. Identify the port communications (default is 443).
  3. Identify whether the protocol is HTTP or HTTPS (default is HTTPS).
  4. Have the credential information .
  5. Identify the timezone of the Juniper host.

Configuration

To add the Juniper JSA integration

  1. Go to Settings > Integrations.

  2. Click Add Integration > Juniper JSA.

    Juniper JSA Integration

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

  5. Select the Credential type and enter the appropriate credentials.
  6. Change the Time Zone to match that of the Juniper JSA host.
  7. Expand Advanced options.

    Juniper JSA Integration (Advanced Options)

  8. (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.
  9. (Optional) Review and update the populated query information (Flows query, Offense query fields, Offense query filter, Correlated Events Query.
  10. (Optional) Enable the special query for DNS Actions and define the Query.
  11. (Optional) Enable the special query for Email Actions and define the Query.
  12. (Optional) Enable the special query for Host CLI Actions and define the Query.

    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.
  13. (Optional) Select Discover network devices automatically.

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

  15. (Optional) Assign a Name.

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

  17. Click Submit.

Verify connectivity

To verify connectivity to Juniper JSA

Click Test to verify that:

  • The Director can communicate with Juniper JSA on the port and protocol specified.
  • Credentials are valid and working.
  • Times match.
  • June 3, 2022
  • October 23, 2023
In This Article