Junos For Security Platforms

JUNOS for Security Platforms
9.b
Instructor Guide
1194 North Mathilda Avenue

Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Course Number: EDU-JUN-JSEC
Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the
property of their respective owners.
JUNOS for Security Platforms Instructor Guide, Revision 9.b
Copyright 2009, Juniper Networks, Inc.
All rights reserved. Printed in USA.
Revision History:
Revision 9.aJuly 2009
Revision 9.bOctober 2009
The information in this document is current as of the date listed above.
The information in this document has been carefully verified and is believed to be accurate for software Release 9.6R1.13. Juniper Networks assumes no
responsibilities for any inaccuracies that may appear in this document. In no event will Juniper Networks be liable for direct, indirect, special, exemplary, incidental
or consequential damages resulting from any defect or omission in this document, even if advised of the possibility of such damages.
Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without notice.
YEAR 2000 NOTICE
Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The JUNOS Software has no
known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
SOFTWARE LICENSE
The terms and conditions for using Juniper Networks software are described in the software license provided with the software, or to the extent applicable, in an
agreement executed between you and Juniper Networks, or Juniper Networks agent. By using Juniper Networks software, you indicate that you understand and
agree to be bound by its license terms and conditions. Generally speaking, the software license restricts the manner in which you are permitted to use the Juniper
Networks software, may contain prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should
consult the software license for further details.
Contents
Chapter 1:
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Chapter 2:
Introduction to JUNOS Security Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Traditional Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Traditional Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Breaking the Tradition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
JUNOS Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Chapter 3:
Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
The Definition of Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Monitoring Security Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Lab 1: Configuring and Monitoring Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Chapter 4:
Security Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Overview of Security Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Policy Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Verifying Policy Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Policy Scheduling and Rematching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Policy Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Case Study: Monitoring Security Policies: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Case Study: Monitoring Security Policies: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Lab 2: Security Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Chapter 5:
Firewall User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Firewall User Authentication Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
Pass-Through Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8
Web Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
A Cleaner Method of Web Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Client Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Using External Authentication Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Verifying Firewall User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Lab 3: Configuring Firewall Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Chapter 6:
SCREEN Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Multilayer Network Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Stages and Types of Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Using JUNOS Software SCREEN OptionsReconnaissance Attack Handling . . . . . . . . . . . 6-16
Using JUNOS Software SCREEN OptionsDenial of Service Attack Handling . . . . . . . . . . . 6-29
Using JUNOS Software SCREEN OptionsSuspicious Packets Attack Handling . . . . . . . . . 6-47
Applying and Monitoring SCREEN Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
Lab 4: Implementing SCREEN Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
Contents iii
Chapter 7:
Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

NAT Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Destination NAT Operation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Source NAT Operation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Monitoring and Verifying NAT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Lab 5: Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Chapter 8:
IPsec VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

VPN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Secure VPN Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
IPsec Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Configuration of IPsec VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
IPsec VPN Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53
Lab 6: Implementing IPsec VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-70
Chapter 9:
Introduction to Intrusion Detection and Prevention . . . . . . . . . . . . . . . . . . . . 9-1

Introduction to JUNOS Software IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
IDP Policy Components and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Signature Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Case Study: Applying the Recommended IDP Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Monitoring IDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Lab 7: Implementing IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Chapter 10: High Availability Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

High Availability Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Chassis Cluster Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Chassis Cluster Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Chassis Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Chassis Cluster Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
Lab 8: Implementing Chassis Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57
Appendix A: Acronym List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B: Answer Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
iv Contents
Course Overview
JUNOS for Security Platforms covers the configuration, operation, and implementation of SRX
Series Services Gateways in a typical network environment. Key topics within this course
include security technologies such as security zones, security policies, intrusion detection and
prevention (IDP), Network Address Translation (NAT), high availability clusters, as well as details
pertaining to basic implementation, configuration, and management. The course includes
extensive hands-on labs configuring and monitoring JUNOS Software for SRX Series devices.
Objectives
After successfully completing this course, you should be able to perform the following:
Describe traditional routing and security and the current trends in

internetworking.
Provide an overview of SRX Series Services Gateways and software architecture.
Describe the logical packet flow and session creation performed by SRX Series
Services Gateways.
Describe, configure, and monitor zones.
Describe, configure, and monitor security policies.
Describe, configure, and monitor firewall user authentication.
Describe various types of network attacks.
Configure and monitor SCREEN options to prevent network attacks.
Explain, implement, and monitor NAT as implemented on JUNOS security

platforms.
Explain the purpose and mechanics of IPsec VPNs.
Implement and monitor policy-based and route-based IPsec VPNs.
Utilize and update the IDP signature database.
Configure and monitor IDP policy with policy templates.
Describe, configure, and monitor high availability chassis clusters.
Intended Audience
The course content is aimed at operators of SRX Series Services Gateways. These operators
include network engineers, administrators, support personnel, and reseller support personnel.
Course Level
JUNOS for Security Platforms is an intermediate level course.
Prerequisites
Students should have basic networking knowledge and an understanding of the OSI model and
the TCP/IP protocol suite. Students should also attend the Introduction to JUNOS Software
(IJS) course and the JUNOS Routing Essentials (JRE) course, or have equivalent experience
prior to attending this class.
Course Overview v
Course Agenda
Day 1
Chapter 1: Course Introduction
Chapter 2: Introduction to JUNOS Security Platforms
Chapter 3: Zones
Lab 1: Configuring and Monitoring Zones
Chapter 4: Security Policies
Lab 2: Security Policies
Day 2
Chapter 5: Firewall User Authentication
Lab 3: Configuring Firewall Authentication
Chapter 6: SCREEN Options
Lab 4: Implementing SCREEN Options
Chapter 7: Network Address Translation
Lab 5: Network Address Translation
Day 3
Chapter 8: IPsec VPNs
Lab 6: Implementing IPsec VPNs
Chapter 9: Introduction to Intrusion Detection and Prevention
Lab 7: Implementing IDP
Chapter 10: High Availability Clustering
Lab 8: Implementing Chassis Clusters
vi Course Agenda
Document Conventions
CLI and GUI Text
Frequently throughout this course, we refer to text that appears in a command-line interface
(CLI) or a graphical user interface (GUI). To make the language of these documents easier to
read, we distinguish GUI and CLI text from chapter text according to the following table.
Style
Description
Usage Example
Franklin
Gothic
Normal text.
Most of what you read in the Lab

Guide and Student Guide.
Courier
New
Console text:
Screen captures
Noncommand-related
syntax
GUI text elements:
Menu names
Text field entry
commit complete
Exiting configuration
mode
Select File > Open, and then
click Configuration.conf in
the Filename text box.
Input Text Versus Output Text

You will also frequently see cases where you must enter input text yourself. Often this will be
shown in the context of where you must enter it. We use bold style to distinguish text that is
input versus text that is simply displayed.
Style
Description
Usage Example
Normal CLI
No distinguishing variant.
Physical interface:fxp0,
Enabled
Normal GUI
CLI Input
GUI Input
View configuration history by

clicking Configuration >
History.
Text that you must enter.
lab@San_Jose> show route

Select File > Save, and enter
config.ini in the Filename
field.
Document Conventions vii
Defined and Undefined Syntax Variables

Finally, this course distinguishes between regular text and syntax variables, and it also
distinguishes between syntax variables where the value is already assigned (defined variables)
and syntax variables where you must assign the value (undefined variables). Note that these
styles can be combined with the input style as well.
Style
Description
Usage Example
CLI
Variable
Text where variable value is already

assigned.
policy my-peers
Text where the variables value is

the users discretion and text where
the variables value as shown in the
lab guide might differ from the
value the user must input.
Type set policy

policy-name.
Click on my-peers in the dialog.
GUI
variable
CLI
Undefined
GUI
Undefined
viii Document Conventions
ping 10.0.1.1
Select File > Save, and enter
filename in the Filename field.
Additional Information
Education Services Offerings
You can obtain information on the latest Education Services offerings, course dates, and class
locations from the World Wide Web by pointing your Web browser to:
http://www.juniper.net/training/education/.
About This Publication

The JUNOS for Security Platforms Student Guide was developed and tested using software
version 9.6R1.13. Previous and later versions of software might behave differently so you
should always consult the documentation and release notes for the version of code you are
running before reporting errors.
This document is written and maintained by the Juniper Networks Education Services
development team. Please send questions and suggestions for improvement to
training@juniper.net.
Technical Publications
You can print technical manuals and release notes directly from the Internet in a variety of
formats:
Go to http://www.juniper.net/techpubs/.
Locate the specific software or hardware release and title you need, and choose
the format in which you want to view or print the document.
Documentation sets and CDs are available through your local Juniper Networks sales office or
account representative.
Juniper Networks Support

For technical support, contact Juniper Networks at http://www.juniper.net/customers/
support/, or at 1-888-314-JTAC (within the United States) or 408-745-2121 (from outside the
United States).
Additional Information ix
x Additional Information

Chapter 1: Course Introduction
This Chapter Discusses:
Objectives and course content information;
Additional Juniper Networks, Inc. courses; and
Juniper Networks Technical Certification Program (JNTCP).
Chapter 12 Course Introduction
Introductions
This slide asks several questions for you to answer during class introductions.
Course Introduction Chapter 13
Course Contents
This slide lists the topics we discuss in this course.
Prerequisites
This slide lists the prerequisites for this course.
General Course Administration

This slide documents general aspects of classroom administration.
Training and Study Materials

This slide describes Education Services materials that are available for reference both
in the classroom and online.
Additional Resources
This slide describes additional resources available to assist you in the installation,
configuration, and operation of Juniper Networks products.
Satisfaction Feedback
Juniper Networks uses an electronic survey system to collect and analyze your
comments and feedback. Depending on the class you are taking, please complete the
survey at the end of the class, or be sure to look for an e-mail about two weeks from
class completion that directs you to complete an online survey form. (Be sure to
provide us with your current e-mail address.)
Submitting your feedback entitles you to a certificate of class completion. We thank
you in advance for taking the time to help us improve our educational offerings.
Juniper Networks Education Services Curriculum

Juniper Networks Education Services can help ensure that you have the knowledge
and skills to deploy and maintain cost-effective, high-performance networks for both
enterprise and service provider environments. We have expert training staff with deep
technical and industry knowledge, providing you with instructor-led hands-on courses
as well as convenient, self-paced eLearning courses.
You can access the latest Education Services offerings covering a wide range of
platforms at http://www.juniper.net/us/en/training/technical_education/.
JNTCP
The Juniper Networks Technical Certification Program (JNTCP) consists of
platform-specific, multitiered tracks that enable participants to demonstrate, through
a combination of written proficiency exams and hands-on configuration and
troubleshooting exams, competence with Juniper Networks technology. Successful
candidates demonstrate thorough understanding of Internet and security
technologies and Juniper Networks platform configuration and troubleshooting skills.
You can learn more information about the JNTCP at
http://www.juniper.net/training/certification/.
Certification Levels
Each JNTCP track has one to four certification levels. Associate-level and
Specialist-level exams are computer-based exams composed of multiple choice
questions. These computer-based exams are administered at Prometric testing
centers worldwide and have no prerequisite certification requirements.
Professional-level and Expert-level exams are composed of hands-on lab exercises
that are administered at select Juniper Networks testing centers. Professional-level
and Expert-level exams require that you first obtain the next lower certification in the
track. Please visit the JNTCP Web site at
http://www.juniper.net/training/certification/ for detailed exam information, exam
pricing, and exam registration.
Prepping and Studying

This slide lists some options for those interested in prepping for Juniper Networks
certification.
Any Questions?
If you have any questions or concerns about the class you are attending, we suggest
that you voice them now so that your instructor can best address your needs during
class.

Chapter 2: Introduction to JUNOS Security
Platforms
Traditional routing and security implementations;
Current trends in internetworking;
SRX Series Services Gateways;
JUNOS Software for the SRX Series; and
Physical and logical packet flow through SRX Series devices.
Chapter 22 Introduction to JUNOS Security Platforms
Traditional Routing
The slide lists the topics we cover in this chapter. We discuss the highlighted topic
first.
Introduction to JUNOS Security Platforms Chapter 23
Built to Forward Packets

The primary responsibility of a router is to forward packets using Layer 3 IP addresses
found in an IP packet header. To forward packets, the router must have a path
determination mechanism. This mechanism could be statically assigned routes,
routing protocols, or policy-based routing.
Packet Processing Is Stateless

Traditionally, routers process packets in a stateless fashion. Routers do not keep track
of bidirectional sessions; they forward each packet individually based on the packet
header.
Separate Broadcast Domains and Provide WAN Connectivity

Routers were originally used to separate broadcast domains. With the introduction of
advanced switching technologies and the birth of virtual LAN (VLAN) standards,
broadcast domains can also be separated using switches. That capability, however,
does not address inter-VLAN connectivity, which still necessitates the use of routers
for forwarding traffic between VLANs. Furthermore, routers provide WAN connectivity
at the network edge.
Layer 3 Packet Forwarding

Routers perform Layer 3 packet forwarding using routing table entries. Routers build
routing tables based on the results of dynamic routing protocols (for example, RIP,
OSPF, IS-IS, and BGP), statically entered routes, or both of these methods. Note that
routers forward packets based on the longest prefix match. For example, in the
graphic on the slide, Router A selects interface ge-0/0/2 to send traffic to destination
10.3.3.10 because 10.3.3.10/32 is a longer prefix match than 10.3.3.0/24. If
entry 10.3.3.10/32 does not exist in the routing table, the router selects interface
ge-0/0/0 as the next hop for the same packet flow.
Promiscuous Behavior of a Traditional Router

A traditional router is a promiscuous device that performs stateless packet
processing. It is promiscuous because once it is configured, it immediately forwards
all traffic by default (provided, of course, that some combination of static and dynamic
routing is configured). Typically, a router operates only at Layer 3 and does not
recognize any security threats in higher-layer protocols. Furthermore, a traditional
router operates per packet, which adds to its fundamentally insecure nature, as it
cannot detect malformed sessions. The network and the router itself are immediately
vulnerable to all security threats.
Typical Treatment of Security

Other than implementing standard access control using IP header information, most
routers are not equipped to secure a network. Traditionally, a full security solution
involves adding a separate firewall device.
Typical Router Positioning

Emphasize the
pointers identified with
deployment of a typical
router, as identified on
Slide 4WAN
connectivity,
separation of
broadcast domains,
and ability to forward
packets.
Enterprise customer premise applications are served by the J Series family of service
routers and, in the case of larger enterprises, M Series routers. Enterprise data center
applications can also be served by M Series routers. Internet service provider (ISP)
networks can be served by M Series, MX Series, or T Series routers. J Series, M Series,
MX Series and T Series routers support the rich routing and class-of-service (CoS)
features needed by networks, and maintain value, stability, and predictably high
performance.
Traditional Security
The slide highlights the topic we discuss next.
Adding Security to the Network

Standalone routers do not provide adequate security to enterprise networks and data
centers. As networks continue to expand, network applications continue to diversify
and expand, and as new methods of remote communications such as telecommuting
increase, the need for added security becomes apparent. Typically, a standalone
firewall is added to the network, increasing costs and maintenance.
Requirements for Firewall Devices

A firewall device must be capable of the following:
Stateful packet processing based on contents of IP and higher-level

packet information, which includes TCP/UDP and the Application Layer;
Network Address Translation (NAT) and Port Address Translation (PAT),

achieving private-to-public translations and vice versa; and
Establishing virtual private networks (VPNs) compounded with

authentication and encryption.
Additional Services
The growth in network security has resulted in additional services provided by
standalone firewalls such as Secure Sockets Layer (SSL) network access, Intrusion
Detection and Prevention (IDP), application-level gateway (ALG) processing, and more.
Firewall: Stateful Packet Processing

Explain to the students
that if the main job of
a router is to allow
packets through (based
on routing
information), the main
job of a firewall is to
protect networks. Also,
explain that the source
port number is a
random number.
Because the main job of a firewall is to protect networks and devices, fundamental
firewall intelligence consists of the ability to make packet processing decisions based
on IP packet header information, including its upper layers.
Stateful packet processing involves the creation of a unidirectional flow, which
consists of six elements of informationsource IP address, destination IP address,
source port number, destination port number, protocol number, and a session token.
The session token is derived from a combination of a routing instance and a zone. The
outgoing flow initiates a session table entry and the expected return flow for that
packet. Both outgoing and incoming flows comprise the session and are entered into
the session table. The session table enables bidirectional communication without any
additional configurational steps for return traffic.
Firewall: NAT and PAT

When a security device resides at the edge of a network, it must be able to replace
private, nonroutable addresses with public addresses before traffic is sent to the
public network. Translation can consist of replacing the IP address, port numbers, or
both, depending on the configuration. Note that NAT can be used on both source and
destination addresses, and PAT can be used on both source and destination ports.
Firewall: Virtual Private Networks

You can use a firewall to build VPNs using the public network as an access medium
between two private sites. As such, the firewall must be able to perform the following:
Encapsulate the original traffic in a packet that can be transported over

the public network;
Encrypt the original packet so that it cannot be easily decoded if it is

intercepted on the public network; and
Authenticate the originating device as a member of the VPNnot a

random device operating on the public network.
Firewall Positioning
The slide illustrates a typical enterprise deployment of firewall devices. Small office
and home offices or retail storefronts use branch firewall devices to provide secured
access to the Internet, as well as an IP Security (IPsec) VPN tunnel back to a central
site.
The enterprise firewall device at the central site provides VPN termination and firewall
protection between internal zones as well as from the Internet, and it might also
provide other security services such as IDP, Web filtering, and antispam services.
Breaking the Tradition

Current Trends
As boundaries of networks are becoming less clear, so are the requirements of
network edge devices. More and more enterprises are interconnecting themselves
through an ISPs virtual cloud by using IP. The Internet has created possibilities and
opportunities for businesses and markets, and it has erased the concept of distance.
With the Internet, however, came network vulnerabilities. Traditionally, routers have
been positioned on the edge of an enterprise network and provided very basic
network security such as stateless firewall filters. Network administrators became
used to relying on separate firewall devices positioned within enterprise DMZs. The
consolidation of these functions at the network edge improves costs, reduces
management overhead, and increases operational simplicity.
A New Perspective
The graphic on the slide illustrates how a device with strong routing and firewall
features can be positioned at network boundaries. Remote offices can deploy SRX
Series branch platforms running JUNOS Software to provide both routing and security
features.
The SRX Series Services Gateway at the enterprise headquarters in this example also
provides routing and security in a high-density, modular chassis. The Dynamic
Services Architecture allows SRX Series Services Gateways to leverage new services
with appropriate processing capabilities without sacrificing overall system
performance. SRX Series Services Gateways are next-generation systems designed to
meet the network and security requirements for the enterprise and service provider
infrastructure, and facilitate data center consolidation, rapid managed services
deployments, and security services aggregation.
SRX Series High-End Systems

The Juniper Networks SRX Series Services Gateways for the high end are
next-generation services gateways based on a revolutionary new architecture that
provides market-leading scalability and service integration. These devices are ideally
suited for large enterprise and service provider networks:
Securing large enterprise data centers;
Securing service provider and collocated data centers;
Aggregating departmental or segmented security solutions; and
Securing managed services and core service provider infrastructure.
Based on the Dynamic Services Architecture, the SRX Series provides unrivaled
scalability. Each services gateway can support almost linear scalability with each
additional Services Processing Card (SPC), enabling a fully equipped SRX5800 to
support more than 120 Gbps of firewall throughput. The SPCs are designed to support
a wide range of services enabling future support of new capabilities without the need
for service-specific hardware. Using SPCs on all services ensures that no resources
are idle, based on specific services being used, maximizing the utilization of equipped
hardware.
The scalability and flexibility of the SRX5000 and SRX3000 lines of services gateways
are supported by equally robust interfaces. The SRX Series high-end line employs a
modular approach to interfaces where the gateway can be equipped with a flexible
number of input/output cards (IOCs).
Continued on next page.
SRX Series High-End Systems (contd.)

With the IOCs sharing the same interface slot as the SPCs, you can configure the
gateway to support the ideal balance of processing, input, and output. Hence, you can
tailor each deployment of the SRX Series to specific network requirements. With this
flexibility, you can configure the SRX5800 to support more than 400 gigabit ports,
with choices of Gigabit Ethernet or 10-Gigabit Ethernet.
The feature integration on the SRX Series is enabled by Juniper Networks JUNOS
Software. By combining the routing heritage of JUNOS Software and the security
heritage of ScreenOS, the SRX Series is equipped with a robust list of features that
include firewall, intrusion detection and prevention (IDP), denial of service (DoS),
Network Address Translation (NAT), and quality of service (QoS).
SRX Series High-End System Components

The SRX Series line of high end systems includes the following integral components:
Input/output card (IOC): To provide the most flexible solution, the

SRX Series employs the same modular architecture for SPCs and IOCs.
With the flexibility to install an IOC or an SPC on a given slot, the SRX
Series can be equipped to support an ideal balance between interfaces
and processing capabilities.
Network Processing Card (NPC): To ensure maximum processing

performance and flexibility, the SRX3000 line utilizes NPCs to distribute
inbound and outbound traffic to the appropriate SPCs and IOCs, to apply
QoS, and to enforce DoS and distributed DoS (DDoS) protections. In the
SRX5000 line, the NPC is integrated into the IOC. Note that a minimum of
one NPC must be installed in platforms in the SRX3000 line to ensure
proper functionality.
Services Processing Card (SPC): SPCs are designed to process all

available services on the gateway. Without the need for dedicated
hardware for specific services or capabilities, no instances exist in which
a piece of hardware is taxed to the limit while other hardware is sitting
idle. All the processing capabilities of the SPCs are designed to process
all configured services on the gateway. Note that a minimum of one SPC
must be installed in an SRX Series high-end system to ensure proper
functionality.
Switch Control Board (SCB): The SCB monitors and controls system
functions and provides the interconnections to all the IOCs within a
chassis through the switch fabrics integrated into the SCB. At least one
SCB is required for the system to function. Two or three SCBs increase
capacity or provide redundancy, depending on the specific platform.
Routing Engine (RE): The RE is an Intel-based PC platform that runs

JUNOS Software. Software processes that run on the RE maintain the
routing tables, manage the routing protocols, control some chassis
components, and provide the interface for system management and user
access to the device.
For more information on specific SRX Series high-end system models and hardware,
visit the Juniper Networks Web site for technical publications at
http://www.juniper.net/techpubs.
Physical Packet Flow for High-End Security Platforms

Note that the
performance of a
high-end SRX Series
Services Gateway
depends on balancing
IOCs with SPCs and
NPCs. Each SPC can
support 20 Gbps of
firewall throughput.
The SPC serving as the
CP will use one half of
its services processing
performing its role as a
CP, leaving only
10 Gbps available for
firewall processing.
The slide illustrates physical packet flow through a high-end security platform running
JUNOS Software. The packet flow coverage includes the SRX5000 and the SRX3000
line of products.
Physical packet flow through a high-end security platform proceeds through the
following sequence of steps:
1.
A packet enters the security platform through the IOC.

(Step 1.5: Oversubscription control applies at the IOC.)
2.
The packet traverses the switch fabric from the IOC to the NPC. (In the
SRX5000 line of products, the NPC integrates with the IOC.) The NPC
performs a flow lookup. If the packet belongs to an existing flow, the NPC
forwards the packet to the SPC associated with the packets session. If
the flow does not currently exist, the NPC installs a new session for the
flow and assigns the flow to an SPC for processing. The NPC also
performs QoS, policing, and shaping.
3.
The packet traverses the switch fabric to its associated SPC, where
security processing and forwarding or routing occurs.
4.
The packet traverses the switch fabric back to an NPC where additional
packet processing such as shaping and QoS occurs.
5.
The packet traverses the switch fabric to the IOC associated with the
egress interface and travels to the attached physical medium.
SRX Series Branch Devices

Juniper Networks SRX Series Services Gateways for the branch provide essential
capabilities that connect, secure, and manage workforce locations sized from
handfuls to hundreds of users. By consolidating fast, highly available switching,
routing, security, and applications capabilities in a single device, enterprises can
economically deliver new services, safe connectivity, and a satisfying end user
experience.
SRX Series for the branch operates with JUNOS Software, the proven operating system
used by core Internet routers in all of the top 100 service providers around the world.
The rigorously tested carrier-class routing features of IP version 4 (IPv4)/IP version 6
(IPv6), OSPF, BGP, and multicast have been proven in over 10 years of worldwide
deployments.
SRX Series Services Gateways for the branch provide perimeter security, content
security, access control, and network-wide threat visibility and control. Best-in-class
firewall and VPN technologies secure the perimeter with minimal configuration and
consistent performance. By using zones and policies, even new network
administrators can configure and deploy an SRX Series branch device quickly and
securely. Policy-based VPNs support more complex security architectures that require
dynamic addressing and split tunneling. For content security, SRX Series for the
branch offers a complete suite of Unified Threat Management (UTM) services
consisting of intrusion prevention system (IPS), antivirus, antispam, Web filtering, and
data loss prevention through content filtering to protect your network from the latest
content-borne threats.
SRX Series Branch Devices (contd.)

Select models feature Content Security Accelerator for high-performance IPS and
antivirus performance. JUNOS security platforms for the branch integrate with other
Juniper Networks security products to deliver enterprise-wide unified access control
and adaptive threat management. These capabilities give security professionals
powerful tools in the fight against cybercrime and data loss.
Branch Platform System Components

The SRX Series line of JUNOS security platforms include the following integral
components:
Multi-core processing unit: The processing unit uses multiple hardware

threads to provide data plane services including security services and
control plane services to the branch device. The SRX branch line of
platforms utilizes a system-on-a-chip (SOC) multi-core processor that
provides the control and data plane functions as well as additional
services such as Ethernet controller technology and a cryptographic
engine.
Physical Interface Modules (PIMs): The SRX Series line of branch and
enterprise devices provide various media interfaces known at PIMs. The
media support includes 10/100 Ethernet, 10/100/1000 Ethernet,
Gigabit Ethernet, T1/E1, T3/E3, ISDN, serial, ADSL and G.SHDSL
interfaces, depending on the model. Some SRX Series branch models
also contain an ExpressCard slot for utilization with a 3G wireless card to
serve as a backup for primary interfaces. Select models contain Power
over Ethernet (PoE) enabled ports.
Services and Routing Engine (SRE): The SRE, a field replacable unit in
the SRX650, houses the processing unit and provides processing power
for security services; routing protocol processes; and other software
processes that control the services gateway interfaces, some of the
chassis components, system management, and user access to the
device.
For more information on specific JUNOS security platform branch models and
hardware, visit the Juniper Networks Web site for technical publications at
http://www.juniper.net/techpubs.
Physical Packet Flow for Branch Security Platforms

In SRX Series branch gateways, control and data plane separation is maintained using
multiple threads on multiple cores within the processor. One hardware core is used for
control plane functions. Packets ingress the device through built-in ports or PIM ports
and pass to an Ethernet switch, which acts as the switch fabric for the device. In SRX
Series branch devices, local switching occurs at the switch so that the CPU or the NPU
is not taxed with switched traffic. As a result, security services such as security policy
and IDP are not available with locally switched traffic. The switch performs CoS
classification and traffic policing. It then passes non-locally switched packets to the
processor where security services, routing lookup, and forwarding lookup is
performed. SRX branch devices then send egress packets to the appropriate egress
port by means of the switch.
Depending on the device type, the CPU might perform hardware acceleration and
cryptographic acceleration. Some branch devices are equipped with a separate
regular expression (REGEX) content processor to provide hardware-based pattern
matching for IDP and antivirus acceleration.
JUNOS Software Architecture

JUNOS Security Platforms Versus a Traditional Router

The traditional router and a JUNOS security platform have completely different starting
points with respect to security and traffic flow.
The traditional router begins by forwarding all traffic. Thus, the network is vulnerable
to all threats. You add security policies to reduce vulnerability until you reach the ideal
configuration. Because the traditional router begins as completely promiscuous and it
requires that you add security policies, a greater chance exists that the network will
remain vulnerable to some threats.
An SRX Series Services Gateway running JUNOS Software begins by forwarding no
traffic. The network is secure but not functional. You add rules to allow traffic until you
reach the ideal configuration. Because a JUNOS security platform begins by
forwarding no traffic and because you must add rules, a greater likelihood exists that
the network will restrict undesirable traffic.
JUNOS for Security Platforms Merges Routing and Security

