Integrations that Automate Tedious Data Collection

Explore how JupiterOne integrates with your digital environment.

Start Your Free Trial

Explore our integrations


Cloud and Infrastructure Integrations

aws integration jupiterone

Amazon Web Services

Learn More

Openshift

Learn More

Identity & Access Integrations

g suite integration jupiterone

G Suite/Google

Learn More
onelogin integration jupiterone

OneLogin

Learn More

Code Repository Integrations

bitbucket integration jupiterone

BitBucket

Learn More
github integration jupiterone

Github

Learn More

Endpoint and Device Management Integrations

wazzuh integration jupiterone

Wazuh OSSEC Agents

Learn More
carbon black integration jupiterone

Carbon Black PSC

Learn More

SentinelOne

Learn More

Code Scanning, Vulnerability and Findings Integrations

veracode integration jupiterone

Veracode

Learn More

Tenable Cloud

Learn More
white hat integration jupiterone

WhiteHat

Learn More

HackerOne

Learn More

Ticketing Integrations

Data ingestion into JupiterOne

JupiterOne simplifies the tedious, error-prone collection of digital assets by automatically ingesting the data via APIs. The data is ingested with read-only level access to these account. After the data is pulled into JupiterOne, it can be automatically maintained and kept up to date using JupiterOne’s scheduler. That means you no longer have to worry about changes in your environment making your current asset inventory worthless, nor do you have to dread manually inputting or removing data when there are changes in employees, devices, etc.

As data is ingested, classes are automatically assigned using the JupiterOne Data Model. The JupiterOne Data Model is a reference model used to describe digital resources and the complex interconnections among all the resources in a technology organization as an entity-relationship graph. The data model is defined by a set of Entities and their Relationships. It represents a reference model, not a strict or rigid structure. Learn more about the JupiterOne Data Model.

What about manual inputs?

While JupiterOne prioritizes automating the asset creation, collection and maintenance process, organizations are able to manually create entries for any of the above integrations as well as tools not listed. This provides the ultimate flexibility for organizations centralizing their security operations.

Users are also able to create their own, custom classes for the data they are ingesting into JupiterOne.

Don't see an integration?

The JupiterOne engineering team is creating and releasing new integrations every couple of weeks. Should you not see an integration listed as coming soon, contact us to see where your desired integration is on the JupiterOne road map.

Providing Complete Visibility for Leading Cloud-Native Organizations

databricks logo

Providing Complete Visibility for Leading Cloud-Native Organizations

databricks logo