Follow Cisco Defense Orchestrator on YouTube.
March 26, 2020
FTD Security Database Updates
CDO allows you to immediately update and, simultaneously, schedule future updates for security databases when you onboard you FTD device. This feature updates the SRU, security intelligence (SI), vulnerability (VDB), and geolocation databases. Note that you can only schedule future updates as part of the onboarding process. See Update FTD Security Databases for more information.
Support for Port Ranges in FTD Service Objects
CDO now supports creating service objects (also referred to as port objects in FTD) that contain a range of port numbers. See Create a Firepower Service Object for more information.
March 24, 2020
Cisco Secure Sign-on Domain Migration
On Tuesday March 24, 2020, at 5pm Pacific Daylight Savings Time, the official domain for Cisco Security Single Sign-on solution was moved from https://security.cisco.com to https://sign-on.security.cisco.com.
We recommend that you update any saved links and update any password managers, so they are referencing the new URL.
This move will limit your access to CDO for a short period of time, but doesn’t limit your ability to perform updates using your local device managers or SSH connections.
If you experience any issues please contact Cisco TAC, who can provide you with technical support.
March 12, 2020
CDO introduces Rulesets for Firepower Threat Defense devices. A ruleset is a collection of access control rules that can be shared by multiple FTD devices. Any change made to the rules of a ruleset affects the other FTD devices that use the ruleset. An FTD policy can have both device-specific (local) and shared (rulesets) rules. You can also create rulesets from existing rules in an FTD device.
This feature is currently available for devices running Firepower Threat Defense 6.5 and later releases.
See FTD Rulesets for more information.
March 5, 2020
Copy or Move rules within an FTD Policy or to Another FTD Policy
It’s now possible to copy or move rules from the policy on one FTD to the policy on another FTD. We have also made it easier to move rules within an FTD policy so you can fine-tune the order in which rules evaluate network traffic.
AnyConnect Software Package Upload to FTD Version 6.5+
You can now use CDO's Remote Access VPN wizard to upload AnyConnect packages from a remote server to a Firepower Threat Defense (FTD) device running FTD 6.5 or later. Ensure that the remote server supports HTTP or HTTPS protocol.
See Upload AnyConnect Software Packages to an FTD Device Running FTD Version 6.5 or Later for more information.
March 3, 2020
Terminology Update in CDO's Interface
In order to manage a device, Cisco Defense Orchestrator (CDO) must have a copy of the device's configuration stored in its own database. When CDO "reads" a configuration, it makes a copy of the configuration stored on the device and saves it to CDO's database. We have renamed some interface options to better describe what you are doing when you perform a read action. This is the new terminology:
- Check for Changes. If a device's configuration status is Synced, the Check for Changes link is available. Clicking Check for Changes directs CDO to compare its copy of the device's configuration with the device's copy of the device's configuration. If there is a difference CDO immediately overwrites its copy of the device's configuration with the copy stored on the device.
- Discard Changes. If a device's configuration is Not Synced, clicking Discard Changes deletes any changes CDO made to its copy of the device configuration and also overwrites it with a copy of the configuration found on the device.
- Accept Without Review. This action overwrites CDO's copy of a device's configuration with the copy of the configuration stored on the device. CDO does not prompt you to confirm the action.
See Reading, Discarding, Checking for, and Deploying Configuration Changes for more information.
February 6, 2020
January 22, 2020
Dynamic Peer Support for Site-to-Site Connections
You can now configure a site-to-site VPN tunnel between two peers when one of the peer's VPN interface has a dynamic IP address. This dynamic peer can be a managed FTD device or an Extranet device.
See Configure Site-to-Site VPN Connections with Dynamically-Addressed Peers for more information.
January 16, 2020
Improved Deployment Experience
CDO has improved its deployment workflow. An additional deployment icon is now visible throughout CDO. You no longer have to return to the Devices & Services page to deploy your configuration changes.
When the deployment icon includes an orange dot it signals that there is at least one configuration change made to at least one of the devices you manage with CDO, that is ready to be deployed.
See Review and Deploy Configuration Changes for All Devices for more information.
Cancelling Bulk Actions
You can now cancel any active bulk action you have taken on multiple devices. For example, assume you have tried to reconnect four managed devices and three of the devices have successfully reconnected but the fourth device has neither succeeded nor failed to reconnect. You can now go to the Jobs page, find the ongoing bulk action and click Cancel to stop the action.
CDO Support for Devices Running Firepower Threat Defense 6.5.0
CDO now manages FTD 6.5.0 devices. These are the aspects of support CDO provides:
- Onboading a device running Firepower Threat Defense (FTD) 6.5.0.
- Support for additional Firepower series devices such as the Firepower 4100 and Firepower 9300.
- Support for a virtual FTD instance on Microsoft Azure.
- See Firepower Threat Defense Support Specifics for a complete list of supported device types.
- Upgrading FTD 6.4.x devices to FTD 6.5.0 devices. Devices can be individual FTDs or FTDs configured in a high-availability pair. These caveats apply to upgrade support:
- Upgrading an HA pair will not be supported for FTDs running 6.5.0 if the device is using a data interface for management.
- Upgrades on Firepower 4100 and Firepower 9300 devices are not currently supported.
- Customers will be able to upgrade to FTD 6.5.0 using the drop-down in the upgrade page in CDO. The link that is provided to the device for 6.5 image download will be a HTTP. This may mean that the image download time could be slightly longer than if the download were done over HTTPS. In addition, if outbound HTTP traffic from the FTD is blocked, the image download will fail.
- When FTD 6.5.0 is installed on a Firepower 1010 you can configure interfaces to run as a regular firewall interface or as a Layer 2 hardware switch port. At this time, switch mode support on CDO is read-only. To create or modify an interface for switch port mode, use the FDM console. CDO continues to develop its support for switch port mode on Firepower 1010s and will announce its full support in What's New when it is available.
- When you onboard an FTD 6.5.0 device using a registration token, you can send connection events, file and malware events, and intrusion events directly to the Cisco cloud without using a Secure Event Connector. See Implementing Cisco Security Analytics and Logging.
- Continued support for FTD 6.4.x features. CDO is continuously developing support for FTD 6.5 features and will release support as it is ready.
For more information about the FTD features CDO supports, review Managing Firepower Threat Defense with Cisco Defense Orchestrator.
IKEv1 Support for Site to Site VPN Connections
CDO now supports creating site-to-site VPN tunnels using Internet Key Exchange version 1 (IKEv1). It helps you to configure site-to-site VPN on legacy firewalls, which does not support Internet Key Exchange version 2 (IKEv2). Internet Key Exchange (IKE) is a key management protocol that is used for authenticating IPsec peers, negotiate and distribute IPsec encryption keys, and automatically establish IPsec security associations (SAs).
See Site-to-Site Virtual Private Network for more information.
Firepower Threat Defense Template Improvements
CDO now allows you to parameterize some aspects of the FTD template to further customize templates. See Configure Firepower Threat Defense Templates for more information.
Smart License Management
You can now manage Cisco Smart Licenses for Firepower Threat Defense devices within CDO. Smart Licensing is conveniently built into our workflows and easily accessible from the CDO interface. You can now perform these Cisco Smart Licensing tasks within CDO:
- Apply a Smart License while onboarding an FTD device using a registration token
- View the licenses applied to a device
- Register the licenses with Cisco Smart Software Manager
- Enable and Disable different license types for your device
See Onboard a Firepower Threat Defense Device with a Registration Token and Smart-licensing an Onboarded FTD for more information.
Amazon Web Services Support
CDO now manages AWS VPC!
Amazon Web Services (AWS) Virtual Private Cloud (VPC) is a commercial cloud computing service that provides users a virtual private cloud associated to your AWS account; this network closely resembles a traditional network that you'd operate in your own data center, with the benefits of using the scalable infrastructure of AWS.
CDO helps you optimize your AWS VPC by identifying problems with objects and rules and gives you ways to fix them. Use CDO to:
- Manage an AWS VPC environment along with your FTD or ASA devices.
- Simultaneously manage all security group rules associated with the AWS VPC.
- Create and customize security group rules with objects that are compatible across other supported platforms, such as FTD and ASA devices.
- View AWS VPC site-to-site VPN connections.
See Managing AWS with Cisco Defense Orchestrator for more information.
Migrate your ASAs to FTD Devices Using CDO
CDO helps you migrate your Adaptive Security Appliance (ASA) to a Firepower Threat Defense (FTD) device. CDO provides a wizard to help you migrate these elements of the ASA's running configuration to an FTD template:
- Access Control Rules (ACLs)
- Network Address Translation (NAT) rules
- Network objects and network group objects
- Service objects and service group objects
Once these elements of the ASA running configuration have been migrated to an FTD template, you can then apply the FTD template to a new FTD device that is managed by CDO. The FTD device adopts the configurations defined in the template, and so, the FTD is now configured with some aspects of the ASA's running configuration.
See Migrating ASA to Firepower Threat Defense Using Cisco Defense Orchestrator for a full explanation of the process of migrating an ASA to an FTD using CDO.
Cisco Introduces a New Single Sign-On Solution using Cisco Secure Sign-on and Duo Multi-factor Authentication
CDO adopts this new solution and converts customer tenants to the Cisco Secure Sign-on identity provider (IdP) and Duo Security multi-factor authenticator.
With Cisco Secure Sign-On, you will benefit from:
- Strong and resilient identity: Security that meets the highest industry standards, including AICPA SOC 2, CSA-Star, and ISO 27001. It also supports segregated FedRAMP and HIPAA environments for customers.
- Duo Multi-Factor Authentication (MFA): Duo MFA integrated with Cisco Secure Sign-On means adaptive, layered, and simplified authentication. One push notification, one tap, instant access.
- A single sign-in for seamless workflows: Enter a single username and password to access all your applications, anywhere, and on any device, while maintaining context through workflows.
- A customized experience: Arrange your work apps on your Cisco Secure Sign-On dashboard any way you want. Tabs and a search bar help keep you organized.
- If you sign in to CDO using your own single sign-on identity provider, this transition to Cisco Secure Sign-On and Duo does not affect you. You continue to use your own sign-on solution.
- If you are in the middle of a free trial of CDO, this transition does affect to you.
See these resources for more information
Cisco Security Analytics and Logging Including Integration with Stealthwatch Cloud
Cisco Security Analytics and Logging improves network visibility so you can quickly detect threats in real time and remediate incidents with confidence and at scale.
With Cisco Security Analytics and Logging you can capture connection, intrusion, file, malware, and Security Intelligence events from all of your Firepower Threat Defense (FTD) devices and view them in one place in CDO.
The events are stored in the Cisco cloud and viewable from the Event Logging page in CDO where you can filter and review them to gain a clear understanding of what security rules are triggering in your network. The Logging and Troubleshooting package gives you these capabilities.
With the Firewall Analytics and Monitoring package, the system can apply Stealthwatch Cloud dynamic entity modeling to your FTD events, and use behavioral modeling analytics to generate Stealthwatch Cloud observations and alerts. If you obtain a Total Network Analytics and Monitoring package, the system applies dynamic entity modeling to both your FTD events and your network traffic, and generates observations and alerts. You can cross-launch from CDO to a SWC portal provisioned for you, using Cisco Single Sign-On.
Onboarding a Firepower Threat Defense Device with a Registration Token
You can now onboard your FTD device using a registration token rather than using an IP address, username and password. This is especially beneficial if your FTD is assigned an IP address using DHCP. If that IP address changes for some reason, your FTD remains connected to CDO. Additionally, your FTD can have an address on your local area network, and as long as it can access the outside network it can be onboarded to CDO using this method.
This method of onboarding is currently available for FTD 6.4 releases and to customers connecting to defenseorchestrator.cisco.com. It is not yet available for customers connecting to defenseorchestrator.cisco.eu.
See Onboard a Firepower Threat Defense Device with a Registration Token for more information.
Cisco Security Analytics and Logging
Cisco Security Analytics and Logging improves network visibility so you can quickly detect threats in real time and remediate incidents with confidence and at scale. Learn more!
Remote Access VPN Support for Firepower Threat Defense
Remote Access (RA) VPN allows individuals to establish a secure connection to your network using supported laptop, desktop, and mobile devices. CDO provides an intuitive user interface for you to setup RA VPN on the Firepower Threat Defense (FTD) devices you have onboarded.
AnyConnect is the only client that is supported on endpoint devices for RA VPN connectivity.
CDO supports the following aspects of RA VPN functionality on FTD devices:
- Transport Layer Security (TLS) or Datagram Transport Layer Security (DTLS) for privacy, authentication, and data integrity
- SSL client-based remote access
- IPv4 and IPv6 addressing
- Shared RA VPN configuration across multiple FTD devices
See Remote Access Virtual Private Network for more information.
See also, Managing Firepower Threat Defense with Cisco Defense Orchestrator for all the other ways CDO can manage your FTD devices.
Firepower Threat Defense High Availability Image Upgrade Support
You can now upgrade FTD HA pairs in CDO. When you upgrade a failover pair, CDO copies the desired upgrade image to both devices for you. CDO temporarily moves the primary device to active mode if it is not already, then upgrades the secondary device. Once the secondary device successfully upgrades, the primary device upgrades. The failover pair upgrades the devices one at a time to minimize network disruption.
To upgrade your failover pairs, see Upgrade a Firepower Threat Defense High Availability Pair for more information.
Site-to-Site VPN for Firepower Threat Defense Devices
Site-to-Site VPN for Firepower Threat Defense devices is now generally available!
CDO allows you to establish secure connections between two sites in different geographic locations. These peers can have any mix of inside and outside IPv4 and IPv6 addresses. Site-to-site tunnels are built using the Internet Protocol Security (IPsec) protocol suite and Internet Key Exchange version 2 (IKEv2). After the VPN connection is established, the hosts behind the local gateway can connect to the hosts behind the remote gateway through the secure VPN tunnel. You can create site-to-site IPsec connections for the following scenarios for devices that are onboarded to CDO:
- Between two managed devices
- Between the managed device and other Cisco peers
- Between the managed device and third-party peers
Firepower Threat Defense High Availability Support
CDO makes high availability (HA) support for Firepower Threat Defense firewalls generally available! You can now onboard an existing HA pair or create an HA pair in CDO. HA configurations make it possible to maintain a secure network in scenarios where a device might be unavailable, such as during an upgrade period or an unexpected device failure; in failover mode, the standby device is already configured to become active, meaning that even if one of the HA devices becomes unavailable, the other device continues to handle traffic.
Most of the features supported for standalone FTD devices also support devices configured for HA. See Firepower Threat Defense High Availability for more information.
Coming soon... support for FTD HA upgrades. At the moment, if you need to upgrade your HA pair, you must execute the upgrade through the active device's FDM console.
Time Range Objects for ASA Devices
You can now customize the rules in your network policies with time range objects; these objects let you execute one-time or recurring rules and customize how your network handles traffic. See Time Range Objects for more information.
Firepower Threat Defense Support
CDO makes support for Firepower Threat Defense firewalls generally available!
CDO is designed for firewall administrators who want a simplified management interface and cloud-access to their Firepower Threat Defense devices. Firepower Device Manager (FDM) administrators will notice many similarities between the FDM interface and the CDO interface. We built CDO with the idea of keeping things as consistent as possible between managers.
CDO can now manage Firepower Threat Defense (FTD) devices running FTD version 6.4.0 and later when it is installed on the ASA 5508-x, ASA 5515-x, ASA 5516-x, ASA 5525-x, ASA 5545-x, ASA 5555-x, the FTD 2100 series devices, the FTD 1000 series devices, or virtual FTD devices.
Use CDO to manage these aspects of your physical or virtual Firepower Threat Defense (FTD) device:
- Device management
- Device upgrade
- Interface Management
- Security Policies
- Promote policy and configuration consistency
- Change tracking
- Monitoring your network
All CDO FTD PIDs are orderable in CCW, including for the Firepower 1000 series and Virtual FTD. The PIDs are platform specific, but common for ASA and FTD. Please consult our ordering guide in Salesconnect for more details.
For more information about the features we support, review Managing Firepower Threat Defense with Cisco Defense Orchestrator.
Meraki MX Support
CDO now manages Meraki MX Firewall Policies!
Meraki MX is an enterprise security and software-defined wide-area-network (SD-WAN) next-generation firewall appliance designed for distributed deployments. You can now manage layer 3 network rules on Meraki MX devices using Cisco Defense Orchestrator.
CDO helps you optimize your Meraki environment by identifying problems with objects and policies and gives you ways to fix them. This applies to policies that are associated to both devices and templates. Use CDO to:
- Simultaneously manage policies on one or more Meraki devices
- Monitor and manage Meraki policies or templates alongside your FTD and ASA devices in an all-encompassing environment.
- Use a Meraki template to manage multiple networks.
- Customize access rules with objects that are compatible across other supported platforms, such as FTD and ASA devices.
See Managing Meraki MX with Cisco Defense Orchestrator for more information.
Updated GUI Navigation
Navigating CDO's UI just got easier.
The policy menu in the navigation bar now guides you to policies grouped by device or function. We only expose the menu paths you need to reach the policies that currently exist on your tenant.
All of FTD's monitoring capabilities are grouped in the Events & Monitoring area of the navigation bar. The Monitoring menu shows you Network Reports and Threats.
Device Connectivity Troubleshooting
This tool allows you to test or troubleshoot connectivity issues between the Secure Device Connector (SDC) and any of your devices. You may want to test this connectivity if your device fails to on-board or if you want to determine, before on-boarding, if CDO can reach your device. See Troubleshoot Device Connectivity with Secure Device Connector for more information.
You can Help us Improve the CDO User Experience
We want to know about your CDO user experience and we now have an easy way for you to tell us. We've added a Provide Feedback button to our Help menu so you can give us your feedback without leaving the CDO portal. Tell us what you like and what we can improve on.
When you leave us your feedback, tell us your role in your company. Are you in the network operations center, the security operation center, or are you in the I-do-it-all-IT-center? Tell us what task you're trying to complete. Are you trying to edit a security policy or find something in the change log?
Here's how to leave us your feedback:
- Log in to CDO.
- Next to your tenant and account name, click the help button and select Provide Feedback.
- Enter your feedback and click Send Email. This generates an email to firstname.lastname@example.org in your local mail server that you must manually send.
A member of our support staff will respond as soon as possible.
Resolution to Container Privilege Escalation Vulnerability Affecting Secure Device Connector: cisco-sa-20190215-runc
The Cisco Product Security Incident Response Team (PSIRT) published the security advisory cisco-sa-20190215-runc which describes a high-severity vulnerability in Docker. Read the entire PSIRT team advisory for a full explanation of the vulnerability.
This vulnerability impacts all CDO customers:
- Customers using CDO's cloud-deployed Secure Device Connector (SDC) do not need to do anything as the remediation steps have already been performed by the CDO Operations Team.
- Customers using an SDC deployed on-premise need to upgrade their SDC host to use the latest Docker version.
See Container Privilege Escalation Vulnerability Affecting Secure Device Connector: cisco-sa-20190215-runc for instructions on how to update a CDO-standard SDC host and a custom SDC host.
Add Labels when Bulk Onboarding ASA Devices
You can now specify custom device labels when bulk onboarding your ASA devices. See Onboard ASAs in Bulk for more information.
Cisco IOS Device Support
Cisco Defense Orchestrator (CDO) allows you to manage Cisco IOS devices. These are the features we support for those devices:
- Onboarding Cisco IOS devices
- View the device configuration
- Read policy and configuration changes from device
- Detect out-of-band changes
- Command line interface support
- Individual CLI commands and groups of commands can be turned into editable and reusable "macros"
- Detect and manage SSH fingerprint changes
- View changes to IOS devices in the Change Log
Schedule Automatic Deployments
After making configuration changes for one or more devices using CDO, you can now schedule the deployment of those changes, to those devices, at a date and time that is convenient for you. For example you can schedule the deployments to occur during your maintenance window or during a time of low network traffic.
See, Enable the Option to Schedule Automatic Deployments, and Schedule Automatic Deployments for more information.
Terminology Change: CDO "Deploys" Changes to the Devices it Manages
We updated the terminology we use to describe transferring changes you made on CDO's local copy of a device's configuration to the device itself. We previously used the word "write" to describe that transfer, now we use the word "deploy" to describe that transfer.
As you manage and make changes to a device's configuration with CDO, CDO saves the changes you make to its own copy of the configuration file. Those changes are considered "staged" on CDO until they are "deployed" to the device. Staged configuration changes have no affect on the network traffic running through the device. Only after CDO "deploys" the changes to the device do they have an affect on the traffic running through the device. When CDO deploys changes to the device's configuration, it only overwrites those elements of the configuration that were changed. It does not overwrite the entire configuration file stored on the device.