Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1, Administration Manual

Page: 387 / 1026

3.
Select the Delete icon (-) at the top of the screen. The
Delete QoS Profile
window
opens.
4.
Click
OK
to delete the profile.
Editing a Quality of Service Profile
1.
Select Object Manager > QoS profiles . The QoS profile screen opens with a list of QoS
profiles.
2.
Select a QoS profile to edit.
3.
Select the Edit icon at the top of the screen. The
Edit QoS Profile
window opens.
4.
Edit the values of the profile.
5.
Click
OK
.
Working with DI Attack Objects
Deep Inspection (DI) attack objects contain attack patterns and protocol anomalies for
known attacks and unknown attacks that attackers can use to compromise your network.
DI attack objects must be part of an attack object group, and a DI Profile object before
you can use them in a firewall rule to prevent malicious traffic from entering your network.
NOTE: Deep Inspection is supported by NS-5GT devices, the NS-HSC, and
all devices running ScreenOS 5.3 or later.
To create a Deep Inspection (DI) Profile object, you add predefined attack object groups
(created by Juniper Networks) and your own custom attack object groups to the Profile
object. After creating the DI Profile, you add the Profile object in the Rule Option column
of a firewall rule. If an attack is detected, the device generates an attack log entry that
appears in the Log Viewer.
For information about configuring Deep Inspection in a firewall rule, see “Creating DI
Profiles” on page 338.
Viewing Predefined DI Attack Objects
NSM contains a database of hundreds of predefined DI attack objects designed to protect
networks from multiple attack vectors. Predefined groups contain attack objects, which
you can use in a DI Profile to match traffic against known and unknown attacks.
NOTE: NSM displays a superset of all predefined DI attack objects. Based
on the platform and ScreenOS firmware version, security devices include a
specific subset of DI attack objects. Therefore, the list of predefined DI attack
objects displayed in the NSM UI might not match the list of predefined DI
attack objects on the physical security device.
337 Copyright © 2010, Juniper Networks, Inc.
Chapter 8: Configuring Objects