
CHAPTER
17-1
Cisco Security Appliance Command Line Configuration Guide
OL-6721-01
17
Applying Filtering Services
This chapter describes ways to filter web traffic to reduce security risks or prevent inappropriate use.
This chapter contains the following sections:
• Filtering Overview, page 17-1
• Filtering ActiveX Objects, page 17-2
• Filtering Java Applets, page 17-3
• Filtering with an External Server, page 17-4
• Filtering HTTP URLs, page 17-7
• Filtering HTTPS URLs, page 17-8
• Filtering FTP Requests, page 17-9
• Viewing Filtering Statistics and Configuration, page 17-10
Filtering Overview
This section describes how filtering can provide greater control over traffic passing through the security
appliance. Filtering can be used in two distinct ways:
• Filtering ActiveX objects or Java applets
• Filtering with an external filtering server
Instead of blocking access altogether, you can remove specific undesirable objects from HTTP traffic,
such as ActiveX objects or Java applets, that may pose a security threat in certain situations.
You can also use URL filtering to direct specific traffic to an external filtering server, such an N2H2
Sentian or Websense filtering server. Filtering servers can block traffic to specific sites or types of sites,
as specified by the security policy.
Because URL filtering is CPU-intensive, using an external filtering server ensures that the throughput of
other traffic is not affected. However, depending on the speed of your network and the capacity of your
URL filtering server, the time required for the initial connection may be noticeably slower when filtering
traffic with an external filtering server.
Komentarze do niniejszej Instrukcji