The new features of JUNOS for security platforms bring new core security capabilities
to JUNOS Software. Because the forwarding algorithm is session-based, security
features are tightly integrated into the forwarding plane, improving security
performance. Session-based forwarding and stateful firewall features derive from
Juniper Networks ScreenOS software.
JUNOS security platforms incorporate ALG functionality, IPsec VPNs, and screen
protection in a flowd module within JUNOS Software. Juniper Networks world-class IDP
technology is also fully integrated into JUNOS for security platforms. We discuss these
features later in this course.
JUNOS Software Elements

SRX Series Services Gateways use JUNOS Software as their base operating system. As
such, these devices deploy all the industry-proven processes of JUNOS Software, such
as the routing process, management process, device control process, and others.
Another building element of JUNOS Software for security platforms is session-based
forwarding, thereby resulting in a strong suite of security features.
Packet-Based JUNOS Forwarding

The JUNOS Software basic control plane, routing protocol process implementation,
per-packet stateless filters, policers, and CoS functions are all packet based.
Furthermore, other nonsecurity-related features, such as all interface encapsulations
and de-encapsulations, use industry-proven JUNOS Software. You can configure SRX
Series Services Gateways using either the CLI or J-Webthe JUNOS Software-based
graphical user interface (GUI).
Session-Based Forwarding
Note that SRX Series
branch platforms have
the capability to
operate strictly in
packet-based mode.
This mode is
configured using the
set security
forwarding-opti
ons family mpls
mode
packet-based
configuration
command and requires
disabling all security
services. Because this
class is focused on
security features and
this functionality will
change in the near
future, we do not cover
this setting.
JUNOS Software for security platforms leverages ScreenOS softwares security

features as well as its flow-based nature. The first packet entering the device follows a
series of path and policy determination schemes. JUNOS Software caches the session
information, the creation of which is triggered by the first packet of the flow. The
cached session is used by subsequent packets of that same flow and the reverse flow
of that session. Using the flow module, which is integrated into the forwarding path,
the hardware performs data-plane packet forwarding. Because JUNOS Software for
security platforms is security-based, all IPv4 packets entering the services gateway on
an interface associate with an incoming zone. Likewise, all IPv4 packets exiting the
device on an interface associate with an outgoing zone. JUNOS Software for security
platforms adds a bundle of high-security features to the regular features of a router,
including stateful firewall, VPNs, NAT, ALGs, and IDP.
Control Plane
The control plane on a JUNOS security platform is implemented using the Routing
Engine. The control plane consists of the JUNOS Software kernel, various processes,
chassis management, user interface, routing protocols and some security features.
Many of the security features resemble ScreenOS features, including the network
security process, the VPN process, the authentication process, and Dynamic Host
Configuration Protocol (DHCP). For its control plane, JUNOS Software for security
platforms deploys these features along with well-known, traditional JUNOS Software
features.
Data Plane
The data plane on JUNOS security platforms, implemented on IOCs, NPCs, and SPCs
for high-end devices and on CPU cores and PIMs for branch devices, consists of
JUNOS Software packet-handling modules compounded with a flow engine and
session management like that of the ScreenOS software. Intelligent packet processing
ensures that one single thread exists for packet flow processing associated with a
single flow. Real-time processes enable JUNOS Software to perform session-based
packet forwarding.
Logical Packet Flow Details

Plan to spend some
time talking about this
slide in detail. It is a
fundamental concept
and we reuse the
diagram throughout
the course.
JUNOS security platforms handle an incoming packet as follows:

1.
The software applies stateless policing filters and CoS classification to

the packet at the ingress.
2.
If the packet does not drop, the software performs a session lookup to
determine whether the packet belongs to an existing session. JUNOS
Software matches on six elements of traffic information for this
determinationsource IP address, destination IP address, source port
number, destination port number, protocol number, and a session token.
3.
If the packet does not match an existing session, the software creates a
new session for it. This process is referred to as the first-packet path. If
the packet matches a session, the software performs fast-path
processing.
Logical Packet Flow Details (contd.)

The first packet of a flow is subject to first-packet-path processing. The software takes
the following steps during first-packet-path processing:
1.
Based on the protocol used and its session layer (TCP or UDP), the
software starts a session timer. For TCP sessions, the default timeout is
30 minutes. For UDP sessions, the default timeout is 1 minute. These
values are the defaults, and you can change them.
2.
The software applies firewall SCREEN options.
3.
If destination NAT is used, the software performs address allocation.
4.
Next, the software performs the route lookup. If a route exists for the
destination prefix, the software takes the next step. Otherwise, it drops
the packet.
5.
The software determines the packets incoming zone by the interface

through which it arrives. The software also determines the packets
outgoing zone by the forwarding lookup.
6.
Based on incoming and outgoing zones, the corresponding security policy

is determined and a security policy lookup takes place. The software
checks the packet against defined policies to determine how to treat the
packet.
7.
If source NAT is used, the software performs address allocation.
8.
The software sets up the ALG service vector.
9.
The software creates and installs the session. Furthermore, the software
caches the decisions made for the first packet into a flow table, which
subsequent packets of that flow use.
10.
The packet now enters the fast-path processing.
Subsequent packets of a flow are all subject to fast-path processing. The software
takes the following steps during fast-path processing:
1.
The software applies firewall SCREEN options.
2.
The software performs TCP checks.
3.
The software applies NAT.
4.
The software applies an ALG.
5.
The software applies packet forwarding features, which include the

following:
a.
Stateless packet filters;
b.
Traffic shaping by packet; and
c.
Packet encapsulation and transmission.
Session Maintenance
When a packet enters the system and does not match any existing sessions, JUNOS
Software creates a new session based on routing and security policy information.
Once this new session is created, the software puts it into a session hash table for
further packet matching and processing. Depending on the protocol and service (TCP
or UDP), the session is programmed with a default timeout. The default TCP timeout is
30 minutes and the UDP default timeout is 1 minute.
Session Cleanup
If no traffic matches the session during the service timeout, JUNOS Software ages out
the session and frees it to a common resource pool for a later reuse.
Session Run-Time Changes Propagation

The flow module is responsible for propagating any run-time changes that happen
during the lifetime of the session. This propagation allows new packets that match the
session to forward using up-to-date information. Routing run-time changes always
propagate into the session. Security policy run-time changes might propagate into the
session in progress, based on the corresponding security policy configuration. We
discuss this topic more thoroughly in a subsequent chapter.
Packet Flow Example: Part 1

We now apply the described decision process to a specific example. As the slide
shows, Host-B at 10.1.20.5 wants to initiate an HTTP session with the Web server at
200.5.5.5. The traffic passes through an SRX Series Services Gateway and is
therefore subject to the decision process.

The slide shows the packet as received by the SRX Series Services Gateway on
interface ge-0/0/1. Following the flowchart, you can track the progress of the packet
through the services gateway:
1.
Based on a lookup in the session table, the JUNOS Software determines

that this session is not an existing session.
2.
The forwarding table shows that the software detects how to reach the
destination network.
3.
Now that the forwarding lookup is complete, the software can determine
the ingress and egress zones required for security policy evaluation.

The following is a continuation of the list from the previous page:
4.
The packet is from host 10.1.20.5 and is an HTTP packet. This packet
matches the policy statement on the slide. The action for this particular
type of traffic is to permit it.
5.
The SRX Series Services Gateway adds the flow information to the
session table. At the same time a return flow is automatically created and
also adds to the session table.
6.
The SRX Series Services Gateway then forwards the packet out
interface ge-1/0/0 (as determined by the destination lookup). JUNOS
Software allows traffic in both directions for this particular session to
pass without any subsequent policy evaluation.
This Chapter Discussed:
Traditional routing and security implementations;
Current trends in internetworking;
SRX Series Services Gateways;
JUNOS Software for the SRX Series; and
Physical and logical packet flow through a JUNOS security platform.
Review Questions
1.
Traditionally, routers process packets on a per-packet basis.
2.
Traditionally, firewalls process packets based on stateful flows.
3.
JUNOS for security platforms uses session-based packet forwarding and by default does not
allow traffic to pass, whereas traditional JUNOS Software uses packet-based forwarding and
by default allows all traffic to pass.
4.
The first packet of a new session is subject to first-path packet processing.

Chapter 3: Zones
Chapter 32 Zones
Zones and their purpose;
Types of zones;
Application of zones;
Configuring zones; and
Monitoring zones.
The Definition of Zones

first.
Zones Chapter 33
Zone Definition
A zone is a collection of one or more network segments sharing identical security
requirements. To group network segments within a zone, you must assign logical
interfaces from the device to a zone.
Traffic Regulation Through a JUNOS Security Platform

The fxp0 interface is
an out-of-band
management interface
that will not pass
transit traffic. If extra
protection is desired
from traffic entering
the fxp0 interface,
consider using a
stateless firewall filter
and applying it as an
input filter to the lo0
loopback interface.
Chapter 34 Zones
Zones enable network security segregation. Security policies are applied between
zones to regulate traffic through the JUNOS security platform. By default, all network
interfaces belong to the system-defined Null Zone. All traffic to or from the Null Zone is
dropped. Special interfaces including the fxp0 management ethernet interface
present in some SRX platforms, chassis cluster fabric interfaces, and internal system
em0 interfaces cannot be assigned to a zone.
Review: Packet Flow

Recall the packet flow through a JUNOS security platform. Specifically, once the
packet enters a flow module, the device examines it to determine whether it belongs
to an already established session. Recall that JUNOS Software matches on six
elements of traffic information to identify a sessionsource
IP address, destination IP address, source port number, destination port number,
protocol number, and a session token.
This chapter focuses on defining, configuring, and monitoring zones.
Zones Chapter 35
Zones and Interfaces

You can assign one or more logical interfaces to a zone. You can also assign one or
more logical interfaces to a routing instance. You cannot assign a logical interface to
multiple zones or multiple routing instances. You must also ensure that all of a zones
logical interfaces are in a single routing instance. Violating any of these restrictions
results in a configuration error as shown in the following examples:
[edit]
user@host# commit check
[edit security zones security-zone trust]
'interfaces ge-0/0/2.0'
Interface ge-0/0/2.0 already assigned to another zone
error: configuration check-out failed
Chapter 36 Zones
Zones and Interface Assignments (contd.)

[edit]
lab@host# commit check
[edit routing-instances A interface]
'ge-0/0/0.0'
RT Instance: Interface ge-0/0/0.0 already configured under instance B
[edit routing-instances B]
'interface'
Interface ge-0/0/0.0 is in more than one routing instance (latest A)
error: dcd_config_read fails to set parsing options
error: configuration check-out failed
[edit]
user@host# commit check
[edit security zones security-zone untrust]
'interfaces ge-0/0/2.0'
Interface ge-0/0/2.0 must be in the same routing instance as other
interfaces in the zone
error: configuration check-out failed"
One exception to the rule exists when all interfaces are assigned to one zone using the
interface all configuration option. In this case, interfaces can belong to multiple
routing instances.
Zones Chapter 37
Interfaces, Zones, and Routing Instances

The slide is animated.
The slide summarizes logical relationships between interfaces, zones, and routing
instances.
Logical interfaces are connections to specific subnets. Zones are logical groupings of
logical interfaces with a common security requirement, and a logical interface can
belong to only one zone. Zone configuration can be as simple as a two-zone setup,
where all interfaces connected to internal networks are in one zone, and all interfaces
connected to the external world are in a different zone. A more complicated
configuration might divide interfaces based on internal department or function in
addition to external and demilitarized zone (DMZ) connections.
A physical device can be broken up into multiple routing instances. A routing instance
is a logical routing construct within a platform running JUNOS Software. Each routing
instance maintains its own routing table and forwarding table. A routing instance can
contain one or more zones, which cannot be shared with other routing instances.
Chapter 38 Zones
Zone Types
The zones within JUNOS Software can be subdivided into two categoriesuser-defined
and system-defined. You can configure user-defined zones, but you cannot configure
system-defined zones. You can subdivide the user-defined category into security and
functional zones. We cover user-defined and system-defined zones in detail on the
next few pages.
Zones Chapter 39
Security Zones
Security zones are a collection of one or more network segments requiring regulation
of inbound and outbound traffic through the use of policies. Security zones apply to
transit traffic as well as traffic destined to any interfaces belonging to the security
zone. You need one or more security policies to regulate intrazone and interzone
traffic. Note that JUNOS Software does not have any default security zones, and you
cannot share a security zone between routing instances.
Chapter 310 Zones
Functional Zones
Functional zones are special-purpose zones that cannot be specified in security
policies. Note that transit traffic does not use functional zones. While the fxp0
management ethernet interface is out-of-band by default, the Management Zone
allows you to assign other network interfaces the same behavior of isolating
management traffic from transit traffic.
Zones Chapter 311
Null Zone
Currently there is only one system-defined zone, the Null Zone. By default, an
interface belongs to the Null Zone. You cannot configure the Null Zone. When you
delete an interface from a zone, the software assigns it back to the Null Zone. JUNOS
Software rejects all traffic to and from interfaces belonging to the Null Zone.
Chapter 312 Zones
Branch Platforms
JUNOS security platforms for the branch ship from the factory with a template
configuration that includes security zones. SRX high-end platforms do not contain
zones in the factory-default template configuration and, therefore, you must configure
required zones manually.
Factory-Default Configuration
In branch devices factory-default configuration, two security zones are defined
trust and untrust. In the template configuration, ge-0/0/0.0 belongs to the
trust zone. In addition, the factory-default configuration file has a security policy
permitting all transit traffic within the trust zone and from the trust zone to the
untrust zone. The security policy prohibits any traffic from the untrust zone to the
trust zone. We discuss security policy in further detail in a subsequent chapter. The
zone names trust and untrust have no system-defined meaning. Like any zones
defined in the configuration, you can modify or delete them. You can revert a JUNOS
Software-based platform to its factory-default configuration by entering the load
factory-default command from the top of the configuration hierarchy.
Zones Chapter 313
Zone Configuration
Chapter 314 Zones
Zone Configuration Procedure

Zone configuration involves the following steps:
Define a security or a functional zone;
Add logical interfaces to the zone; and
Optionally, identify some combination of system services and protocols

allowed into the device through the interfaces belonging to the zone. If
you omit this step, all traffic entering through the zones interfaces
destined for the device is blocked.
Zones Chapter 315
Configuration Mode
To define a zone you must enter configuration mode, as illustrated on the slide.
Defining a Zone Type

Once you enter the configuration mode, you can define a zone type. Recall that you
can configure only two types of zonesfunctional, which is used for device
management only (no transit traffic is permitted), and security. You define zones
under the security configuration stanza. Note that user-defined zone names are
case sensitive and can contain any standard characters, like any other variable name
in JUNOS Software.
Functional Zone Specifics

The following are two important configuration characteristics of the functional zone:
Chapter 316 Zones
1.
You can define only one type of functional zonemanagement; and
2.
The functional zone does not have a user-defined name.
Adding Logical Interfaces to the Zone

Now you are ready to add logical interfaces to the zone. The slide illustrates two
variations. The first example illustrates adding interface ge-0/0/1.0 to the security
zone, called HR, and the second example illustrates adding interface ge-0/0/1.100 to
the functional management zone. If you omit the specification of the logical unit of the
interface, JUNOS Software assumes unit 0. Also, you can assign all interfaces to a
zone by using the keyword all. Should you choose to assign all interfaces to a zone,
you will not be able to assign any interfaces to a different zone.
Zones Chapter 317
Specifying Types of Traffic Permitted into the Device: Part 1

Without explicit configuration, traffic destined for a JUNOS security platform is not
permitted. You can specify types of traffic allowed into the device using the
host-inbound-traffic configuration option under a specific zone or under an
interface configured in a zone. By default, all outbound traffic originating from the
device is always allowed.
Chapter 318 Zones

When specifying types of traffic permitted into a JUNOS security platform, you use
some combination of system-services and protocols configuration options.
JUNOS Software provides you with the ability to refer to all system services and
protocols and respective ports with the help of the all keyword. To open all ports for
all services, use the any-service keyword. In addition, you can isolate any
exceptions to the referred list of protocols or system services with the help of the
except keyword. The examples on the following pages illustrate the use of this
keyword.
Zones Chapter 319
Specifying Types of Traffic Permitted into the Device: Part 2 (contd.)

You can specify any of the following system services:
[edit security zones]
user@host# set security-zone HR host-inbound-traffic system-services ?
Possible completions:
all
All system services
any-service
Enable services on entire port range
+ apply-groups
Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
dns
DNS and DNS-proxy service
except
Type of incoming system-service traffic to disallow
finger
Finger service
ftp
FTP
http
Web management service using HTTP
https
Web management service using HTTP secured by SSL
ident-reset
Send back TCP RST to IDENT request for port 113
ike
Internet Key Exchange
lsping
Label Switched Path ping service
netconf
NETCONF service
ntp
Network Time Protocol service
ping
Internet Control Message Protocol echo requests
rlogin
Rlogin service
rpm
Real-time performance monitoring
rsh
Rsh service
snmp
Simple Network Management Protocol service
snmp-trap
Simple Network Management Protocol traps
ssh
SSH service
telnet
Telnet service
tftp
TFTP
traceroute
Traceroute service
xnm-clear-text
JUNOScript API for unencrypted traffic over TCP
xnm-ssl
JUNOScript API service over SSL
Chapter 320 Zones
Specifying Types of Traffic Permitted into the Device: Part 2 (contd.)

You can specify any of the following protocols:
[edit security zones]
user@host# set security-zone HR host-inbound-traffic protocols ?
all
All protocols
+ apply-groups
Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
bfd
Bidirectional Forwarding Detection
bgp
Border Gateway Protocol
dvmrp
Distance Vector Multicast Routing Protocol
except
Protocol type of incoming traffic to disallow
igmp
Internet Group Management Protocol
ldp
Label Distribution Protocol
msdp
Multicast Source Discovery Protocol
nhrp
Next Hop Resolution Protocol
ospf
Open Shortest Path First
pgm
Pragmatic General Multicast
pim
Protocol Independent Multicast
rip
Routing Information Protocol
router-discovery
Router Discovery
rsvp
Resource Reservation Protocol
sap
Session Announcement Protocol
vrrp
Virtual Router Redundancy Protocol
Zones Chapter 321

You can specify allowed traffic either at the zone level of configuration or the interface
level within a zone. As with any configuration in JUNOS Software, the precedence rule
of more specific configuration applies here as well. In other words, interface-level
configuration (as it is more specific) overrides the zone-level configuration. In the
examples on the slide, only HTTP system services are allowed into interface ge-0/0/1,
which is part of the HR Zone. All other interfaces associated with the HR Zone can
accept all system services.
Chapter 322 Zones
Check Your Knowledge: Part 1

In this example, a
security zone named
HR is configured.
Interfaces ge-0/0/0.0
and ge-0/0/1.0 belong
to that zone. Inbound
Telnet and FTP traffic
are allowed into the
device through these
interfaces. All other
inbound traffic that is
local to the device on
these interfaces is
dropped.
The slide shows an example of zone configuration. What types of traffic are allowed
into the specified zone and interfaces?
Zones Chapter 323

In this example, a
security zone named
HR is configured.
Interfaces ge-0/0/0.0
and ge-0/0/1.0 belong
to that zone. As the
SNMP service is
specified to be allowed
only through
interface ge-0/0/1.0,
SNMP will not be
allowed into
interface ge-0/0/0.0.
In addition, Telnet and
FTP services will be
allowed only using the
ge-0/0/0.0 interface
and not the
ge-0/0/1.0 interface.
Chapter 324 Zones
The slide shows another example of zone configuration. What types of traffic are
allowed into the specified zone and interfaces?

In this example, a
security zone named
zone1 is defined. It
permits all inbound
services with the
exception of Telnet.
There are two
interfaces that belong
to security zone
zone1
ge-0/0/0.0 and
ge-0/0/1.0.
Interface ge-0/0/0.0
permits all services
with the exception of
Telnet.
Interface ge-0/0/1.0
permits all services
with the exception of
HTTP and FTP
services.
The slide shows the third example in this series. What does this configuration do?
Zones Chapter 325
Monitoring Security Zones

Chapter 326 Zones
Monitoring Zones
No additional mouse
click is necessary.
The slide illustrates the show security zones command, which is useful for zone
monitoring. The command provides information on the zone type and name along with
the number and names of interfaces bound to the zone.
Zones Chapter 327
Monitoring Traffic Permitted into Interfaces: Part 1

No additional mouse
click is necessary.
Chapter 328 Zones
Using the show interfaces interface-name extensive command enables

you to view zone specifics. The command displays information on permitted protocols
and system services allowed into the device through the corresponding interfaces. In
addition, the command provides information on flow statistics through the interface.
Monitoring Traffic Permitted Into Interfaces: Part 2

No additional mouse
click is necessary.
The slide provides the continuation of the output from the previous page.
Zones Chapter 329
Chapter 330 Zones
Zones and their purpose;
Types of zones;
Application of zones;
Zone configuration; and
Zone monitoring.
Review Questions
1.
A zone is a collection of one or more network segments sharing identical security
requirements.
2.
Overall, there are two types of zones in JUNOS Softwareuser-defined and system-defined
zones. User-defined zones include security and functional zones, both of which you can
configure. The Null Zone is a system-defined zone that you cannot configure. The security
zone facilitates transit packets and packets to the device itself. The functional zone facilitates
only management traffic. The Null Zone is a placeholder for interfaces that do not belong to
any zone. All interfaces belonging to the Null Zone drop all packets.
3.
To configure a zone, you must perform the following steps: (1) Define a security zone or a
functional zone; (2) Add logical interfaces to the zone; and (3) Optionally, add services and
protocols that must be permitted into the device.
4.
You can specify traffic types to be allowed into a JUNOS security platform using the
host-inbound-traffic statement.
Zones Chapter 331
Lab 1: Configuring and Monitoring Zones

The slide provides the objective for this lab.
Chapter 332 Zones

Chapter 4: Security Policies
Security policy functionality;
Components of a security policy;
Configuring a security policy; and
Verification and monitoring of security policies.
Chapter 42 Security Policies
Overview of Security Policy

first.
Security Policies Chapter 43
What Is a Security Policy?

A security policy is a set of statements that controls traffic from a specified source to a
specified destination using a specified service. If a packet arrives that matches those
specifications, the SRX Series device performs the action specified in the policy.
Network security policies are highly valuable for secure network functionality. Network
security policies outline all network resources within a business and the required
security level for each resource. JUNOS Software provides a set of tools to implement
a network security policy within your organization. Security policies enforce a set of
rules for transit traffic, identifying which traffic can pass through the firewall and the
actions taken on the traffic as it passes through the firewall.
Review: Packet Flow

No additional mouse
click is necessary.
The slide reviews packet flow through the flow module of a JUNOS security platform.
When the device examines the first packet of a flow, based on incoming and outgoing
zones, it determines the corresponding security policy, and it performs a security
policy lookup. The system checks the packet against defined policies to determine
how to treat the packet.
In this chapter, we focus on the security policies portion of JUNOS Software.
Transit Traffic Examination

JUNOS Software for security platforms always examines transit traffic by using security
policies. As illustrated on the slide, should no match exist in the security policy, the
default security policy applies to the packet. We highlight the default security policy in
a subsequent slide.
host-inbound-traffic Examination
If the destination of traffic is the devices incoming interface, security policies are not
applicable. The only examination that takes place is the list of services and protocols
allowed into that interface using the host-inbound-traffic statement within a
zone definition. (See Chapter 3: Zones for details.)
JUNOS Software examines security policies if the traffic destination is any interface
other than the incoming interface. This process is true regardless of whether the
incoming interface and the destination interface are in the same zone (intrazone
traffic) or in different zones (interzone traffic).
The flowchart on the slide illustrates the order of packet examination. When the
device receives traffic destined to itself, it first examines whether the destination of
the traffic is the incoming interface. If so, it skips the policy examination. Otherwise,
the corresponding security policies evaluate the traffic. If no policy match exists for
the traffic, the default policy action applies. We discuss the default security policy on
the next slide. If traffic matches a security policy that permits it, the device then
examines the list of services and protocols allowed into the destination interface
within the corresponding zone, and applies the corresponding action.
System-Default Security Policy

By default, JUNOS Software denies all traffic through an SRX Series device. In fact, an
implicit default security policy exists that denies all packets. You can change this
behavior by configuring a standard security policy that permits certain types of traffic,
or by configuring the default policy to permit all traffic as shown in the following screen
capture.
[edit security policies]

user@host# set default-policy permit-all
[edit security policies]
user@host#
Factory-Default Security Policies

The factory-default template configuration file in branch security platforms has three
preconfigured security policies (not to be confused with the system-default security
policy discussed in the previous paragraph):
1.
Trust-to-trust zone policy: Permits all intrazone traffic within the trust
zone;
2.
Trust-to-untrust zone policy: Permits all traffic from the trust zone to the
untrust zone; and
3.
Untrust-to-trust zone policy: Denies all traffic from the untrust zone to the
trust zone.
Security Policy Conceptual Example

We now examine an example of a packet flow through a JUNOS security platform.
The devices interfaces are separated into three security zonesprivate, external, and
public. The business requirement calls for an SSH application to be allowed from
Host B, located in the private zone, to Host D, located in the external zone. To meet the
requirement, we created the security policy illustrated on the slide.
The following is the sequence of events that takes place:
1.
Host B initiates the SSH session to Host D.
2.
The JUNOS security device receives traffic and examines it using its
security policy from the private zone to the external zone. The security
policy permits that traffic.
3.
The Host B-to-Host D flow triggers the creation of the reverse flow from
Host D to Host B. The slide identifies the contents of this newly formed
session. It consists of two flowssource to destination and destination to
source.
4.
Host D sends the return traffic, from Host D to Host B. The device, using a
pre-created session, permits the return traffic through to Host B.
Policy Ordering
Because policies execute in the order of their appearance in the configuration file, you
should be aware of the following:
Policy order is important.
New policies go to the end of the policy list.
You can change the order of policies in the configuration file using the
JUNOS Software insert command.
The last policy is the default policy, which has the default action of
denying all traffic.
Editing Security Configurations

Like any other JUNOS Software configuration stanza, you can delete, deactivate,
activate, insert, annotate, and copy security policies.
Policy Components
Security Policy Contexts

When defining a policy, you must associate it with a source zone, or incoming zone
named the from-zone. Also, you must define a destination zone, or an outgoing zone
named the to-zone. Within a direction of source and destination zones, you can define
more than one policy, referred to as an ordered set of policies, which JUNOS Software
executes in the order of their configuration.
Recall that a zone is a collection of multiple logical interfaces with identical security
requirements. JUNOS Software always checks all transit trafficintrazone and
interzonethrough the use of security policies.
Security Policy Components

Within the defined context title, each policy is labeled with a user-defined name.
Under the user-defined name is a list of matching criteria and specified actions,
similar to a JUNOS Software routing policy. One major difference is that each security
policy must contain a matching source address, destination address, and application.
Actions for traffic matching the specified criteria include permit, deny, reject, log, or
count.
JUNOS Software also uses policy to invoke the use of Intrusion Detection and
Prevention (IDP) policies, the Unified Thread Management (UTM) feature for branch
devices, and firewall authentication. We discuss IDP and firewall authentication in
detail in subsequent chapters.
Policy Match Criteria

Each of the defined policies must include the following matching criteria:
Source addresses: This criterion can be in the form of address sets or

individual addresses. You can group individual addresses into address
sets.
Destination addresses: This criterion can be in the form of an address

sets or individual addresses. You can group individual addresses into
address sets.
Applications or application sets: This criterion can be user-defined or

