Managing FDM Devices with Cisco Defense Orchestrator

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book

Results

Updated:
September 6, 2024

Chapter: Integrating CDO with Cisco Security Cloud Sign On

Integrating CDO with Cisco Security Cloud Sign On

SecureX and CDO

The Cisco SecureX platform connects the breadth of Cisco's integrated security portfolio and the customer's infrastructure for a consistent experience that unifies visibility, enables automation, and strengthens your security across network, endpoint, cloud, and applications. By connecting technology in an integrated platform, SecureX delivers measurable insights, desirable outcomes, and unparalleled cross-team collaboration. For more about what SecureX is and what this platform offers, see About SecureX.

Allowing SecureX to access your CDO tenant results in a summarization of device events, including a total count of device as well as a count of devices with errors, devices with conflicts, and devices that may currently be out-of-sync. The summary of events also provides a second window that tallies currently applied policies and the objects associated to those policies. Policies are defined by device-type, and objects are identified via object type.

Multiple steps are required to add a CDO module to the SecureX dashboard. See Add CDO to SecureX for more information.


Warning

If you have not already merged your CDO and SecureX accounts, you may not be able to see the events for all of your onboarded devices. We strongly recommend merging your accounts before you create a CDO module inSecureX. See Merge You CDO and SecureX Accounts for more information.

Merge Your CDO and SecureX or Cisco XDR Tenant Accounts

If your Secure Firewall Threat Defense or On-Prem Firewall Management Center is used with CDO or Cisco Security Analytics and Logging (SaaS) and SecureX or Cisco XDR, you must link your CDO tenant account with the SecureX or Cisco XDR tenant account associated with the device.

Be mindful of when you initiate this process. This merging process may take an extended amount of time.

See Merge Accounts for instructions.


Note

If you have accounts on more than one regional cloud, you must merge accounts separately for each regional cloud.

Add CDO to SecureX

Allow SecureX to access your registered devices and add the CDO module to the SecureX dashboard to see a summary of your device policies and objects alongside the other Cisco platforms in your security portfolio.


Note

Be mindful of when you initiatie this process. Merging CDO to SecureX may take an extended amount of time.

Before you begin

We strongly recommend the following action items before connecting SecureX in CDO:

  • You must be at least an Administrator for your SecureX account.

  • You must have a SuperAdmin user role for your CDO tenant.

  • Merge your tenant accounts in Security Services Exchange to facilitate tenant communication. See Merge Your CDO and SecureX Accounts for more information.

  • After merging your CDO tenant with Security Services Exchange, ensure that you log out of your CDO tenant and log in again.

  • If you have not already done so, configure Cisco Secure Sign-On as your SAML single sign-on identity provider (IdP) and Duo Security for multi-factor authentication (MFA). Both CDO and SecureX use this as an authentication method. See Integrate Your SAML Single Sign-On with Cisco Defense Orchestrator for more information.


Note

Note: If you have multiple tenants, you must create one module per tenant in SecureX. Each tenant requires a unique API token for authorization.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco