Rulebase Organization and Flow

Reply
L3 Networker

Rulebase Organization and Flow

I hate having OCD sometimes because its things like this I struggle with. How are others organizing their rules? Are you grouping them by source IP? Zone? Common Apps? I have "business units" so each business unit has rules. So After each group of business unit rules there needs to be a deny for that "group" So I was starting to organize by source ip, build all the rules and then put a deny from that source to any and move on. But now I am like "But what if other sources need to access those sources but its still a rule for business unit A then it will be in another section based on a different source IP. I don't think there is a right or wrong way to do this and Yes it will be different for all, but I am just trying to get ideas to better help me. 

Tags (2)
L6 Presenter

Re: Rulebase Organization and Flow

To be honest I have no grouping whatsoever apart from the logical sequence of flow to make things work.

I tend not to mix source IP, source zone or source user in the same policy to make things less complicated but thats just me....

The search filter is my saviour....   

 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!