New and Changed Features
This section describes new features as well as enhancements to existing features starting in Junos OS Release 18.2R1 for cSRX support.
New Features in Junos OS Release 18.2R1 for cSRX
Support for unified policies (SRX Series, cSRX)—Starting in Junos OS Release 18.2R1, unified policies are now supported on all SRX Series devices, allowing granular control and enforcement of dynamic Layer 7 applications within the traditional security policy.
Unified policies are the security policies, where you can use dynamic applications as match conditions along with existing 5-tuple or 6-tuple matching conditions (with user firewall) to detect application changes over time, and allow you to enforce a set of rules for the transit traffic.
Unified policies allow you to use dynamic application as one of the policy match criteria rule in each application. Application identification (AppID) is applied on the traffic, and the application is identified after several packets are checked.
Before identifying the final application, the policy cannot be matched precisely. A potential policy list is made available, and the traffic is permitted using the potential policy from the list.
After the application is identified, the final policy is applied to the session. Policy actions such as permit, deny, reject, or redirect is applied on the traffic as per the policy rules.
The following features support unified policies:
Application Identification (AppID)—Unified policy leverages the application identity information from the Application Identification (AppID). AppID provides the information such as dynamic application classification, default protocol and port of an application. For any application included in the dependent list of another application, AppID provides this information.
Application firewall (AppFW)—Unified policy configuration handles AppFW functionality and simplifies the task of configuring firewall policy to permit or block application traffic from the network.
If you configure a unified policy with a dynamic application as one of the matching conditions, then the configuration eliminates the additional steps involved in AppFW configuration—that is, configuring a security policy to invoke the application firewall service.
Starting in Junos OS Release 18.2R1, the Application Firewall (AppFW) functionality is deprecated— rather than immediately removed—to provide backward compatibility and a chance to bring your configuration into compliance with the new configuration.
The [edit security application-firewall] hierarchy and all configuration options under this hierarchy are deprecated.
ICAP service redirect—Internet Content Adaptation Protocol (ICAP) service redirect functionality is supported when the device is configured with unified policies.
IDP—Starting with Junos OS Release 18.2R1, with unified policies support, when a security rule has IDP enabled, the name of the actual IDP policy is replaced. This is to simplify IDP policy usage and to provide flexibility to have multiple policies active at the same time.
All IDP matches will now be handled within the unified policies. As a part of session interest check IDP will enabled if IDP policy is present in any of the matched rules.
IDP policy is activated in security policies, by permitting the IDP policy within the application services using the set security policies from-zone zone-name to-zone zone-name policy policy-name then permit application-services idp-policy idp-policy-name command.
Since IDP policy name is directly use in the security policy rule, the [edit security idp active-policy policy-name] statement is deprecated.
UTM—A new dynamic-application policy match condition is added to SRX Series devices, allowing an administrator to more effectively control the behavior of Layer 7 applications. To accommodate Layer 7 application-based policies in UTM, the [edit security utm default-configuration] command is introduced. If any parameter in a specific UTM feature profile configuration is not configured, then the corresponding parameter from the UTM default configuration is applied.
Additionally, during the initial policy lookup phase which occurs prior to a dynamic application being identified, if there are multiple policies present in the potential policy list which contains different UTM profiles, the SRX Series device applies the default UTM profile until a more explicit match has occurred.
cSRX Architecture Illustration
The cSRX Container Firewall inherits many of the branch SRX Series Junos OS features. This topic outlines the SRX series features supported by cSRX along with the features that are not applicable in a containerized environment.
SRX Series Features Supported on cSRX
Table 1 provides a high-level summary of the feature categories supported on cSRX and any feature considerations.
To determine the Junos OS features supported on cSRX, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. See Feature Explorer.
Table 1: SRX Series Features Supported on cSRX
Application Firewall (AppFW)
Application Identification (AppID)
Application Tracking (AppTrack)
Basic firewall policy
Brute force attack mitigation
CLI only. No J-Web support.
Two revenue network interfaces (eth1, and eth2).
Intrusion Detection and Prevention (IDP)
For SRX Series IPS configuration details, see:
IPv4 and IPv6
Malformed packet protection
Network Address Translation (NAT)
For SRX Series NAT configuration details, see:
Basic Layer 3 forwarding with VLANs.
Layer 2 through 3 forwarding functions: secure-wire forwarding or static routing forwarding
SYN cookie protection
For SRX Series user firewall configuration details, see:
Unified Threat Management (UTM)
For SRX Series UTM configuration details, see:
For SRX Series UTM antispam configuration details, see:
Zones and zone-based IP spoofing
SRX Series Features Not Supported on cSRX
Table 2 lists SRX Series features that are not applicable in a containerized environment, that are not currently supported, or that have qualified support on cSRX.
Table 2: SRX Series Features Not Supported on cSRX
SRX Series Feature
|Application Layer Gateways|
|Authentication with IC Series Devices|
Layer 2 enforcement in UAC deployments
Note: UAC-IDP and UAC-UTM also are not supported.
|Class of Service|
High-priority queue on SPC
|Data Plane Security Log Messages (Stream Mode)|
Flow monitoring cflowd version 9
Ping Ethernet (CFM)
Traceroute Ethernet (CFM)
|Ethernet Link Aggregation|
LACP in standalone or chassis cluster mode
Layer 3 LAG on routed ports
Static LAG in standalone or chassis cluster mode
|Ethernet Link Fault Management|
Physical interface (encapsulations)
|Flow-Based and Packet-Based Processing|
End-to-end packet debugging
Network processor bundling
Aggregated Ethernet interface
IEEE 802.1X dynamic VLAN assignment
IEEE 802.1X MAC bypass
IEEE 802.1X port-based authentication control with multisupplicant support
Interleaving using MLFR
PPPoE-based radio-to-router protocol
Promiscuous mode on interfaces
|IP Security and VPNs|
Acadia - Clientless VPN
Hardware IPsec (bulk crypto) Cavium/RMI
IPsec tunnel termination in routing instances
Multicast for AutoVPN
Suite B implementation for IPsec VPN
DS-Lite concentrator (also known as AFTR)
DS-Lite initiator (also known as B4)
|Log File Formats for System (Control Plane) Logs|
Binary format (binary)
Remote instance access
Spotlight Secure integration
CCC and TCC
Layer 2 VPNs for Ethernet connections
|Network Address Translation|
Maximize persistent NAT bindings
Note: Only supported on physical interfaces and tunnel interfaces, such as gr, ip, and st0. Packet capture is not supported on a redundant Ethernet interface (reth).
BGP extensions for IPv6
BGP route reflector
Bidirectional Forwarding Detection (BFD) for BGP
Layer 3 Q-in-Q VLAN tagging
|Unified Threat Management|
|Upgrading and Rebooting|
Boot instance configuration
Boot instance recovery
Junos Space Virtual Director
Changes in Behavior and Syntax
This section lists the changes in behavior of Junos OS features and changes from Junos OS Release 18.2R1 for the cSRX. For the most complete and latest information about changes in command behavior and syntax applicable to all SRX Series platforms in Junos OS Release 18.2R1, see Changes in Behavior and Syntax for SRX.
Application System Cache for Application Services (SRX Series, cSRX Instances)
Starting with Junos OS 18.2R1, the default behavior of the ASC has changed as follows:
Security services such as security policies, application firewall (AppFW), Juniper Sky ATP, IDP, and UTM do not use the ASC by default.
Miscellaneous services such as APBR and AppTrack use the ASC for application identification by default.
The change in the default behavior of the ASC affects the legacy Application Firewall (AppFW) functionality. With the ASC disabled by default for the security services starting in Junos OS Release 18.2 onwards, the AppFW will not use the entries present in the ASC.
You can revert to the ASC behavior as in Junos OS releases prior to 18.2 by using the set services application-identification application-system-cache security-services command.
The SRX Series device may become susceptible to application evasion techniques if the ASC is enabled for security services. We recommend that you enable the ASC only when the performance of the device in its default configuration (disabled for security services) is not sufficient for your specific use case.
Use the following commands to enable or disable the ASC:
Enable the ASC for security services:user@host# set services application-identification application-system-cache security-services
Disable the ASC for miscellaneous services:user@host# set services application-identification application-system-cache no-miscellaneous-services
Disable the enabled ASC for security services:user@host# delete services application-identification application-system-cache security-services
Enable the disabled ASC for miscellaneous services:user@host# delete services application-identification application-system-cache no-miscellaneous-services
You can use the show services application-identification application-system-cache command to verify the status of the ASC.
The following sample output provides the status of the ASC:
user@host>show services application-identification application-system-cache
Application System Cache Configurations: application-cache: on Cache lookup for security-services: off Cache lookup for miscellaneous-services: on cache-entry-timeout: 3600 seconds
For Junos OS Release prior to 18.2R1, application caching is turned on by default. You can manually turn this caching off using the CLI.