Cisco Secure Workload
Visualize Cisco Secure Workload user roles and scopes, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
- Release Notes
Installation
To use the Cisco Secure Workload integration, you need an API Key and API Secret with the specific capabilities the integration requires. The integration authenticates using HMAC-SHA256 request signing — every request is signed with the API Secret, so no write access is granted.
Prerequisites
- Log in to your Cisco Secure Workload dashboard.
- Click your account name in the upper right corner and choose API Keys.
- Click Create API Key and enter an optional description.
- Under Capabilities, select all three of the following:
user_role_scope_management— read users, roles, and application scopesflow_inventory_query— query workload inventory, packages, and vulnerabilitiesapp_policy_management— read application workspaces and security policies
- Click Create. Copy the API Key and API Secret and store them securely — the secret is shown only once.
- Note the URL of your Cisco Secure Workload dashboard (for example,
https://<tenant>.tetrationpreview.com).
See Cisco Secure Workload OpenAPIs for full details on API key capabilities and authentication.
Configuration in JupiterOne
Navigate to Integrations in JupiterOne, select Cisco Secure Workload, and click New Instance.
Creating an instance requires the following:
- API Key — The API Key generated in Cisco Secure Workload.
- API Secret — The API Secret generated alongside the API Key.
- API URI — The base URL of your Cisco Secure Workload dashboard (for example,
https://<tenant>.tetrationpreview.com).
Click Create to finish. The integration will begin running on the polling interval you selected, or you can trigger it manually at any time.
Next steps
Once configured, your Cisco Secure Workload data will populate in JupiterOne. See the Instance management guide to learn how to edit, disable, or re-run your integration instance.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | csw_account | Account |
| Interface | csw_interface | Application |
| Package | csw_package | CodeModule |
| Policy | csw_policy | ControlPolicy |
| Role | csw_role | AccessRole |
| Scope | csw_scope | Group |
| User | csw_user | User |
| Workload | csw_project | Project |
| Workload Finding | csw_workload_finding | Finding |
| Workload Vulnerability | csw_workload_vulnerability | Finding, Vulnerability |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
csw_account | HAS | csw_user |
csw_account | HAS | csw_role |
csw_account | HAS | csw_policy |
csw_interface | HAS | csw_scope |
csw_package | HAS | csw_workload_finding |
csw_policy | HAS | csw_scope |
csw_project | HAS | csw_interface |
csw_project | HAS | csw_package |
csw_project | HAS | csw_workload_finding |
csw_role | USES | csw_scope |
csw_scope | HAS | csw_scope |
csw_user | HAS | csw_role |
csw_user | ASSIGNED | csw_scope |
Csw Workload Finding
csw_workload_finding inherits from Finding
Csw Workload Vulnerability
csw_workload_vulnerability inherits from Finding, Vulnerability
Release Notes
- 2025-06-05 — Promoted Cisco Secure Workload vulnerability findings to carry both the Vulnerability and Finding entity classes, enabling cross-integration vulnerability queries.