Download and Run the Juniper ATP Cloud Script

The Juniper ATP Cloud uses a Junos OS op script to help you configure your SRX Series Firewall to connect to the Juniper ATP Cloud cloud service. This script performs the following tasks:

Downloads and installs certificate authority (CAs) licenses onto your SRX Series Firewall.
Note:
- You can enroll SRX1600, SRX2300 and SRX4300 firewalls with Trusted Platform Module (TPM)-based certificates for TLS-based authentication and a secure connection with the Juniper ATP Cloud. For more information about TPM, see Encryption with Trusted Platform Module. Since the TPM-based certificates are used for connections between the SRX Series Firewall and Juniper ATP Cloud, you must allow traffic to the junipersecurity.net domain on ports 8444 and 7444.
- To enroll SRX300, SRX320, SRX340, SRX345, SRX380, SRX5400, SRX5600, and SRX5800 Series Firewalls with Juniper ATP Cloud, ensure that TPM-based encryption is not configured on these devices. Enrollment to Juniper ATP Cloud is not supported with TPM-based encryption.
Creates local certificates and enrolls these certificates with the cloud server.
Performs basic Juniper ATP Cloud configuration on the SRX Series Firewall.
Establishes a secure connection to the cloud server.

Note:

Juniper ATP Cloud requires that both your Routing Engine (control plane) and Packet Forwarding Engine (data plane) can connect 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 hostname contains only alphanumeric ASCII characters (a-z, A-Z, 0-9), the underscore symbol (_) and the dash symbol (-).

For SRX300, SRX320, SRX340, SRX345, SRX380 and SRX550 Series firewalls, you must run the set security forwarding-process enhanced-services-mode command and reboot the device before running the op script or before running the request services advanced-anti-malware enroll command.

To download and run the Juniper ATP Cloud scripts:

Note:

Starting in Junos OS Release 19.3R1, you can use the request services advanced-anti-malware enroll command on the SRX Series Firewall to enroll a device to the Juniper ATP Cloud Web Portal. With this command, you do not have to perform any enrollment tasks on the Web Portal. All enrollment is done from the CLI on the SRX Series Firewall. See Enroll an SRX Series Firewall Using the CLI.

In the Web UI, click Devices and then click Enroll.
The Enroll window appears. See Figure 1.

Figure 1: Enrolling Your SRX Series Firewall
Copy the highlighted contents to your clipboard and click OK.
Note:
When enrolling devices, Juniper ATP Cloud generates a unique op script for each request. Each time you click Enroll, you’ll get slightly different parameters in the op script. The screenshot above is just an example. Do not copy the above example onto your SRX Series Firewall. Instead, copy and paste the output you receive from your Web UI and use that to enroll your SRX Series Firewalls.

Paste this command into the Junos OS CLI of the SRX Series Firewall you want to enroll with Juniper ATP Cloud. Press Enter. Your screen will look similar to the following.

Note:

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

In the Juniper ATP Cloud Web portal, click Devices.

The SRX Series Firewall you enrolled now appears in the table. See Figure 2.

Figure 2: Example Enrolled SRX Series Firewall

(optional) Use the show services advanced-anti-malware status CLI command to verify that connection is made to the cloud server from the SRX Series Firewall. Your output will look similar to the following.

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

As stated earlier, the script performs basic Juniper ATP Cloud configuration on the SRX Series Firewall. These configurations include:

Note:

You should not copy and run the following examples on your SRX Series Firewall. The list here is simply to show you what is being configured by the op script. If you run into any issues, such as certificates, rerun the op script again.

Creating a default profile.

Establishing a secured connection to the cloud server. The following is an example. Your exact URL is determined by your geographical region. See table.

Table 1: Customer Portal URLs
Location	Customer Portal URL
United States	Customer Portal: https://amer.sky.junipersecurity.net
European Union	Customer Portal: https://euapac.sky.junipersecurity.net
APAC	Customer Portal: https://apac.sky.junipersecurity.net
Canada	Customer Portal: https://canada.sky.junipersecurity.net

Configuring the SSL proxy.

Configuring the cloud feeds (allowlists, blocklists and so on.)

Juniper ATP Cloud uses SSL forward proxy as the client and server authentication. Instead of importing the signing certificate and its issuer’s certificates into the trusted-ca list of client browsers, SSL forward proxy now generates a certificate chain and sends this certificate chain to clients. Certificate chaining helps to eliminate the need to distribute the signing certificates of SSL forward proxy to the clients because clients can now implicitly trust the SSL forward proxy certificate.

The following CLI commands load the local certificate into the PKID cache and load the certificate-chain into the CA certificate cache in PKID, respectively.

Where:

ssl_proxy_ca.crt (Signing certificate)	Is the SSL forward proxy certificate signed by the administrator or by the intermediate CA.
sslserver.key	Is the keypair.
ssl-inspect-ca	Is the certificate ID that SSL forward proxy uses in configuring the root-ca in the SSL forward proxy profile.
certificate-chain	Is the file containing the chain of certificates.

The following is an example of SSL forward proxy certificate chaining used by the op script.

Note that you cannot enroll the SRX Series Firewall to Juniper ATP Cloud if the SRX Series Firewall is in FIPS mode due to a PKI limitation.

To check your certificates, see Troubleshooting Juniper Advanced Threat Prevention Cloud: Checking Certificates. We recommend that you re-run the op script if you are having certificate issues.