Table 14: Firewall Data Elements
(continued)
Description
Data Element
You must include HTTP, FTP, or Telnet service objects in the Service column of the rule to enable
remote users to authenticate themselves using Authentication. You can include other services
as well, or specify all services.
If authentication succeeds, the NSM allows the remote user to establish a connection to the
destination address. If authentication fails, NSM drops the initial connection.
If the source address supports multiple remote user accounts (for example, a Unix host running
Telnet) or it is located behind a NAT device that uses a single IP address for all NAT assignments,
only the first remote user from that source address must initiate and authenticate an HTTP, FTP,
or Telnet connection. All subsequent remote users from that source address do not have to
authenticate, and can pass matching network traffic to the destination address.
If you use WebAuth, to make a connection to the destination address in the rule, the remote user
must first initiate an HTTP connection to the WebAuth server. Your security device responds
with a login prompt. After the remote user provides a user name and password, NSM attempts
to authenticate the user credentials. If authentication succeeds, NSM permits the remote user
to establish a connection to the destination address. If authentication fails, NSM drops the initial
connection. The possible values:
•
no-auth
•
infranet-auth
•
auth
•
webauth
auths
You can determine when a security device applies a rule to network traffic by defining a schedule
for the rule.
schedule
If you select
HA Session Backup
, a rule with the Permit action will not be active when the session
switches to the modern link. When this happens, the rule takes the Deny action.
ha_session_backup
Disable modem idle timer reset. (default = false)
no-idle-reset
Traffic shaping enables you to control the amount of bandwidth that is available to the matching
network traffic in a rule. It also enables you to set a priority that determines how the security
device handles matching network traffic that exceeds the defined maximum bandwidth. For
security devices running ScreenOS 5.3 or later, you can also manage the flow of traffic through
the security device by limiting bandwidth at the incoming point. The possible values:
•
gbw
•
priority
•
mbw
traffic
37
Copyright © 2010, Juniper Networks, Inc.
Chapter 5: Security Data Model
Summary of Contents for NETWORK AND SECURITY MANAGER 2010.4 - API GUIDE REV 1
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 10: ...Copyright 2010 Juniper Networks Inc x Network and Security Manager 2010 4 API Guide...
Page 12: ...Copyright 2010 Juniper Networks Inc xii Network and Security Manager 2010 4 API Guide...
Page 20: ...Copyright 2010 Juniper Networks Inc 2 Network and Security Manager 2010 4 API Guide...
Page 24: ...Copyright 2010 Juniper Networks Inc 6 Network and Security Manager 2010 4 API Guide...
Page 34: ...Copyright 2010 Juniper Networks Inc 16 Network and Security Manager 2010 4 API Guide...
Page 92: ...Copyright 2010 Juniper Networks Inc 74 Network and Security Manager 2010 4 API Guide...
Page 98: ...Copyright 2010 Juniper Networks Inc 80 Network and Security Manager 2010 4 API Guide...
Page 100: ...Copyright 2010 Juniper Networks Inc 82 Network and Security Manager 2010 4 API Guide...
Page 112: ...Copyright 2010 Juniper Networks Inc 94 Network and Security Manager 2010 4 API Guide...
Page 128: ...Copyright 2010 Juniper Networks Inc 110 Network and Security Manager 2010 4 API Guide...
Page 138: ...Copyright 2010 Juniper Networks Inc 120 Network and Security Manager 2010 4 API Guide...
Page 152: ...Copyright 2010 Juniper Networks Inc 134 Network and Security Manager 2010 4 API Guide...
Page 165: ...PART 6 Index Index on page 149 147 Copyright 2010 Juniper Networks Inc...
Page 166: ...Copyright 2010 Juniper Networks Inc 148 Network and Security Manager 2010 4 API Guide...