Skip to main content

JupiterOne proof types and permissions

Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.

Hyperproof supports collecting information directly from JupiterOne.

When you add a Hypersync for JupiterOne to controls or labels you can automatically collect the following proof types:

Requirements

To connect to JupiterOne and collect proof your JupiterOne configuration must meet the following requirements.

  • API Token - To generate your API Token, in JupiterOne navigate to Settings > API Tokens.

  • Account ID - To locate your account ID, in JupiterOne navigate to Settings > Account Management.

Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.

Connection configuration

When you create a Hypersync for JupiterOne for the first time, you must provide the following information:

  • API Key - Enter the API Token that the JupiterOne administrator created for Hyperproof

  • Account ID - Enter the account ID for your JupiterOne account.

Note

You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need. Additionally, you can create multiple Hypersyncs for a single control or label.

Additional documentation