system-defined. JUNOS Software supports system-crafted default
applications and application sets, referred to using the format
junos-application, where application is the name of the
actual application. You can also define your own applications.
You must specify all matching components. If you omit any of these components,
JUNOS Software will not allow you to commit the configuration.
Creating Address Book Entries

The slide illustrates the syntax that you must use when creating address book entries.
An address book within a zone can consist of individual addresses or address sets. An
address set is a set of one or more addresses defined within an address book.
Address sets are useful when you must refer to a group of addresses more than once.
If the matching criteria needs no specific address, no address book entry is
necessary. In this case, you can specify the configuration option any as the source or
destination address in a security policy.
Defining Custom Applications

JUNOS Software has many built-in applications, such as junos-rsh, junos-sip,
junos-bgp, and so forth. You can customize the list of predefined applications (thus
expanding the overall list), which gives you the capability to support complex
applications.
To configure a custom application, define the application name, associate the
application with a protocol and ports. Use the application-protocol
configuration option to associate the custom application with an application-level
gateway (ALG). A user-configured application has a timeout value associated with it.
JUNOS Software applies the timeout value to the created session. Once the timeout
expires, the software clears the session from the session table. You can modify the
timeout value for a specific application. Note that the new timeout value applies only
to new sessionsnot to existing ones.
Creating Policy Match Entries

You enter all policies under the from-zone...to-zone stanza for that particular
traffic direction. The from-zone...to-zone stanza associates the policies under it
with a source zone and a destination zone. Under a specific zone direction, each
security policy contains a name, match criteria, and an action. This example focuses
on match criteria. The system executes all policies in the order of their appearance
within a configuration file.
Basic Policy Actions

Each policy has a list of basic and advanced actions associated with it. The basic
actions are the following:
permit: Allows traffic flow;
deny: Results in a silent packet drop; and
reject: Results in a packet drop and the sending of an Internet Control

Message Protocol (ICMP) unreachable message for UDP traffic and a TCP
reset register suppression time (RST) message for TCP traffic.
Log and Count Traffic

For each of these actions, you can configure JUNOS Software to log and count traffic
as well. To view counters, use the show security policies detail
operational mode command. We discuss logging in detail in subsequent slides.
Advanced Permit Settings

Among the policy actions mentioned on the previous slide, the following advanced
permit settings exist:
Firewall authentication;
IPsec VPN tunnel;
IDP; and
UTM features.
Firewall authentication enables you to restrict and permit users accessing protected
resources that could be located in different zones. JUNOS Software offers two
methods of firewall authentication:
Pass-through: Firewall users that are using FTP, Telnet, or the Hypertext
Transfer Protocol (HTTP) to access protected resources across the device
receive authentication through a username and password. The JUNOS
security platform intercepts the session and then performs user
authentication.
Web authentication: Firewall users use HTTP or HTTP over Secure

Sockets Layer (HTTPS) to access an IP address of the JUNOS security
device, instead of the protected resource. The device acts as a proxy,
authenticating the user with a username and password and caches the
information.
Advanced Permit Settings (contd.)

We discuss firewall authentication in more detail in the chapter titled, Firewall User
Authentication.
If a policy associates with a preconfigured IPsec VPN tunnel, the tunnel creation
occurs dynamically upon the receipt of the first packet that matches such a policy. The
policy-based IPsec VPN can be one of two typesIKE or manual. We discuss
IPsec VPNs in more detail in the chapter titled,IPsec VPNs.
A policy can associate with an IDP policy. IDP policies inspect traffic and enforce
various attack detection and prevention techniques. We discuss IDP in more detail in
the chapter titled, Introduction to IDP.
In branch devices only, a policy can also associate traffic with UTM features such as
antivirus, content filtering, and Web filtering.
Policy Components Summary

The following is a summary of the policy components:
A security policy is positioned within the from-zone and the to-zone

direction of traffic within configuration;
Each policy has a set of matching conditions;
Each policy has a set of actions that the system performs upon success
of all matching conditions;
Many security policies within the same direction of the flow can exist; and
Policy order is important, because policies execute in the order of their

appearance in the configuration file.
Verifying Policy Operation

Control Plane Logging

JUNOS Software logs control plane events either locally or to an external syslog device.
Locally stored logs are stored on the Routing Engine under the /var/log directory;
you can view them by using the show log log-name operational mode command.
To configure logs to be sent to an external syslog server, use the host configuration
option. The example on the slide shows the control plane logging statements present
in a factory-default configuration.
Branch Device Data Plane Logging

Data plane logging in JUNOS security platforms for the branch can be stored locally or
on an external system log (syslog) server. Use the session-close and
session-init configuration options within a security policy to log the start and
close of sessions matching a policy.
The slide illustrates a sample log file configuration for branch devices. Logs are stored
locally in the /var/log directory when designated with a filename. To send logs to
an external device, use the host IP address configuration option.
The default facility and severity for data plane session logging is user info. To
enable a Network and Security Manager (NSM) device to be able to retrieve logs,
name the log file default-log-messages, as shown on the slide, and include the
structured-data configuration option.
High-End SRX Series Data Plane Logging

Data plane logging in high-end SRX Series devices must go to an external syslog
device. JUNOS Software does not support local data plane logging because of the high
volume of session handling that a high-end SRX Series Services Gateway supports.
The slide illustrates the configuration of data plane logging for SRX Series high-end
devices.
Currently, JUNOS Software supports one stream of logging traffic. Supported
collection devices include UNIX syslogd-based servers and Juniper Networks STRM.
Logging Sessions in Security Policy

Use the session-close and session-init configuration options to log the start
and close of sessions matching a policy. The slide illustrates the configuration of the
policy log action.
Collecting Security Policy Statistics

Use the count security policy action to collect statistics and make them available
using operational show commands. The count security policy action is not necessary
to enable statistics collection in security policy logs. Logs containing
session-close messages contain statistics by default. The case study later in this
chapter provides examples of both forms of statistics collection.
Operational Monitoring Commands

Various show commands are available for monitoring the application of security
policy. The show security policies command allows you to view details about
an applied policy such as the policy index number, policy matching conditions, and
policy actions. Use the detail command option to view statistics associated with
policy counters.
The show security flow session command displays active sessions on the
device and each sessions associated security policy. Note that this command output
is categorized per Services Processing Unit (SPU) application-specific integrated
circuit (ASIC). The following output is from a services gateway containing two services
processing cards (SPCs) and therefore, four total SPUs. Only one session is active on
the services gateway:
user@host> show security flow session
0 sessions displayed
Session ID: 210000935, Policy name: permit-ftp/5, Timeout: 1768
In: 10.100.0.2/50054 --> 10.200.1.2/21;tcp, If: ge-1/2/1.10
Out: 10.200.1.2/21 --> 10.100.0.2/50054;tcp, If: ge-1/0/1.40
Tracing Security Policy

The configuration shown on the slide enables the tracing of security policy evaluation
and sessions on a JUNOS security platform. Use the packet-filter configuration
option to log only details concerning selected sessions. Note that because of the
architectural design of Juniper Networks security and routing platforms, you can
enable reasonably detailed tracing in a production network without negative impact
on overall performance or packet forwarding. However, it is a good practice to disable
traceoptions when not troubleshooting the device to reduce the impact on system
resources.
Policy Scheduling and Rematching

Policy Scheduling
A policy scheduler is a method for scheduling a policy execution for a specified
duration or a set of durations. A policy scheduler is optional. A scheduler supports
system time updates either through manual configuration or through the Network
Time Protocol (NTP) by synchronizing itself with the time changes.
Rules for Scheduling

The following rules apply to policy scheduling:
An individual policy can have only one scheduler applied;
Multiple policies can use the same scheduler; and
A scheduler must be referenced in a policy to become active. Without a

defined scheduler within a policy, the policy is always active.
Security Policy Scheduler Components

A security policy scheduler provides you with the flexibility to identify the start date and
time and stop date and time for policy enforcement. In particular, the scheduler
components include the following:
Slot schedule: This component consists of the start date and time and
the stop date and time of policy enforcement; and
Daily schedule: This component consists of the start time, the stop time,
the all-day option, and the exclude option.
Policy Scheduler Details

A policy scheduler turns on recurrently or once at the specified time. Recall that a
policy scheduler activates and deactivates a policy according to the scheduled time,
which you configure. Once you create the scheduler, you must apply it to a policy. The
default behavior of a policy is to execute at all times.
Optionally Applying the policy-rematch Statement

JUNOS Softwares default behavior is to not disturb sessions in progress when you
make configuration changes to security policies. For example, you can modify an
address field or modify the actions of a policy used for session examination. By
default, because a session was pre-established, it continues to be operational without
any interruptions. You can change that default behavior by enabling the
policy-rematch statement. Once you enable the statement, every time a
configuration change to a policy occurs, it reflects in the sessions in progress.
Configuration changes, such as source addresses, destination addresses, and
application changes, cause policy re-evaluation as the system performs a policy
lookup. If the newly matched policy is not the policy referred to by the session, the
session clears. If an IPsec VPN change occurs, the JUNOS security platform clears the
session.
Optionally Applying policy-rematch Statement (contd.)

The following list explains the actions that JUNOS Software performs on impacted
sessions in progress based on whether the policy-rematch flag is enabled or
disabled.
When the policy-rematch flag is enabled:
The software inserts a policy: no impact;
The software modifies the action field of a policy from permit

to either deny or reject: all existing sessions are dropped; and
The software modifies some combination of source address,

destination addresses, and applications fields: JUNOS Software
re-evaluates policy lookup.
When the policy-rematch flag is disabled (default behavior):
The software inserts a policy: no impact;
The software modifies the action field of a policy from permit

to either deny or reject: all existing sessions continue; and
The software modifies some combination of source address,

destination addresses, and applications fields: all existing
sessions continue unchanged.
Note that irrespective of the value of policy-rematch policy flag, deletion of the
policy causes the device to drop all impacted existing sessions.
Policy Case Study

Case Study: Creating Policies

The next series of slides presents an example and configurations for a setup in which
two zones existHR and Public. The private PCs A and B, located in the HR Zone, must
communicate with Server C in the Public Zone using a custom application set.
Restrictions are placed on the rest of the 10.1.0.0/16 network that are logged and
counted.
Case Study: Entering Host Addresses into the HR Zone

Emphasize to students
that the order of
configuration steps on
this page and other
pages is not important
because you perform
the configuration
changes in the
candidate
configuration file.
The slide presents the configuration that adds host addresses belonging to zone HR.
The hosts include PC_A and PC_B, whose addresses are 10.1.10.5 and 10.1.20.5
respectively. The rest of the 10.1.0.0/16 subnet is also defined, which is named
other-10-1 in the address book. In addition, the PC_A and PC_B addresses are
grouped into an address set named HR_PCs.
Case Study: Entering Host Addresses into the Public Zone

The slide presents the configuration that adds host addresses belonging to the Public
Zone. The Public Zone has Server_C, whose address is 1.1.70.250. The rest of the
1.1.7.0/24 subnet is also defined, named other-1-1-70 in the address book. In
addition, an address set, named address-Public, consists of the Server_C
address for now.
Case Study: Adding New Applications

The slide presents the configuration of a new application, HR-telnet, for the HR
Zone. The configuration shows that the new application is added under the
applications stanza. In addition, the new application set, named
HR-Public-applications consists of two predefined applications, junos-ftp
and junos-ike, and the newly defined HR-telnet application.
Case Study: Creating Policy Entries: Part 1

We must now define the policies from the HR Zone to the Public Zone. We must define
two policies. The purpose of the first one, named HR-to-Public on the slide, is to
permit traffic from the HR Zone to Public Zone, provided that its source address
belongs to the address set HR_PCs, its destination address belongs to the address
set address-Public, and its application is part of HR-Public-applications.
Matching traffic is logged and counted.
Case Study: Creating Policy Entries: Part 2

The slide shows the definition of the next policy for the same directionfrom the HR
Zone to the Public Zone. This policy denies packets, logs, and counts packets for only
the following cases:
The source address of the packet must be other-10-1;
The destination address must be other-1-1-70; and
The application must be junos-ftp.
If a packet does not match the previous policyHR-to-Publicor

otherHR-to-Public, the default security policy examines it, resulting in the device
dropping it.
Case Study: Optionally Creating a Scheduler

We now create a scheduler named schedulerHR. Its purpose is to activate policy
HR-to-Public on a daily basis, from 9:00 am until 5:00 pm, excluding weekends
(Saturday and Sunday). Because HR-to-Public is the only policy that permits some
traffic, application of the scheduler results in the JUNOS security device blocking all
traffic completely on a daily basis after 5:00 pm and on weekends.
Case Study: Optionally Applying a Scheduler

The slide shows the application of the previously defined scheduler schedulerHR to
the HR-to-Public policy.
Check Your Knowledge

What are the answers to the questions posed on the slide?
The questions on the slide are open-ended to spark conversation among the students. The
answers can vary, but the policies illustrated do permit FTP traffic between the HR Zone and
the Public Zone provided traffic matches the address book and application parameters and is
initiated within scheduled times.
The configuration examples do not indicate that network administrators should be able to use
Telnet to access the device. Recall that you must configure a zone with the
host-inbound-traffic option to allow traffic that is local to the device.
Case Study: Monitoring Security Policies: Part 1

The slide output is
abbreviated. The full
output would include
all addresses within an
address list and all
applications within an
application set.
The slide shows the output of the show security policies detail command
for one of the policies in the case study. We removed some content for brevity.
Case Study: Monitoring Security Policies: Part 2

The slide shows an example of the data plane log output resulting from live FTP traffic
transiting the case studys security policy. We captured the output on an external UNIX
syslogd-enabled server.
Security policy functionality;
Security policy configuration, including:
Policy match conditions;
Policy actionsbasic and advanced;
Policy scheduling; and
Security policy verification and monitoring.
Review Questions
1.
The basic components of a policy are: (1) policy name; (2) source zone and destination zone;
(3) matching conditions, consisting of one or many source addresses or sets, one or many
destination addresses or sets, one or many applications or sets; and (4) actions.
2.
The default action for every policy set is to deny traffic.
3.
The policy scheduler enables the user to dynamically activate or deactivate a security policy. If
you deactivate a policy, and no other matches are found, the default security policy examines
the packet.
4.
You can reorder policies using the JUNOS Software insert command.
Lab 2: Security Policies

The slide provides the objective for the lab.

Chapter 5: Firewall User Authentication
The purpose of firewall user authentication;
Implementing pass-through authentication;
Implementing Web authentication;
Using client groups; and
Monitoring firewall user authentication.
Chapter 52 Firewall User Authentication
Firewall User Authentication Overview

first.
Firewall User Authentication Chapter 53
The Purpose of Firewall User Authentication

Firewall user authentication provides another layer of protection in the network on top
of security zones, policies, and screens. With firewall authentication, you can restrict
or permit users individually or in groups. Users attempting to access a network
resource receive a prompt from JUNOS Software for a username and password even if
a security policy is in place permitting the traffic.
Users can be authenticated using a local password database or using an external
password database. JUNOS Software supports RADIUS, Lightweight Directory Access
Protocol (LDAP), or SecurID authentication servers.
The example on the slide illustrates a user (Host A) attempting to access a network
resource belonging to the Public Zone. With firewall user authentication configured,
the user must first authenticate with the JUNOS security platform before accessing
the resource. In this example, the device can query an external authentication server
to determine the authentication result. The security policy must also allow traffic flow.
Once the user receives authentication, subsequent sessions from the same source IP
address bypass firewall user authentication. This behavior is especially important
when considering the usage of firewall user authentication for a network that might
have source-based Network Address Translation (NAT) employed.
Pass-Through Authentication
Two types of firewall user authentication are availablepass-through or Web
authentication. Pass-through authentication must first be triggered by Telnet, FTP, and
Hypertext Transfer Protocol (HTTP) traffic. In this type of firewall authentication, the
user initiates a session to a remote network device or resource. If traffic matches the
security policy configured for pass-through authentication, the SRX Series Services
Gateway intercepts the session. The user receives a prompt for a username and
password. If the authentication is successful, subsequent traffic from the same
source IP address is automatically allowed to pass through the device, provided it
matches the applied security policy.
Web Authentication
Web authentication is valid for all types of traffic. With Web authentication configured,
users must first directly access the JUNOS security platform using HTTP. The user
enters the address or hostname of the device into a Web browser and then receives a
prompt for a username and password. If authentication is successful, the user can
then access the restricted resource directly. Subsequent traffic from the same source
IP address is automatically allowed access to the restricted resource, as long as
security policy allows for it.
Local Authentication
JUNOS Software supports local authentication on the JUNOS security platform itself as
well as RADIUS, LDAP, and SecurID external authentication servers. The local
password database supports authentication and authorization.
RADIUS Authentication
JUNOS Software supports Juniper Networks Steel-Belted Radius for authentication as
well as authorization. The JUNOS security platform acts as a RADIUS client and
communication uses UDP. RADIUS uses a shared secret key to encrypt user
information during the exchange.
LDAP Authentication
An LDAP server is another form of external authentication server. JUNOS Software
supports authentication only when utilizing an LDAP server. JUNOS Software is
compatible with LDAP Version 3 and Microsoft Windows Active Directory.
SecurID Authentication
An RSA SecurID server can be used for external authentication. This method allows
users to enter either static or dynamic passwords as credentials. A dynamic password
is a combination of a users PIN and a randomly generated token that is valid for a
short period of time. JUNOS Software supports SecurID servers for authentication only
and does not support the SecurID challenge feature.
The slide illustrates the process used for pass-through firewall authentication. A user
attempts to connect directly to a remote network resource using either Telnet, HTTP, or
FTP. The JUNOS security platform intercepts the first packet and stores it in memory.
The device prompts the end user for a username and password. If authentication is
successful, a configurable banner displays to the user, and the original buffered
packet travels to its destination. JUNOS Software allows subsequent traffic from the
same source IP address until the user is idle for 10 minutes. At this point,
authentication must be performed again for further traffic to pass through the device.
The default idle timeout of 10 minutes is configurable as shown:
[edit access profile profile-name]

user@host# set session-options client-idle-timeout ?
<client-idle-timeout> Time in minutes of idleness after which access is
denied
Creating an Access Profile

The slide provides an example of a basic access profile. This example shows the
configuration of a user-defined profile name. One or more clients are configured
within the profile, representing end users. The client-name represents the username.
The password is entered in plain-text format but displays in encrypted form when you
view the configuration.
Associating the Access Profile with an Authentication Type

Once an access profile has been defined, it must be associated with pass-through
firewall authentication. The slide shows a basic example of this configuration. JUNOS
Software also allows you to set a customized banner that will display to the end user.
JUNOS Software can display an initial login banner, a successful authentication
banner, and a failed authentication banner when configuring pass-through
authentication.
Apply Pass-Through Authentication as Policy Action

Enable pass-through and Web authentication using security policies. To be subject to
firewall user authentication, traffic must align with the policys matching conditions
and have an extended action of permit, specifying the type of firewall authentication to
use. The slide shows an example of applying pass-through firewall authentication to a
security policy.
Web Authentication
Web Authentication
The slide illustrates the process used for Web firewall authentication. A user that
requires access to a remote network resource must first access the JUNOS security
platform directly using a Web browser. The device prompts the end user for a
username and password. If authentication is successful, a configurable banner
displays and the user gains permission to access the remote resource. JUNOS
Software allows subsequent traffic from the same source IP address until the user is
idle for 10 minutes. At this point, authentication must be performed again for further
traffic to pass through the device. The default idle timeout of 10 minutes is
configurable as shown here:
[edit access profile profile-name]

user@host# set session-options client-idle-timeout ?
<client-idle-timeout> Time in minutes of idleness after which access is
denied
Enabling the HTTP Process

To use Web authentication, the SRX Series device must initiate the httpd process. The
slide highlights the required configuration to enable this system process for the
device. The highlighted configuration allows HTTP access for Web management using
the J-Web user interface and also allows for the use of Web authentication. You can
also configure this feature to restrict access to an individual interface or a group of
interfaces. The security zone containing the interface to be used for Web
authentication (or for the J-Web user interface) must allow HTTP traffic as host
inbound traffic.
Enabling Interface for Web Authentication

The interface that users access for Web authentication must be enabled for
authentication. The slide illustrates a sample configuration for enabling Web
authentication on the ge-0/0/0 interface. We recommend using a secondary IP
address as the Web authentication address. The Web authentication address must be
in the same subnet as the primary interface address. Use the preferred
configuration option to ensure that traffic sourced from this interface continues to use
the primary address as its source address.
Creating an Access Profile

Web authentication can use the same profile as pass-through authentication. The
example on the slide shows the configuration of a user-defined profile name. One or
more clients are configured within the profile representing end users. The client-name
represents the username. The user enters the password in plain-text format but it
displays in encrypted form when you view the configuration.
Associating the Access Profile with an Authentication Type

The access profile must associate with Web authentication using the same
configuration structure as pass-through authentication. The slide shows a basic
example of this configuration. JUNOS Software also allows you to set a customized
banner that will display to the end user. Web authentication supports a customized
banner for successful authentication only.
Applying Web Authentication as Policy Action

Pass-through and Web authentication are enabled using security policies. To be
subject to firewall user authentication, traffic must align with the policys matching
conditions and have an extended action of permit, specifying the type of firewall
authentication to use. The slide shows an example of applying Web firewall
authentication to a security policy.
A Cleaner Method of Web Authentication

Directly accessing the device through a browser before gaining access to a remote
resource is burdensome. To alleviate this burden, JUNOS Software allows Web
redirection. The slide illustrates the configuration of Web redirection. With Web
redirection enabled, the device responds to the user device with an HTTP redirect
message, which tells the user device to use HTTP to access the JUNOS security
platform at a particular address. JUNOS Software uses the address of the interface on
which the initial user request was received. You must enable Web authentication for
this interface and for the system itself, just as you would for standard Web
authentication.
Client Groups
Using Client Groups

A client group is a list of groups associated with a client. Client groups allow for easier
management of multiple firewall users. Security policy references client groups in the
same manner in which it references individual clients. The slide shows a simple
conceptual example of using client groups to manage multiple users. The next two
slides utilize this example for illustrating the configuration of client groups.
Adding Client Groups to a User

The slide provides an example configuration of three users associated with various
groups. A number of groups (contained in square brackets in the example
configuration) represent a client group.
Configuring a Policy to Use Client Groups

Once client groups have been organized, groups can be referenced in a security policy
with firewall authentication. Groups can be used in place of individual clients. The
slide illustrates the use of a client group in a security policy. In this example, Group-A
from the previous slide is subject to pass-through authentication.
Which Users Have Telnet Access to the Engineering Resource?

In the referenced example configuration, firewall authentication is enabled and the
security policy specifies only client group Group-A. Client group Group-A associates
with user1 and user2. Therefore, user1 and user2 have access to the engineering
remote network resource (if they authenticate successfully).
What if All Three Users Use the Same Source IP Address?

Firewall user authentication is based on the source IP address. As we discussed
earlier in this chapter, once firewall authentication is successful, subsequent sessions
from the same source IP address are not subject to further authentication within the
idle timeout period. In this example, if user1 or user2 were to authenticate first, user3
would also be able to access the remote engineering resource.
Default Client Groups

JUNOS Software allows the configuration of a default client group to serve as a
catch-all for all users within an access profile. This setup allows ease of management
by categorizing users in access profiles. If a user or client does not associate with a
client group and a default client group exists, the user associates with the default
client group. The client group can consist of one or more groups.
Using External Authentication Servers

Adding Servers to the Access Profile

You configure external authentication server details within an access profile. JUNOS
Software supports only one external authentication server for access profiles, but you
can use it in conjunction with the local password database. You must specify an
authentication order if you plan to use an external server. The JUNOS security platform
will try to authenticate with the first method listed. If the configuration does not list the
password database in the authentication order and the listed method of external
authentication is unreachable, JUNOS Software still consults the local password
database. However, if the listed external authentication method fails, JUNOS Software
does not consult the local password database, denying user access.
Verifying Firewall User Authentication

Viewing the Authentication Table

The first example on the slide illustrates how to view the current authentication table.
This table contains a list of users and their associated access profiles. It shows the
source IP address, source and destination security zones, the authentication result,
and the current age of the idle timer. You can also sort the authentication table by
source IP address or user ID by issuing the command with the address or
identifier command options as shown in the following output:
user@host> show security firewall-authentication users ?
<[Enter]>
Execute this command
address
Locate authentication entry by ip address
identifier
Locate authentication entry by id
Viewing Authentication Table History

The slide shows how to view a historical authentication table. This table keeps a
record of firewall authentication attempts in brief form, including date and time
stamps. This command also supports the use of the address and identifier
command options.
The purpose of firewall user authentication;
Implementation of pass-through authentication;
Implementation of Web authentication;
Using client groups; and
Monitoring firewall user authentication.
Review Questions
1.
JUNOS Software supports RADIUS, LDAP, and SecurID external authentication servers.
2.
In pass-through authentication, the user attempts to access the remote network resource
directly, and the JUNOS security platform intercepts the session to perform firewall
authentication, while buffering the session. The buffered session is released as long as
authentication is successful. In Web authentication, the user must first access an IP address
belonging to the JUNOS security device using a Web browser; the authentication is
performed using this HTTP session. The user can then proceed to access the remote network
resource as long as authentication is successful. FTP, Telnet, and HTTP traffic trigger
pass-through authentication, while an HTTP session must trigger Web authentication.
3.
A client group is a list of groups associated with a client. Groups can be used in security
policies in place of individual clients for ease of management.
4.
Use the show security firewall-authentication history command to
view a history of firewall authentication attempts.
Lab 3: Configuring Firewall Authentication


Chapter 6: SCREEN Options
SCREEN options and their meanings;
Various types of attacks prevented by SCREEN options;
SCREEN options advantages;
Configuration of SCREEN options; and
Applying and monitoring SCREEN options.
Chapter 62 SCREEN Options
Multilayer Network Protection

first.
SCREEN Options Chapter 63
Networks Are Under Attack

The first few slides in
this chapter to provide
a context and
framework for the use
of SCREEN options.
Although basic network security issues have changed very little over the past decade,
the network security landscape has changed dramatically. Todays IT professionals
must still protect the confidentiality of corporate information, prevent unauthorized
access, and defend the network against attacks. They also face new challenges as
their networks become more complex and dynamic. The following list examines some
of these issues:
Ubiquitous Internet access: The growing availability of Internet access

has made every home, office, and business partner a potential entry
point for an attack. The corporate network is vulnerable to attacks that
hackers can deliberately launch and from remote users logging onto the
corporate network and unknowingly hiding an attack within their
sessions. The trend of working at home and using a work PC for personal
use increases the possibility of dangerous and annoying attacks such as
spyware, phishing, and spam.
Internal attacks: While stopping external attacks remains a constant

challenge, the attacks that originate from inside the network by
employees are equally challenging. Internal attacks can range from
unauthorized server or resource access to a disgruntled employee
destroying or stealing proprietary information.
Networks Are Under Attack (contd.)
Regulatory compliance: As new national and industry regulations

emerge, security is a continual emphasis. Whether the requirement is to
encrypt all data or simply to protect it from unauthorized access,
complying with these new regulations complicates matters for you as a
security administrator.
Changing levels of trust: Remote employees, business partners,

customers, and suppliers might have different levels of access to
corporate resources. You must take appropriate measures to protect the
corporate network at all these levels. While the number of applications to
which remote users have access through the demilitarized zone (DMZ)
increases, companies are simultaneously trying to reduce costs by
minimizing the application instances between internal and external
users. This approach makes it necessary for security policies to
accommodate application use by both groups.
Points of Vulnerability Equal Points of Control

Again, this page sets a
context. As we go
forward, we refer back
to these control points
as locations to deploy
the solutions.
The key to striking a balance between tight network security and the network access
required by employees, business partners, and customers is a layered security
solution. A layered security solution gives you a complete set of tools you can deploy to
achieve end-to-end security from the remote site to the data center. If one layer fails,
the next layer stops the attack, limits the damage that might occur, or does both.
Points of Vulnerability Equal Points of Control (contd.)

