Related Documentation
- J Series
- Security Zones and Interfaces Overview in the Junos OS Security Configuration Guide

- SRX Series
- Example: Configuring Zones for a User Logical System
- User Logical System Configuration Overview
- Understanding Logical Systems Security Profiles
- Understanding Logical System Interfaces and Routing Instances
- Security Zones and Interfaces Overview in the Junos OS Security Configuration Guide

Understanding Logical System Zones
Security zones are logical entities to which one or more interfaces are bound. Security zones can be configured on the master logical system by the master administrator or on user logical systems by the user logical system administrator. On a logical system, the administrator can configure multiple security zones, dividing the network into network segments to which various security options can be applied.
The master administrator configures the maximum and reserved numbers of security zones for each user logical system. The user logical system administrator can then create security zones in the user logical system and assign interfaces to each security zone. From a user logical system, the user logical system administrator can use the show system security-profile zones command to view the number of security zones allocated to the user logical system and the show interfaces command to view the interfaces allocated to the user logical system.
![]() | Note: The master administrator can configure a security profile for the master logical system that specifies the maximum and reserved numbers of security zones applied to the master logical system. The number of zones configured in the master logical system count toward the maximum number of zones available on the device. |
The master and user administrator can configure the following properties of a security zone in a logical system:
- Interfaces that are part of a security zone.
- Screen options—For every security zone, you can enable a set of predefined screen options that detect and block various kinds of traffic that the device determines as potentially harmful.
- TCP-Reset—When this feature is enabled, the system sends a TCP segment with the RESET flag set when traffic arrives that does not match an existing session and does not have the synchronize flag set.
- Host inbound traffic—This feature specifies the kinds of traffic that can reach the device from systems that are directly connected to its interfaces. You can configure these parameters at the zone level, in which case they affect all interfaces of the zone, or at the interface level. (Interface configuration overrides that of the zone.)
There are no preconfigured security zones in the master logical system or user logical system.
The management functional zone (MGT) can only be configured for the master logical system. There is only one management interface per device and that interface is allocated to the master logical system.
The all interface can only be assigned to a zone in the master logical system by the master administrator.
The user logical system administrator can configure and view all attributes for a security zone in a user logical system. All attributes of a security zone in a user logical system are also visible to the master administrator.
Related Documentation
- J Series
- Security Zones and Interfaces Overview in the Junos OS Security Configuration Guide

- SRX Series
- Example: Configuring Zones for a User Logical System
- User Logical System Configuration Overview
- Understanding Logical Systems Security Profiles
- Understanding Logical System Interfaces and Routing Instances
- Security Zones and Interfaces Overview in the Junos OS Security Configuration Guide



