Deploying Policies Overview
When you finish creating and verifying your security configurations, you can deploy these configurations and keep them ready to be pushed to the security devices. CSO enables you to push security configurations to the devices all at once by providing a single interface that is intuitive.
The deployment workflow provides the ability to save and publish different services to be updated at a later time to the appropriate firewalls (during downtime). This enables administrators to review their firewall and NAT policies before updating the device. Administrators also save troubleshooting time, avoid errors, and save costs associated with errors. Verify and tweak your security configurations before updating them to the device. This approach helps you keep the configurations ready and update these configurations to the devices during the maintenance window.
When you deploy policies, the process takes into account the priority and precedence values set on the policy and the order of rules on the device. Rules are published in the order of their priority groups.
If you change the priority or precedence of a published policy, the policy must be republished for the changes to take effect. Sometimes, changing priority or precedence in one policy can affect other policies in the same priority group. However, such dependent policies do not need to be republished in order for their changes in priority or precedence to take effect. It will be enough if the policy which is updated is republished.
There are three ways in which you can view and deploy your security configurations:
Click on the deployment icon present in the CSO Customer Portal banner and use the deployment panel that appears, to deploy policies. See Using the Deployment Icon to Deploy Policies.
Note:The deployment icon is highlighted in orange if there are undeployed configurations.
Use the Deployments page. See About the Deployments Page.
Select a firewall, NAT or SD-WAN policy from its respective landing pages and click Deploy. For more information, see Deploying Policies.