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.

Figure 4-4. User Groups<br />

user group<br />

named<br />

“accounting”<br />

user group<br />

named<br />

“engineering”<br />

Rule elements<br />

Figure 4-4, shows five users divided into two user groups:<br />

“Accounting” and “Engineering.” Suppose you want to allow both<br />

user groups Telnet access to the Internet. Also suppose you want to<br />

authenticate the “Accounting” user group differently from the<br />

“Engineering” user group. In this example you create two nearly<br />

identical rules to allow Telnet access, one for each user group. The<br />

only difference in the rules for each user group would be the<br />

authentication method you specify for each group.<br />

Network objects<br />

internal<br />

network<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

Internet<br />

A network object is an entity for which you configure the <strong>Sidewinder</strong><br />

<strong>G2</strong> to allow or deny connections. A network object can be an IP<br />

address, a host, a network domain, a netmap, a subnet, or netgroup.<br />

When you create rules, you must specify a network object as the<br />

source or destination <strong>of</strong> the connection. (You may also select the All<br />

option, which serves as a wildcard.) The following subsections<br />

provide an overview <strong>of</strong> how each network object is used.<br />

Note: IP Filter rules can only use IP address, subnet, and some host (localhost) network<br />

objects.<br />

Understanding Policy Configuration 4-9

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

Saved successfully!

Ooh no, something went wrong!