Skip to main content

Cisco Secure Workload

Visualize Cisco Secure Workload user roles and scopes, and monitor changes through queries and alerts.

Installation​

info

You will need to create a new API Key and API Secret in Cisco Secure Workload for this integration. See their documentation for more information.

Required Permissions in Cisco Secure Workload​

The API credentials must have read-only access to the following resources via the OpenAPI:

  • Users (/openapi/v1/users) - to retrieve user account information
  • Roles (/openapi/v1/roles) - to retrieve role definitions and permissions
  • Scopes (/openapi/v1/app_scopes) - to retrieve application scope configurations
  • Applications (/openapi/v1/applications) - to retrieve application definitions
  • Workloads (/openapi/v1/inventory) - to retrieve workload inventory and configurations
  • Packages (/openapi/v1/software/packages) - to retrieve software package information
  • Policies (/openapi/v1/applications/{id}/policies) - to retrieve security policies

The integration uses HMAC-SHA256 signature authentication with API Key and Secret. Ensure the API credentials are created with Observer or Read-Only scope capabilities and no write permissions are required.

Configuration in JupiterOne​

To install the Cisco Secure Workload integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Cisco Secure Workload. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • The Account Name used to identify the Cisco Secure Workload account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Cisco Secure Workload API Key and API Secret.

  • The API URI for your Cisco Secure Workload dashboard.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.