Symantec Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series, Administration Manual

Page: 178 / 861

178 Defining your security environment
Understanding how protocols affect traffic
Viewing port usage for all protocols
The Protocols tab lists the predefined protocols included with the security gateway. It also lists custom
protocols that you or other administrators create.
You can display the destination and source ports used by these protocols. The default display includes
a column that shows the destination low ports.
Prerequisites
None.
To view port usage
1 In the SGMI, in the left pane, under Assets, click Protocols .
2 In the right pane, on the Protocols tab, to view the list of protocols sorted by port number, click the
Destination Low Port header.
3 To display of other port values for the protocols, in the View menu, click Show Columns .
4 In the Show Columns dialog box, click Destination High Port, Source Low Port, or Source High Port.
5 Click Close .
6
To return the protocols table to its default display, in the View menu, click Show Columns , and
then, in the Show Columns dialog box, click Reset to Defaults .
Related information
None.
Configuring custom protocols to handle data from special applications
You can create custom protocols based on any supported transport protocol and associate them with a
range of destination ports. A custom protocol is a generic protocol that you define to manage traffic
flow for custom applications that are not supported by the standard protocols delivered with the
security gateway. You can configure generic services provided by hosts residing on either side of the
security gateway.
When you create new protocols, make sure that the ports that you use are not already in use by one of
the predefined protocols or other protocols that you have created.
Like the commonly-used protocols, you can use custom protocols in rules or to create filters or filter
groups.
The protocol options shipped with the security gateway let you define custom protocols for two
purposes:
■
As the basis for packet filters
■
As the basis for custom services that you define for GSPs and include in service groups that are
used in rules
Once defined, you can use generic services in service groups in addition to the standard services
supported by the security gateway. Like standard services (such as Telnet, FTP, and HTTP), custom
generic services appear to external hosts attempting to access them as ports on the security gateway.
To let IDS events be triggered on a new protocol that you create, you must add the protocol to one of
the IDS/IPS services on the IDS/IPD portmap.
Most characteristics of protocols that are predefined are read-only. The only fields you can change are
whether a GSP is used as the proxy, whether the protocol uses a native service, and if so, the native
service port.
You can modify all properties of the protocols that you create.