18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Application Defenses<br />

Application<br />

Defenses<br />

4-14 Understanding Policy Configuration<br />

Please note the following points about service groups:<br />

The services in a service group can be either all allowed or all<br />

denied on a proxy rule. It is not possible to use the same proxy<br />

rule to allow access to a subset <strong>of</strong> services in a service group while<br />

at the same time deny access to a different subset <strong>of</strong> services.<br />

Service groups are extremely effective when implemented in a<br />

proxy rule that regulates access for a user group or netgroup. Keep<br />

in mind, however, that all members in the user group or netgroup<br />

must conform to the same security policy (that is they will all be<br />

allowed or denied access to the same collection <strong>of</strong> services).<br />

Authentication can be configured for a service group rule, even if<br />

not every service in the group permits authentication. The<br />

<strong>Sidewinder</strong> <strong>G2</strong> is able to differentiate which services require<br />

authentication within a group. Mixed service groups<br />

(authenticating and non-authenticating services) are best used with<br />

allow rules. You can use SSO to require authentication for all<br />

services in a service group.<br />

You can define as many service groups as needed.<br />

As always, the sequencing <strong>of</strong> rules within the active rule group<br />

remains important, regardless <strong>of</strong> whether a service group is used.<br />

Application Defenses allow you to configure advanced applicationspecific<br />

properties for each proxy, including basic timeout properties<br />

and application-specific permissions. You can also configure key<br />

services such as anti-virus, anti-spam, SSL decryption, and Web<br />

services management.<br />

You can create Application Defenses in advance and then select the<br />

defense for each rule that you create, or you can create defenses<br />

during rule creation. Whether you create Application Defenses in<br />

advance or within a proxy rule, the defense will be saved to a<br />

common database and can be used for other proxy rules without<br />

needing to be recreated for other rules.<br />

Application proxies that allow you to configure connection properties<br />

are included in the Standard Application Defense. (You can also<br />

configure transparency properties for the Telnet proxy within a<br />

Standard Application Defense.) Application proxies that allow you to<br />

configure advanced, application-specific options (such as anti-virus,<br />

application permissions, etc.) as well as connection properties have<br />

their own branch in the Defenses branch (e.g., Web, Secure Web,<br />

Mail, Multimedia).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!