Layered security allows you to apply the appropriate level of resource protection to the
various network entry locations based upon your different security, performance, and
management requirements. The following are vulnerable points in the network:
Remote access occurs when a user connects to the corporate network

through a public or private connection. The key security goal to pursue
with remote access is the protection of content and user identity as they
traverse the network.
Site-to-site communications, both employee and nonemployee, are the

interactions between two offices of any type or any size. The site-to-site
security layers must protect resources at both sites from external threats
such as session hijacking, U-turn attacks, and Trojan or worm attacks
launched from a trusted PC that has been compromised. Internal attacks
are increasingly common and can include unauthorized server access,
improper use of bandwidth, and planting of spyware.
The network perimeter represents the point at which external traffic

gains initial access to the network, as well as the point through which
internal traffic traverses the Internet. With the diversity of traffic that the
perimeter represents, the security solution must protect against the
widest range of attacks using an assortment of security layers that can
include a VPN, denial of service (DoS) protection, a firewall, antivirus
scanning, an intrusion detection service (IDS), and possibly antispam
scanning.
At the heart of an enterprise is the network data center (or network core)
where the applications and data that drive day-to-day business reside.
Financial, human resources, and manufacturing applications with
supporting data represent the company crown jewels and, if
compromised, can sink even the most stable enterprise. The core
network security layers must protect these business-critical resources by
preventing unauthorized user access, containing internal attacks
launched by disgruntled employees, and protecting against
application-level attacks.
In conjunction with applying layered security to the network core, IT

departments are increasingly deploying security internally on LANs to
prevent unauthorized user access to network resources, to encrypt and
decrypt communications, and to contain damage that might occur if an
attack succeeds.
Attack Detection System: SCREEN Options

The most obvious element of JUNOS Software for security platforms is basic access
control using security policies. These policies define who and what has access to the
network. JUNOS Software uses stateful inspection to protect the network from
malicious content. With stateful inspection, JUNOS security platforms collect data
such as source and destination IP addresses, source and destination port numbers,
and packet sequence numbers from TCP and UDP pseudosessions. The device then
maintains this data in state tables for future use in analyzing traffic.
Through the deployment of custom security zones, you can use JUNOS Software not
only to protect the perimeter of your network, but also to provide segmentation of your
internal infrastructure. Used internally, SRX Series Services Gateways provide
additional layers of access control to protect against the organization's sprawling
definition of authorized user.
Using SCREEN options, JUNOS security platforms can protect against more than 30
different internal and external attacks, including SYN flood attacks, UDP flood attacks,
and port scan attacks. DoS attack protection leverages stateful inspection to look for
and then allow or deny all connection attempts that require crossing an interface on
their way to and from the intended destination.
When applied, SCREEN options pertain to traffic at its entry point. JUNOS Software
applies SCREEN checks to traffic prior to the security policy processing, thereby
resulting in less resource utilization.
Review: Packet Flow

It highlights the focus
of this chapter and
points out SCREEN
options within the
flow.
Before discussing SCREEN options, we revisit packet flow through a JUNOS security
platform. Note that SCREEN processing occurs before any packet processing, which
results in fewer resources used and better protection of the JUNOS security platform
itself.
Stages and Types of Attacks

Stages of an Attack
To understand SCREEN option configuration, we must first discuss the stages of
network attacks and the types of network attacks. A network attack consists of three
major stages. In the first stage, the attacker performs reconnaissance on the target
network. This reconnaissance might consist of many different kinds of network
probes. In this information-gathering phase, the attacker works to gather information
about the target network, any open ports, and the operating systems in use.
In the second stage, the attacker launches an attack at the target network. To protect
themselves, attackers must also conceal the origin point of the attack and attempt to
remove any evidence that an attack took place.
Depending on the type of attack, a third phase can occur. After infiltrating a trusted
machine, the attacker can use that machine as a point of origin for further invasion of
the network. Traffic now appears to originate from the trusted system, which might not
be subject to the same security scans as an outside system.
IP Address Sweep
Attackers can better plan their attack when they first know the layout of the targeted
network, possible entry points, and constitution of their victims.
An address sweep occurs when one source IP address sends Internet Control
Message Protocol (ICMP) packets to different hosts. The purpose of this scheme is to
send traffic to various hosts in hope that one replies, thus revealing an address to
target.
Port Scanning
A port scan occurs when one source IP address sends IP packets containing TCP SYN
segments to different ports at the same destination IP address. The purpose of this
scheme is to scan services in hope that one port will respond, thus identifying a
service to target.
IP Options
RFC 791, Internet Protocol, specifies a set of options to provide special routing
controls, diagnostic tools, and security. RFC 791 states that these options are
unnecessary for the most common communications and, in reality, they rarely
appear in IP packet headers. When they do appear, they are frequently being put to
illegitimate use.
OS Probes
An attacker might try to probe the targeted host to learn its operating system. Because
TCP standards do not dictate how to respond to anomalous traffic, different operating
systems respond differently to anomalies. The response to the anomaly gives the
attacker information about the type of operating system running on a given host.
Evasion Techniques
Whether gathering information or launching an attack, the attacker generally tries to
avoid detection. Although some IP address and port scans are blatant and easily
detectable, more advanced attackers use a variety of means to conceal their activity.
Forms of Denial of Service Attacks

The intent of a DoS attack is to overwhelm the targeted victim with a tremendous
amount of fake traffic so that the victim becomes so preoccupied processing fake
traffic that it is unable to process legitimate traffic. In the case of a router or firewall
device, the goal of a DoS attack is to fill up the device session table so that no new
sessions can establish. An attacker can also launch a network DoS or a DoS targeting
various operating systems.
This chapter explains each of the attacks and JUNOS Softwares ability to handle
these attacks.
Types of Attacks: Suspicious Packets

Attackers can craft packets to perform reconnaissance or launch DoS attacks.
Sometimes the intent of a crafted packet is unclear, but its crafted nature suggests
that it is being put to an insidious use.
Using JUNOS Software SCREEN OptionsReconnaissance Attack

Handling
SCREEN OptionsBest Practices

Prior to analyzing JUNOS Software SCREEN options in detail, we discuss best practice
suggestions for SCREEN option use.
You should understand the applications and their behavior within your network before
you begin implementing features that might have an impact on legitimate traffic.
Furthermore, you must understand the traffic patterns traversing your network. To
determine appropriate thresholds for limit-based SCREEN functions, you must first
know what is typical of your network. For example, if you want to enable SYN flood
protection, you must first determine what constitutes an acceptable number of
connection requests. This determination requires a period of observation and analysis
to establish a baseline for typical traffic flows. You must also consider the maximum
number of concurrent sessions required to fill up the session table of the particular
JUNOS security platform you are using. To see the maximum number of sessions that
your session table supports, use the CLI command show security flow
session summary. Remember the output of this command reports statistics for
each Services Processing Unit (SPU) separately.
You can use the alarm-without-drop statement, as illustrated on the slide, to
gather the traffic going to and through your JUNOS security platform. The gathered
information might help you to better understand your networks vulnerabilities.
Typically, you want to deploy SCREEN options only in vulnerable zones.
IP Address Sweep and TCP Port ScanThe Attack

An address sweep occurs when one source IP address sends a predefined number of
ICMP packets to various hosts within a predefined interval of time. The purpose of this
attack is to send ICMP packets, which are typically echo requests, to various hosts,
hoping that at least one host replies. Once attackers receive a reply, they uncover an
address, which becomes a target.
Port scanning occurs when one source IP address sends IP packets containing TCP
SYN segments to a predefined number of different ports at the same destination IP
address within a predefined time interval. This attack attempts to scan the available
services hoping that at least one port responds, thereby identifying an attack target.
The Defense
JUNOS Software internally logs the number of ICMP echo request packets from one
remote source. You can set up a threshold interval, ranging from 1000 to 1,000,000,
measured in microseconds for those ICMP packets. The default threshold value is
5000. By using the default settings, if a remote host sends ICMP echo request traffic
to 10 addresses in 0.005 seconds (5000 microseconds), the JUNOS security device
flags that remote host as an address sweep attacker. The flagging process results in
the rejection of all further ICMP echo requests from that host for the remainder of the
configured threshold time period.
The Defense (contd.)

For TCP port scanning protection, JUNOS Software internally logs the number of
different ports scanned from one remote source. The configured threshold value is in
microseconds, ranging from 1000 to 1,000,000. The default threshold value is 5000
microseconds. JUNOS Software flags the traffic as an attack when 10 ports are
scanned within the threshold value. Once port scanning detection triggers, JUNOS
Software silently drops all further packets from the remote source for the remainder of
the configured threshold time period.
IP Address Sweep and Port ScanningSCREEN Options

The slide is animated
and illustrates the
attack.
The slide illustrates an IP address sweep or port scanning attack. During an IP

address sweep attack, the attacker, using one source IP address, sends ICMP packets
to different hosts in hopes that at least one host replies, thereby uncovering an
address to target.
During a port scanning attack, the attacker, using one source IP address, sends IP
packets containing TCP SYN segments to a defined number of different ports at the
same destination IP address within a defined interval. The attacker hopes that at least
one port responds, thereby uncovering a service to target.
To block IP address sweeps or TCP port scans originating in a particular security zone,
you must perform the configuration illustrated on the slide. Note that this
configuration only defines the SCREEN optionit does not activate it. To activate the
SCREEN option, you must apply it within a security zone. We address this topic later in
the chapter.
The Attack
RFC 791 specifies a set of options within an IP packet, providing special routing
controls, diagnostic tools, and security. Within an IP packet header, these options
come after the destination address field. Although the original intent for these options
was to enhance network functionality, most common communications do not require
them. As the Internet expanded and continues to expand, attackers have started
abusing the options field of a packet, causing problems to networks and network
devices. An attacker can abuse the record route, timestamp, security, and stream ID
fields.
The Defense
To compensate for the vulnerability that these IP options fields create, JUNOS
Software tracks packets that have any of these option fields used, flags them as a
network reconnaissance attack, and records the event. You can view the events in the
SCREEN counters list for the ingress interface.
IP OptionsSCREEN Options
The slide illustrates an IP packet header, highlighting the options field. An attacker can
misuse bits within the options field to cause problems with networks. You can define
SCREEN options to detect the IP options that an attacker can use. These IP options
fields include record route, timestamp, security, and stream ID. JUNOS Software flags
an event in which a device configured with the appropriate SCREEN options receives a
packet with any of these IP options. JUNOS Software marks the event as a network
reconnaissance attack and records the associated ingress interface.
The slide illustrates the syntax for this SCREEN option definition. You can configure
each of the options independently. Note that this configuration only defines the
SCREEN optionsit does not activate them. To activate the SCREEN options, you must
apply them within a security zone. We address this topic later in the chapter.
The Attack
Prior to launching an exploit, an attacker might probe the targeted host, trying to learn
its operating system. Various operating systems react to TCP anomalies in different
ways. With that knowledge, an attacker can decide which further attack might inflict
more damage to the device, the network, or both.
The Defense
JUNOS Software configured with the appropriate SCREEN options blocks operating
system probes by detecting any of the following invalid TCP flag settings:
Both SYN and FIN flags set;
FIN flag set and ACK flag not set; or
No flags set.
TCP traffic matching any of these criteria is immediately, and silently, dropped.
Operating System ProbesSCREEN Options

The slide illustrates the TCP header, highlighting the SYN and FIN flags, which an
attacker might use to launch the attack. The slide also illustrates the configuration of
SCREEN options designed to block these probes. You configure each statement
independently as follows:
To detect the condition when both SYN and FIN flags are set, use the
syn-fin configuration option;
To detect the condition when the FIN flag is set and the ACK flag is not
set, use the fin-no-ack configuration option; and
To detect the condition when no flags are set, use the tcp-no-flag
configuration option.
Note that this configuration only defines the SCREEN optionsit does not activate
them. To activate the SCREEN options, you must apply them within a security zone. We
address this topic later in the chapter.
The Attack
IP address spoofing is one of the earliest and most well known attacks. An attacker
simply inserts a fake source address into the packet header source address field in an
attempt to make the packet appear as if it is coming from a trusted source.
The Defense
JUNOS Software provides IP address spoofing detection with the help of forwarding
table entries. JUNOS Software compares the source IP address of an incoming packet
with the closest prefix match found in its forwarding table. If the interface associated
with that prefix is different from the ingress interface of the packet, the software
concludes that the packet has a spoofed source IP address and discards it. Once it
detects IP spoofing, JUNOS Software silently drops all spoofed packets.
IP Spoofing DetectionSCREEN Option

and illustrates the
attack. No additional
mouse click is
necessary.
The slide illustrates an IP spoofing attack in which the attacker uses an IP address
belonging to the range of IP addresses within the private zone. JUNOS Software
compares the source IP address 168.10.10.1 of the incoming packet with the closest
match prefix found in its forwarding table, which is 168.10.10/24. It then detects that
the interface associated with prefix 168.10.10/24 is different from the ingress
interface of the packet, which is ge-1/0/0. The software concludes that the packet
has a spoofed source IP address and discards it.
To set up the JUNOS Software IP spoofing SCREEN option, you must perform the
configuration shown on the slide. Note that this configuration only defines the
SCREEN optionit does not activate it. To activate the SCREEN option, you must apply
it within a security zone. We address this topic later in the chapter.
The Attack
Source routing allows users to specify the packets desired path when traversing a
network. This feature provides additional aid to users during network troubleshooting.
Unfortunately, over the years, attackers have started to abuse source route options.
They use the fields to hide their true address and access restricted areas of a network
by specifying a different route.
The Defense
Depending on the configuration, JUNOS Software either blocks any packets with loose
or strict source route options settings, or detects those options as being set, and
records them. If you choose to block the suspect packets, the software silently
discards the packets.
IP Source Route OptionsSCREEN Options

and illustrates the
attack. No additional
mouse click is
necessary.
Using the illustration shown on the slide, we assume that network 3.3.3.0/24 checks
for spoofed IP addresses. The attacker, who is aware of this checking, wants to direct
traffic through network 5.5.5.0/24. The attacker spoofs the source address to be part
of network 5.5.5.0/24, and by using the loose source option, directs the packet
through network 5.5.5.0/24. Because the packet came from the 5.5.5.0/24 network
and has the source address of that subnet, it seems to be valid. However, it has the
loose source route option set. We also assume that you enabled the SCREEN option
that discards the packets with the source route option set. As a result, when the
packet arrives at the ge-1/0/0 interface, the JUNOS security platform rejects it.
To set up the JUNOS Software IP source route options SCREEN options, you must
perform configuration as shown on the slide. You can configure each of the options
independently. Note that this configuration only defines the SCREEN optionsit does
not activate them. To activate the SCREEN options, you must apply them within a
security zone. We address this topic later in the chapter.
Using JUNOS Software SCREEN OptionsDenial of Service Attack

Handling
Goals of DoS Attacks

If attackers discover a firewall, they might launch a DoS attack against it. In fact, many
attackers consider the successful DoS firewall attack to be equivalent to a network
attack because a firewall under DoS stops sending any traffic to and from a protected
network.
Firewall and Router Device DoS Attacks

An attacker might use two methods in an attempt to immobilize a JUNOS security
platform. Because JUNOS Software for security platforms is a session-based operating
system in which each packet flow creates a session, DoS attacks attempt to fill up the
session table in the hope that the device will reach its session table limit. Attackers
can use two methods to fill up the session table: session table flood and SYN-ACK-ACK
proxy flood.
Network DoS Attacks

A network DoS attack results in the flooding of many network resources with
enormous amounts of some combination of SYN, ICMP, and UDP packets. Depending
on the learned intelligence information, an attacker might target a specific host or a
specific network segment for attacks. JUNOS Software has the capability to mitigate
those attacks, which we discuss in the upcoming pages.
OS-Specific DoS Attacks

Should attackers identify an OS in use, they might launch an OS-specific DoS attack,
focusing on one-packet or two-packet kills. These attacks include the Ping of Death
attack, the Teardrop attack, and the WinNuke attack. JUNOS Software has the
capability to mitigate these attacks, which we discuss in the upcoming pages.
The Attack
The slide lists some of the forms that session table floods can take.
The Defense
To control session table floods, JUNOS Software offers the ability to set up a
source-based session limit so that it can prevent attacks such as the Nimda virus
(which infects servers and then generates massive amounts of traffic from those
servers). By recognizing that all connection attempts originate from the same source
IP address, JUNOS Softwares session table flood control also mitigates any attempts
to fill up the session table of the attacked JUNOS security device.
In addition to the source-based session limit, JUNOS Software offers the flexibility to
limit the number of concurrent sessions to the same destination IP address, which
protects your device from a distributed denial of service (DDoS) attack. DDoS attacks
can come from hundreds of various hosts, known as zombie agents, which are under
the control of an attacker.
Session Table FloodSCREEN Option

The slide illustrates the required configuration to limit the number of concurrent
sessions based on source IP address, destination IP address, or both.
JUNOS Software offers a default maximum number for a source-based or
destination-based session limit, which is 128 concurrent sessions. The valid range of
sessions depends upon the type of JUNOS security platform.
Note that the configuration shown on the slide only defines the SCREEN option. To
activate the SCREEN option, you must apply it within a security zone. We address this
topic later in the chapter.
Firewall and Router Device DoSSYN-ACK-ACK Proxy Flood: The Attack

and illustrates the
attack.
A SYN-ACK-ACK attack uses TCP connections. The attacker, using a seemingly normal
TCP connection, sends the SYN-ACK-ACK pattern, hoping that the targets will respond
and immobilize themselves. In the illustration shown on the slide, a malicious user
initiates a Telnet connection. The user sends a SYN segment to the Telnet server
behind the JUNOS security platform. JUNOS Software intercepts the SYN segment,
creates an entry in its session table, and proxies a SYN-ACK segment to the user. The
user replies with an ACK segment. At this point, the initial 3-way handshake is
complete. The server sends a login prompt to the user. The malicious user does not
log in. Instead, such a user continues to initiate SYN-ACK-ACK sessions, leading the
devices session table to its limit, which can result in rejecting legitimate connection
requests.
SYN-ACK-ACK Proxy Flood: The Defense

SYN-ACK-ACK proxy protection enables a JUNOS security platform to detect malicious
intent behind a seemingly normal TCP connection. Because the device acts as a proxy
for a TCP connection, creating a session table and proxying a SYN-ACK segment to the
sender, it can detect SYN-ACK-ACK sessions appearing after the success of the initial
session setup. JUNOS Software rejects further connection requests from an IP
address after the number of connections from that address reaches the SYN-ACK-ACK
proxy threshold. The default value of the proxy threshold is 512 connections from a
single IP address. The configured threshold can range from 1 to 250,000
connections.
The slide illustrates the syntax required to configure the SYN-ACK-ACK proxy flood
SCREEN option, limiting the number of concurrent TCP sessions from a single source.
Note that this configuration only defines the SCREEN optionit does not activate it. To
activate the SCREEN option, you must apply it within a security zone. We address this
The Attack
A SYN flood occurs when a network resource becomes overwhelmed with SYN
segments initiating uncompleted connection requests to the point where it cannot
accept legitimate connections. Very often a SYN flood attack inundates a site with SYN
segments containing forged or spoofed IP source addresses with nonexistent or
unreachable addresses, thereby forcing the targeted network resources to respond
with SYN/ACK segments to those addresses, then wait for responding ACK segments.
As the SYN/ACK segments travel to nonexistent or unreachable IP addresses, a
response never occurs, thus leading to a connection timeout. SYN floods also fill up
the memory buffer of the targets, potentially disrupting the operating system. A SYN
flood is usually directed at one or more network resources resulting in a network DoS.
The Defense
JUNOS Software can prevent SYN floods by limiting the number of SYN segments per
second permitted to pass through the JUNOS security platform. You can set the attack
threshold based on the destination address, source address, or both. This behavior
shields hosts on the protected network from incomplete 3-way handshakes. The next
two pages list the specifics of these protection schemes.
SYN FloodsSCREEN Options

The slide illustrates the JUNOS Software SCREEN options that you can implement to
handle SYN floods.
and illustrates the
attack.
Note that the illustrated configuration only defines the SCREEN option. To activate the
SCREEN options, you must apply it within a security zone. We address this topic later
in the chapter.
SYN FloodsSCREEN Options (contd.)

You can set up the following threshold parameters for proxying uncompleted TCP
connection requests:
Alarm threshold: This threshold is the number of proxied, half-complete

TCP connection requests per second before an alarm logs. This counter
begins after the below attack threshold triggers.The default and
configurable range varies by device type.
Attack threshold: This threshold is the number of SYN segments per

second required to trigger the SYN proxy mechanism. Although you can
set any threshold number within a specified range, we recommend that
you determine normal traffic patterns at your sites. The default and
Source threshold: This threshold is the number of SYN segments

received per second from a single source IP address, regardless of the
destination IP address and port number. Once requests reached the
threshold, further connection attempts drop. The default and
Destination threshold: This threshold is the number of SYN segments

received per second for a single destination IP address and destination
port pair. Once requests reach the threshold, further connection
attempts to the destination drop. The default and configurable range
varies by device type.
Timeout: This parameter is the maximum length of time before a

half-completed connection drop from the queue. The default is 20
seconds, and the range is 150 seconds.
Although these threshold parameters are independent of each other, you can
combine the SCREEN options in the configuration for better protection against
attacks.
SYN Cookie Advantages

The SYN proxying
feature described
previously can help
protect victim hosts
from SYN floods but
often makes the
firewall the target of
the attacker by
overwhelming its CPU
and session table
resources. The SYN
cookie feature does
not invoke costly
resource-intensive
actions, such as route
and session lookup,
session creation, and
so forth, until receipt
of a valid SYN cookie,
prior to allowing new
TCP connection flow
processing.
As mentioned previously when we discussed SYN floods, SYN segments directed at

network resources can render a network segment unusable. The SYN cookie feature
helps JUNOS security platforms ensure receipt of a valid SYN cookie response prior to
allowing processing of a new TCP connection flow, thereby avoiding the invoking of
resource-intensive actions such as route and session lookups. A SYN cookie is
stateless, and as such it does not set up a session, which requires policy and route
lookups. This stateless nature is the prime advantage of using a SYN cookie over the
traditional SYN proxying mechanism.
SYN Cookie Details

The SYN cookie was originally invented by D. J. Bernstein and Eric Shenk. Its purpose
is to minimize the impact of spoofed SYN flood attacks. The SYN cookie uses a
cryptographic hash to generate a unique TCP initial sequence number (ISN) when it
receives a SYN segment. The hash uses a counter, local address, foreign address, and
local and foreign ports to generate the cookie. JUNOS Software then sends a SYN/ACK
segment back with this cookie as an ISN. After it receives the ACK segment back, it
cryptographically verifies whether it is a valid ACK segment based on the cookie.
SYN Cookie Handling

The slide illustrates how a TCP connection establishes when a SYN cookie is active.
Once the SYN cookie is enabled, the JUNOS security platform becomes the
TCP-negotiating proxy for the destination host. It replies to each incoming SYN
segment with a SYN/ACK segment containing an encrypted cookie as its ISN. If there
is no response to the packet containing the cookie, the software notes the attack as
an active SYN attack, thereby stopping it.
and illustrates the
attack.
However, if the initiating host responds with a TCP packet containing the cookie plus 1
in the TCP ACK field, the software extracts the cookie, subtracts 1 from the value, and
recomputes the cookie to validate that it is a legitimate ACK message.
If the cookie is legitimate, the software starts the TCP proxy process by setting up a
session and sending a SYN to the destination host with the source information from
the original SYN message. When JUNOS Software receives a SYN/ACK from the
destination host, it sends ACK messages to the destination and the originating hosts.
Now the connection establishes and the two hosts can communicate directly.
ICMP FloodThe Attack

An ICMP flood typically occurs when ICMP echo request messages overload the victim,
causing resources to stop responding to valid traffic.
ICMP FloodThe Defense

JUNOS Software allows you to set up a threshold, which, once exceeded, invokes the
ICMP flood attack protection feature. Once requests exceed the threshold value (set in
packets per second), the software ignores any further ICMP echo request messages
for the remainder of that second plus the next second. The default and configurable
range varies by device type.
UDP FloodThe Attack

UDP flooding occurs when an attacker sends IP packets containing UDP datagrams
with the purpose of slowing down the target to such a degree that it cannot accept any
valid connections.
UDP FloodThe Defense

JUNOS Software UDP flood protection enables you to set up the threshold value,
which, once exceeded, invokes the UDP flood attack protection feature. The default
value and configurable range are in packets per second and vary by device type.
ICMP and UDP Flood HandlingSCREEN Options

and illustrates the
attack.
The slide illustrates an attacker trying to overload the target with an ICMP flood, a UDP
flood, or both. The slide illustrates the configuration syntax for ICMP and UDP flood
protection. Note that the configuration shown on the slide only defines the SCREEN
options. To activate the SCREEN options, you must apply them within a security zone.
We address this topic later in the chapter.
The Attack
A LAND attack occurs when an attacker sends spoofed SYN packets containing the IP
address of the target as both the destination and the source IP address. A receiving
system responds by sending the SYN-ACK packet to itself, creating an empty
connection that lasts until it reaches the session idle timeout. Flooding a system with
such empty connections can overwhelm one or more network resources resulting in a
network DoS.
The Defense
When you enable the JUNOS Software SCREEN option to block LAND attacks, JUNOS
Software combines elements of the SYN flood defense and IP spoofing protection to
detect software and block any malicious attempts of this nature.
LAND AttackSCREEN Option

The slide illustrates the impact of the LAND attack on network resources.
and illustrates the
attack.
Once you enable the LAND attack SCREEN option, the network is protected from the
attack.
The slide illustrates the configuration syntax for the LAND attack SCREEN option. Note
that the illustrated configuration only defines the SCREEN option. To activate the
SCREEN option, you must apply it within a security zone. We address this topic later in
the chapter.
The Attacks
The Ping of Death is an OS-targeted attack. It uses an oversized ICMP packet (larger
than 65,507 bytes), which can trigger a wide range of adverse OS reactions, including
DoS, crashing, freezing, and rebooting.
Teardrop attacks exploit the reassembly of fragmented IP packets. One of the fields in
the IP header is the fragment offset field, which indicates the starting position of the
data contained in a fragmented packet relative to the data of the original
unfragmented packet. When the sum of the offset and size of one fragmented packet
differ from that of the next fragmented packet, the packets overlap. A server
attempting to reassemble such a packet can crash.
WinNuke is a DoS attack targeting any computer on the Internet running Windows.
The attacker sends a TCP segment, usually to NetBIOS port 139 with the urgent flag
set, to a host with an established connection. This TCP segment introduces a NetBIOS
fragment overlap, which causes many machines running Windows to crash.
The Defense
To handle the Ping of Death attack, the JUNOS Software SCREEN option detects
oversized and irregular ICMP packets, even when the attacker hides the total packet
size by purposefully fragmenting it. To handle the Teardrop attack, the JUNOS
Software SCREEN option detects the discrepancy in a fragmented packet and drops it.
To handle the WinNuke attack, the software detects the urgency flag, unsets it, clears
the pointer, and forwards the modified packet. It then logs the attempted WinNuke
attack event.
PC-Based OS DoSSCREEN Options

The slide illustrates the syntax for configuring the Ping of Death, Teardrop, and
WinNuke SCREEN options.
Note that the illustrated configuration only defines the SCREEN options. To activate
the SCREEN options, you must apply them within a security zone. We address this
Using JUNOS Software SCREEN OptionsSuspicious Packets Attack

Handling
The Attack
ICMP, when used properly, provides an excellent aid for error reporting and network
probe capabilities. Typically, ICMP packets have very short messages. Therefore,
typically, ICMP packets do not fragment.
The Defense
JUNOS Software blocks any fragmented ICMP packet. In addition, the software drops
ICMP packets with a length greater than 1024 bytes.
ICMP Abnormalities DetectionSCREEN Option

