18.07.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 4: Understanding Policy Configuration<br />

Rule elements<br />

108<br />

Service groups<br />

A service group is a collection <strong>of</strong> selected proxies and/or servers. Once<br />

defined, a service group can be used in a proxy rule to regulate access to the<br />

services in the group. There are important administrative benefits gained by<br />

using service groups: While a typical proxy rule will regulate access for a single<br />

proxy or server, a proxy rule that is implemented using a service group can<br />

regulate access for multiple proxies and/or servers. Grouping services together<br />

in this manner enables you to reduce the overall number <strong>of</strong> rules you define,<br />

which in turn reduces the overall complexity <strong>of</strong> your rule database. A less<br />

complex rule database means there is less chance <strong>of</strong> introducing errors that<br />

may affect the integrity <strong>of</strong> your security policy. You can also configure<br />

Application Defense groups for rules that use service groups to specify<br />

advanced properties for each proxy included in that rule. (See “Application<br />

Defenses” on page 109 for an overview <strong>of</strong> Application Defenses.)<br />

Example <strong>of</strong> a rule that uses a service group<br />

Here’s an example that illustrates the power <strong>of</strong> a service group.<br />

Assume you have a netgroup named eng_net_grp that consists <strong>of</strong> all the<br />

engineers in your organization. If you want to grant Web, FTP, and Telnet<br />

access to this group, you might do so by defining three separate rules. Table 9<br />

illustrates how these three rules might look in the rule database.<br />

Table 9: Typical rules not using service groups<br />

No. Name Service Service Type Enabled Action<br />

1 http_out HTTP proxy Enabled Allow<br />

2 ftp_out FTP proxy Enabled Allow<br />

3 telnet_out Telnet proxy Enabled Allow<br />

A better option, however, is to use a service group. This enables you to<br />

accomplish the same thing with one proxy rule. Create a service group that<br />

contains the HTTP, FTP, and Telnet proxies, then use this service group when<br />

defining the proxy rule. Table 10 illustrates the service group you might create,<br />

and Table 11 illustrates how the resulting proxy rule will appear in a rule.<br />

Table 10: Sample service group<br />

Service Group Name Selected Proxies Selected Servers<br />

EngServGrp HTTP, FTP, Telnet

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

Saved successfully!

Ooh no, something went wrong!