close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview of Policy Enforcer and Juniper ATP Cloud
play_arrow Concepts and Configuration Types to Understand Before You Begin
play_arrow Installing Policy Enforcer
play_arrow Configuring Policy Enforcer Settings, Connectors, and Backup
play_arrow Guided Setup for Juniper ATP Cloud with Juniper Connected Security
- Using Guided Setup for Juniper ATP Cloud with Juniper Connected Security
play_arrow Guided Setup for Juniper ATP Cloud
- Using Guided Setup for Juniper ATP Cloud
play_arrow Guided Setup for No Juniper ATP Cloud (No Selection)
- Using Guided Setup for No Juniper ATP Cloud (No Selection)
play_arrow Configuring Juniper ATP Cloud with Juniper Connected Security(without Guided Setup)
play_arrow Configuring Juniper ATP Cloud (without Guided Setup)
play_arrow Configuring Cloud Feeds Only
- Configuring Cloud Feeds Only
play_arrow Configuring No Juniper ATP Cloud (No Selection) (without Guided Setup)
play_arrow Threat Prevention - Configure
play_arrow Threat Prevention- Monitor
play_arrow Troubleshooting
play_arrow Migration Instructions for Spotlight Secure Customers
- Moving From Spotlight Secure to Policy Enforcer

list Table of Contents

English

keyboard_arrow_right

Policy Enforcer Ports

date_range 17-Oct-23

arrow_backward

arrow_forward

Note:

While using Policy Enforcer in Connected Security deployment, SRX Series Firewalls"?>SRX Series Firewalls do not submit files for detection via Policy Enforcer. SRX Series Firewalls"?>SRX Series Firewalls still need to reach the ATP Cloud cloud server via internet, to submit files for malware detection and analysis. If SRX Series Firewalls"?>SRX Series Firewalls are connected to the internet via another firewall or proxy, then that device must have 8080 and 443 ports open.

You will need to open ports for Policy Enforcer to communicate with other products and devices.

Table 1 lists the ports that Policy Enforcer uses to communicate with Security Director.

Table 1: Policy Enforcer Ports to Communicate with Security Director
Service	Protocol	Port	In	Out
HTTPS	TCP	8080	X
HTTPS	TCP	443		X

Table 2 lists the ports that Policy Enforcer uses to communicate with SRX Series Firewalls.

Table 2: Policy Enforcer Ports to Communicate with SRX Series Firewalls
Service	Protocol	Port	In	Out
HTTPS	TCP	443	X

Table 3 lists the ports that Policy Enforcer uses to communicate with the Juniper ATP Cloud server to download feeds.

Note:

Connectivity between Juniper ATP Cloud and Policy Enforcer is certificate-based. Once the trust is established, every request is within a context of valid token.

Table 4 lists the ports that Policy Enforcer uses to communicate with ca.junipersecurity.net.

Table 3: Policy Enforcer Ports to Communicate with cloudfeeds.sky.junipersecurity.net
Service	Protocol	Port	In	Out
HTTPS	TCP	443		X

Table 4 lists the ports that Policy Enforcer uses to communicate with ca.junipersecurity.net.

Table 4: Policy Enforcer Ports to Communicate with ca.junipersecurity.net
Service	Protocol	Port	In	Out
HTTPS	TCP	8080		X

Table 5 lists the remaining Policy Enforcer services.

Table 5: Policy Enforcer Services
Service	Comments
DNS	Used for basic network connection.
NTP	Used to synchronize system clocks with the Network Time Protocol (NTP).

If you are using NSX with Policy Enforcer (or Security Director), the following ports must be opened on NSX.

Table 6: NSX Ports
Port	In	Comments
443	X	Used for communication between NSX and Security Director.
7804	X	Used for outbound SSH based auto discovery of devices.
22	X	Used for host management and image upload over sftp.

arrow_backward PREVIOUS Installing Policy Enforcer with KVM

NEXT arrow_forward Identifying the Policy Enforcer Virtual Machine In Security Director

Policy Enforcer User Guide

Policy Enforcer Ports

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Policy Enforcer User Guide

Policy Enforcer Ports

Related Documentation

Stay in touch