Skip to main content

GitLab proof types

Written by Hyperproof Support
Updated over 3 weeks ago

πŸ“ 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, you can automatically collect the following proof types:

GitLab proof types and fields

Proof type

Fields

Testable

Branch Protection

Branch Pattern, Applied branches, Branch Protection Enabled, Allowed to Merge, Allowed to Push, Allow force push, Require approval

Yes

Commits

Commit SHA, Author, Message, Date

Yes

Members

Account, Email, Access granted, Access expires, Max Role

Yes

Merge Request Settings

<Approval Rules true or false>

<Approval Rules>

No

Merge Requests

Title, Merged At, Requested By, Approved By, Merged By

Yes


​

GitLab notes on proof types


❗ Important

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


  • Branch Protection (requires Maintainer or Owner role)

  • Commits (requires Reporter role or higher)

  • Members (requires Guest role or higher)

  • Merge Request Settings (requires Maintainer or Owner role)

  • Merge Requests (requires Reporter role or higher)

When configuring the Hypersync for GitLab , note the following:

  • The Branch field displays the first 50 branches until you begin typing the branch name. The list of branches is filtered and updated based on the text you enter in the Branch field.

  • The Project field displays up to 100 projects at a time. If the project you need doesn't display, begin typing the full name of the project in the Project field. The list of projects is filtered and updated based on the text you enter in the Project field.

  • The Project namespace field displays up to 1000 projects at a time. If the namespace you need doesn't display, begin typing the full name in the Project namespace field. The list of namespaces is filtered and updated based on the text you enter in the Project namespace field.

Additional documentation

Connecting to GitLab


πŸ“ 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.


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.


πŸ“ Note

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

Service

Current IP address

New IP address

Main app

4.154.201.6

4.155.77.155

Integrations

4.246.104.90

4.155.78.5

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


  • Hyperproof US IP addresses - 20.184.128.53, 52.9.169.38, 52.159.252.1


    πŸ“ Note

    IP address 52.9.169.38 will be deprecated and replaced with 52.159.252.1 in the future. To prevent connectivity issues, it is recommended that you include all three IP addresses in your allowlists.


  • Hyperproof EU IP addresses - 9.141.172.46, 4.185.45.100

  • Hyperproof Gov IP addresses - 4.154.201.6, 4.246.104.90

See Hyperproof instances for more information.

Did this answer your question?