Release Notes for Policy Enforcer
Product Compatibility
This section describes the supported hardware and software versions for Policy Enforcer. For Security Director requirements, see the Security Director 19.4R1 release notes.
Supported Security Director Software Versions
Policy Enforcer is supported only on specific Security Director software versions as shown in Table 1.
Table 1: Supported Security Director Software Versions
Policy Enforcer Software Version | Compatible with Security Director Software Version | Junos OS Release (Juniper Sky ATP Supported Devices) |
|---|---|---|
19.4R1 | 19.4R1 | Junos 15.1X49-D120 or Junos 17.3R1 and later |
The times zones set for Security Director and Policy Enforcer must be the same.
Supported Devices
Table 2 lists the SRX Series devices that support Juniper Sky ATP and the threat feeds these devices support.
Table 2 lists the general Junos OS release support for each platform. However, each Policy Enforcer software version has specific requirements that take precedence. See Table 1 for more information.
Table 2: Supported SRX Series Devices with Juniper Sky ATP and Feed Types
Platform | Model | Junos OS Release | Supported Threat Feeds |
|---|---|---|---|
vSRX | 2 vCPUs, 4GB RAM | Junos 15.1X49-D60 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX300, SRX320 | Junos 15.1X49-D90 and later | C&C, GeoIP |
SRX Series | SRX340, SRX345, SRX550M | Junos 15.1X49-D60 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX1500 | Junos 15.1X49-D60 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX5400, SRX5600, SRX5800 | Junos 15.1X49-D62 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX4100, SRX4200 | Junos 15.1X49-D65 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX4600 | Junos 18.1R1 and later | C&C, antimalware, infected hosts, GeoIP |
SRX Series | SRX3400, SRX3600 | Junos 12.1X46-D25 and later | C&C, GeoIP |
SRX Series | SRX1400 | Junos 12.1X46-D25 and later | C&C, GeoIP |
SRX Series | SRX550 | Junos 12.1X46-D25 and later | C&C, GeoIP |
SRX Series | SRX650 | Junos 12.1X46-D25 and later | C&C, GeoIP |
Table 3 describes the hardware and software components that are compatible with JATP.
Table 3: Supported Hardware and Software Versions Compatible with JATP
Platform | Hardware Requirements | Software Versions |
|---|---|---|
vSRX | Junos 19.1R1.6 and above | |
SRX Series | SRX320, SRX300 | Junos 19.1R1 and above |
SRX Series | SRX4100, SRX4200, SRX4600 | Junos 15.1X49-D65 and above for SRX4100 and SRX4200 Junos 18.1R1 and above for SRX4600 |
SRX Series | SRX340, SRX345, SRX550m | Junos 15.1X49-D60 and above |
SRX Series | SRX5800, SRX5600, SRX5400 | Junos 15.1X49-D50 and above |
SRX Series | SRX1500 | Junos 15.1X49-D33 and above |
The SMTP e-mail attachment scan feature is supported only on the SRX1500, SRX4100, SRX4200, SRX5400, SRX5600, and SRX5800 devices running Junos OS Release 15.1X49-D80 and later. vSRX does not support the SMTP e-mail attachment scan feature.
In Policy Enforcer Release 18.3R1, Policy Enforcer supports SRX Series devices running Junos OS Release 17.3R1 and later.
Table 4 lists the supported EX Series and QFX Series switches.
Table 4: Supported EX Series Ethernet Switches and QFX Series Switches
Platform | Model | Junos OS Release |
|---|---|---|
EX Series | EX4200, EX2200, EX3200, EX3300, EX4300 | Junos 15.1R6 and later |
EX Series | EX9200 | Junos 15.1R6 and later |
EX Series | EX3400, EX2300 | Junos 15.1R6 and later Junos 15.1X53-D57 and later |
QFX Series | QFX5100, QFX5200 vQFX | Junos 15.1R6 and later Junos 15.1X53-D60.4 |
Table 5 lists the supported MX Series routers that support the DDoS and C&C feed types.
Table 5: Supported MX Routers and Feed Types
Platform | Model | Junos OS Release | Supported Juniper Sky ATP Threat Feeds |
|---|---|---|---|
MX Series | MX240, MX480, MX960 | Junos 14.2R1 and later | DDoS |
MX240, MX480, MX960 | Junos 18.4R1 and later | C&C (Mark MX Series router as perimeter device in secure fabric) | |
vMX | Junos 16.2R2.8 | - |
Table 6 shows the supported SDN and cloud platforms.
Table 6: Supported SDN and Cloud Platforms
Component | Specification |
|---|---|
VMware NSX for vSphere | 6.3.1 and later Note: For sites that are running vSphere 6.5, vSphere 6.5a is the minimum supported version with NSX for vSphere 6.3.0. |
VMware NSX Manager | 6.3.1 and later |
Third-Party Wired and Wireless Access Network
Table 7 lists the third-party support and required server.
Table 7: Third-party Wired and Wireless Access Network
Switch/Server | Notes |
|---|---|
Third-party switch | Any switch model that adheres to RADIUS IETF attributes and supports RADIUS Change of Authorization from ClearPass is supported by Policy Enforcer for threat remediation. |
ClearPass RADIUS server | Must be running software version 6.6.0. |
Cisco ISE | Must be running software version 2.1 or 2.2. |
Forescout CounterACT | Must be running software version 7.0.0. Note: To obtain an evaluation copy of CounterACT for use with Policy Enforcer, click here. |
Pulse Secure | Must be running software version 9.0R3. |
If you use Juniper Networks EX4300 Ethernet switch to integrate with the third-party switches, the EX4300 must be running Junos OS Release 15.1R6 or later.
Juniper Networks Contrail, Microsoft Azure, and AWS Specifications
Table 8 shows the required components for Juniper Networks Contrail.
Table 8: Juniper Networks Contrail Components
Model | Software Version | Supported Policy Enforcer Mode |
|---|---|---|
Juniper Networks Contrail | 5.0 | Microsegmentation and threat remediation with vSRX |
vSRX | Junos OS 15.1X49-D120 and later | Microsegmentation and threat remediation with vSRX |
Table 9 shows the required Policy Enforcer components for AWS.
Table 9: AWS Support Components
Model | Software Version | Supported Policy Enforcer Mode |
|---|---|---|
vSRX | Junos OS 15.1X49-D100.6 and later Junos OS 19.2R1 and later | vSRX policy based on workload discovery AWS with JATP |
To get started with Microsoft Azure, see Getting Started with Microsoft Azure.
Table 10 shows the required Policy Enforcer components for Microsoft Azure.
Table 10: Microsoft Azure Support Components
Model | Software Version | Supported Policy Enforcer Mode |
|---|---|---|
vSRX | Junos OS 15.1X49-D110.4 and later | vSRX policy based on workload discovery |
Virtual Machine
Policy Enforcer is delivered as an OVA or a KVM package to be deployed inside your VMware ESX or QEMU/KVM network with the following configuration:
2 CPU
8-GB RAM (16 GB recommended)
You must increase the RAM to 16-GB if you configure more than 256 custom dynamic addresses, allowlist, or blocklist.
120-GB disk space
Table 11: Supported Virtual Machine Versions
Virtual Machine | Version |
|---|---|
VMware | VMware ESX server version 4.0 or later or a VMware ESXi server version 4.0 or later |
QEMU/KVM | CentOS Release 6.8 or later |
Supported Browser Versions
Security Director and Policy Enforcer are best viewed on the following browsers.
Table 12: Supported Browser Versions
Browser | Version |
|---|---|
Google Chrome | 75.x |
Internet Explorer | 11 on Windows 7 |
Firefox | 67.0 and later |
Upgrade Support
Upgrading Policy Enforcer follows the same rules as for upgrading Security Director. You can upgrade only from the previously released version. This includes the minor releases. For example, you can upgrade to Policy Enforcer Release 19.4R1 only from Policy Enforcer Release 19.3R1. However, Policy Enforcer 19.3R1 can be upgraded from 18.4R1 -> 19.1R1 -> 19.1R2 -> 19.2R1->19.3R1 or 18.1R2 -> 18.2R1 -> 18.3R1 -> 18.4R1 -> 19.1R1 -> 19.1R2 -> 19.2R1 -> 19.3R1.
When you upgrade your system from Policy Enforcer Release 19.3R1 to Policy Enforcer Release 19.4R1, you must restart the Policy Enforcer virtual machine using the reboot command.
For complete upgrade instructions, see Upgrading Your Policy Enforcer Software.
For more information about the Security Director upgrade path, see Upgrading Security Director.
Known Behavior
Policy Enforcer supports only the default global domain in Junos Space Network Management.
When you are creating a connector for third-party devices, it is mandatory to add at least one IP subnet to a connector. You cannot complete the configuration without adding a subnet.
If you replace a device as part of RMA and if that device is already in secure fabric, you must remove the device from secure fabric and add it again. Otherwise, feeds are not downloaded to the replaced device.
JATP zone creation or assignment cannot be done in the General Setup Wizard.
Ensure that the time difference between the JATP and the SRX Series devices is less than 20 seconds to avoid the enrollment failure.
When the vSRX device is disenrolled with JATP and enrolled again, you might see the device shown twice in the Feed Sources page in Security Director.
When the feed source is JATP, you must change the Infected host state in the JATP portal. There are no Dashboard widgets to show the JATP related threats or Infected hosts in Security Director.
During the JATP enrollment, it may state that Juniper Sky ATP license is not present. You can ignore this warning.
For SRX Series devices in a chassis cluster, both primary and secondary chassis cluster nodes needs to be discovered in Security director before adding them to secure fabric. If only one chassis cluster node is discovered and added to secure fabric, the feed download does not work after failover to secondary node.
Known Issues
This section lists the known issues in Policy Enforcer Release 19.4R1.
For the most complete and latest information about resolved Policy Enforcer defects, use the Juniper Networks online Junos Problem Report Search application.
When a host is marked as infected host by Juniper Sky ATP, you cannot resolve the host from the Security Director monitoring page. You can only see the current status. If you try to take any action on the infected host, error occurs.
Workaround: Use the Juniper Sky ATP portal to take actions on the infected host. PR1458969
Resolved Issues
This section lists the issues fixed in Policy Enforcer Release 19.4R1.
For the most complete and latest information about resolved Policy Enforcer defects, use the Juniper Networks online Junos Problem Report Search application.
Unable to export Juniper Sky ATP hosts list from Security Director user interface. PR1461157
The addition of SRX Series Chassis Cluster to a secure fabric site fails for the first time. Workaround: To successfully add the cluster SRX Series to a secure fabric site at the first instance, Junos Space must first discover both the cluster nodes. PR1477825