To forward traffic to the IDP rulebases, enable IDP and select one of the following modes:
•
In inline mode, IDP is directly in the path of traffic on your network and can detect and
block attacks. For example, you can deploy the ISG2000 or ISG1000 with integrated
Firewall/VPN/IDP capabilities between the Internet and an enterprise LAN, WAN, or
special zones such as DMZ.
•
In inline tap mode, IDP can detect attacks and provide notification. IDP receives a copy
of a packet while the original packet is forwarded on the network. IDP examines the
copy of the packet and flags any potential problems. IDP’s inspection of packets does
not affect the forwarding of the packet on the network.
You must deploy the ISG2000 or ISG1000 device inline. You cannot connect a device
that is in inline tap mode to an external TAP or SPAN port on a switch.
Selecting either mode enables IDP for the firewall rule, and configures the security device
to forward all permitted traffic to the IDP rulebases for further processing.
Limiting Sessions per Policy from Source IPs
With the session-limit option, you can restrict sessions from a particular Source IP address
to all your devices running ScreenOS 6.1 and later. In NSM, you can set the following
options from the Session Limit tab in the Configure Options window of the device.
•
Session limit per src-ip on policy
•
Session count
•
Alarm without drop packet
When the sessions reach the threshold limit, the system drops all subsequent sessions.
If you enable the "alarm without drop packet" option, the packet is not dropped, but an
alarm message is raised. If you do not set a source IP, the device lists the session counts
of all the source IP addresses in the policy.
In cross-vsys traffic, since there is one policy per vsys to permit traffic, each cross-vsys
session is permitted by two policies. However, the session limit policy is only for the
ingress vsys. You must configure the session limit in the ingress vsys policy to limit the
session count.
In a synchronized NSRP setup, the session limit policy also counts sessions in the slave
device, which does not impose any limit. When the slave becomes the master, a new
session is created only if the existing session count does not exceed the threshold. If the
threshold is exceeded, the packet is dropped. A new session can be created only when
the session counts drop below the threshold when existing sessions are aged out.
Configuring the Session Close Notification Rule
An idle TCP connection remains established until terminated by either the client or the
server. If, for any reason, the client or an intermediate device shuts down, the server
continues to wait on the connection. As an intermediate security device, a device running
ScreenOS maintains a session for each TCP connection until it times out. Traffic can
resume if a client sends an RST (reset) packet, but the client needs to be informed of
Copyright © 2010, Juniper Networks, Inc.
458
Network and Security Manager Administration Guide
Содержание NETWORK AND SECURITY MANAGER 2010.3
Страница 6: ...Copyright 2010 Juniper Networks Inc vi...
Страница 36: ...Copyright 2010 Juniper Networks Inc xxxvi Network and Security Manager Administration Guide...
Страница 52: ...Copyright 2010 Juniper Networks Inc 2 Network and Security Manager Administration Guide...
Страница 90: ...Copyright 2010 Juniper Networks Inc 40 Network and Security Manager Administration Guide...
Страница 144: ...Copyright 2010 Juniper Networks Inc 94 Network and Security Manager Administration Guide...
Страница 146: ...Copyright 2010 Juniper Networks Inc 96 Network and Security Manager Administration Guide...
Страница 234: ...Copyright 2010 Juniper Networks Inc 184 Network and Security Manager Administration Guide...
Страница 310: ...Copyright 2010 Juniper Networks Inc 260 Network and Security Manager Administration Guide...
Страница 364: ...Copyright 2010 Juniper Networks Inc 314 Network and Security Manager Administration Guide...
Страница 366: ...Copyright 2010 Juniper Networks Inc 316 Network and Security Manager Administration Guide...
Страница 478: ...Copyright 2010 Juniper Networks Inc 428 Network and Security Manager Administration Guide...
Страница 576: ...Copyright 2010 Juniper Networks Inc 526 Network and Security Manager Administration Guide...
Страница 580: ...Copyright 2010 Juniper Networks Inc 530 Network and Security Manager Administration Guide...
Страница 592: ...Copyright 2010 Juniper Networks Inc 542 Network and Security Manager Administration Guide...
Страница 684: ...Copyright 2010 Juniper Networks Inc 634 Network and Security Manager Administration Guide...
Страница 690: ...Copyright 2010 Juniper Networks Inc 640 Network and Security Manager Administration Guide...
Страница 696: ...Copyright 2010 Juniper Networks Inc 646 Network and Security Manager Administration Guide...
Страница 698: ...Copyright 2010 Juniper Networks Inc 648 Network and Security Manager Administration Guide...
Страница 748: ...Copyright 2010 Juniper Networks Inc 698 Network and Security Manager Administration Guide...
Страница 778: ...Copyright 2010 Juniper Networks Inc 728 Network and Security Manager Administration Guide...
Страница 870: ...Copyright 2010 Juniper Networks Inc 820 Network and Security Manager Administration Guide...
Страница 872: ...Copyright 2010 Juniper Networks Inc 822 Network and Security Manager Administration Guide...
Страница 898: ...Copyright 2010 Juniper Networks Inc 848 Network and Security Manager Administration Guide...
Страница 908: ...Copyright 2010 Juniper Networks Inc 858 Network and Security Manager Administration Guide...
Страница 910: ...Copyright 2010 Juniper Networks Inc 860 Network and Security Manager Administration Guide...
Страница 995: ...PART 6 Index Index on page 947 945 Copyright 2010 Juniper Networks Inc...
Страница 996: ...Copyright 2010 Juniper Networks Inc 946 Network and Security Manager Administration Guide...