AtGuard/NIS System Wide/General RulesThe following are some examples of rules that would be used in the System Wide Settings portion of Internet Access Control in some versions of NIS/NPF and General Rules in NIS2003, and should be placed at the top of the rule set. These rules would generally be in the order shown below:
Rule examples here were made with NIS v.4 which permits multiple remote addresses in a rule. Those using earlier version would have to make individual rules for each remote address. ***Note: Denotes any comments on the rule.
***Note: An example monitor/log only rule for a specific application that could be created to monitor traffic to later customize existing rule(s) for that application. | Top |
***Note: An example of a common global permit rule for LAN traffic. This example shows individual IP's, but could also be a range of IP's or the subnet, your choice. While this traffic can be permitted via the Internet Zone Control "Trusted" sites in the Personal Firewall Settings, some prefer to have specific rules for this traffic which would allow the user to monitor this traffic if and when desired. No logging is available for sites/traffic permitted via the Internet Zone Control.
***Note: An example global block rule for traffic to specic sites/remote addresses. While this traffic can be blocked via the Internet Zone Control "Restricted" sites in the Personal Firewall Settings, some prefer to have specific rules for this traffic which would allow the user to monitor this traffic. No logging is available for sites/traffic permitted via the Internet Zone Control.
***Note: Don't want to see all those Code Red/Nimda scans in your logs. An example of how a global block rule could be used to block a particular inbound communication, but not clutter up your logs. | Top |
Customizing Your Rule Set Contributors: CrazyM, jvmorris Last updated: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|