Link Search Menu Expand Document

Using Our GitHub Repositories

To use the content in our GitHub repositories, you must have them configured in orchestration. These repositories are typically configured by default, however, if your tenant is missing them you can use the instructions below to add them.

Managing Git Repositories


403 - Rate Limit Exceeded

Are you seeing a 403 error when you try to import content from GitHub? Some of the repositories we configure for you are created without credentials. Unauthenticated API requests to GitHub are rate-limited so, if you want to avoid this, you can update the repository configurations with an account key using the steps below.


Creating the Git Repository for Atomic Actions

  1. In SecureX orchestration, expand the main menu and click on Admin and then Git Repositories
  2. Click on the New Git Repository button (or click on the existing repository you want to update)
  3. Provide a name for the repository (suggested: CiscoSecurity_Atomics)
  4. Set No Account Keys to True (see above)
  5. Fill in the Git information:
    • Protocol: HTTPS
    • REST API Repository Type: GitHub
    • REST API Repository: api.github.com/repos/CiscoSecurity/sxo-05-security-workflows
    • Branch: Main
    • Code Path: Atomics
  6. Click Submit

Creating the Git Repository for Workflows

  1. In SecureX orchestration, expand the main menu and click on Admin and then Git Repositories
  2. Click on the New Git Repository button (or click on the existing repository you want to update)
  3. Provide a name for the repository (suggested: CiscoSecurity_Workflows)
  4. Set No Account Keys to True (see above)
  5. Fill in the Git information:
    • Protocol: HTTPS
    • REST API Repository Type: GitHub
    • REST API Repository: api.github.com/repos/CiscoSecurity/sxo-05-security-workflows
    • Branch: Main
    • Code Path: Workflows
  6. Click Submit

Adding an Account Key

Note: If your GitHub account has two-factor authentication enabled, you’ll need to use a personal access token. To generate a token, check out these instructions.

  1. In SecureX orchestration, expand the main menu and click on Account Keys
  2. Click on the New Account Key button and change the type to Git Password-Based Credentials
  3. Give the account key a meaningful Display Name
  4. Enter your GitHub username and password under the Git section (Note: If you’re using a personal access token, put the token instead of your password)
  5. Click Submit
  6. Expand the main menu and click on Admin and then Git Repositories
  7. Click on CiscoSecurity_Atomics:
    • Change No Account Keys to False
    • Select the account key you created as the Default Account Key
    • Click the Submit button
  8. Repeat step 7 for the CiscoSecurity_Workflows repository