The slide illustrates an IP packet header, highlighting the protocol field, which is equal
to 1 for ICMP, the total packet length field, the fragment offset field, and the M (more
fragments) field. Once you set the ICMP abnormalities detection SCREEN option,
JUNOS Software blocks any ICMP packets that have the M flag set or have an offset
value indicated in the fragment offset field. Furthermore, the SCREEN option can
include blocking unusually large ICMP packets (> 1024 bytes). To set up this SCREEN
option, you must perform the configuration shown on the slide.
Note that this configuration only defines the SCREEN option. To activate the SCREEN
option, you must apply it within a security zone. We address this topic later in the
chapter.
IP Packet FragmentsThe Attack

As packets traverse different networks, it is sometimes necessary to fragment them
based on the maximum transmission unit (MTU) for each network. IP fragments might
contain an attackers attempt to exploit the vulnerabilities in the packet reassembly
code of specific IP stack implementations. When the victim receives these packets,
the results can range from processing packets incorrectly to crashing the entire
system.
Bad IP Address OptionsThe Attack

Some attackers can abuse the IP option fields, the original intent of which was (and
still is) to provide special routing controls, diagnostic tools, and security. By
misconfiguring these options, attackers produce either incomplete or malformed
fields within a packet. Attackers can use these malformed packets to compromise
hosts on the network.
The Defense
Once you define the corresponding SCREEN option, JUNOS Software detects and
drops all IP packet fragments or packets with incorrectly formatted IP options that it
receives at the interfaces bound to the SCREEN options protected zone.
IP Packet Fragments and Bad IP Options DetectionSCREEN Option

The slide illustrates an IP packet header and highlights the more fragment (M),
fragment offset and IP options fields. Using the block-frag SCREEN option, JUNOS
Software checks whether the M field is set or if a nonzero value is in the fragment
offset field. If it finds any of these values set, it begins blocking fragmented IP
packets.
Attackers can configure the IP options field incorrectly, resulting in incomplete or
malformed fields. To set up the bad IP options SCREEN option, you must perform the
configuration shown on the slide.
chapter.
The Attack
IPv4 protocol field values of 137 or greater are currently unassigned and should be
used only for nonstandard or experimental protocols. Unless your network uses a
nonstandard or experimental protocol, you should block packets containing an IPv4
protocol field value of 137 or greater.
The Defense
drops any packet that uses an unknown protocol.
Unknown ProtocolsSCREEN Option

The slide illustrates an IP packet header and highlights the protocol field containing
the protocol number. To set up the unknown protocols detection SCREEN option, you
must perform the configuration shown on the slide.
chapter.
The Attack
IP encapsulates a TCP SYN segment into an IP packet that initiates a TCP connection.
Because the purpose of this packet is to initiate a connection and invoke a SYN/ACK
segment in response, the SYN segment typically does not contain any data.
Furthermore, because the IP packet is small, no legitimate reason exists for it to
fragment. A fragmented SYN packet is anomalous, and as such, it is suspect. When a
victim receives these packets, the results can range from processing packets
incorrectly to crashing the entire system.
The Defense
drops all received SYN fragments.
SYN FragmentsSCREEN Option

The slide illustrates IP and TCP headers and highlights the M and fragment offset
fields, which are part of the IP header, and the SYN flag, which is part of the TCP
header. Using the syn-frag SCREEN option, JUNOS Software checks SYN segments
to see whether the M field is set or if a nonzero value is in the fragment offset field. If
it finds SYN fragments, it begins blocking the SYN fragment packets.
To set up the SYN fragment SCREEN option, you must perform the configuration
shown on the slide.
chapter.
Applying and Monitoring SCREEN Options

Syntax for SCREEN Options Commands

The slide illustrates the JUNOS Software syntax that you must use when configuring
SCREEN options.
and reveals the steps in
order.
First you must define the SCREEN options. Then you must apply these options to the
desired zone. Recall that JUNOS Software applies SCREEN options at the ingress zone
of the JUNOS security platform prior to applying any security policy or route lookup.
Example
Consider the example illustrated on the slide. Two zones exist in this network: private
and public. The objective is to use SCREEN options to protect the private zone from
ICMP abnormalities, ICMP floods, and session table floods.
Case Study: Step 1Creating the SCREEN Option

The slide illustrates the creation of a SCREEN option named protect, which lists the
necessary options needed to meet the objective from the previous slide. The following
list describes the behavior of each SCREEN option:
icmp fragment: Blocks any ICMP packets that have the More Fragments
flag set or that have an offset value indicated in the offset field.
icmp large: Blocks any ICMP packets with a length greater than 1024
bytes.
icmp flood threshold: Ignores any ICMP packets received above the
configured threshold. This protection remains in effect for the duration of
the second when the threshold is reached, as well as the following
second.
source-ip-based session limit: Limits the number of sessions from one

source IP address to the specified number.
Note that by enabling SCREEN protection from large ICMP packets combined with
ICMP fragmented packets, you are also automatically enabling protection from the
Ping of Death attack.
Example: Step 2Applying the SCREEN Option

and emphasizes part of
the configuration.
The slide illustrates the application of the SCREEN option to the public zone.
Attack Monitoring: Part 1

You can monitor SCREEN statistics using the show security screen
statistics zone zone-name command. You can tell which values are
incrementing by issuing the command multiple times.

The slide shows the result of the show security screen ids-option
screen-name command, which displays the protect SCREEN option content.
Note the correspondence between the actual configuration of the protect SCREEN
option and the monitoring show security screen ids-option
screen-name command.

The slide illustrates an example traceoptions configuration for monitoring
SCREEN options operations. After committing the configuration, you can view the
resulting trace file using the show log filename command.
The meaning of SCREEN options;
Various types of attacks that SCREEN options can detect and prevent;
Advantages of using JUNOS Softwares SCREEN options;
Configuration of zone-based SCREEN options to block attacks; and
SCREEN option application and monitoring.
Review Questions
1.
The purpose of SCREEN options in JUNOS Software is to offer better network protection
to the networks behind the JUNOS security platform, and to the device itself, from malicious
information or attacks.
2.
The available SCREEN options include IP address sweep detection, port scanning detection,
network investigation triggering, operating system probe blocking, abnormal SYN and FIN
flags setting detection, IP spoofing detection, bad IP source route options detection, ICMP
abnormalities detection, and DoS attack detection.
3.
Beyond offering network and host protection against malicious attacks, the main advantage of
using SCREEN options is that JUNOS Software performs SCREEN checks prior to security
policy processing, which results in fewer resources used for malicious packet processing.
4.
There are two main goals for a DoS attack: immobilizing hosts and immobilizing networks.
5.
Apply SCREEN options under the security zones configuration stanza.
Lab 4: Implementing SCREEN Options


Chapter 7: Network Address Translation
The purpose and functionality of Network Address Translation (NAT) and

Port Address Translation (PAT);
NAT processing;
Configuration of destination NAT
Configuration of source NAT; and
Monitoring and verifying NAT operation.
Chapter 72 Network Address Translation
NAT Overview
first.
Network Address Translation Chapter 73
Network Address Translation

Historically, the NAT concept was born because of the shortage of public IPv4
addresses. Many organizations moved to deploy so-called private addresses using the
IPv4 private addressing space, as identified in RFC 1918. These addresses include
the following ranges:
10.0.0.010.255.255.255 (10.0.0.0/8 prefix);
172.16.0.0172.31.255.255 (172.16.0.0/12 prefix); and
192.168.0.0192.168.255.255 (192.168.0.0/16 prefix).
Because private addresses are not routable within the public domain, edge network
devices can deploy the NAT feature to replace private, nonroutable addresses with
public addresses prior to sending traffic to the public network and vice versa.
Translation consists of replacing the IP address (NAT), port numbers (PAT), or both,
depending on the configuration.
While primarily deployed to translate private addresses to public addresses, NAT can
translate from any address to any other address, including public to public and private
to private addresses.
You can use PAT in conjunction with NAT. Specifically, PATs invaluable benefit is that
several hosts can use a single public address. In this situation, PAT enables a unique
host and application match during the NAT process.
Review: Packet Flow

This animation slide
emphasizes the focus
of this chapter.
A JUNOS security platform implements NAT and PAT into both first path and fast path
flows processing. The slide reviews the NAT process position within the overall packet
flow. Note that destination NAT and source NAT occur separately in the first path
packet flow.
NAT and PAT Processing

During first packet processing, a combination of destination and source IP address
information and port translation information set up occurs. In first packet processing,
destination NAT processing occurs before security policy and route lookups while
source NAT processing occurs after security policy and route lookups. Based on the
first packet of a session, JUNOS Software installs NAT and PAT information into the
session table for fast path processing. This information speeds up subsequent packet
processing.
Two Basic Types of NAT

Two basic types of NAT existdestination NAT and source NAT. Destination NAT
translates the destination IP address of a packet. Source NAT translates the source IP
address of a packet. Both destination and source NAT can deploy either static or
dynamic address mapping.
Combination of Destination and Source NAT and PAT

Destination and source NAT and PAT can co-exist within the same platform. You can
deploy both source and destination NAT and PAT simultaneously, applying each within
its own flow direction.
Dynamic Versus Static Address Translation and Port Translation

Dynamic address translation implies that the association between the original
address and port and the translated address and port is not fixed. On the other hand,
static address translation implies that the association between the original address
and port and the translated address and port is fixed and has a one-to-one mapping.
We address this topic in more detail later in the chapter.
Destination NAT Operation and Configuration

Destination IP Address and Port Translation

Destination IP address and port translation imply that the device translates the
destination IP address to a different IP address, the destination port number to a
different port number, or both.
Two Mechanisms for Destination NAT and PAT

JUNOS Software supports two mechanisms to perform destination NAT and PAT:
Static NAT, which is a one-to-one mapping with no PAT; and
Standard pool-based NAT, which is a one-to-one mapping with or without

PAT, using address pools.
VoIP ALGs
Voice over IP (VoIP) application-level gateways (ALGs) dynamically generate the
allow-incoming table for packets from the public network into the private
network. The table contains the list of dynamically generated addresses for voice
traffic.
Matching Conditions
Traffic that requires destination NAT is subject to a two-layer matching scheme.
Similar to security policy, NAT rule creation occurs under a context indicating traffic
direction. The directional context is the first layer of matching. NAT rules are organized
in rule-sets. Each rule-set contains this context by requiring a from clause. The from
clause can indicate an interface, zone, or routing-instance. If rule-sets overlap by
targeting the same traffic, the rule-set with the most specific context takes
precedence. Interfaces are the most specific context, while routing-instances are the
least specific.
The second layer of matching occurs within NAT rules using a match option. These
options include source-address, destination-address, and
destination-port number. An exception to this second layer of matching is static
destination NAT, which supports only the destination-address match option.
This information is evaluated using packet headers.
NAT Rule Actions

Traffic that matches a directional context and NAT rule-matching condition is subject
to a NAT action. NAT actions are specified using a then clause and include off,
pool (followed by a user-defined pool name), and static-nat prefix (followed
by a user-defined address prefix). A destination NAT pool can contain a maximum of
one address or address-range and one port.
Overlap
Static NAT rules take precedence over dynamic destination NAT rules.
Note the following general guidelines regarding addresses, rule-sets, or rules that
overlap:
Addresses used for NAT pools, whether it be source NAT pools or

destination NAT pools, should never overlap;
If more than one rule-set matches traffic, the rule-set with the most
specific context takes precedence; and
Within a rule-set, the ordering of rules is significant. Rules evaluation

occurs sequentially. In other words, if traffic matches two rules within the
same rule-set, the first rule listed in the configuration is the only rule
applied.
Use the JUNOS Software insert command to adjust rules within a rule-set.
Live Configuration Changes

If a change is made to a NAT rule or pool that is currently in use, JUNOS Software tears
down the affected session once the change is committed. JUNOS Software re-initiates
the session as soon as it receives further matching traffic.
Static Destination NAT Sample Topology

The slide illustrates a sample topology that demonstrates static destination NAT using
JUNOS Software. Using the topology shown on the slide, we discuss enabling static
destination NAT for traffic destined to 100.0.0.1 coming from the Untrust Zone. The
traffic should translate to a private IP address of 10.1.10.5.
Static Destination NAT Configuration

The slide illustrates the required configuration to enable static destination NAT for the
given example. JUNOS Software static NAT requires a rule-set association with a
directional context. In this example, traffic from the Untrust Zone with a destination
address of 100.0.0.1 translates to a destination address of 10.1.10.5
Verifying the Result

Use the show security flow session command to observe NAT translation.
The output shows traffic entering the JUNOS security platform using the public
address 100.0.0.1 from a public host at 1.1.70.6. The return traffic from this flow
originates with the private address 10.1.10.5.
Static Source NAT

The slide illustrates the creation of a second session. Once static destination NAT is
enabled and a session triggers, JUNOS Software automatically creates a reverse static
source NAT session. Neither the destination static NAT session, nor the source static
NAT session creation occurs until traffic that matches the NAT rule actually traverses
the device.
Pool-Based Destination NAT Sample Topology

The slide illustrates a sample topology that demonstrates pool-based destination NAT
using JUNOS Software. Using the topology shown on the slide, we will enable
pool-based destination NAT for traffic destined to 100.0.0.1 coming from the Untrust
Zone. The traffic should translate to a private IP address of 10.1.10.5.
Pool-Based Destination NAT Configuration with a Single Address

The slide illustrates the required configuration to enable destination NAT for the given
example. JUNOS Software pool-based NAT requires a user-defined address pool and a
rule-set that associates with a directional context. In this example, traffic from the
Untrust Zone with a destination address of 100.0.0.1 translates to a destination
address of 10.1.10.5. This example includes a pool with only one available address
and no port translation.
Pool-Based Destination NAT Configuration with an Address Pool

Network
administrators rarely
implement destination
NAT using pools with
multiple addresses.
However, JUNOS
Software includes this
feature and it may be
used for
load-balancing traffic
to a session-unaware
server such as a DNS
server.
The slide illustrates the required configuration to enable destination NAT for the given
example. JUNOS Software pool-based NAT requires a user-defined address pool and a
rule-set that associates with a directional context. In this example, traffic from the
Untrust Zone with a destination address of 100.0.0.1 translates to a destination
address within a range of 10.1.10.5 to 10.1.10.6. There is no port translation.
Pool-Based Destination NAT Configuration with PAT

The slide illustrates the required configuration to enable destination NAT and PAT for
the given example. JUNOS Software pool-based NAT requires a user-defined address
pool and a rule-set that associates with a directional context. In this example, traffic
from the Untrust Zone with a destination address of 100.0.0.1 and a destination port
of 80 translates to a destination address of 10.1.10.5 and a destination port of 8080.
Result of NAT with PAT

The output shows traffic entering the device using the public destination address
100.0.0.1 and destination port of 80 from a public host at 1.1.70.6. The return traffic
from this flow originates with the private address 10.1.10.5 and private port 8080.
The show security nat destination pool all command illustrates the
pool of translated addressesin this case a single addressand the translated port
number. You can also view this output for an individual address pool by specifying the
pool name instead of using the all option.

Use the show security nat destination rule all operational mode
command to view NAT rules as JUNOS Software programs them. The output on the
slide illustrates the rule. You can verify traffic translation by this rule by the translation
hits counter.
You can also view this output for an individual NAT rule by specifying the rule name
instead of using the all option.
Source NAT Operation and Configuration

Source IP Address and Port Translation

Source IP address and port translation imply that the router translates the source IP
address to a different IP address, the port number to a different port number, or both.
Three Mechanisms for Source NAT and PAT

JUNOS Software supports three methods to perform source NAT and PAT:
Interface-based source NAT, which is the translation of the original

source IP address to the egress interfaces address always employing
PAT;
Standard pool-based NAT, which is a dynamic mapping of the original

source address to an address from a user-defined pool with or without
PAT; and
Source NAT with address shifting, which is a one-to-one mapping of the

original source address to a user-defined pool performed by shifting the
IP addresses without PAT.
Matching Conditions
Traffic requiring source NAT application is subject to a two-layer matching scheme.
Similar to security policy, JUNOS Software creates source NAT rules under a context
indicating traffic direction. The directional context is the first layer of matching. NAT
rules are organized in rule-sets. For source NAT, each rule-set contains this context by
requiring a from clause and a to clause. The from and to clauses indicate an interface,
zone, or routing-instance. If rule-sets overlap by targeting the same traffic, the rule-set
with the most specific context takes precedence. Interfaces are the most specific
context, while routing-instances are the least specific.
The second layer of matching is performed within NAT rules using a match option.
These options include source-address and destination-address. This
information is evaluated using packet headers.
NAT Rule Actions

Traffic that matches a directional context and NAT rule-matching condition is subject
to a NAT action. Source NAT actions are specified using a then clause and include
off, pool (followed by a user-defined pool name), and interface (followed by a
user-defined interface name including the logical unit).
Overlap
Static source NAT (reverse mapping of static destination NAT) rules take precedence
over dynamic source NAT rules.
Note the following general guidelines regarding addresses, rule-sets, or rules that
overlap:
Addresses used for NAT pools, whether it be source NAT pools or

destination NAT pools, should never overlap;
If more than one rule-set matches traffic, the rule-set with the most
specific context takes precedence; and
Within a rule-set, the ordering of rules is significant. Rules evaluation

occurs sequentially. In other words, if traffic matches two rules within the
same rule-set, the first rule listed in the configuration is the only rule
applied.
Use the JUNOS Software insert command to adjust rules within a rule-set.
Live Configuration Changes

If a change is made to a NAT rule or pool that is currently in use, JUNOS Software tears
down the session once the change is committed. JUNOS Software re-initiates the
session as soon as it receives further matching traffic.
Interface-Based Source NAT Sample Topology

The slide illustrates a sample topology that demonstrates interface-based source NAT
using JUNOS Software. Using the topology shown on the slide, we will enable
interface-based source NAT for traffic sourced from the network attached to the
ge-0/0/2.0 interface with a destination belonging to the Untrust Zone. The traffic
should translate to use the egress interface address 1.1.70.5.
Interface-Based Source NAT Configuration

The slide illustrates the required configuration to enable interface-based source NAT
for the given example. Similar to static NAT, pools are not necessary for this
configuration. Interface-based NAT requires a rule-set to associate with a directional
context. In this example, traffic from the network attached to the
ge-0/0/2.0 interface that has a destination address belonging to the 1.1.70/24 prefix
translates to a source address of the egress interface.

The output shows traffic entering the device using the private source address
10.1.10.5 destined to a public host at 1.1.70.6. The return traffic from this flow travels
to the translated public address 1.1.70.5.
The show security nat source summary command provides a quick look at
the rule-set, rule, context, and rule action resulting from this configuration.
Pool-Based Source NAT Sample Topology with PAT

The slide illustrates an example topology that demonstrates pool-based source NAT
and PAT using JUNOS Software. Using the topology shown on the slide, we will enable
pool-based source NAT with PAT for traffic destined to the Untrust Zone and sourced
from the Trust Zone. Only traffic belonging to the 10.1.10/24 network should
translate. The traffic should translate to a public source IP address of 207.17.137.229.
Pool-Based Source NAT Configuration with PAT

The slide illustrates the required configuration to enable source NAT and PAT for the
given example. JUNOS Software pool-based NAT requires a user-defined address pool
and a rule-set that associates with a directional context. In this example, traffic from
the Trust Zone destined to the Untrust Zone and with a source address belonging to
the prefix 10.1.10/24 translates to a source address of 207.17.137.229. In JUNOS
Software, PAT is automatically enabled for pool-based source NAT.

10.1.10.5 destined to a public host at 1.1.70.6. Source address translation occurs
and the return traffic is sent to the public address 207.17.137.229.
The show security nat source summary command provides a quick way to
look at existing source NAT rules and pools. In this case, the source NAT pool contains
a single address, and PAT is enabled by default. The source NAT rule illustrates the
parameters set by the configuration with an associated action of translation using
Pool A.
PAT Is Default
As illustrated in the previous example, JUNOS Softwares implementation of source
NAT enables PAT by default. Because PAT is enabled and the number of available ports
is near 64,000, it is rare that a source NAT pool will exhaust.
Address Persistence
Regardless of the large available source NAT pool, there is no guarantee that JUNOS
Software will use the same source IP address for different traffic types associated
with the same source host. To ensure the use of the same address, configure the
address-persistent global source NAT option as shown on the slide.
Pool-Based Source NAT Sample Topology Without PAT

The slide illustrates a sample topology that demonstrates pool-based source NAT
without PAT using JUNOS Software. Using the topology shown on the slide, we will
enable pool-based source NAT without PAT for traffic destined to the Untrust Zone and
sourced from the Trust Zone. Only traffic belonging to the 10.1.10/24 network should
translate. The traffic should translate to a public source IP address range consisting of
the 207.17.137/24 network.
Disabling PAT dramatically reduces the number of addresses available in a source
pool. Recall that previously, using PAT, approximately 64,000 variations were available
per address. Without PAT, each address in the source pool must use its original source
port, which can lead to higher pool utilization. To combat this problem, we will enable
a backup method to use the egress interface address if a pool is exhausted of
addresses. We refer to this backup method as an overflow pool. An overflow pool can
use the egress interface (as in this example) or a separate user-defined pool. In either
case, the overflow pool must have PAT enabled, which is the mandated default for
interface-based NAT.
Pool-Based Source NAT Configuration Without PAT

The slide illustrates the required configuration to enable source NAT without PAT for
the given example. JUNOS Software pool-based NAT requires a user-defined address
pool and a rule-set that associates with a directional context. In this example, traffic
from the Trust Zone destined to the Untrust Zone and with a source address belonging
to the 10.1.10/24 prefix translates to a source address belonging to the 207.17.137/
24 prefix. PAT is explicitly disabled and an overflow pool is defined using the egress
interface address, in case pool A becomes exhausted of all available addresses.
Recall that interface-based source NAT uses PAT by default.

10.1.10.5 destined to a public host at 1.1.70.6. Source address translation is
performed, and the return traffic is destined to the public address 207.17.137.127.
The show security nat source summary command provides a quick way to
look at existing source NAT rules and pools. In this case, the source NAT pool contains
the 207.17.137.1 through 207.17.137.254 address range and PAT is disabled. The
source NAT rule illustrates the parameters set by the configuration with an associated
action of translation using pool A.
Pool Utilization
If JUNOS Software runs out of addresses in a source NAT pool, further packets
requiring translation will drop. We already discussed one method to overcome this
problemusing an overflow pool. While an overflow pool is a handy tool, you likely also
want to know that this situation has occurred so that you can take measures to
increase the pool size or evaluate the usage patterns.
To enable SNMP traps,
you must configure
SNMP under the
[edit system]
configuration
hierarchy. For more
information about
SNMP configuration,
refer to the Juniper
Networks technical
documentation.
JUNOS Software provides a pool utilization alarm for monitoring pool usage. The
utilization alarm is disabled by default. The slide shows the configuration for the pool
utilization alarm, which is global to the source NAT stanza. The values represent a
percentage of pool utilization. Once pool utilization reaches the raise-threshold (in this
case, 50%), the JUNOS security platform sends an SNMP trap notification to a
configured network management station. If traffic falls below the clear-threshold,
JUNOS Software sends an SNMP trap to the network management station. Note that
while the pool utilization alarm is disabled by default, if configured, the default setting
for the clear-threshold is 80 percent of the raise-threshold.
Source NAT with Address Shifting Sample Topology

The slide illustrates a sample topology that demonstrates source NAT with address
shifting using JUNOS Software. Using the topology shown on the slide, we will enable
source NAT with address shifting for traffic destined to the Untrust Zone and sourced
from the Trust Zone. Only traffic belonging to the 10.1.10/24 network should be
translated starting with the 10.1.10.5 address for shifting purposes. The traffic should
translate to a public source IP address range consisting of the 207.17.137/24
network.
By definition, this type of translation is one-to-one, static, and without PAT. If the
original source address range is larger than the address range in the user-defined
pool, packets might drop. Use the previously discussed tools to assist in this situation.
Source NAT with Address Shifting Configuration

The slide illustrates the required configuration to enable source NAT with address
shifting for the given example. JUNOS Software source NAT with address shifting
requires a user-defined address pool and a rule-set that associates with a directional
context. In this example, traffic from the Trust Zone destined to the Untrust ZoneTrust
Zone and with a source address belonging to the 10.1.10/24 prefix translates to a
source address belonging to the 207.17.137/24 prefix. The 10.1.10.5 address is
configured as the host-address-base and serves as a starting point for address
shifting.

10.1.10.5 destined to a public host at 1.1.70.6. Source address translation is
performed, and the return traffic travels to the public address 207.17.137.1.
The show security nat destination pool all command illustrates the
pool of translated addresses. In the example, because address shifting is used for this
pool, the full range is not listed; however, the output shows that 254 total addresses
are available. The 10.1.10.5 address shows as the base starting address for address
shifting. The output also illustrates that PAT is disabled for this type of address
translation. You can view this output for an individual address pool by specifying the
pool name instead of using the all option.
Pop Quiz!
The off NAT action is useful for detailed control. The configuration shown on the slide
represents how you might use a NAT off action. In this example, all traffic sourced
from the 10.1.10.0/24 network, with the exception of traffic destined to the
172.18.20.0/24 has source NAT applied to it. Recall that the ordering of rules within a
rule-set is significant. In the example, traffic matching the directional context (from the
Trust Zone to the external zone) is first evaluated by rule 1 and then evaluated by
rule 2.
Proxy ARP
When to Use Proxy ARP

JUNOS Software for security platforms requires a proxy Address Resolution Protocol
(ARP) configuration whenever translated traffic belongs to the same subnet as the
ingress interface. This task is not automatic and you must configure it as needed.
When a network device needs to send a packet to a destination IP address using
ethernet, the device sends an ARP request to obtain the layer two MAC address
associated with the destination IP address. Once that association is in place, the
sending device typically stores this information in memory and subsequently
addresses ethernet frames to the appropriate Layer 2 MAC address. Without proxy
ARP, if an interface receives an ARP request for an address other than its own, it
ignores the packet. It assumes the packet is meant for another device attached to the
same broadcast media. Using proxy ARP, the interface acts as a proxy for the
destination by replying to ARP requests on behalf of the intended destination. Packets
destined for the intended destination then travel to the proxying device, which can
then forward the packets to the actual destination.
The slide illustrates the configuration hierarchy and options for NAT proxy ARP.
Proxy ARP Example

The slide illustrates a sample situation requiring proxy ARP and the associated
configuration. In the example, the device performs source translation for traffic from
the Trust Zone, translating the private source address to a public source address in
the 1.1.70.10 to 1.1.70.100 address range. The NAT source pool belongs to the same
subnet as the public interface. For return traffic to successfully reach the 10.1.10.5
host, the device must perform proxy ARP for the 1.1.70.101.1.70.100 address
range.
Monitoring and Verifying NAT Operation

Key Monitoring Commands

The slide lists four operational mode show commands used to verify and monitor NAT
operation. We repeatedly illustrate these commands throughout examples in this
chapter. You can use the show security nat commands for source or destination
NAT.
Traceoptions for NAT Operation

Traceoptions are available for a more detailed view of NAT operation. The traceoptions
log is stored as /var/log/security-trace by default, or optionally, the user can define a
different log name.
NAT internal operation consists of two main componentsthe Packet Forwarding
Engine (PFE) and the Routing Engine (RE). The PFE is divided into two elementsthe
ukernal element and the real-time element. Traceoptions flags can be set to trace NAT
operation within the PFE ukernal, the PFE real-time element, or within the RE. The
output that follows lists all the available flags for tracing NAT operation.
Traceoptions for NAT Operation (contd.)

