Security Policy Organization

[gheimer]

Anyone have any good tricks to organizing an ever-growing list of security policies?  We have quite a few especially with inspecting internal to internal traffic.  The firewall uses a top down approach to inspection, so I wanted to see if there was a way to insert a break or notation marker to keep things a little more organized.  Was going to just put in a dead policy that denied traffic to something very specific which wouldn't be tagged an use that as my line break.  Open to suggestions._

[ukhapre]

Setting up security rules with Numbers is one idea. Its easier to look up for rules then.

If additional rules need to be put in the middle of those - put 1-1 / 1-2.

[darren_g]

I just group them by source interface - outside, DMZ, inside etc - and add rules within their sections.

Then I just filter the view based on source zone to narrow it down, e.g.

(from/member eq 'outside')

Cheers.

[rmonvon]

You can also use tag to group your rules. tags like inbound, outbound, etc.

[mikand]

Anyone who knows what the status is of grouping rules so you can easily expand/minimize the whole group (similar to how it was done in Juniper NSM but also Checkpoint Smartcenter among others)?

[VinceM]

Hi,

Just tag your rule. and use the research bar for filtering.

the ad is you can have one rule member of many goups. Exemple, you rule from mail server to dma relay can be member of all : Mail and linux and hosting groups in same time . Thing that you can't do with just "normal" grouping.

V.