Sysdig
Visualize Sysdig account, teams, and users, and monitor changes through queries and alerts.
- Installation guide
- Sysdig data model
Installation
This integration requires you to obtain and provide both a Sysdig API toek and your Sysdig SaaS Region:
- Retrieve your Sysdig API Token
- You will need to confirm the SaaS Region for your Sysdig account. You will need to input the Sysdig endpoint for your account (e.g.,
us2
).
Configuration in JupiterOne
To install the Sysdig integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Sysdig. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Sysdig account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
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 Sysdig API Token and Region.
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.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | sysdig_account | Account |
Agent | sysdig_agent | Scanner |
Cluster | sysdig_cluster | Cluster |
Finding | sysdig_finding | Finding |
Image Scan | sysdig_image_scan | Assessment |
Scanner | sysdig_scanner | Service |
Team | sysdig_team | Team |
User | sysdig_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
sysdig_account | HAS | sysdig_agent |
sysdig_account | HAS | sysdig_cluster |
sysdig_account | HAS | sysdig_image_scan |
sysdig_account | HAS | sysdig_scanner |
sysdig_account | HAS | sysdig_team |
sysdig_account | HAS | sysdig_user |
sysdig_agent | SCANS | sysdig_cluster |
sysdig_image_scan | IDENTIFIED | sysdig_finding |
sysdig_scanner | PERFORMED | sysdig_image_scan |
sysdig_team | HAS | sysdig_user |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
sysdig_finding | IS | *cve* | FORWARD |