topic Re: Using "Any" as zone for a converted policy in General Topics

Using "Any" as zone for a converted policy

Cesar.pevezFajardo — Fri, 20 Jan 2012 15:03:05 GMT

I'm converting a security policy from a Check Point device to a PAN device using the PAN converter. By default the converter sets source and destination zones as "Any". Can I use the rule like that? Is there any problem that such configuration might cause in the future or after replacing the devices? Do I need to specify zones in the rules? Please send me your comments. Thanks.

Re: Using "Any" as zone for a converted policy

mikand — Fri, 20 Jan 2012 20:05:40 GMT

The zones can be compared to "vlans". Instead of just specify the interface you specify the zone (a single interface can have one or multiple zones or if you want to call them vlans).

The point of specify to/from zone is to limit which traffic is allowed (or for that matter denied).

For example if you wish all hosts to query your dns-servers then you can select source-zone: any. But lets say you wish to limit so only clients from the client-zone should be able to do this then you set the source-zone to "clients" (or whatever you might call that zone).

Or the other way around, if you want any hosts except those from client-zone you can first have a deny for traffic from client-zone to dns-zone (and appid: dns) followed by a rule that allows any zone to the dns-zone (and appid: dns).

Using any as zone is good in the moment of first test but I would recommend you to tighten up the rules so only the traffic that should be allowed really is allowed.

Re: Using "Any" as zone for a converted policy

pandragon — Sat, 21 Jan 2012 02:43:56 GMT

While automated converters do the bulk of job, such migration projects would need some additional "human" touch. It will be good to perform one round of manual analysis and use specific zones as source & destination rather than any. Other learning from such migration projects is that sometimes the source or destination is spread across all the zones hence we might be tempted to leave it as "any". It may be a good practice to select all zones by name rather than "any". Because subsequently in future, when we add new zones, we may have to spend more time in analyzing the impact on old rules with "any" zone. This little time spent will help in future troubleshooting of existing rules based on zone names.