415
Enabling remote access with clientless VPN
Using rules to allow or deny clientless VPN access
Related information
For further information related to this topic, see the following:
■
“VPN Profile Properties—General tab”
■
“Creating and assigning roles”
■
“Using portal pages to customize the user experience”
Using rules to allow or deny clientless VPN access
Clientless VPN rules determine whether the remote users are allowed or denied access to internal
network resources. Rules contain a series of expression statements that is matched to all resource
requests made by the user.
You can create rules as exact match expressions, meaning if the URL the user attempts to access does
not exactly match the profile, the user is not granted access. You can also enter rules as regular
expressions. This lets you grant or deny access to a wide range of resources using one access rule.
Clientless VPN roles let you easily assign access privileges to users from a hierarchical (parent/child)
system of inheritance; the child role inherits the access privileges of all its parent roles. Access
privileges depend on the rules or rule sets that are bound to a particular role.
A rule defines URLs that identify internal network resources. Each rule is identified by a unique name.
There are two types of clientless VPN rules:
Rule components
A rule specifies the minimum requirements needed in the URL to identify a resource. The most
significant URL components of an access rule are:
About simple rules
Simple rules let you quickly define access permission and create elementary matching patterns for the
most essential URL components. A simple rule identifies specific resources and the attributes required
for access. To use more sophisticated pattern matching, use the advanced rules.
Simple rules
Identifies resources that have straightforward attributes (such as an email server), or if you
are uncomfortable using regular expressions.
Advanced rules
Identifies a resource and the attributes required to access it. The attributes vary by resource
protocol and are entered as regular expressions. An advanced rule can identify one or more
resource protocols that are located on the same host.
Access type
Determines whether the rule allows or denies access to the resource.
Resource protocol
Defines the type of traffic controlled by the rule, including File, Mail (email), MAPI,
Microsoft Outlook, HTTP (Web), HTTPS (secure Web), FTP, TELNET, TCP, UDP, and VPN.
Host name
A pattern matching the domain name or IP of the computer/server where the resource is
located.
Summary of Contents for Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series
Page 76: ...76 Managing administrative access Enabling SSH for command line access to the appliance...
Page 242: ...242 Defining your security environment Controlling full application inspection of traffic...
Page 243: ...243 Defining your security environment Controlling full application inspection of traffic...
Page 269: ...268 Limiting user access Authenticating using Out Of Band Authentication OOBA...
Page 373: ...372 Preventing attacks Enabling protection for logical network interfaces...
Page 509: ...508 Generating reports Upgrade reports...
Page 553: ...552 Advanced system settings Configuring advanced options...
Page 557: ...556 SSL server certificate management Installing a signed certificate...
Page 861: ...860 Index...