Components of a Security Policy in SonicOSX 7.0

08/31/2020 1 4712

DESCRIPTION:

There are three steps at high level on SonicOSX 7.0 which can be observed below where first section is the match attribute used to classify the packet, perform the rule lookup and then rule match; second section being the action taken on the packet and third section as action profile used to take those additional actions (BWM,Security Services etc).

SonicOSX 7.0 combines layer 4 and 7 policies, providing admins a centralized location for configuring policies.

RESOLUTION:

Match criterion
We can match the traffic based on the following parameters

1. Source and destination zone
2. IP version - IPv4/IPv6
3. Source and destination address
4. Source and destination port/services
5. Users to be included
6. Geo location
7. Application
8. Web category
9. URL
10. Custom match
11. Schedules

We use the Source/Destination and App/URL/Custom Match tabs in the security policy to match.

Actions

There are three types of actions that can be taken once the match is done:

1. Allow
2. Deny
3. Discard

We use the Action section of the security policy to take any necessary action.

Action Profile

Along with the actions stated above, there are some additional actions that can be taken for certain types of traffic.

1. Bandwidth management and QoS
2. Apply security services like GAV, Anti -Spyware, IPS and Botnet filtering
3. Perform additional CFS actions, such as a passphrase, confirm, safe search, consent, wipe cookies, etc
4. Reporting, logging, and Syslog
5. Adjusting miscellaneous settings such as connection timeouts, SIP/H323 settings, etc

We use a security rule Action to apply additional actions to the matched traffic and selected action type.

Once a security rule is added, it can be divided into these three sections easily and can be depicted in the same way on the UI.