Describes how to read, discard, and deploy configuration changes to effectively manage and apply network configuration modifications.
Read all device configurations
This task allows you to synchronize device configurations when changes have been made to devices outside of Security Cloud Control, ensuring that Security Cloud Control's copy matches the device's local configuration.
If a configuration change is made to a device outside of Security Cloud Control, the device configuration stored on Security Cloud Control and the device's local copy of its configuration are no longer the same. You many want to overwrite Security Cloud Control's copy of the device's configuration with the configuration stored on the device to make the configurations the same again. You can perform this task on many devices simultaneously using the Read All link.
For more information about how Security Cloud Control manages the two copies of the device configuration, refer to Reading, Discarding, Checking for, and Deploying Configuration Changes.
Here are three configuration statuses where clicking Read All will overwrite Security Cloud Control's copy of the device's configuration with the device's copy of the configuration.
-
Conflict Detected: If conflict detection is enabled, Security Cloud Control polls the devices it manages every 10 minutes for changes made to their configurations. If Security Cloud Control finds that the configuration on the device has changed, Security Cloud Control displays a "Conflict detected" configuration status for the device.
-
Synced: If the device is in a synced state, and you click Read All, Security Cloud Control immediately checks the devices to determine if there have been any changes made to its configurations directly. After clicking Read All, Security Cloud Control confirms your intent to overwrite its copy of the device's configuration and then Security Cloud Control performs the overwrite.
-
Not Synced: If the device is in the Not Synced state, and you click Read All, Security Cloud Control warns you that there are pending changes made to the device's configuration using Security Cloud Control and that proceeding with the Read All operation will delete those changes and then overwrite Security Cloud Control's copy of the configuration with the configuration on the device.
Procedure
The device configurations are read from the selected devices and Security Cloud Control's copy of the configurations is updated to match the local device configurations.
Configuration reading from ASA to Security Cloud Control
Configuration reading is a management process that
-
enables Security Cloud Control to maintain its own copy of the ASA running configuration file for device management
-
occurs during device onboarding when Security Cloud Control reads and saves a copy of the device configuration file for the first time, and
-
provides options to Check for Changes, Accept without Review, or Read Configuration when reading configurations from an ASA.
When Security Cloud Control needs to read ASA configurations
Security Cloud Control needs to read an ASA configuration in these circumstances:
-
When deployment of configuration changes to the ASA fails and the device state is not listed or Not Synced.
-
When device onboarding fails and the device state is No Config.
-
When changes are made to the device configuration outside of Security Cloud Control and those changes have not yet been polled or detected. In this case, the device state is Synced or Conflict Detected.
In these cases, Security Cloud Control needs a copy of the last known configuration stored on the device.
For more information, refer to Reading, Discarding, Checking for, and Deploying Configuration Changes.
Read configuration changes on ASA device
This task enables you to manually synchronize your ASA device with Security Cloud Control to resolve onboarding or deployment failures.
Use this procedure when you need to resolve onboarding failures or deployment issues by reading configuration changes directly from your ASA device.
Follow these steps to read configuration changes on your ASA device:
Procedure
The device configuration is read from the ASA device and synchronized with Security Cloud Control, resolving onboarding or deployment failures.
Reading changes from firewalls
Reading changes from firewalls is a configuration management process that
-
requires Security Cloud Control to maintain its own copy of the device configuration file
-
involves onboarding the device when Security Cloud Control first reads and saves its configuration file, and
-
replaces the existing copy in the database when checking the configuration from the device.
Configuration change management processes
When you check the configuration from the device, Security Cloud Control saves a new copy of the device configuration file and replaces the copy in its database.
Related processes include:
-
Detecting changes made directly to the Cisco IOS or SSH device outside of Security Cloud Control
-
Undoing configuration changes that have been started on Security Cloud Control but not deployed to the IOS or SSH device
For more information about these processes, refer to:
Preview and deploy configuration changes for all devices
This task allows you to deploy pending configuration changes to managed devices in Security Cloud Control and verify the deployment results.
Security Cloud Control informs you when you have made a configuration change to a device in your organization, but you have not deployed that change, by displaying an orange dot on the deploy icon
. Each device affected by these changes displays a status of "Not Synced" in the Security Devices page. Click Deploy to review which devices have pending changes and deploy the changes to those devices.
This deployment method is available for all supported devices.
You can use this deployment method for a single configuration change. Alternatively, you can wait and deploy multiple changes at once.
This deployment method is only available when Security Cloud Control Firewall Management has been onboarded to Security Cloud Control.
Procedure
-
In the menu bar of Security Cloud Control click the Deploy button
. -
Select the devices with changes you want to deploy. If a device displays a yellow caution triangle, you cannot deploy changes to that device. Hover your pointer over the yellow caution triangle to see the reason.
-
(Optional) If you want to see more information about a pending change, click the View Detailed Change log link to open the change log associated with that change. Click the Deploy icon to return to the Devices with Pending Changes page.
-
Click Deploy Now to deploy the changes immediately to the devices that you selected. You will see the progress in the Active jobs indicator in the Jobs tray.
-
(Optional) After the deployment has finished, in the Platform menu, click Firewall, and then select . You will see a recent "Deploy Changes" job showing the results of the deployment.
Configuration changes are successfully deployed to the selected devices. The deployment status can be monitored through the Jobs tray and verified in the Events & Logs section.
Configuration deployment to firewall devices
Configuration deployment to firewall devices is a process that
-
pushes pending configuration changes to managed firewall devices
-
supports Cloud-Delivered Firewall Management Center-managed Firewall Threat Defense devices, and
-
can be initiated from either the Security Devices page or the Deployments page.
Supported device types
From Security Cloud Control, you can deploy pending configuration changes to these devices:
-
Cloud-Delivered Firewall Management Center-managed Firewall Threat Defense devices
Deploy configuration changes from security devices page
Deploy configuration changes from deployments page
Before you begin
When you make configuration changes to a Firewall Threat Defense device through the Cloud-Delivered Firewall Management Center, the device can take up to 10 minutes before it displays as Not Synced in Security Cloud Control and becomes available for deployment.
Monitor deployments from deployments page
Deploy configuration changes from Security Cloud Control to ASA
A configuration deployment is a network management process that
-
transfers staged configuration changes from Security Cloud Control to the running configuration of an ASA device
-
updates only the modified configuration elements without overwriting the entire configuration file, and
-
allows changes to take effect on network traffic passing through the device.
Why does Security Cloud Control deploy changes to an ASA
When you manage and make changes to a device configuration with Security Cloud Control, Security Cloud Control saves those changes to its own copy of the configuration file. Those changes are considered staged on Security Cloud Control until they are deployed to the device. Staged configuration changes have no effect on the network traffic running through the device. Only after Security Cloud Control deploys the changes to the device do they have an effect on the traffic running through the device. When Security Cloud Control deploys changes to the device's configuration, it only overwrites those elements of the configuration that were changed. These actions do not overwrite the entire configuration file on your device.
The ASA has a running configuration file (sometimes called the running config) and a startup configuration file (sometimes called the startup config). The configuration stored in the running config file is enforced on traffic passing through the ASA. After you change the running config and confirm the device behaves as you want, deploy those changes to the startup config. When you reboot the ASA, it starts using the startup config as its configuration starting point. If you do not save your changes to the startup config, you lose them when you reboot the ASA.
Deploying changes from Security Cloud Control to an ASA writes those changes to the running configuration file. When you are satisfied with how those changes affect the device, deploy them to the startup configuration file.
You can start deployments for one device or several devices simultaneously. You can schedule single or recurring deployments for a device.
If you use the command line interface on Security Cloud Control to make a change to an ASA, those changes are not staged on Security Cloud Control. They are deployed directly to the running configuration of the ASA. When you make changes that way, your device remains synced with Security Cloud Control.
Deploy configuration changes
This task enables you to update your device configuration via the GUI or Device Configuration page to ensure your network remains secure.
This section assumes you are using Security Cloud Control's GUI or editing the Device Configuration page to make changes to an ASA configuration file, and not using Security Cloud Control's CLI interface or CLI macro interface.
Follow these steps to update an ASA configuration:
Procedure
The configuration changes are deployed to your device and your network configuration is updated according to the changes made through the two-step deployment process.
Deploy configuration changes made using the Security Cloud Control GUI
This task allows you to apply configuration changes from Security Cloud Control to your device's running configuration.
Use this procedure to review pending updates, check synchronization status, and apply changes effectively after making configuration modifications through the Security Cloud Control GUI.
Procedure
The configuration changes are successfully deployed to your ASA and the device status returns to synced.
Schedule automatic deployments
Schedule automatic deployments is a configuration feature that enables your tenant to deploy changes automatically either to a single device or to all devices with pending changes.
Deployment scheduling information
For more information about the deployment scheduling feature, refer to scheduling automatic deployments.
Deploy configuration changes using Security Cloud Control's CLI interface
This task allows you to deploy configuration changes to devices using the CLI interface, enabling direct command execution for configuration management and device updates.
Use the CLI interface when you need to make configuration changes to devices through direct command entry. This method is useful for single commands, batch operations, or applying configuration file sections.
Procedure
The configuration changes are deployed to the device's running configuration. If you choose to deploy to disk, the changes are also saved to the startup configuration.
Deploy configuration changes by editing the device configuration
This task allows you to deploy configuration changes by directly editing the device configuration in Security Cloud Control, enabling direct modification of the ASA running configuration.
This procedure is for advanced users who are familiar with the syntax of an ASA configuration file. This method makes changes directly to the running configuration file stored on Security Cloud Control.
Procedure
-
From the Security Cloud Control Home page, click Firewall.
-
Choose
-
Click the appropriate device type tab.
-
Select the device whose configuration you want to change.
-
Click View Configuration in the Actions pane.
-
Click Edit.
-
Make your changes to the running configuration and Save them.
-
Return to the Security Devices page. In the Not Synced pane, click Preview and Deploy...
-
In the Device Sync pane to review the changes.
-
Click Replace Configuration or Apply Changes to Device depending on the kind of change it is.
The configuration changes are deployed to the device and the device configuration is updated with your modifications.
Deploy configuration changes for a shared object on multiple devices
This task enables you to efficiently modify and deploy configuration changes to multiple devices that share a common policy or object, ensuring consistent updates across your network infrastructure.
Use this procedure when you are making changes to a policy or object shared by two or more devices. You can change a common policy on however many devices use it.
Procedure
-
Open and edit the Policies page or the Objects page containing the shared object you want to edit.
-
Review the shared device list and confirm that you want to make the changes on all the devices mentioned.
-
Click Confirm.
-
Click Save.
-
Click the Deploy icon
and deploy your changes to the affected devices.
The configuration changes are deployed to all devices that share the modified policy or object, ensuring consistent updates across your network infrastructure.
Deploy changes to a device
Deploy saved configuration changes from Security Cloud Control to the actual device.
Use this procedure to deploy changes to a single FTD, Meraki, or AWS VPC device.
Procedure
The configuration changes are deployed to the selected device and the device status updates to reflect successful synchronization.
Cancelling changes
Cancelling changes is a deployment control action that
-
stops the deployment process when you click Cancel during deployment
-
prevents changes from being deployed to the device
-
keeps changes in a pending state on Security Cloud Control for future editing and deployment to FDM-managed device.
Discarding changes
Discarding changes is a configuration management action that removes all uncommitted modifications made to device configurations and reverts the system to the last deployed state.
Change discarding behavior
When you click Discard all while previewing changes, the system performs these actions:
-
Deletes the changes you made
-
Deletes any other changes that other users made but did not deploy to the device
-
Reverts Security Cloud Control pending configuration to the last read or deployed configuration before any changes were made
Bulk deploy device configurations
Use bulk deployment to efficiently apply configuration changes to multiple devices at once, particularly when you have modified shared objects that affect several devices.
If you have made changes to multiple devices, for instance by editing a shared object, you can apply those change to all of the affected devices at once.
Procedure
Configuration changes are deployed to all selected devices simultaneously, and the deployment status can be monitored through the Jobs interface.
Preview and deploy On-Premises Firewall Management Center configurations
This task allows you to deploy configuration changes made in Security Cloud Control to your On-Premises Firewall Management Center and ensures configuration synchronization between systems.
If you have made configuration changes to an object, such as changing a value or adding an override to an object, you can deploy all those changes at once to your On-Premises Firewall Management Center.
This task deploys configuration changes only to On-Premises Firewall Management Center. To deploy these changes to your Firewall Threat Defense devices, you must deploy these changes manually from your On-Premises Firewall Management Center. For more information, see Configuration Deployment in the Cisco Secure Firewall Management Center Device Configuration Guide.
Procedure
The configuration changes are deployed to your On-Premises Firewall Management Center and the system status shows as synchronized. You must manually deploy these changes to your managed Firewall Threat Defense devices from your On-Premises Firewall Management Center.
Scheduled automatic deployments
A scheduled automatic deployment is a Security Cloud Control feature that
-
allows you to make configuration changes to one or more devices and schedule the deployment at a convenient time
-
deploys all staged changes saved on Security Cloud Control at the specified date and time, and
-
requires enabling the scheduling option in the Tenant Settings tab before use.
Deployment requirements and behavior
You can only schedule deployments if you Enable scheduled automatic deployments in the Tenant Settings tab of the Settings page. Once this option is enabled, you can create, edit, or delete scheduled deployments.
If there were changes made directly to the device that have not been read to Security Cloud Control, the scheduled deployment will be skipped until that conflict is resolved. The Jobs page will list any instance where a scheduled deployment fails. If Enable the Option to Schedule Automatic Deployments is turned off, all scheduled deployments are deleted.
You can also view and delete scheduled deployments from the Jobs page.
If you schedule a new deployment for multiple devices, and some of those devices already have deployments scheduled, the new scheduled deployment overwrites the existing scheduled deployments.
When you create a scheduled deployment, the schedule is created in your local time, not in the time zone of the device. Scheduled deployments do not automatically adjust for daylight savings time.
Schedule an automatic deployment
Schedule automatic deployments to streamline the deployment process and align with maintenance windows. This can be configured as a single event or a recurring event for convenience.
The deployment schedule can be a single event or a recurring event. You may find recurring automatic deployments a convenient way to line up recurring deployments with your maintenance window.
This procedure applies only to ASAs and FDM-managed devices.
To schedule deployments for Secure Firewall Threat Defense devices managed by on-premises Firewall Management Center or Cloud-Delivered Firewall Management Center, see Scheduling.
If you schedule a deployment for a device that has an existing deployment scheduled, the new scheduled deployment overwrites the existing deployment.
Follow these steps to schedule a one-time or a recurring deployment for a single device:
Procedure
The automatic deployment is scheduled according to your selected configuration. The system will execute deployments at the specified time intervals.
Edit a scheduled deployment
Edit the timing parameters of scheduled deployments to ensure device configurations are deployed at the most appropriate times for your network operations.
Use this procedure when you need to modify the scheduling parameters of an existing deployment to better align with maintenance windows or operational requirements.
Before you begin
Follow these steps to edit a scheduled deployment:
Procedure
The scheduled deployment is updated with your new timing parameters and will execute according to the modified schedule.
Delete a scheduled deployment
This task allows you to remove scheduled deployments that are no longer needed or need to be rescheduled.
Use this procedure when you need to cancel or remove a previously scheduled deployment from your devices.
If you schedule a deployment for multiple devices, and then change or delete the schedule for some of the devices, the original scheduled deployment for the remaining devices will be preserved.
Procedure
The scheduled deployment is deleted from the selected devices.
Check for configuration changes
Check for configuration changes to determine if the device's configuration has been modified directly on the device and no longer matches the copy stored on Security Cloud Control.
Use Check for Changes to determine if the device's configuration has been changed directly on the device and it is no longer the same as the copy of the configuration stored on Security Cloud Control. You will see the this option when the device is in the "Synced" state.
Procedure
The system compares configurations and presents options to either accept or reject the changes found on the device.
Discard configuration changes
Use this task to discard undeployed configuration changes and restore synchronization between Security Cloud Control and the device configuration.
Click Discard Changes when you want to "undo" all the undeployed configuration changes you made to a device's configuration using Security Cloud Control. When you click Discard Changes, Security Cloud Control completely overwrites its local copy of a device's configuration with the configuration stored on the device.
When you click Discard Changes, your device's configuration status is in a Not Synced state. After you discard your changes, the copy of the configuration on Security Cloud Control will be the same as the copy of the configuration on the device and the configuration status in Security Cloud Control will return to Synced.
Follow these steps to discard all of your undeployed configuration changes for a device:
Procedure
The device configuration status returns to Synced, and the configuration copy on Security Cloud Control matches the configuration on the device.
Discard On-Premises Firewall Management Center configuration changes
This task allows you to undo all configuration changes made in Security Cloud Control and restore the configuration to match what is stored on the device.
Use this procedure when you need to undo all configuration changes you made in Security Cloud Control, such as changes to objects shared between your Security Cloud Control and On-Premises Firewall Management Center. When you perform this task, Security Cloud Control completely overwrites its local configuration copy with the configuration stored on the device.
Procedure
All configuration changes are discarded and the local configuration copy in Security Cloud Control matches the configuration stored on the On-Premises Firewall Management Center. The status returns to Synced.
Out-of-band changes on devices
Out-of-band changes are configuration modifications that
-
are made directly on the device without using Security Cloud Control
-
may be made using the device's command-line interface over an SSH connection or by using a local manager like the Adaptive Security Device Manager (ASDM) for the ASA, the FDM for the FDM-managed device, or for an On-Premises Firewall Management Center on the On-Premises Firewall Management Center user interface, and
-
cause a conflict between the device's configuration stored on Security Cloud Control and the configuration stored on the device itself.
Detecting out-of-band changes on devices
If Conflict Detection is enabled for an ASA, or an FDM-managed device, a Cisco IOS device, or an On-Premises Firewall Management Center, Security Cloud Control checks the device every 10 minutes searching for any new changes made directly to the device's configuration outside of Security Cloud Control.
If Security Cloud Control finds that there are changes to the device's configuration that are not stored on Security Cloud Control, it changes the Configuration Status of that device to the "Conflict Detected" state.
When Security Cloud Control detects a conflict, one of these conditions is likely:
-
There have been configuration changes made to the device directly that have not been saved to Security Cloud Control's database.
-
In the case of an FDM-managed device, there may be "pending" configuration changes on the FDM-managed device that have not been deployed.
-
In the case of an On-Premises Firewall Management Center, there may be changes made, for instance, to objects outside Security Cloud Control, which are pending to be synchronized with Security Cloud Control or changes made in Security Cloud Control which are pending to be deployed to the On-Premises Firewall Management Center.
on the details pane. Review any warnings and click
in the navigation bar to view the results of the bulk deploy.
.