📝 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.

When you create a Hypersync between Hyperproof and GitLab Self-Managed, you can automatically collect the following proof types:

GitLab Self-Managed proof types and fields

​

❗ Important

To use all proof types, use an account with a Maintainer or Owner role.

📝 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.

💡 Tip

Personal access tokens can be created in GitLab by navigating to Preferences > User Settings. Be sure to select the read_api and read_user checkboxes.

Certain cloud services offer specialized options for IP filtering in their cloud consoles to lock down specific cloud API endpoints for security and compliance purposes. You can use the Hyperproof static IP addresses to allow communication between Hyperproof Hypersyncs and your cloud service.

If your instance is on a private network, add the static IP address for the Hyperproof instance where your organization is hosted to your company's allowlist.

📝 Note

IP addresses for the Hyperproof Gov will be deprecated and replaced, as shown in the following table:

To prevent connectivity issues, it is recommended that you include all four IP addresses in your allowlists.

See Hyperproof instances for more information.