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

Page: 169 / 861

169 Defining your security environment
Understanding how protocols affect traffic
Use the following table to identify protocols that are paired with proxies.
* When properly configured within a service group, the HTTP protocol can be used for HTTPs.
See “Customizing the HTTP protocol to pass HTTPS traffic” on page 187.
Using protocols that are not paired with proxies
Some protocols that are less commonly used are defined on the security gateway, but are not
associated with application-specific proxies.
The security gateway passes services for these protocols using the Generic Service Proxy (GSP). By
default, the GSP is enabled to pass TCP-, UPD-, and IP-based traffic.
Use the following table to identify protocols that are not associated with proxies.
Table 6-1
Supplied protocols with their associated application proxy
Protocol name Type Port Associated proxy
cifs TCP-based 139 CIFS
dns_tcp TCP-based 53 DNS
dns_udp UDP-based 53 DNS
dns_udp_s2s UDP-based 53 DNS
exec TCP-based 512 RCMD
ftp TCP-based 21 FTP
h323 TCP-based 1720 (UDP 20000 -
30000) H323
* http TCP-based 80 HTTP
login TCP-based 513 RCMD
nbdgram UDP-based 138 NBDGRAM
nntp TCP-based 119 NNTP
ntp UDP-based 123 NTP
ntp-tcp TCP-based 123 NTP
ping ICMP-based n/a Ping
pop3 TCP-based 110 POP3
realaudio TCP-based 7070 RealAudio
rtsp TCP-based 554 RTSP
shell TCP-based 514 RCMD
smtp TCP-based 25 SMTP
telnet TCP-based 23 Telnet
Table 6-2 Supplied protocols with no associated application proxy
Protocol name Type Port
AH IP-based n/a
AIM TCP-based 5190