Table 12: Backdoor Rulebase Data Elements
(continued)
Description
Data Element
For each attack that matches a rule, you can choose an action
that will occur if the IDP detects interactive traffic. The
following actions are possible:
•
Accept = IDP accepts the interactive traffic
•
Drop Connection = IDP drops the interactive connection
without sending an RST packet to the sender. This prevents
the traffic from reaching its destination. This action is
selected to drop connections from traffic that is not prone
to spoofing.
•
Close Client = IDP closes the interactive connection to the
client but not to the server.
•
Close Server = IDP closes the interactive connection to the
server but not to the client.
•
Close Client and Server = IDP closes the interactive
connection and sends a RST packet to both the client and
the server. If IDP is operating in an inline tap mode, IDP sends
a RST packet to both the client and the server but does not
close the connection.
action
Sets the operation to detect or ignore. If you select detect,
choose an action to perform if backdoor traffic is detected.
op
If this parameter is enabled, the API logs an attack and creates
log records with attack information. You can display this
information real time in the Log Viewer. For more critical
attacks, you can set an alert flag that will appear in the log
record.
log
This parameter configures a rule that only applies to messages
in specified VLANs. The possible settings are:
•
Any (default) = Any rule will be applied to messages in any
VLAN and to messages without a VLAN tag. This setting has
the same effect as not specifying a VLAN. Any can be sent
to devices that do not support VLAN tagging.
•
None = A rule will be applied only to messages that do not
have a VLAN tag. Rules with this value set cannot be sent
to devices that do not support VLAN tagging.
•
vlan_list_collection = Specifies the VLAN tags to which the
rule applies. You must create VLAN objects before applying
them to the rules. Rules with this value set cannot be sent
to devices that do not support VLAN tagging.
vlan
Action to be taken on the log. This can include configuring
SNMP, Syslog, CSV, XML, script, and e-mail settings.
log-actions
29
Copyright © 2010, Juniper Networks, Inc.
Chapter 5: Security Data Model
Содержание NETWORK AND SECURITY MANAGER 2010.4 - API GUIDE REV 1
Страница 6: ...Copyright 2010 Juniper Networks Inc vi...
Страница 10: ...Copyright 2010 Juniper Networks Inc x Network and Security Manager 2010 4 API Guide...
Страница 12: ...Copyright 2010 Juniper Networks Inc xii Network and Security Manager 2010 4 API Guide...
Страница 20: ...Copyright 2010 Juniper Networks Inc 2 Network and Security Manager 2010 4 API Guide...
Страница 24: ...Copyright 2010 Juniper Networks Inc 6 Network and Security Manager 2010 4 API Guide...
Страница 34: ...Copyright 2010 Juniper Networks Inc 16 Network and Security Manager 2010 4 API Guide...
Страница 58: ...Figure 10 IDP Rulebase Copyright 2010 Juniper Networks Inc 40 Network and Security Manager 2010 4 API Guide...
Страница 92: ...Copyright 2010 Juniper Networks Inc 74 Network and Security Manager 2010 4 API Guide...
Страница 98: ...Copyright 2010 Juniper Networks Inc 80 Network and Security Manager 2010 4 API Guide...
Страница 100: ...Copyright 2010 Juniper Networks Inc 82 Network and Security Manager 2010 4 API Guide...
Страница 112: ...Copyright 2010 Juniper Networks Inc 94 Network and Security Manager 2010 4 API Guide...
Страница 128: ...Copyright 2010 Juniper Networks Inc 110 Network and Security Manager 2010 4 API Guide...
Страница 138: ...Copyright 2010 Juniper Networks Inc 120 Network and Security Manager 2010 4 API Guide...
Страница 152: ...Copyright 2010 Juniper Networks Inc 134 Network and Security Manager 2010 4 API Guide...
Страница 165: ...PART 6 Index Index on page 149 147 Copyright 2010 Juniper Networks Inc...
Страница 166: ...Copyright 2010 Juniper Networks Inc 148 Network and Security Manager 2010 4 API Guide...