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 />

Policy configuration basics<br />

The following steps outline the basic processing that takes place when an<br />

outbound Telnet connection request arrives at a <strong>Sidewinder</strong> <strong>G2</strong> with the above<br />

active rules in place.<br />

1 A outbound Telnet request arrives at the <strong>Sidewinder</strong> <strong>G2</strong>.<br />

2 The request is processed by the active IP Filter rules. No match is found, so<br />

the request is forwarded to the proxies.<br />

3 The request is processed by the proxies. The telnet proxy is listening<br />

(enabled), so the request is forwarded to the active proxy rules.<br />

4 The request is processed by the first rule in the Active Rules table, which is<br />

the NetMeeting rule. The request does not match the rule criteria.<br />

5 The request is forwarded to the next rule in the table, a rule group called<br />

<strong>Administration</strong>, and is inspected in sequential order by each rule contained<br />

within that group. No match is found in this rule group.<br />

6 The request is forwarded to the next rule in the table, a rule called Internet<br />

Services. A match is found (because the Telnet proxy is included in the<br />

service group used in this rule).<br />

7 The request is processed according to the specifications in the Internet<br />

Services rule. The Internet Services rule is an allow rule with NAT enabled.<br />

The request bypasses all other rules and groups contained in the active<br />

rules table, the internal address <strong>of</strong> the request is translated, and the request<br />

is granted.<br />

Ordering proxy rules within a rule group<br />

The order in which rules and nested groups appear in the active rule group is<br />

significant. When the <strong>Sidewinder</strong> <strong>G2</strong> is looking for a rule match, it searches the<br />

active rules in sequential order (beginning with the first rule or nested group<br />

within the group, then the second, and so on). The first rule that matches all the<br />

characteristics <strong>of</strong> the connection request (service type, source, destination,<br />

and so on) is used to determine whether to allow or deny the connection.<br />

Therefore, you should always place rules that allow or deny the most frequent<br />

traffic near the top <strong>of</strong> an active rule group to reduce the processing time.<br />

Important: If the characteristics <strong>of</strong> a connection request matches more than one<br />

rule, the first one it matches will be used and the search will stop.<br />

For example, suppose you want to allow access to FTP services on the<br />

Internet for all systems except those included in a netgroup called<br />

“publications.” The scenarios below illustrate both the incorrect and correct rule<br />

placement.<br />

101

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

Saved successfully!

Ooh no, something went wrong!