[edit security nat traceoptions]
user@host# set flag ?
all
Trace everything
destination-nat-pfe Trace destination nat events on PFE-ukernel side
destination-nat-re
Trace destination nat events on RE side
destination-nat-rt
Trace destination nat events on PFE-RT side
source-nat-pfe
Trace source nat events on PFE-ukernel side
source-nat-re
Trace source nat events on RE side
source-nat-rt
Trace source nat events on PFE-RT side
static-nat-pfe
Trace static nat events on PFE-ukernel side
static-nat-re
Trace static nat events on RE side
static-nat-rt
Trace static nat events on PFE-RT side
The purpose and functionality of NAT and PAT;
NAT processing;
Configuring destination NAT;
Configuring source NAT; and
Monitoring and verifying NAT operation.
Review Questions
1.
Destination NAT processing occurs before security policy processing and source NAT
processing occurs after security policy processing.
2.
Static source NAT is supported in one of two waysusing source NAT with address shifting
or the automatic creation of a return session when using static destination NAT.
3.
The NAT off action is for detailed control within NAT rule-sets.
4.
A NAT proxy ARP configuration is necessary when the translated address belongs to the
same subnet as the ingress interface.
5.
The commands used to monitor NAT operations are show security flow
session, show security nat source summary (or show security nat
destination summary), show security nat source pool (or show
security nat destination pool), and show security nat source
rule (or show security nat destination rule).
Lab 5: Network Address Translation


Chapter 8: IPsec VPNs
Chapter 82 IPsec VPNs
Various types of virtual private networks (VPNs);
Major security concerns;
IP Security (IPsec) VPNs and their functionality;
IPsec VPN configuration using policy-based and route-based methods;

and
IPsec VPN monitoring.
VPN Types
first.
IPsec VPNs Chapter 83
The Meaning Behind VPNs

VPNs are used to transport private network traffic over a public network infrastructure.
The term VPN has been used broadly in the networking industry for decades. For
instance, the networking industry has referred to X.25, Frame Relay, and ATM
infrastructures as VPN networks. As the Internet spread and as carriers and service
providers migrated all their service offerings to IP, new forms of VPNs emerged.
Types of VPNs Today

We can subdivide these new forms of VPNs into three categories:
Clear-text VPNs: These VPNs include Layer 3 VPNs, Layer 2 VPNs

(Kompella and Martini implementations), and virtual private LAN service
(VPLS). These VPNs rely on MPLS services and the use of signaling
protocols over IP.
Secure VPNs: These VPNs are IPsec VPNs, carrying payload over IP
securely. We will discuss these VPN types in this chapter.
Combination of clear-text and secure VPNs: These VPNs are based on

Layer 3 VPNs, built on MPLS technology, and compounded with IPsec
security.
Secure VPNs
A network device that builds secure VPNs must be able to perform the following
actions:
It highlights the
encrypted packet
between private and
public sites.
Encrypt the original packet so that it cannot be easily decoded should it

be intercepted on the public network;
Verify the original payload ensuring data integrity; and
Authenticate the originating device as a member of the VPN, rather than

a random device operating on the public network.
This chapter focuses on end-to-end static IPSec VPNs. However, note that JUNOS
security platforms also support end-to-site dynamic VPNs and VPN establishment
using the NetScreen Remote VPN client. See the Juniper Networks technical
documentation at http://www.juniper.net/techpubs for further information on these
features.
Secure VPN Requirements

Security Concerns
Three driving concerns exist for network security: confidentiality, integrity, and
authentication.
Confidentiality: Online banking, credit card information, or a companys

competitive informationhow do we keep this information secure from
the man in the middle? We want information stored in such a way that if
someone were to capture this datagram, the information would appear
meaningless.
Integrity: Even though the information might be secure and hidden,

meaning that someone might not be able to determine or understand its
contents, it could still be possible for someone to change it. Someone
could tweak bits to change the data from what was originally sent
through the network. So how do we ensure that if the data is
compromised, the remote station recognizes this fact and refuses to
process the information?
Authentication: How does the remote station verify that the information
came from the device from which it expected it to come? You do not want
to be communicating and sending critical information to the wrong
recipient!
ConfidentialityData Encryption
The first of the three VPN security concerns is confidentiality.
Encryption provides data confidentiality. Encryption is the method of taking user
datareferred to as plaintextand converting it into unreadable or secret data named
ciphertext. An encryption algorithm and keys (strings of bits that seed the encryption
process) are applied to the data, resulting in ciphertext.
To reverse the process and decrypt the ciphertext, you must know both the encryption
algorithm and encryption key. You can decrypt encrypted data in one of two ways:
Symmetric key encryption: This method uses the same key for both
encryption and decryption; and
Asymmetric key encryption: This method uses a private key for

encryption and a mathematically related public key for decryption.
The cipher strength depends on the key size; the larger the key, the more secure the
cipher output. The trade-off is in processing timelarger keys use more computational
cycles to encrypt and decrypt.
ConfidentialitySymmetric Key Encryption

Symmetric key encryption is the most straightforward form of encryption with the least
amount of overhead. We refer to it as symmetric because the key used to encrypt the
data is the same key used to decrypt the data. Thus, the same key must be known on
both sides of a connection.
It illustrates the order
of symmetric key
encryption.
Symmetric key sizes range from 40 bits1024 bits. These keys are considered to be
very fast as they are not very long, and they are widely used for bulk data encryption.
However, because the key must be known to both the sender and the receiver, key
management is a problem when using symmetric keys.
Examples of symmetric key encryption include Rivest Cipher 4 (RC4), Data Encryption
Standard (DES), Advanced Encryption Standard (AES), and Blowfish.
Public Key Encryption

It illustrates the order
of public key
encryption events.
The public, asymmetric key encryption method requires a pair of mathematically

related keys. One of the keys is kept secret and known only to the owner; this key is
the private key. The owner distributes the other key widely and anyone can access it;
this key is the public key. You can only decrypt data encrypted by the private key by
using the corresponding public key, and vice versa. The keys are mathematically
related such that it is almost impossible to derive one key out of another.
Public key sizes range from 512 to 2048 bits. Because of the large size, these keys
are extremely slow and generally not feasible for bulk data encryption. However, public
keys are widely used for user and device authentication (for example, digital
certificates). An example of public, asymmetric key encryption is RSA.
Integrity
Now that we have the data encrypted as it traverses the Internet, we must ensure that
the data is not subject to modification along the way. Even though a novice hacker
might not be able to crack the encryption algorithm and key, the hacker can still wreak
havoc by modifying bits that the encrypted payload carries. If this modification
happens, the decrypted output does not match the original data. Who knows what the
consequences might be!
Hashing solves this problem by creating a fingerprint of the data, similar to a cyclic
redundancy check (CRC) checksum. Before data travels, it traverses a hashing engine
that produces a fixed-length hash output. It places the hash in a field in the packet
along with the data before it travels over the network. The destination device takes the
same data and runs it through the same hashing algorithm, calculating its own hash.
The destination device then compares the hash that it calculated against the hash
carried in the packet. The same hash in both locations proves data integrity in transit.
If the hashes do not match, the packet drops.
JUNOS Software supports MD5, SHA1, and 256-bit SHA2 hashing.
One-Way Hash Algorithms

A hash function must have two basics properties:
You should not be able to calculate the original data from the hashed
output. This property ensures that you cannot derive the plaintext from
the ciphertext.
It must be mostly collision resistant. A collision occurs when two different

inputs give the same output. It must not be possible to predict a different
input value that gives the same output. This property is necessary
because the purpose of hashing is to verify that the data has not
changed.
To see how it is possible to create a one-way function, think of the example on the
slide, which shows a modulus operation. Given the value of 3, it is not possible to
determine the original value because an infinite range of possible answers exists.
However, this example is not suitable as a real-world hash function because it does
not satisfy the collision-resistant requirementa malicious person can change the
plaintext by any multiple of the modulus number and know that the hashed value
remains the same.
The most secure and widely used hash function is the Secure Hash Algorithm 1
(SHA-1). SHA-1 is preferred over Message Digest 5 (MD5), although MD5 is still widely
supported. These functions produce a fixed-length output that is useful when working
with IP packets because the overhead of transmitting the hash value is predictable.
IntegrityThe Hash Process

The following list outlines the hash process:
It illustrates the hash
process.
1.
The sender runs the data through the hash process.
2.
The sender appends the hash value to the data and sends both the data
and the hash value to the receiver.
3.
The receiver separates the data and the hash value.
4.
The receiver hashes the data.
5.
The receiver then compares the calculated hash value to the received
hash value. If the hash values match, the data is unaltered.
Source Authentication
Encryption protects the packet contents from being viewed on the public network.
Hashing verifies that the data is unaltered. But how do you validate the source of the
data?
The software performs source authentication using the Hashed Message
Authentication Code (HMAC). The sender appends a secret preshared key to the data,
then performs the hash function. For hashes to successfully match, the receiver must
append the same key value to the data before performing the hash function. The key
itself never transmits along with the data.
HMAC Authentication
The following list outlines hashing with HMAC:
It illustrates HMAC.
1.
The sender appends the preshared key to the data, then performs the
hash function.
2.
The data and hash value travel to the receiver.
3.
The receiver separates the data and the hash value.
4.
The receiver appends the preshared key to the data, then performs the
hash function.
5.
The receiver then compares the calculated hash value to the received
hash value. If the hash values match, the data is unaltered. If the hash
values do not match, either the data itself is corrupt, or the keys did not
match, meaning the source is invalid. Either way, the receiver discards
the packet.
Key Exchange
As we already discussed, both encryption and authentication are dependent on
security keys, which leads to the problem of key exchange. If keys must be the same
on both sides of a connection, how can you securely exchange key information?
One option is to manually configure the keys on both sides of the connection. Manual
key configuration is straightforward, but misconfigurations, especially when each
device has a different administrator, are common. Furthermore, manual configuration
usually means that keys rarely change, which is itself a potential security issue; given
a large enough sample, any code can be broken.
Automating the key exchange process is a good idea, but we must overcome the
problem of sending keys across a public network. Anyone intercepting the key has the
ability to decode the data.
The Solution
Whitfield Diffie and Martin Hellman developed a solution to this problem in 1970. The
Diffie-Hellman algorithm is a method whereby two parties can agree upon a secret key
known only to them. The strength of the technique is that it allows the participants to
create the secret value over an unsecured medium without exchanging the secret
value itself. This method also makes it impossible to perform reverse generation of
the secret if it is somehow intercepted.
Diffie-Hellman Groups
Diffie and Hellman proposed five groups of prime numbers and generator values to
use in their key exchange algorithm. Each group generates unique keys using a
combination of exponential and modulus calculations.
Juniper Networks does
not support Groups 3
and 4.
JUNOS Software supports Diffie-Hellman (DH) Groups 1, 2, and 5. The larger the
prime numberthe stronger the keyand the more computationally intensive the
calculation. Diffie-Hellman Group 1 uses a 768-bit prime number. Diffie-Hellman
Group 2 uses a 1024-bit prime number. Diffie-Hellman Group 5 uses a 1536-bit prime
number.
You must configure both tunnel peers to use the same DH group; otherwise, the key
generation process fails.
The DH Key Exchange Process

It illustrates the DH
key exchange process.
Using the same DH group, each JUNOS security platform creates unique public and
private keys. These keys are mathematically related by means of the DH algorithm.
The public key values exchange across the network. Each peer then runs its local
private key and the received public key value through the DH algorithm to compute a
common session key. The session key itself never passes across the network.
IPsec Details
IPsec Overview
IPsec is a set of standards that defines how the encryption, validation, and
authentication methods we just discussed are actually implemented in networks.
IPsec works at Layer 3; it supports both unicast and multicast traffic.
IPsec: A Two-Step Process

IPsec VPNs consists of two major steps:
It emphasizes the topic
that we cover next
tunnel establishment.
1.
IPsec tunnel establishment: You can manually establish an IPsec tunnel

or the Internet Key Exchange (IKE) protocol can do it dynamically.
2.
IP traffic processing: During this step payload protection takes place

using security parameters defined in the tunnel establishment phase.
We cover the first stepIPsec tunnel establishment using IKEon the next several
pages.
Step 1: Tunnel Establishment Using Internet Key Exchange

IKE is a secure key management protocol used by IPsec to have information
exchanged in a secure and dynamic manner with little or no intervention. The IKE
proposal exchange is Phase 1 of the IPsec tunnel establishment process. The
following attributes exchange between IPsec peers as a part of the IKE process:
Encryption algorithm;
Hash algorithm;
Authentication method; and
Diffie-Hellman group.
Once IPsec peers negotiate these attributes, they secure future attribute exchanges
used to protect data. IKE exchanges authenticate using one of the following methods:
Preshared keys;
Digital signatures; or
Public key encryption.
IKE is preferable to manual keys in IPsec implementations because of the ease of

management and scalability.
Security Associations
A security association (SA) is a set of policies and keys used to protect information.
SAs establish upon the successful completion of IKE negotiations. An SA is uniquely
identified by the security parameter index (SPI) value, the tunnel destination address,
and the security protocolEncapsulating Security Payload (ESP) or authentication
header (AH)in use. The lifetime of an SA can be based on either a time value or a
value determined by the volume of traffic protected by the proposal.
SA Database
SAs are stored in a security association database. Each entry includes the name of
the particular VPN, the remote gateway IP address, the SPIs for each direction, the
agreed-upon security protocol, encryption, and authentication algorithms and keys.
IKE Phases
IKE tunnel establishment happens in two phases:
Phase 1 establishes a secured channel between gateways for Phase 2

negotiations to occur. The Diffie-Hellman key exchange algorithm
establishes a shared key for encryption.
Phase 2 establishes the specific VPN connections. SAs are negotiated on

behalf of IPsec to determine the encryption and authentication
algorithms to use when sending user data. The SA is identified by a
unique SPI that is also negotiated during Phase 2.
A single Phase 1 channel can establish multiple Phase 2 SAs or VPNs. If wanted, a
second Diffie-Hellman exchange can be performed during Phase 2 to negotiate a new
tunnel key. Because of the encryption on this exchange, it is named Perfect Forward
Secrecy (PFS).
IKE Phase 1: Main Mode

IKE main mode is used when both tunnel peers have static IP addresses. The Phase 1
exchange determines the following attributes:
It illustrates the
sequence of events of
IKE Phase 1 in main
mode.
Hash algorithm;
DH group; and
Authentication method:
Preshared keys;
Digital signatures; and
Public key encryption.
The first two messages validate the peer configuration (by checking the cookie against
the locally configured peer IP address) and negotiate the parameters listed previously.
Both tunnel peers must have at least one configured matching proposal for Phase 1
exchange success.
The next two messages exchange Diffie-Hellman public key values and nonces
necessary to compute the shared key.
The last two messages send simple identification information using the negotiated
key; these messages validate that the key calculation was correct.
IKE Phase 1: Main Mode (contd.)

For Message 1 and Message 2, peers exchange cookies and SA proposals. Cookies
are 8-byte pseudo-random numbers generated by the sending machine (I=initiator)
and receiving machine (R=receptor). Every cookie is unique to the machine and to
each particular exchange. These cookies guarantee uniqueness and replay protection
by hashing the sender's IP address, port, protocol, and timestamp, which results in a
unique identifier known only to the originator. Hence, they are included in every IPsec
packet and used to identify communication. In turn, the receptor inserts its known
cookie in Message 2 if it accepts the SA proposal.
An IPsec SA proposal contains the following:
Phase 1 authentication method (main mode or aggressive mode);
DH group number;
Authentication algorithm; and
Key lifetime.
For Message 3 and Message 4, the DH public values exchange to create a common
session key. Nonces, which are essentially random numbers, also exchange at this
time for use as seeds for keys generated later.
After both sides exchange their DH public values, a key is created on each side to
encrypt the rest of the IKE Phase 1 messages. The session key is a result of the
exchanged public keys traveling to each partner.
Messages 5 and 6 contain the preshared key.
IKE Phase 1: Aggressive Mode

It illustrates the
IKE Phase 1 in
aggressive mode.
IKE aggressive mode is used when one of the tunnel peers has a dynamic IP address
that could be a remote end user dialing in to the Internet, or a remote site using DHCP
to acquire an IP address. (Main mode cannot be used because the first two messages
validate peer IP addresses. In the case of a dynamic host address, the peer cannot
preconfigure the address.)
Phase 1 aggressive mode must initiate by the device with the dynamic IP address. The
first two messages negotiate policy and exchange DH public values and nonces. In
addition, the second message authenticates the responder; the ID hash is compared
with the locally configured peer ID.
The third message authenticates the initiator and provides a proof of participation in
the exchange.
IKE Phase 2: Quick Mode

It illustrates the
IKE Phase 2.
Once Phase 1 is complete, proposals exchange to establish a specific VPN. The

following attributes are negotiated in Phase 2:
Security protocol (ESP or AH);
Tunnel mode or transport mode;
Proxy IDs; and
Optional DH group.
Upon successful completion of quick mode, user data encrypts between the
configured IPsec peers. Both tunnel peers must have at least one matching proposal
configured for Phase 2 exchange success.
The result of Phase 2 is to create an IPsec VPN for user data to securely transmit
through the network.
IKE Phase 2: Quick Mode (contd.)

For Message 1 and Message 2, a Phase 2 proposal list exchanges. The list contains
encrypted and authenticated information that determines the algorithms and keys for
encrypting and authenticating user data. The Phase 2 proposal list contains the
following items:
ESP or AH;
DH group number (0 for no PFS);
Authentication algorithm;
Key lifetime;
Proxy ID (policy rule); and
DH public keys (optional if using PFS).
Message 3 acknowledges information sent from quick mode Message 2 so that the
Phase 2 tunnel can establish.
IPsec: A Two-Step ProcessStep 2

It fades the tunnel
establishment step and
text associated with it,
drawing the focus to
Step 2.
Now that we have covered the tunnel establishment step of the IPsec process, we
cover the next stepIPsec traffic processing. Once the IPsec tunnel establishes, the
devices are ready to send the payload using the IPsec attributes and protocols, which
ensure payload protection.
Goal of IPsec Traffic Processing

During the IPsec traffic processing step, the devices have one goalto ensure traffic
protection.
IPsec Modes
IPsec handles the payload using one of two modestransport or tunnel. We discuss
each mode in the next few pages.
IPsec Protocols
IPsec uses two protocols to ensure payload securitythe AH protocol and the ESP
protocol. Again, we discuss each of these protocols in the next few pages.
IPsec Modes
You can implement IPsec in the following two modes:
Tunnel mode: This mode is the most commonly implemented method.

Tunnel mode is implemented between IPsec gateways or an IPsec
gateway and a remote client providing secure access to the networks
behind the gateway. In this method, end systems need not be aware of
the IPsec protocol suite. All encryption and decryption takes place on the
IPsec gateways on behalf of the hosts behind the gateway.
Transport mode: This mode is implemented between IPsec end systems.

End systems should be aware of the IPsec protocol suite. They do all the
encryption and decryption of data.
IPsec Protocols
Two protocols exist that IPsec can use to ensure payload securityAH protocol and
ESP:
AH provides only data integrity, authentication, and antireplay services.

AH is identified by IP protocol number 51. It uses MD5 or SHA-1 to
provide data integrity services.
ESP provides data confidentiality, data integrity, authentication, and

antireplay services. It does not use a transport protocol like TCP or UDP; it
rides directly on top of IP using protocol number 50. ESP uses symmetric
key algorithms like DES, triple Data Encryption Standard (3DES), or AES,
and hash methods like MD5 and SHA-1 to provide security services.
Antireplay services ensure that third parties cannot capture and
retransmit datagrams. By checking sequence numbers, a receiver can
determine receipt of a packet and can discard any repetitions.
Example: Tunnel Mode AH Packets

AH authenticates only the immutable fields in the IP header. Fields like time to live
(TTL) and type of service (ToS) change during packet transit, so these fields do not
receive authentication. The new IP header contains protocol number 51, signifying AH.
The AH header contains the following items:
Next header: Information on the next expected segment;
Payload length: Indicates the size of the payload;
SPI: An arbitrary 32-bit value that, in combination with the destination IP

address and security protocol (AH), uniquely identifies the security
association for this datagram; and
Sequence number: An unsigned 32-bit field containing a monotonically

increasing counter value (sequence number). It is used to detect
antireplay.
Example: Tunnel Mode ESP Packets

In tunnel mode, the ESP header inserts between the new IP header and the original IP
header. The new IP header contains protocol 50, representing ESP. The ESP header
contains the following information:
SPI: An arbitrary 32-bit value that, in combination with the destination IP

address and security protocol (ESP), uniquely identifies the security
association for this datagram; and
Sequence number: An unsigned 32-bit field containing a monotonically

increasing counter value (sequence number); it is used to detect
antireplay.
The ESP trailer contains the following information:
Padding/pad length: Depending on original data size, padding might be

required to fill the packet; and
Next header: Information on the next expected segment.
ESP Auth is the integrity check value (that is, the hash value) for this packet.
Traffic Processing: Part 1

The following list describes the order of traffic processing:
It illustrates the
sequence of events.
1.
The packet arrives at the remote JUNOS security platform.
2.
JUNOS Software looks up the destination route and determines the

Egress Zone.
3.
JUNOS Software looks up the security policy. The traffic matches a tunnel
policy.
4.
The original packet receives encryption.
5.
JUNOS Software hashes the packet with an authentication key.
6.
JUNOS Software builds the tunnel packet with a new IP header, IPsec
header, and hash value. The new packet travels to the tunnel peer.
Traffic Processing: Part 2

This list is a continuation of the list from the previous page, describing the order of
traffic processing:
It illustrates the
sequence of traffic
processing through the
IPsec tunnel.
7.
The corporate JUNOS security platform receives the encrypted packet.
8.
JUNOS Software looks up the incoming SPI in the local SA database. The
matching record contains encryption and authentication algorithms, and
keys.
9.
JUNOS Software compares the locally calculated hash with the received
hash.
10.
JUNOS Software decrypts the packet.
11.
JUNOS Software performs the routing lookup for the decrypted packet
and determines the Egress Zone.
12.
JUNOS Software checks the associated security policy. It forwards the

packet if the tunnel policy exists for the packet.
IPsec Processing Summary

The slide provides a summary of all the steps of IPsec traffic processing.
Configuration of IPsec VPN

IPsec Implementation Methods

JUNOS Software offers two methods for IPsec VPN implementation:
Policy-based VPNs: To implement this method, a security policy specifies

as its action the IPsec VPN tunnel for transit traffic that meets the
policys match criteria. Policy-based VPNs are required when one
endpoint of the tunnel uses dynamic addressing. For policy-based IPsec
VPNs, a new tunnel generates for each flow of traffic that matches the
policy. Because each tunnel requires its own negotiation process and a
separate pair of SAs, the use of policy-based IPsec VPNs can require
more resources than route-based IPsec VPNs.
Route-based VPNs: Unlike the process for policy-based IPsec VPNs, for
route-based IPsec VPNs, a policy refers to a destination addressnot an
IPsec VPN tunnel. Because a destination address is used, route-based
VPNs are generally the best VPNs to use when a routing protocol
adjacency must be formed across the tunnel. When JUNOS Software
searches a route that must send traffic to the destination address, it
finds a route associated with a secure tunnel interface (st0.x). The tunnel
interface is bound to a specific IPsec VPN tunnel, and traffic routes to the
tunnel if the policy action is permit. With a route-based IPsec VPN, in
most cases, only one VPN exists between two sites.
Elements of IPsec VPN Configuration:

IPsec VPN configuration consists of three steps:
1.
Configuring IKE Phase 1;
2.
Configuring IKE Phase 2; and
3.
Applying the IPsec implementation method, which includes implementing

either policy-based VPNs or route-based VPNs.
Configuring IKE Phase 1 Parameters: Step A

IKE Phase 1 configuration requires that you perform the following steps:
A.
Configure IKE Phase 1 proposals;
B.
Configure IKE policies and reference the proposals; and
C.
Configure the IKE gateway and reference the policy.
The slide addresses Step A, which is optional, as you can use the JUNOS Software
predefined proposals. The following are the predefined proposals:
basic:
Proposal 1: preshared key, DH g1, DES, and SHA1
Proposal 2: preshared key, DH g1, DES, and MD5
compatible:
Proposal 1: preshared key, DH g2, 3DES, and SHA1
Proposal 2: preshared key, DH g2, 3DES, and MD5
Proposal 3: preshared key, DH g2, DES, and SHA1
Proposal 4: preshared key, DH g2, DES, and MD5
Configuring IKE Phase 1 Parameters: Step A (contd.)
standard:
Proposal 1: preshared key, DH g2, 3DES, and SHA1
Proposal 2: preshared key, DH g2, AES128, and SHA1
Configuring IKE Phase 1 Parameters: Step B

The slide illustrates the syntax for Step B of IKE Phase 1 configuration, which is policy
configuration. For this step you must either refer to the preconfigured proposal from
Step A or use a system-defined proposal. Also, within the policy you must specify the
preshared key and mode of IKEmain or aggressive.
Configuration of IKE Phase 1 Parameters: Step C

The slide illustrates the last step of IKE Phase 1 configuration, which is gateway
configuration. In this step you must refer to the policy configured in the previous step,
define the peer address, and specify the outgoing interface. Optionally, you can
configure dead peer detection (DPD) to send a DPD request packet if the device does
not receive traffic from a peer for the number of seconds specified with the
interval option. You can also configure DPD to consider the peer unavailable after
a threshold number of interval periods is reached. For example, assume that the
interval value is 10 seconds and the threshold value is 5. If the device does not
receive traffic from a peer for 10 seconds, it sends a DPD request packet to it. The
JUNOS security platform then considers the peer unavailable after five sequences of
waiting for 10 seconds.
Configuring IKE Phase 2 Parameters: Step A

IKE Phase 2 configuration requires that you configure the following steps:
A.
IKE Phase 2 proposals;
B.
IKE Phase 2 policies; and
C.
IKE Phase 2 VPN tunnel.
The slide addresses Step A, which is optional, as you can use predefined proposals.
The following are the predefined proposals:
basic:
Proposal 1: no PFS, ESP, DES, and SHA1
Proposal 2: no PFS, DH g1, DES, and MD5
compatible:
Proposal 1: no PFS, ESP, 3DES, and SHA1
Proposal 2: no PFS, ESP, 3DES, and MD5
Proposal 3: no PFS, ESP, DES, and SHA1
Proposal 4: no PFS, ESP, DES, and MD5
Configuring IKE Phase 2 Parameters: Step A (contd.)
standard:
Proposal 1: ESP, DH g2, 3DES, and SHA1
Proposal 2: ESP, DH g2, AES128, and SHA1
Configuring IKE Phase 2 Parameters: Step B

The slide illustrates the syntax for Step B of IKE Phase 2 configuration, which is policy
configuration. For this step, you must either refer to the preconfigured proposal from
Step A or use a system-defined proposal. Also, within the policy, you have the option to
configure PFS to use with the three supported groups of DH as the method for JUNOS
Software to generate the encryption key.
Configuring IKE Phase 2 Parameters: Step C

The slide illustrates the last step of IKE Phase 2 configuration, which is VPN
configuration. In this step, you must refer to the policy defined in the previous step, as
well as the gateway preconfigured in Step C of IKE Phase 1. If you are configuring a
route-based VPN, you must bind the st0.x interface to the VPN, as illustrated on the
slide. If you manually set up a tunnel, you must specify all the necessary attributes
manually. Should you choose to do so, you can set up all the necessary parameters
under the security ipsec vpn configuration stanza. The optional
establish-tunnels command specifies when to activate IKE-- immediately, or
on-traffic. The immediately option signals the device to activate IKE
immediately after VPN configuration or configuration changes are committed. The
on-traffic option signals the device to activate IKE only when payload traffic
flows.
Applying IPsecPolicy-Based IPsec VPNs

If you are implementing a policy-based IPsec VPN, you must apply the configured VPN
from within the security policy, as illustrated on the slide.
Applying IPsecRoute-Based IPsec VPNs

If you are implementing a route-based IPsec VPN, you must perform the following
steps:
1.
Configure the secure tunnel interface (st0.x);
2.
Configure a static route or enable dynamic routing that points to the st0.x
interface;
3.
Add the st0.x interface to the appropriate security zone; and
4.
Bind the st0.x interface to the IPsec VPN.
IPsec VPN Monitoring

Example: Creating Policy-Based IPsec VPNs Using IKE

