Skip to main content



Cisco Defense Orchestrator

Onboard an ASA Device


Running Configuration File Prerequisite

The running configuration file of your ASA must be less than 4.5 MB. To confirm the size of your running configuration file, see Confirming ASA Running Configuration Size.

IP Addressing Prerequisite

Each ASA, ASAv, or ASA security context must have a unique IP address and the SDC must connect to it on the interface configured to receive management traffic.

Device Certificate Prerequisites

If your ASA device does not have a compatible certificate, onboarding the device may fail. Ensure the following requirements are met:

  • The device uses a TLS version equal to or greater than 1.0.
  • The certificate presented by the device is not expired, and its issuance date is in the past (i.e. it is already valid, not scheduled to become valid at a later date). 
  • The certificate must be a SHA-256 certificate. SHA1 certificates are not accepted.
  • One of these conditions is true:
    • The device uses a self-signed certificate, and it is the same as the most recent one trusted by an authorized user.
    • The device uses a certificate signed by a trusted Certificate Authority (CA), and provides a certificate chain linking the presented leaf certificate to the relevant CA.

Open SSL Cipher Prerequisites

If the device does not have a compatible SSL cipher suite, the device cannot successfully communicate with the Secure Device Connector (SDC). Use any of the following cipher suites:

  • DHE-RSA-AES128-SHA256
  • DHE-RSA-AES256-SHA384
  • DHE-RSA-AES256-SHA256

If the cipher suite you use on your ASA is not in this list, the SDC does not support it and you will need to update the cipher suite on your ASA.

Onboarding Procedure

Use this procedure to onboard a single live ASA appliance, virtual ASA, or an ASA security context to CDO. If you want to onboard multiple ASAs at once, see Onboard ASAs in Bulk.

  1. Navigate to the Devices & Services page.
  2. Click the blue plus button blue_cross_button.png to onboard an ASA.
  3. Click the ASA tile.
  4. Select the Secure Device Connector (SDC) that this device will communicate with. The default SDC is displayed but you can change it by clicking the SDC name.
  5. Give the device a name.
  6. Enter the location (IP address, FQDN, or URL) of the device or service. The default port is 443.
  7. Once the location of the device or service is verified, enter the username and password of the ASA administrator, or similar highest-privilege ASA user, that CDO will use to connect to the device. 
  8. (Optional) Enter a label for the device. You will be able to filter your list of devices by this label. See Labels and Label Groups for more information.
  9. After labeling your device or service, you can view it in the Devices & Services list.

Note: Depending on the size of the configuration and the number of other devices or services, it may take some time for the configuration to be analyzed.

About Onboarding ASA Security Contexts

See Onboard ASA Security Contexts

About Onboarding an ASA that is Part of a High Availability Pair

Only onboard the primary device of the high-availability pair. Do not onboard the secondary device. The primary device of the high availability pair is onboarded like any other ASA.


Cannot onboard ASA due to certificate error

Environment: ASA is configured with client-side certificate authentication.

Solution: Disable client-side certificate authentication.

Details: ASAs support credential-based authentication as well as client-side certificate authentication. CDO cannot connect to ASAs that use client-side certificate authentication. Before onboarding your ASA to CDO, make sure it does not have client-certificate authentication enabled by using this procedure:

  1. Open a terminal window and connect to the ASA using SSH.
  2. Enter global configuration mode.
  3. At the hostname (config)# prompt, enter this command: 

no ssl certificate-authentication interface interface-name port 443

The interface name is the name of the interface CDO connects to.

  • Was this article helpful?