Link Search Menu Expand Document

Licensing

When you import content into Cisco SecureX orchestration, such as workflows and atomic actions, it’s important to be mindful of and comply with the applicable license for that content. This page explains some of the different license sources you are likely to see depending on where content is obtained from and what your responsibilities are as a user of the platform.

Use of the SecureX platform is governed by the Cisco End User License Agreement and the SecureX Offer Description unless you have a different applicable signed agreement with Cisco.

However, workflows and atomic actions you import into SecureX are governed by different license agreements. You are responsible for checking the source of what you import into SecureX and reviewing the applicable agreement. Below are a few of the common sources and licenses that may govern workflows and atomic actions for SecureX.

Regardless of which agreement applies, it is very important that you test your workflows and atomic actions carefully in a test environment before putting them into production.


Which License Applies?

The following table gives some examples of sources for SecureX workflows and atomic. We recommend you go to the source repository to review licensing details when in doubt.

Content Source Applicable License
The following Cisco Security Github Repositories:
CiscoSecurity_Workflows
CiscoSecurity_Atomics

Note: These repositories contain workflows and atomic actions developed by Cisco as well as third party integration partners. All atomic actions and workflows sourced from this repository are governed by the MIT License.
MIT License
Cisco DevNet Content in DevNet Code Exchange and Automation Exchange is typically hosted in Github. As such, you should refer to the repository you’re obtaining content from for any applicable licenses
Third Party When you obtain content from third parties, it is your responsibility to know how the content is licensed. Typically, the license is available in the applicable repository. If not, you should ask the provider for the applicable license