The IPsec monitoring
section illustrates the
results of monitoring
commands based on
actual examples. This
section of the chapter
consists of two
examples
policy-based IPsec
VPNs and route-based
IPsec VPNs. First,
each example
illustrates the required
configuration. Next,
we provide the display
of monitoring
commands.
Consider the following example: you must implement a policy-based IPsec VPN
between two SRX Series Services Gateways named Edge and Remote, as illustrated
on the slide. A policy-based IPsec VPN implies that you must refer to the VPN tunnel
from within the policies at each end, as demonstrated on the slide.
Example: Configuring IKE Phase 1 Parameters

The slide illustrates the configuration of the following parameters for IKE Phase 1:
1.
Proposal for IKE Phase 1: Recall that this step is optional, because you
can use JUNOS Softwares predefined proposals (the choices are basic,
compatible, or standard). On the slide, we named the configured
proposal ike-phase1-proposal. We decided to use authentication
algorithm md5, encryption algorithm 3des-cbc, a DH key exchange of
group 2, and preshared keys as the authentication method.
2.
A policy, called ike-policy1: Within the policy we specified the mode

that IKE Phase 1 will usemain mode, in this case. We referred to the
proposal ike-phase1-proposal, and we specified the preshared
key.
3.
Gateway, called ike-phase1-gateway: Within the gateway stanza

we referred to the policy ike-policy1, specified the address of peer
Remote (1.1.70.1), and specified the external interface that IKE will use
to establish the tunnel (ge-1/0/1.0). Also, we decided to use DPD so
that a peer sends a DPD request packet to another peer if it does not
hear from it for 20 seconds. Suppose it is Edge that sends the DPD
request packet to Remote. After sending the DPD request packet, Edge
considers Remote to be unavailable after five sequences of waiting for
20 seconds.
You must repeat the illustrated configuration on the Remote device, defining the
appropriate external interface and gateway address.
Example: Configuring IKE Phase 2 Parameters for Policy-Based IPsec

VPNs
The slide illustrates configuration of IKE Phase 2 parameters for our example. Our
configuration consists of the following:
1.
A proposal for IKE Phase 2: Recall that this step is optional because you
compatible, or standard). We named the configured proposal
ike-phase2-proposal. We decided to use authentication algorithm
hmac-md5-96, encryption algorithm 3des-cbc, and the ESP protocol.
2.
A policy called ipsec-pol1: Within the policy we referred to the

proposal ike-phase2-proposal, and we specified that IPsec will use
DH Group 2 as its PFS.
3.
A VPN tunnel, called TunnelA: Within the tunnel we referred to the

gateway ike-phase1-gateway and the IKE Phase 2 policy
ipsec-pol1. We also specified that tunnels should establish
immediately.
Note that you should repeat the configuration illustrated for the Edge device on the
Remote device.
Monitoring Policy-Based IPsec VPNs

Once you finish and commit all the configurations, you must ensure that the tunnels
are working properly by following the order of how IPsec works. First ensure that IKE
Phase 1 is working properly, then ensure that IKE Phase 2 is working properly. To
check that IKE Phase 1 functions properly, check whether the SAs are formed.
Similarly, you perform IKE Phase 2 checking by viewing the resulting SAs.
The slide illustrates both commands with the resulting outputs. Also, you can view the
IPsec statistics that specify the number of transit packet bytes that the device has
encrypted and decrypted.
Example: Creating Route-Based IPsec VPNs Using IKE

Consider another example: In this case you need to set up the IPsec tunnel using the
route-based method and IKE. Recall that a route-based VPN requires only one tunnel
between JUNOS security platforms, while a policy-based VPN sets up a tunnel for every
new flow.
You must ensure that both ends of the VPN tunnel have a secure tunnel interface
configuredin our case it is the st0.0 interface, with IP address 1.1.80.0/28.
Furthermore, you must ensure that each of the devices has a valid route referring to
the st0.0 interface. In our case we are using static route 0.0.0.0/0.
Example: Configuring a Security Zone for a Route-Based IPsec VPN

Once you configure interface st0.0, you must add it to the corresponding security
zone. In our case, we must add it to the Public security zone. Also note that
although the slide provides the configuration for the Edge device, you must also
repeat it for the Remote device.
Example: Configuring IKE Phase 1 Parameters

The slide illustrates the configuration of the following parameters for IKE Phase 1:
1.
The proposal for IKE Phase 1: Recall that this step is optional because
you can use JUNOS Softwares predefined proposals (the choices are
basic, compatible, or standard). We named the configured
proposal ike-phase1-proposal. We decided to use authentication
algorithm md5, encryption algorithm 3des-cbc, a DH key exchange of
group2, and preshared keys as the authentication method.
2.
A policy, called ike-policy1: Within the policy, we specified the mode

that IKE Phase 1 will usethe main mode, in this case. We referred to the
proposal ike-phase1-proposal, and we specified the preshared
key.
3.
A gateway, called ike-phase1-gateway: Within the gateway stanza

we referred to the policy ike-policy1, specified the address of the
peer Remote (1.1.70.1), and specified the external interface IKE will
use to establish the tunnel (ge-1/0/1.0). Also, we decided to use DPD so
that a peer will send a DPD request packet to another peer if it does not
hear from it for 20 seconds. Suppose that it is Edge that sends the DPD
request packet to Remote. After sending the DPD request packet, Edge
considers Remote to be unavailable after five sequences of waiting for
20 seconds.
Note that you must repeat the illustrated configuration at the Remote device, defining
the appropriate external interface and gateway address.
Example: Configuring IKE Phase 2 Parameters for a Route-Based IPsec

VPN
The slide illustrates configuration of IKE Phase 2 parameters for our example. Our
configuration consists of the following:
1.
A proposal for IKE Phase 2: Recall that this step is optional, because you
compatible, or standard). We named the configured proposal
ike-phase2-proposal. We decided to use authentication algorithm
hmac-md5-96, encryption algorithm 3des-cbc, and the ESP protocol.
2.
A policy, named ipsec-pol1: Within the policy we referred to the

proposal ike-phase2-proposal, and we specified that IPsec will use
DH group2 as its PFS.
3.
A VPN tunnel, called TunnelA: Within the tunnel we referred to the

gateway ike-phase1-gateway and the IKE Phase 2 policy
ipsec-pol1. We also specified that tunnels should establish
immediately. Furthermore, we bound the st0.0 interface to the tunnel.
When you compare the configuration on the slide to the policy-based IPsec IKE
Phase 2 configuration, you will notice that the only difference between the two is the
statement binding interface st0.0 to the tunnel.
Note that we must also repeat the configuration illustrated for the Edge device at the
Remote device.
Monitoring a Route-Based IPsec VPN: Part 1

Once you finish and commit all the configurations, you must ensure that the tunnels
work properly by following the order of how IPsec works. First ensure that IKE Phase 1
works properly, then ensure that IKE Phase 2 works properly. To check that IKE Phase
1 functions properly, you must check whether the SAs form. Similarly, you perform IKE
Phase 2 checking by viewing the resulting SAs.
The slide illustrates both commands with the resulting outputs. Also, you can view
IPsec statistics that specify the number of transit packet bytes that the device
encrypts and decrypts.

One of the differentiating points of a route-based IPsec VPN is that it uses the st0
interface. Therefore, you can use the show interfaces st0.x command to view
whether the interface is up as well as how much information transits through it. If
there is a problem in establishing the route-based IPsec tunnel, the st0 interface is
not in the up state. The slide illustrates the results of the show interface st0
detail command for the Edge device.

The slide is the continuation of the show interfaces st0 detail command
from the previous slide. It provides statistical information for the st0 interface,
including flow input, flow output, and flow error statistics.

As we work with a route-based IPsec VPN, it is useful to check the routing table
entries, ensuring that an active route referring to the st0 interface exists. In our case,
the 0.0.0.0/0 default route, using interface st0.0 as its next hop, is active.
Other IPsec VPN Monitoring Commands

You can enable traceoptions to debug IKE Phase 1 and Phase 2. Also, you can
clear IKE Phase 1 and Phase 2 SAs and statistics using the clear security ike
and clear security ipsec operational commands.
Common IPsec Configuration Problems

You should be aware of the following common problems when configuring IPsec VPNs:
Proposal mismatch: The IKE Phase 1 proposal lists configured on each

side do not agree. In this case, the initiator of the tunnel sees
retransmissions and a retransmission limit indicator. The problem is
evident at the destination gateway (the responder). The responder
rejects all proposals sent by the initiator.
Preshared key mismatch: The keys do not match.
No route information is available: To establish a gateway, you must either

configure an explicit route or a default route (or use a dynamic routing
protocol) to be used to reach the remote gateway.
The destination gateway is misconfigured: It might happen that the

destination gateway (responder) does not recognize the incoming
request as originating with a valid peer gateway. Any of the following
misconfigurations could cause this problem:
The peer gateway is not configured correctly;
The outgoing interface is not the right one; or
A proposal mismatch exists.
Various types of VPNs;
Major security concerns;
IPsec VPNs and their functionality;
IPsec VPN configuration using policy-based and route-based methods;

and
IPsec VPN monitoring.
Review Questions
1.
The three major security concerns are confidentiality, integrity, and authentication.
2.
The main difference between ESP and AH is that AH does not provide confidentiality, while
ESP does.
3.
JUNOS Software supports the use of the MD5 and SHA protocols to ensure data integrity.
4.
The two modes available in IKE Phase 1 are main and aggressive.
Lab 6: Implementing IPsec VPNs


Chapter 9: Introduction to Intrusion Detection
and Prevention
The purpose of the JUNOS Software Intrusion Detection and Prevention

(IDP) feature;
Utilizing and updating the IDP signature database;
Utilizing and configuring IDP policy using a policy template; and
Monitoring IDP operation.
Chapter 92 Introduction to Intrusion Detection and Prevention
Introduction to JUNOS Software IDP

first.
Introduction to Intrusion Detection and Prevention Chapter 93
What Is IDP?
Initially, network defense consisted of basic stateless firewall protection. Network
devices, such as routers, often provided this feature. As network attacks became
more sophisticated, network defense also had to become more sophisticated. Stateful
firewalls, authentication mechanisms, and VPN devices utilizing encrypted traffic
offered additional protection from harmful network traffic and malicious users.
Traditional firewalls might not detect some malicious traffic because manufacturers
design VPN devices and firewalls for high-speed operation of VPN control and access
control. For these types of attacks, the solution is to use IDP.
The JUNOS Software IDP feature provides additional security beyond a firewall. While
a firewall traditionally inspects only Layers 3 and 4, JUNOS Software utilizes the IDP
feature to decode and reassemble the protocol stream and thus sees traffic from the
applications point of view (Layer 7). When IDP reassembles the data stream, JUNOS
Software examines the stream for specified attack patterns. If no problem with the
stream exists, JUNOS Software forwards the original packets. If the software detects a
problem within the stream, IDP can drop packets, close or drop sessions, prevent
future sessions, and log attacks for review by network administrators.
Utilizing IDP in combination with SCREEN options, zones, security policies, and other
JUNOS security features offers a complete approach to network security.
Fully Integrated IDP

JUNOS security platforms have IDP functionality fully integrated into JUNOS Software.
This integration means no additional hardware or operating system is necessary,
resulting in less cost, lower management overhead, and increased operational
simplicity.
Live Attack Database

Juniper Networks maintains a database of attack signatures for use with the IDP
feature. With a valid license, users can retrieve updates manually by running a CLI
command or automatically by configuring a JUNOS security platform to update its
database at regular intervals. The full security package download includes various
policy templates. These policy templates offer protection against a variety of common
attacks. Once you install the templates, you can customize them to fit the traffic
patterns of a particular network.
IDP Successes
Check the security
portal for updates on
recent attack
prevention successes.
Stressing a recent
attack or worm such as
the Conficker worm,
which has predefined
attack objects
associated with it, will
emphasize the
timeliness of signature
database updates.
The JUNOS Software IDP feature regularly protects networks from the latest Microsoft
vulnerabilities. The attack database updates as new threats emerge, keeping JUNOS
Software on the leading edge of network defense. IDP allows you to stop attacks
before they fully compromise the network. In the past, you often had to take a reactive
approach to network security by parsing logs for security threats before being able to
take action. In the meantime, the network remained vulnerable. Using IDP, you can be
proactive by stopping attacks as they occur, and by preventing future attacks. IDP
uses attack signatures to protect your network from thousands of known attacks. It
can also detect protocol anomalies to protect your network from unknown or potential
attacks. Juniper Networks maintains a Web-based security portal
(http://www.juniper.net/security) listing the latest attack database updates, Microsoft
security bulletins, attack trends, and other useful security information.
IDP Policy Components and Configuration

IDP Policy Framework

Policy drives the IDP attack detection engine. IDP policy enables selective
enforcement of various IDP attack detection and prevention techniques on network
traffic passing through the IDP engine. Users can write very granular rules to match a
section of traffic based on zones, networks, and applications. Users can then apply
specific attack prevention techniques on that traffic, and take active or passive
preventive actions.
The slide illustrates the structural view of an IDP policy. An IDP policy can consist of
two types of rulebasesan intrusion prevention system (IPS) rulebase and an exempt
rulebase. A rulebase is a collection of rules. Rules contain a collection of configuration
objects and are similar in structure to security policy because they use configuration
objects to create match conditions and resulting actions. Once you create an IDP
policy, the action of a security policy applies it. Although many IDP policies might exist
within the configuration, only one IDP policy is active on a JUNOS security platform.
IDP Configuration Objects

JUNOS Software uses configuration objects to build IDP rules. Use configuration
objects to match on zones, source and destination networks, applications, and
attacks or attack groups.
IDP Policy Matching Conditions

The slide shows a sample IDP policy configured with the JUNOS Software template
policy named Recommended. The slide shows a rule named rule 2 in an IPS rulebase
with the matching conditions highlighted. In this case, the rule matches on traffic from
any zone and source address to any zone and destination address. The rule also
matches on an application type of default. When you select this application type, the
software bases application matches on the attack or attack group objects. JUNOS
Software automatically matches on application or service settings associated with the
defined attack or attack group object. You can also specify a configured application or
application-set or use the any option.
The sample configuration on the slide shows a predefined attack group designed for
Internet Control Message Protocal (ICMP) attacks. Predefined attack and attack group
objects are part of the signature database that can be downloaded from Juniper
Networks. We discuss the signature database on subsequent slides. You can also
specify custom attack and attack group objects or dynamic attack group objects.
Custom attacks and attack groups are user-defined configuration objects. The
software builds dynamic attack groups using filters that match on a particular option,
such as an application. For more information on custom attacks and groups or
dynamic attack groups, refer to http://www.juniper.net/techpubs for the Juniper
Networks technical documentation.
IDP Policy Actions

The slide shows the same sample policy rule as the previous slide, but with the action
section of the rule highlighted. This example defines an action of Recommended. This
type of action is only applicable to IPS rulebases utilizing predefined attack objects. A
Juniper Networks recommended action is associated with all predefined attack
objects. A rule can have one of the following actions:
no-action: JUNOS Software takes no action (used when you only need
to generate a log);
ignore-connection: JUNOS Software stops scanning traffic for the

rest of the connection;
mark-diffserv: JUNOS Software assigns the indicated

service-differentiation value to the packet then passes it on normally;
drop-packet: JUNOS Software drops a packet before it can reach its

destination, but does not close the connection;
recommended: The action that Juniper Networks recommends when it

detects a predefined attack;
drop-connection: JUNOS Software drops the connection, preventing

traffic for the connection from reaching its destination;
IDP Policy Actions (contd.)
close-client: JUNOS Software closes the connection and sends a

RST packet to the client but not to the server;
close-server: JUNOS Software closes the connection and sends a

RST packet to the server but not to the client; and
close-client-and-server: JUNOS Software closes the connection

and sends an RST packet to both the client and the server.
The example on the slide also illustrates a notification action. This action instructs
JUNOS Software to log the attack.
Additional IDP Policy Actions

The slide lists a continuation of IDP policy actions. IP actions prevent repeat attacks.
This rule action applies to future sessions that have the same IP action attributes of
the flow on which the software detects an attack. For example, you could configure
one of the IP actions in a rule to block all future HTTP sessions between two hosts if
the software detects an attack on a session between those hosts. Optionally, you can
specify a timeout value defining that the action should apply only if new sessions
initiate within a specified timeout value in seconds. (The default IP action timeout is 0,
which means no timeout.) IP action attributes consist of a combination of the following
fields:
Source IP;
Destination IP;
Destination Port;
From Zone; and
Protocol.
Additional IDP Policy Actions (contd.)

These IP action attributes can be used only in certain combinations and list as targets
in the following output:
[edit security idp idp-policy Recommended rulebase-ips rule 2]
user@host# set then ip-action target ?
destination-address Match destination
service
Match source, destination, dst-port and protocol
source-address
Match source
source-zone
Match source-zone
zone-service
Match source-zone, destination, dst-port, protocol
The following are possible IP actions:
ip-block: JUNOS Software silently drops all packets matching the IP

action rule;
ip-close: JUNOS Software closes any new sessions matching the IP

action rule by sending an RST packet to the client and server; and
ip-notify: JUNOS Software generates a log when it finds a session

matching the IP action rule.
You can use the severity action to override the default attack severity to a configured
value.
Applying IDP Policy

You enable IDP policies by specifying the IDP policy in a security policy, as shown on
the slide. The security policy action must be to permit the flow. Note that once an IDP
policy is in use, any change to the [edit security idp] hierarchy, the
associated security policy configuration, or the associated custom applications
causes an IDP policy recompilation when you issue the commit.
Active IDP Policy

Recall that only one IDP policy is active on a JUNOS security platform at any given
time. The slide shows how to configure the active IDP policy.
Evaluating IDP Rulebases

Once the software compiles an IDP policy, it pushes the policy to the data plane where
the IDP policy evaluation occurs. IDP policy evaluates only the first packet of a
session. If a match occurs, the software creates a set of objects and caches them
within the session for use with attack detection on subsequent packets.
JUNOS Software evaluates all IDP rules (unlike security policy) but does so
sequentially. If a new session matches multiple rules, JUNOS Software performs the
most severe action among the rules. The slide shows the order of severity associated
with rule actions.
Emphasize the
importance of using
caution when defining
terminal rules. An
inappropriate terminal
rule leaves a network
open to attacks.
You can make an IDP rule terminal using the configuration shown on the slide. When
the software configures a match in a terminal rule for the source, destination, zones,
and application, it does not continue to check subsequent rules for the same source,
destination, and application. It does not matter whether traffic matches the attack
objects in the matching rule or not. This option is useful for disregarding traffic that
originates from a known trusted source. Terminal rules should appear near the top of
the rulebase and before other rules that would match the same traffic.
Exempt Rulebases
The functionality of an exempt rulebase complements an IPS rulebase. You can write
rules in an exempt rulebase to skip detection of a set of attacks in certain traffic.
Carefully written rules in an exempt rulebase can significantly reduce the number of
false positives generated by an IPS rulebase. Note that you must configure an IPS
rulebase before using an exempt rulebase. Rules in an exempt rulebase have the
same matching conditions as those of an IPS rulebase. The exception is that you
cannot configure the application object, which means rules match all applications.
When configuring attack or attack-group objects in an exempt rulebase, note that
these attacks are attacks the software should not inspect in traffic matching this rule.
No actions are available for exempt rulebases.
Signature Database
The Signature Database

Visit https://
services.netscreen.
com/restricted/
sigupdates/
nsm-updates/HTML/
index.html to view
the current list of IDP
attack objects and
attack group objects.
You might find it
useful to illustrate
this site to your
students. As of
JUNOS Software
Release 9.5R1,
attack objects are
not viewable using
the JUNOS Software
CLI.
The signature database is one of the major components of IDP. It contains definitions
of different objectssuch as attack objects, application signature objects, and service
objectsthat it uses to define IDP policy rules. As a response to new vulnerabilities,
Juniper Networks periodically provides a file containing attack database updates on
its Web site. You can download this file to protect your network from new threats. The
database lists the attack objects alphabetically, and the names consist of the attack
object group name and the name of the attack object, as shown on the slide.
The security package, which you can download from Juniper Networks, also includes
IDP policy templates to help you implement IDP policy on your JUNOS security
platform. You can use the template policies as they are, or you can customize them for
your network environment. Templates exist for a multitude of network scenarios. The
most widely used template is called the Recommended policy. We discuss
downloading the signature database and policy templates on subsequent slides.
IDP Signature Update License

Note that a license is
not required to operate
the IDP feature on a
JUNOS security
platform. You can
create and implement
custom attack objects
and custom policies
without a license. The
license is necessary
only for updating the
signature database
provided by Juniper
Networks.
To update the IDP signature database, an IDP signature license is necessary. The slide
illustrates the configuration command for adding a system license, and the result of a
successful license addition.
Updating the Security Package Manually

Note that if you
perform a signature
database update that
modifies or removes
objects that are
currently configured
on your device,
JUNOS Software will
not allow subsequent
commit operations
until the policy is
modified.
You can download the Juniper Networks security package manually or automatically at
specified time intervals. The slide illustrates the operational mode commands to
download the security package and check the status of the download. You must
connect the JUNOS security platform to the Internet to update a device directly.
Alternatively, you can download the update to a Network and Security Manager (NSM)
device, which can be configured to push the updated database to your JUNOS security
platform.
Installing the Security Package

Once you successfully download the security package, you must install it. The slide
illustrates the operational mode commands for installing the security package and
verifying the status of an installation.
Automatic Downloads
As mentioned previously, you can configure a JUNOS security platform to automatically
download the security package. The slide also shows an example configuration of
automating the download.
Signature and Attack Database Version

The slide illustrates the operational mode command used to verify the attack
database. The version includes a time and date stamp so you can check the date of
your local database.
Checking Your Connection to the Update Server

The slide illustrates the operational mode command used to check the server
connection from your JUNOS security platform. This command not only verifies
network connectivity, but also provides the remote database version, which is useful
for comparing version differences with the previous command output.
Case Study: Applying the Recommended IDP Policy

Applying the Recommended IDP Policy: Part 1

This slide and the next two slides demonstrate the steps necessary for downloading
and installing the Juniper Networks recommended IDP policy. The slide shows the
operational mode commands used to download and install the latest policy templates
provided by Juniper Networks. Recall that a JUNOS security platform must have an IDP
signature license to download the signature database or associated policy templates.

JUNOS Software downloads Juniper Networks policy templates in the form of a commit
script. Once you download and install the policy templates, you must activate the
template commit script with the configuration mode command shown on the slide.
You must perform a commit action to activate a commit script. In this example, we use
the JUNOS Software CLI auto-completion feature to verify the availability of the policy
templates for configuration as the active IDP policy. For more information regarding
commit scripts, refer to http://www.juniper.net/techpubs for the Juniper Networks
technical publications.

The next step is to set the recommended policy as the active policy. Recall that only
one IDP policy can be active on a JUNOS security platform. As illustrated on the slide,
you must delete or deactivate the commit script. This step is important because every
subsequent commit will overwrite any changes that you made to template policies.
The final step to activating the recommended IDP policy is to apply the IDP action to a
security policy. Do not forget to commit the changes!
Monitoring IDP Operation

Verifying the Application of IDP Policy

The slide shows a sample output of the show security policies
policy-name command. By using the detail option, you can verify that you
enabled IDP for this security policy.
Monitoring IDP Status and Statistics

The slide illustrates the show security idp status command. This command
provides traffic statistics related to the IDP policy engine. It also outputs the active IDP
policy and IDP detector version.
IDP Counters
The command shown on the slide along with one of the command arguments provides
various counters useful in monitoring IDP operation.
Monitoring Memory Utilization

On high-end SRX
devices, the output of
the command shown
on the slide is
displayed on each
services processor unit
(SPU) independently.
SPUs are the dedicated
ASICs that are used for
security processing
within a services
processing card (SPC)
and vary by platform.
For branch devices, the
SPU notation always
shows as FPC 0 PIC 0.
If the IDP process runs out of memory, the software no longer evaluates traffic for
attacks. Use the command shown on the slide to monitor memory utilization.
IDP Logging
You enable logging using the notification action. JUNOS Software stores logs
according to the data plane logging configuration present on the JUNOS security
platform.
When you configure an IDP rule for logging, each matching event creates a log entry.
Because the software generates IDP event logs during an attack, log generation
happens in bursts, generating a much larger volume of messages during an attack. In
comparison to other event messages, the message size is also much larger for
attack-generated messages. The log volume and message size are important
concerns for log management. To better manage the volume of log messages, IDP
supports log suppression. Log suppression limits multiple instances of the same log
occurring from the same or similar sessions over a given period of time. The software
enables log suppression by default but you can adjust attributes through configuration
under the [edit security idp sensor-configuration log
suppression] hierarchy.
IDP Traceoptions
You can configure IDP traceoptions to log control plane events. Currently, the only flag
available is the all flag. By default, the software logs IDP traceoptions events to the
/var/log/idpd file.
The purpose of the JUNOS Software IDP feature;
Utilizing and updating the IDP signature database;
Utilizing and configuring IDP policy using a policy template; and
Monitoring IDP operation.
Review Questions
1.
JUNOS Software processes the rule with the most severe action.
2.
The exempt rulebase exempts specified traffic from IDP policy.
3.
Evaluation of a rulebase stops only when the software matches a terminal rule.
4.
To apply an IDP policy, you must make it the active policy and reference an IDP action in a
security policy.
Lab 7: Implementing IDP


High availability (HA) clustering and its functionality;
Chassis cluster components;
Chassis cluster operation;
Chassis cluster configuration; and
Chassis cluster monitoring.
Chapter 102 High Availability Clustering
High Availability Overview

first.
High Availability Clustering Chapter 103
High Availability Characteristics

Sessions that are
subject to IDP
inspection are
currently not
supported for stateful
session failover.
Multicast traffic is
currently not
supported on a chassis
cluster.
The JUNOS Software high availability (HA) feature provides stateful session failover.
This ability applies to TCP and UDP sessionsthose that deploy Network Address
Translation (NAT), IP Security (IPsec), or authentication, as well as those that do not.
High availability includes the synchronization of configuration files and the dynamic
runtime session states between JUNOS security platforms deploying it. The JUNOS
Software implementation of high availability clustering currently supports an
active-passive redundancy for the control plane and an active-active redundancy for
the data plane. Check the Juniper Networks technical documentation for high
availability support specific to your platform at http://www.juniper.net/techpubs.
High Availability Using Chassis Clusters

JUNOS Software achieves high availability on JUNOS security platforms using chassis
clustering. Chassis clustering provides network node redundancy by grouping two like
devices into a cluster. The two nodes back each other up with one node acting as the
primary and the other as the secondary node, ensuring the stateful failover of
processes and services in the event of system or hardware failure. A control link
between services processing cards (SPCs) or revenue ports and an Ethernet data link
between revenue ports connect two like devices. JUNOS security platforms must be
the same model, and all SPCs, network processing cards (NPCs), and input/output
cards (IOCs) on high-end platforms must have the same slot placement and hardware
revision.
The chassis clustering feature in JUNOS Software is built on the high availability
methodology of Juniper Networks M Series and T Series platforms and the TX Matrix
platform, including multichassis clustering, active-passive Routing Engines (REs) ,
active-active Packet Forwarding Engines (PFEs), and graceful RE switchover capability.
Considering all the process implementations on M Series and T Series platforms, most
of which have complete hardware and control plane redundancies, the JUNOS
Software implementation for JUNOS security platforms mirrors the RE and PFE backup
system and RE and PFE redundancy using Ethernet interfaces. JUNOS security
platforms add redundancy features by introducing interchassis clustering and stateful
failovers. Devices in a chassis cluster synchronize the configuration, kernel, and PFE
session states across the cluster to facilitate high availability, failover of stateful
services, and load balancing.
Chassis Cluster Components

Chassis Cluster Components

A chassis cluster consists of the following components:
Cluster identification, including cluster-id id and node id;
Redundancy groups (RGs); and
Chassis cluster interfaces:
fxp1: The control plane interface;
fxp0: The out-of-band management interface;
fab: The data plane interface; and
reth: A redundancy interface.
We address all chassis cluster components in the next section of this chapter.
cluster-id Details
You can deploy up to fifteen chassis clusters in your environment. A unique
cluster-id value, which ranges from 115, identifies each cluster. A JUNOS
security platform can belong to only one cluster at any given time. The device ignores
high availability configuration and acts as a standalone device if a cluster-id
value is zero. When a device joins a cluster, it becomes a node within that cluster,
identified by a node id. If you choose to alter a cluster-id id or node id
parameter, you must reboot the device to activate the changes.
node id Details
The node id uniquely identifies a JUNOS security platform within a cluster. Because
only two nodes can exist in a cluster, node id values range from 01.
Recall the interface naming structure used by JUNOS Software:
(media type)-(fpc slot #)/(pic slot #)/(port #), for example, ge-1/0/3.
In the case of JUNOS security platforms, the Flexible PIC Concentrator (FPC) can be
either an IOC , an SPC, a Physical Interface Module (PIM), or a fixed interface. The
software uses the node id value to offset the FPC slot value in the interface name of
a device. Specifically, the software uses the following formula to calculate the FPC slot
number:
Cluster interface FPC slot number=
(node id * max FPC slots) + standalone FPC slot number.
For example, a Juniper Networks SRX5800 Services Gateway has a maximum of 12
slots. Using the FPC slot number calculation, you can determine that the second slot
on node 1 of a chassis cluster uses an interface name of ge-13/x/y or xe-13/x/y.
Redundancy Group
A redundancy group (RG) is an abstract construct that includes and manages a
collection of objects. It contains objects on both nodes of a cluster. An RG is primary
on one node and backup on the other node at any given time. When an RG is primary
on a node, its objects on that node are active.
JUNOS security platforms support up to 256 RGs. RGs are independent units of
failover, and one RGs primacy does not affect the other RGs primacy. In other words,
one of the RGs can be primary on node 0, while the other RG is primary on node 1.
When an RG fails over, all its objects fail over together.
When you initialize a JUNOS security platform in chassis cluster mode, the system
creates a redundancy group called RG0. RG0 manages the primacy and failover
between the REs on each node of the cluster. As is the case for all redundancy groups,
RG0 can be primary on only one node at a time. The node on which RG0 is primary
determines which RE is active in the cluster. You must explicitly create RGx in the
configuration and manage interface redundancy. RGx can contain up to 15 redundant
Ethernet interfaces called reth interfaces. We discuss reth interfaces in detail later in
this chapter.
Three RG Object States

An RG object can be in one of the following three states:
A blank state, which is the starting state for an RG;
A primary state; or
A secondary state.
RG Object State Transitions

As indicated on the diagram on the slide, an RG object state can transition from blank
to either primary or secondary. In addition, an RG object in the primary state can
transition to the secondary state, and vice versa. Both primary and secondary states
can transition back to the blank state when you delete an RG from the configuration
file or when the device reboots.
RG Primacy Rules
The rules for RG primacy are as follows:
An RG is primary on the node with the higher priority.
By default, both nodes have the same priority for RG0, but you can
change the default setting to specify which node is primary for RG0. You
must explicitly configure the node priority for RGx.
If you initialize both nodes of a cluster at the same time and you do not
change the default setting for RG0 node priority, Node 0 takes
precedence.
If one node of the cluster initializes before the other, the first node to
initialize takes precedence and remains the primary node for the RG
unless the preempt configuration option is present. Note that the
preempt configuration option is not supported on RG0.
RG State Transitions
For RGx to fail over automatically to another node, the software must monitor its
interfaces. When you configure an RGx, you can specify a set of interfaces the RG is to
monitor for status, checking whether the interface is up or down. When you configure
an interface for RGx to monitor, you give it a weight value. RGx has a threshold
tolerance value initially set to 255. When an interface monitored by RGx becomes
unavailable, the software subtracts its weight from the threshold. When the threshold
reaches zero, all objects within RGx fail over to the other node.
Illustration of RGxs Use for Load Balancing

This is an animation
slide.
This slide illustrates an example of load balancing between two nodes of a cluster.
Specifically, RG1 is primary on Node 0 for destination network 10.10.0.0/16, and RG2
is primary on Node 1 for destination network 10.20.0.0/16. In addition, RG1 is
secondary on Node 1 for destination network 10.10.0.0/16, and RG2 is secondary on
Node 0 for destination network 10.20.0.0/16.
Chassis Cluster Interfacesreth

The reth interface
index number
determines the
interface ID.
A reth is a pseudo-interface that includes a physical interface from each node of a

cluster. A reth can contain either two physical Ethernet interfaces, referred to as child
interfaces of the reth interface. Each reth can contain only two interfaces because a
cluster contains only two nodes. Although reth interfaces must be the same kind
either Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernetthey do not need to be
in the same slots on each node. A reth child interface associates with the reth
interface as part of the child interface configuration. A reth child interface inherits
properties of its parent interface. A reth interface inherits its failover properties from
RGx. Consequently, a reth interface can remain active even if one of its child
interfaces becomes unavailable. Only one child interface of a reth interface can
accept and send traffic at a time. A reth interface has a virtual MAC address, which is
based on the cluster ID and the interface ID.
Chassis Cluster Interfacesfxp0

JUNOS security platform management interfaces allow out-of-band network access
and network management to each node in the cluster. Only high-end security
platforms contain an fxp0 interface. For branch security platforms in a chassis cluster,
JUNOS Software designates one of the revenue ports to act as the fxp0 interface.
Refer to your products documentation at http://www.juniper.net/techpubs to
determine which port acts as the fxp0 interface for your specific branch device.
We recommend giving each node in a chassis cluster a unique IP address for the fxp0
interface of each node. This practice allows independent node management. To
accomplish this practice, you must configure interfaces in separate configuration
groups under the [edit groups] configuration hierarchy. We cover details
regarding configuration of groups later in this chapter.
Chassis Cluster Interfacesfxp1

Each SPC on a high-end SRX Series platform has two ports for use as a chassis cluster
control link, named fxp1. Currently, the software supports only a single control link. On
high-end security platforms, the control link connects through ports on SPCs. Use
Port 0 if the RE is in RE Slot 0 within the chassis, and use Port 1 if the RE is in RE Slot
1. Branch security platforms use revenue ports for the chassis cluster control link.
Check the documentation specific to your device to determine which port to use.
On high-end security platforms, configuration is necessary to designate the ports
associated with fxp1 as shown:
[edit chassis cluster]
user@host1# show
control-ports {
fpc slot port port;
fpc slot port port;
}
The system provides each fxp1 control link interface with an internal IP address and
uses the proprietary Trivial Network Protocol (TNP) to transmit the session state, the
configuration file, and liveliness signals across the nodes. JUNOS Software
periodically transmits heartbeat signals over the control link to determine the health
of the control link. If the number of missed heartbeats reaches the configured
threshold and the fabric link is operational, the system signals a control link failure.
Chassis Cluster Interfacesfxp1 (contd.)

If the control link fails, JUNOS Software disables the secondary node to prevent the
possibility of each node becoming primary for all RGs, including RG0.
Once a secondary node is disabled, you must reboot the node to resume operation.
You can make this reboot automatic on some JUNOS security platforms using the
control-link-recovery configuration option as follows:
{primary:node0}[edit chassis cluster]
user@host# show
control-link-recovery;
Chassis Cluster Interfacesfab

JUNOS Software uses the fabric (fab) interface for the high availability data plane.
When the system creates the fab interface, the software assigns it an internally
derived IP address that it uses for packet transmission. The fab is a physical
connection between two Ethernet interfaces on the same LAN. Both interfaces must
be the same media type. Unlike the control link that has system-determined
interfaces, you specify the physical interfaces to use for the fab data link in the
configuration.
Similar to the fxp1 control link, the fab link uses fabric probes to determine the health
of the link. If JUNOS Software determines that there has been a fabric link failure, it
disables the secondary node, and a reboot is required to restore operation.
JUNOS Software does not support traditional interface features such as firewall filters,
policies, logical interfaces, or system services on the fab link, and the fab link is not
configured under a security zone. Although JUNOS Software does not support
fragmentation on the fab link, it does support jumbo frames up to 8980 bytes.
Therefore, we recommend that no interface in a chassis cluster exceed this maximum
transmission unit (MTU) size.
Purpose of Real-Time Objects

To provide for session or flow redundancy, the data plane synchronizes its state by
sending special payload packets named real-time objects (RTOs) from one node to the
other across the fab data link. By transmitting information about a session between
the nodes, RTOs ensure the consistency and stability of sessions if a failover occurs;
thus, they enable the system to continue to process traffic belonging to existing
sessions. To ensure session information synchronization between the two nodes, the
data plane gives RTO packets priority over transit traffic.
Dynamics of RTOs
JUNOS Software creates RTOs dynamically in memory. Some examples of dynamically
created RTOs include session table entries and IPsec security associations (SAs).
Chassis Cluster Interface Summary

The slide summarizes all the cluster interfaces that we just discussed.
Chassis Cluster Operation

Cluster Operation: Forming a Cluster

The first chassis in a cluster forms a cluster upon booting up. It transitions from the
blank state to the primary state.
Cluster Operation: Joining a Cluster

A chassis can join an existing cluster. The RG0 of the joining chassis transitions from
the blank state to the secondary state. RGx transitions from the blank state to either
the primary state or the secondary state based on a combination of priorities and
preempt configurations. The join operation causes the joining chassis to perform
configuration synchronization as well. A join operation might cause the existing cluster
node to change its RGx states from primary to secondary.
Cluster Operation: Leaving a Cluster

A leave action happens when a node chassis reboots or powers off. This leave action
can trigger RG state changes from secondary to primary in another cluster node.
Cluster Operation: Splitting a Cluster

JUNOS Software offers automatic protection from split scenarios by disabling the
secondary node if either the control link or the fabric link suffers a loss of keepalives
or heartbeat messages. You must reboot the disabled node to have it rejoin the
cluster. However, if JUNOS Software detects a failure on both links simultaneously,
such as in the case of a system failure, both devices become primary nodes.
Cluster Operation: Merging a Cluster

A merge action happens when a split cluster regains connectivity. The merged cluster
can cause RG state transitions from primary to secondary.
One Node Handling Transit Traffic

The slide illustrates the packet flow in active-passive mode for the data plane. In this
case, Node 0 is the primary node, and Node 1 is the secondary node.
Both Nodes Handling Transit Traffic

This is an animation
slide.
In active-active mode for the data plane, two nodes handle transit traffic. This slide
illustrates the packet flow in which ingress and egress interfaces are on different
devices of a cluster. The node containing the egress interface for the first flow in a
session always acts as the host of the session. In this case, the flows active session is
on Node 1, and the flows backup session is on Node 0.
At this time, JUNOS security platforms support active-active mode for the data plane
only. The control plane always acts in an active-passive fashion, with the secondary
node providing redundancy to the primary node.
Chassis Cluster Configuration

Connecting the Two Devices

Ensure that you interconnect two JUNOS security platforms of the same model, with
SPCs inserted in identical slots (on a high-end platform), as follows:
Connect the ports for use as the control link. On high-end platforms, use
the SPC port with the same number as the RE slot. On branch platforms,
use the appropriate revenue port specific to the model of device.
Connect the Ethernet interfaces of the two nodes to create the fabric link
(fab interface).
Configuring Control Ports

For high-end platforms, enable the SPC control plane ports in the configuration and
commit the configuration.
Enabling Clustering
Enabling chassis clustering involves setting a cluster-id id and node id on
each chassis in the cluster. The cluster-id value is the same on both nodes. To
activate clustering, once you set the cluster-id id and the node id, you must
reboot the node designated as the primary device first, then reboot the desired
secondary node.
Enabling the Chassis Cluster

The slide illustrates the configuration required to enable the SPC control plane ports
for high-end security platforms.
It also displays the syntax of a command that is necessary to set up the cluster-id
id and node id. Note that you perform this command in operational mode and the
mandatory reboot is available as part of the command.
Enabling the Chassis Cluster on the Second Node

Because the second node inherits the configuration associated with the primary node,
no control port configuration is necessary. The slide illustrates the operational mode
command required to add the second node to the chassis cluster.
Cluster Configuration Steps

Once you reboot a node of a cluster, you are ready to configure other cluster
parameters. The slide lists the configuration steps you must follow to accomplish
cluster configuration.
Configuring the Management Interface

You configure management access to the cluster by defining a unique hostname for
each node and assigning a unique IP address for the fxp0 interface on each node.
Note that the configured group names must be node0 and node1. You must apply
the configured groups using the apply-groups configuration stanza, as illustrated
on the slide.
Configuring Fabric Interfaces

You configure the fab interface between the two nodes using the syntax illustrated on
the slide. The member interface for fab0 is an Ethernet interface on Node 0, and the
member interface for fab1 is an Ethernet interface on Node 1. Both fab interfaces
must be of the same media type.
Configuring a Redundancy Group

The slide illustrates the syntax necessary for configuring an RG. You perform the
configuration under the chassis cluster configuration stanza. The configuration
includes specifying the following:
The node priorities (the higher number takes precedence);
The number of gratuitous Address Resolution Protocol (ARP) requests

that an interface can send to notify other network devices of its presence
after an RG to which it belongs fails over;
Weights to the monitored interfaces; and
An optional preemption, which allows a node with a better priority to

initiate a failover to become primary for the configured RG.
Configuring a Redundant Ethernet Interface

To create a reth interface, you configure the two physical interfaces independently.
You configure the rest of the parameters pertaining to reth interfaces at the
interfaces reth number configuration stanza. Once you commit the
configuration, all child interfaces of a reth interface inherit those parameters.
Because reth interfaces are pseudo-interfaces, you must define the number of reth
interfaces in a cluster by configuring reth-count.
Configuring Cluster Failover Parameters

The following are the cluster failover parameters that you can configure, should you
choose to alter their default values:
heartbeat-interval: Interval or duration when all nodes in the

cluster receive the heartbeat message broadcast; and
heartbeat-threshold: Number of missed heartbeats that must be

exceeded to declare the cluster node dead.
Disabling a Chassis Cluster

The slide illustrates the operational mode command used to remove a JUNOS security
platform from a cluster. Enter it first on the primary node and then on the secondary
node. Because it will have its configuration synced to the primary node configuration,
the secondary node will also need its interfaces renamed.
Chassis Cluster Monitoring

Example: Network Diagram Prior to Issuing the Cluster-Forming

Command
Consider the example on the slide. Two high-end security platforms, host1 and host2,
interconnect together using Gigabit Ethernet interfaces as well as SPC control ports in
Slot 3. We connected both nodes to the server site using the ge-0/0/0 interface and
to the Internet using the ge-1/0/0 interface.
Form a Cluster
To form a cluster using high-end security platforms, you must configure the control
ports on the node. Because the secondary nodes configuration will be synchronized
with the primary nodes configuration, you are only required to configure control ports
on the node designated as primary. Make sure to commit the configuration.
For all JUNOS security platforms, use the operational mode commands shown on the
slide to set the cluster identification number and node identification number. The
operational mode command also allows you to perform the mandatory reboot on each
device. Remember to perform this operation first on the node designated to be the
primary node and then on the node designated as secondary.
Example: Network Diagram After Issuing the Cluster-Forming Command

After you reboot the SRX Series Services Gateways, they form a cluster. The cluster
formation results in interface names changing, as illustrated on the slide.
Cluster Status Check

Use the show commands illustrated on the slide to display the status of the chassis
cluster and the cluster interfaces.
Configuring the Management Interface

Next, configure the management interface using the groups and apply-groups
configuration stanzas, as illustrated on the slide.
Configuring the Fabric Interfaces

In the example on the slide, the fab0 and fab1 interfaces of the cluster use ge-0/0/2
and ge-12/0/2 physical interfaces. The slide depicts the configuration of the fab0 and
fab1 interfaces as well as the resulting status. Note that the fab interfaces now show
a link status of up.
Configuring a Redundancy Group

The slide illustrates the configuration of RG0 and RG1. Node 0 is primary because its
priority is higher than Node 1s priority. RG1 monitors the ge-0/0/0 interface
connected to the server site. If the ge-0/0/0 interface becomes unavailable, RG1 fails
over to Node 1 and the ge-12/0/0 interface.
Viewing Redundancy Groups

To view the RG status, use the show chassis cluster status command. This
command allows you to see which nodes are primary and secondary for RG0 and RG1.
You can also verify that you enabled preemption or if a manual failover is in effect. We
discuss manual failovers on a subsequent slide.
Configuring reth Interfaces

In the example on the slide, one reth interface is shownreth1and it belongs to
RG1. Interfaces ge-0/0/0 and ge-12/0/0 constitute the reth1 interface. The total
number of reth interfaces that the cluster will recognize is two (based on a
reth-count value).
Configuring Cluster Failover Parameters

According to the configuration on the slide, heartbeat messages between the nodes in
the cluster happen every 1200 milliseconds. In addition, the system assumes the
node is dead if the number of missed heartbeats exceeds five.
Monitoring Cluster Statistics

Use the show chassis cluster statistics command to display chassis
cluster counters. The counters are useful for troubleshooting and verifying proper
operation.
Manual Failover
You can initiate a failover manually with the request command shown on the slide. A
manual failover bumps up the priority of the redundancy group for that member to
255. Be careful with manual failovers. An RG0 failover implies an RE failover. An RE
failover kills all processes running on the primary node and spawns them on the new
primary RE, which can result in a loss of state, such as routing state.
Resetting a Manual Failover

After a manual failover, the new primary node continues in that role until a reset or
failback occurs. If a failback occurs, the manual failover is lost, and the software
bases state election on priority and preempt settings. A failback in manual failover
mode can occur if the primary node fails or if the threshold of an RG reaches zero.
Chassis Cluster Logging

JSRP stands for
Juniper Services
Redundancy Protocol,
and its name derives
from ScreenOS NSRP,
or Netscreen
Redundancy Protocol.
Use the show log jsrpd command to view chassis cluster events. The jsrpd
process is the process associated with managing chassis cluster events. For some
chassis cluster events, the software dynamically populates this log.
Traceoptions
You can also configure traceoptions for chassis cluster operations. You can set flags
for many events.
{primary:node0}[edit]
user@host# set chassis
all
cli
configuration
eventlib
fsm
heartbeat
init
interface
routing-socket
socket
uspipc
cluster traceoptions flag ?

Trace
Trace
Trace
Trace
Trace
Trace
Trace
Trace
Trace
Trace
Trace
all events
CLI events
configuration events
event library events
finite state machine events
JSRPD heartbeats
initialization events
interface related events
routing socket events
socket events
USP IPC events
High availability clustering and its functionality;
Chassis cluster components;
Chassis cluster operation;
Chassis cluster configuration; and
Chassis cluster monitoring.
Review Questions
1.
The control plane of a chassis cluster uses SPC ports on high-end systems and revenue ports
on branch platforms and is named fxp1. The data plane connects using physical ports named
fab0 and fab1.
2.
The fab interface serves as the data plane link between nodes in a chassis cluster and
transmits RTOs to replicate session state between the two nodes.
3.
An RG is an abstract entity that manages the redundancy of a group of objects. The software
creates RG0 when a chassis cluster forms to manage primacy of REs. The software uses RGx
to manage primacy of reth interfaces.
4.
The default threshold for interface monitoring is 255.
Lab 8: Implementing Chassis Clusters

Appendix A: Acronym List

AES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Encryption Standard
AH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . authentication header
ALG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .application-level gateway
ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Resolution Protocol
ASIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .application-specific integrated circuit
CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . class-of-service
CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cyclic redundancy check
DDoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . distributed denial of service
DES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Encryption Standard
DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Host Configuration Protocol
DMZ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . demilitarized zone
DoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . denial of service
DPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .dead peer detection
ESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encapsulating Security Payload
FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexible PIC Concentrator
GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . graphical user interface
HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .high availability
HMAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hashed Message Authentication Code
HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hypertext Transfer Protocol
HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hypertext Transfer Protocol over Secure Sockets Layer
ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Control Message Protocol
IDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intrusion Detection and Prevention
IDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . initial domain part
IDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . intrusion detection service
IKE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Key Exchange
IOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .input/output card
IPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . intrusion prevention system
IPsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Security
IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP version 4
IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP version 6
ISN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . initial sequence number
ISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet service provider
JNTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Juniper Networks Technical Certification Program
LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lightweight Directory Access Protocol
MD5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Message Digest 5
MTU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . maximum transmission unit
NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Address Translation
NSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Network and Security Manager
NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Network Time Protocol
PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Address Translation
PFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Forwarding Engine
PFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Perfect Forward Secrecy
PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Interface Module
PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Power over Ethernet
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . quality of service
RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Engine
RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . register suppression time
SA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . security association
SCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Control Board
Acronym List A1
SHA-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Secure Hash Algorithm 1

SPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . services processing card
SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .security parameter index
SPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Services Processing Unit
SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secure Sockets Layer
TNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Trivial Network Protocol
ToS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . type of service
TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . time to live
UTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unified Threat Management
VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . virtual LAN
VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . voice over IP
VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .virtual private LAN service
VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .virtual private network
A2 Acronym List
Appendix B: Answer Key

Chapter 1:
Course Introduction
This chapter contains no review questions.
Chapter 2:
Introduction to JUNOS Security Platforms

1.
Traditionally, routers process packets on a per-packet basis.
2.
Traditionally, firewalls process packets based on stateful flows.
3.
JUNOS for security platforms uses session-based packet forwarding and by default does not
allow traffic to pass, whereas traditional JUNOS Software uses packet-based forwarding and by
default allows all traffic to pass.
4.
The first packet of a new session is subject to first-path packet processing.
Chapter 3:
Zones
1.
A zone is a collection of one or more network segments sharing identical security requirements.
2.
Overall, there are two types of zones in JUNOS Softwareuser-defined and system-defined
zones. User-defined zones include security and functional zones, both of which you can
configure. The Null Zone is a system-defined zone that you cannot configure. The security zone
facilitates transit packets and packets to the device itself. The functional zone facilitates only
management traffic. The Null Zone is a placeholder for interfaces that do not belong to any
zone. All interfaces belonging to the Null Zone drop all packets.
3.
To configure a zone, you must perform the following steps: (1) Define a security zone or a
functional zone; (2) Add logical interfaces to the zone; and (3) Optionally, add services and
protocols that must be permitted into the device.
4.
You can specify traffic types to be allowed into a JUNOS security platform using the
host-inbound-traffic statement.
Answer Key B1
Chapter 4:
Security Policies
1.
The basic components of a policy are: (1) policy name; (2) source zone and destination zone;
(3) matching conditions, consisting of one or many source addresses or sets, one or many
destination addresses or sets, one or many applications or sets; and (4) actions.
2.
The default action for every policy set is to deny traffic.
3.
The policy scheduler enables the user to dynamically activate or deactivate a security policy. If
you deactivate a policy, and no other matches are found, the default security policy examines
the packet.
4.
You can reorder policies using the JUNOS Software insert command.
Chapter 5:
Firewall User Authentication

1.
JUNOS Software supports RADIUS, LDAP, and SecurID external authentication servers.
2.
In pass-through authentication, the user attempts to access the remote network resource
directly, and the JUNOS security platform intercepts the session to perform firewall
authentication, while buffering the session. The buffered session is released as long as
authentication is successful. In Web authentication, the user must first access an IP address
belonging to the JUNOS security device using a Web browser; the authentication is performed
using this HTTP session. The user can then proceed to access the remote network resource as
long as authentication is successful. FTP, Telnet, and HTTP traffic trigger pass-through
authentication, while an HTTP session must trigger Web authentication.
3.
A client group is a list of groups associated with a client. Groups can be used in security policies
in place of individual clients for ease of management.
4.
Use the show security firewall-authentication history command to view a
history of firewall authentication attempts.
Chapter 6:
SCREEN Options
1.
The purpose of SCREEN options in JUNOS Software is to offer better network protection to the
networks behind the JUNOS security platform, and to the device itself, from malicious
information or attacks.
B2 Answer Key
Chapter 6:
SCREEN Options (contd.)

2.
The available SCREEN options include IP address sweep detection, port scanning detection,
network investigation triggering, operating system probe blocking, abnormal SYN and FIN flags
setting detection, IP spoofing detection, bad IP source route options detection, ICMP
abnormalities detection, and DoS attack detection.
3.
Beyond offering network and host protection against malicious attacks, the main advantage of
using SCREEN options is that JUNOS Software performs SCREEN checks prior to security policy
processing, which results in fewer resources used for malicious packet processing.
4.
There are two main goals for a DoS attack: immobilizing hosts and immobilizing networks.
5.
Apply SCREEN options under the security zones configuration stanza.
Chapter 7:
Network Address Translation

1.
Destination NAT processing occurs before security policy processing and source NAT processing
occurs after security policy processing.
2.
Static source NAT is supported in one of two waysusing source NAT with address shifting or
the automatic creation of a return session when using static destination NAT.
3.
The NAT off action is for detailed control within NAT rule-sets.
4.
A NAT proxy ARP configuration is necessary when the translated address belongs to the same
subnet as the ingress interface.
5.
The commands used to monitor NAT operations are show security flow session, show
security nat source summary (or show security nat destination summary),
show security nat source pool (or show security nat destination pool),
and show security nat source rule (or show security nat destination
rule).
Chapter 8:
IPsec VPNs
1.
The three major security concerns are confidentiality, integrity, and authentication.
2.
The main difference between ESP and AH is that AH does not provide confidentiality, while ESP
does.
Answer Key B3
Chapter 8:
IPsec VPNs (contd.)

3.
JUNOS Software supports the use of the MD5 and SHA protocols to ensure data integrity.
4.
The two modes available in IKE Phase 1 are main and aggressive.
Chapter 9:
Introduction to Intrusion Detection and Prevention

1.
JUNOS Software processes the rule with the most severe action.
2.
The exempt rulebase exempts specified traffic from IDP policy.
3.
Evaluation of a rulebase stops only when the software matches a terminal rule.
4.
To apply an IDP policy, you must make it the active policy and reference an IDP action in a
security policy.

1.
The control plane of a chassis cluster uses SPC ports on high-end systems and revenue ports
on branch platforms and is named fxp1. The data plane connects using physical ports named
fab0 and fab1.
2.
The fab interface serves as the data plane link between nodes in a chassis cluster and
transmits RTOs to replicate session state between the two nodes.
3.
An RG is an abstract entity that manages the redundancy of a group of objects. The software
creates RG0 when a chassis cluster forms to manage primacy of REs. The software uses RGx
to manage primacy of reth interfaces.
4.
The default threshold for interface monitoring is 255.
B4 Answer Key

Junos For Security Platforms

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Junos For Security Platforms

Transféré par

Droits d'auteur :

Formats disponibles

JUNOS for Security Platforms

1194 North Mathilda Avenue

Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Introduction to JUNOS Security Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Security Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Firewall User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

SCREEN Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

IPsec VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Introduction to Intrusion Detection and Prevention . . . . . . . . . . . . . . . . . . . . 9-1

Chapter 10: High Availability Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Appendix A: Acronym List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Describe traditional routing and security and the current trends in

Provide an overview of SRX Series Services Gateways and software architecture.

Describe, configure, and monitor zones.

Describe, configure, and monitor security policies.

Describe, configure, and monitor firewall user authentication.

Describe various types of network attacks.

Configure and monitor SCREEN options to prevent network attacks.

Explain, implement, and monitor NAT as implemented on JUNOS security

Explain the purpose and mechanics of IPsec VPNs.

Implement and monitor policy-based and route-based IPsec VPNs.

Utilize and update the IDP signature database.

Configure and monitor IDP policy with policy templates.

Describe, configure, and monitor high availability chassis clusters.

Most of what you read in the Lab

GUI text elements:

Text field entry

Input Text Versus Output Text

View configuration history by

lab@San_Jose> show route

Document Conventions vii

Defined and Undefined Syntax Variables

Text where variable value is already

Text where the variables value is

Type set policy

Click on my-peers in the dialog.

viii Document Conventions

About This Publication

Juniper Networks Support