Protecting essential communications example

You can make sure that essential communications are protected and cannot be cut off.

Company A has a engine system administered by multiple administrators of various degrees of familiarity with networking, engines, and Secure SD-WAN Engines. The administrators must often make quick changes to respond to the needs of the company and attend to any problems detected.

In this situation, it is possible that someone might accidentally change the Engine Policy in such a way that important services are cut off. The administrators decide to separate the rules allowing the most important business communications from rules that deal with non-essential traffic to minimize this risk. The administrators:

Create a Firewall Template Policy and select the predefined Firewall Template as the basis of the policy.
Cut and paste the rules allowing essential communications from their current Engine Policy into the new Firewall Template Policy.

In this case, all administrators are allowed to edit the new Firewall Template Policy as well.
Add an insert point below the copied rules in the Firewall Template Policy.

Having the insert point below the essential rules prevents the rules added to the inheriting Engine Policy from affecting the essential communications.
Re-parent their current Engine Policy to use the new template, moving it down a step in the policy hierarchy.
After validating the policy and making sure that the rules are correct, refresh the current Engine Policy.

Most daily editing is done in the Engine Policy. There is less risk of someone accidentally changing the essential rules in the Firewall Template Policy, because the rules are not editable in the Engine Policy.