Skip to main content

Ingesting assets

Before you can query and act on your data in JupiterOne, you need to bring your assets into your workspace. Most organizations start with integrations, which populate and refresh the majority of their assets automatically, and then fill the gaps with custom data.

Managed integrations​

JupiterOne offers more than 200 managed integrations with cloud providers, identity providers, endpoint and vulnerability tools, and other technologies. Once you configure an integration instance, it pulls assets and relationships from that tool on a polling interval, so your data stays current without manual work.

On-premise and self-hosted sources​

Some sources, such as applications in your own data center or behind a firewall, are not reachable from JupiterOne's cloud. Run these integrations on a JupiterOne collector deployed inside your network.

Custom data​

If JupiterOne does not have an integration for a tool, or you want to enrich assets that integrations already ingest, you can import your own data:

For guidance on gathering and classifying your data before you import it, see Custom data ingestion.

Creating assets in JupiterOne​

You can also create individual assets directly in your workspace. This is useful for a small number of assets that no integration or import covers.

What's next​

Once data is flowing into JupiterOne, review your assets in the Assets section of your workspace. Continue to Working with assets to learn how to explore and manage them.

Contents