Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Enroll an SRX Series Firewall using Juniper ATP Cloud Web Portal

Only devices enrolled with Juniper ATP Cloud can send files for malware inspection.

Before enrolling a device, check whether the device is already enrolled. To do this, use the Enrolled Devices page or the Device Lookup option in the Juniper Security Director Cloud UI. If the device is already enrolled, disenroll it first before enrolling it again.


If a device is already enrolled in a realm and you enroll it in a new realm, none of the device data or configuration information is propagated to the new realm. This includes history, infected hosts feeds, logging, API tokens, and administrator accounts.

As of Junos Release 19.3R1, there is another way to enroll the SRX Series Firewall without having to interact with the ATP Cloud Web Portal. You run the “enroll” command from the SRX and it performs all the necessary enrollment steps. See Enroll an SRX Series Firewall Using the CLI.

Juniper ATP Cloud uses a Junos OS operation (op) script to help you configure your SRX Series Firewall to connect to the Juniper Advanced Threat Prevention Cloud service. This script performs the following tasks:

  • Downloads and installs certificate authority (CAs) licenses onto your SRX Series Firewall.

  • Creates local certificates and enrolls them with the cloud server.

  • Performs basic Juniper ATP Cloud configuration on the SRX Series Firewall.

  • Establishes a secure connection to the cloud server.

  • Juniper ATP Cloud requires that both your Routing Engine (control plane) and Packet Forwarding Engine (data plane) is connected to the Internet.

  • The data plane connection should not go through the management interface, for example, fxp0. You do not need to open any ports on the SRX Series Firewall to communicate with the cloud server. However, if you have a device in the middle, such as a firewall, then that device must have ports 8080 and 443 open.

  • The SRX Series Firewall uses the default inet.0 routing table and an interface part of inet.0 as source-interface for control-plane connection from SRX Series Firewall to ATP Cloud. If the only Internet-facing interface on SRX Series Firewall is part of a routing instance, then we recommend that you add a static route pointing to the routing instance. Else, the control connection will fail to establish.

  • Juniper ATP Cloud requires that your SRX Series Firewall host name contain only alphanumeric ASCII characters (a-z, A-Z, 0-9), the underscore symbol ( _ ) and the dash symbol ( - ).


If you are configuring explicit web proxy support for SRX Series services/Juniper ATP Cloud connections, you must enroll SRX Series Firewalls to Juniper ATP Cloud using a slightly different process, see Explicit Web Proxy for Juniper ATP Cloud.

To enroll a device in Juniper ATP Cloud using the Web Portal, do the following:

  1. From the Juniper Security Director Cloud UI, select Shared Services > Advanced Threat Prevention > ATP Devices. Click the Enroll button on the Enrolled Devices page.
  2. Copy the command to your clipboard and click OK.
  3. Paste the command into the Junos OS CLI of the SRX Series Firewall you want to enroll with Juniper ATP Cloud and press Enter. (Note that this command must be run in operational mode.)

If the script fails, disenroll the device (see Remove an SRX Series Firewall From Juniper Advanced Threat Prevention Cloud) and then re-enroll it.


(Optional) Use the show services advanced-anti-malware status CLI command to verify that a connection is made to the cloud server from the SRX Series Firewall.

Once configured, the SRX Series Firewall communicates to the cloud through multiple persistent connections established over a secure channel (TLS 1.2) and the SRX Series Firewall is authenticated using SSL client certificates.

In the Juniper Security Director Cloud UI Enrolled Devices page, basic connection information for all enrolled devices is provided, including serial number, model number, tier level (free or not) enrollment status in Juniper ATP Cloud, last telemetry activity, and last activity seen. Click the serial number for more details. In addition to Enroll, the following buttons are available:

Table 1: Button Actions




Use the Enroll button to obtain a enroll command to run on eligible SRX Series Firewalls. This command enrolls them in Juniper ATP Cloud and is valid for 7 days. Once enrolled, SRX Series Firewall appears in the Devices and Connections list.


Use the Disenroll button to obtain a disenroll command to run on SRX Series Firewalls currently enrolled in Juniper ATP Cloud. This command removes those devices from Juniper ATP Cloud enrollment and is valid for 7 days.


Running the Enroll or Disenroll command will commit any uncommitted configuration changes on the SRX Series Firewall.


Generating a new Enroll or Disenroll command invalidates any previously generated commands.

Device Lookup

Use the Device Lookup button to search for the device serial number(s) in the licensing database to determine the tier (premium, feed only, free) of the device. For this search, the device does not have to be currently enrolled in Juniper ATP Cloud.


Removing an SRX Series Firewall is different than disenrolling it. Use the Delete option only when the associated SRX Series Firewall is not responding (for example, hardware failure). Clicking the delete button dissassociates the SRX Series Firewall from the cloud without running the Junos OS operation (op) script on the device (see Enrolling and Disenrolling Devices). You can later enroll it using the Enroll option when the device is again available.

For HA configurations, you only need to enroll the cluster primary. The cloud will detect that this is a cluster and will automatically enroll both the primary and backup as a pair. Both devices, however, must be licensed accordingly. For example, if you want premium features, both devices must be entitled with the premium license.


Juniper ATP Cloud supports both active-active and active-passive cluster configurations. The passive (non-active) node does not establish a connection to the cloud until it becomes the active node.


The License Expiration column contains the status of your current license, including expiration information. There is a 60 day grace period after the license expires before the SRX Series Firewall is disenrolled from Juniper ATP Cloud.