Connect your code to Cysmiq

Use this article when you are ready to connect GitHub, GitLab, or Bitbucket so Cysmiq can discover repositories and start scanning.

What to check first

• Open Settings, then Integrations.

• Choose the version control provider you want to connect.

• Confirm you have the right admin permissions or access token before starting setup.

Provider requirements

• GitHub Cloud: organization owner access or admin access for the account you plan to connect.

• GitHub Enterprise Server: admin access to create and install a GitHub App on your Enterprise Server instance.

• GitLab: group owner access and a personal access token with the api scope.

• Bitbucket Cloud: workspace admin access and a workspace access token with repository, pull request, webhook, project, and account read/write scopes.

• Bitbucket Data Center: a reachable server URL and a personal access token that can read the projects and repositories you want to scan. The token and its owner need Repository admin permission to create repository webhooks.

Connect Bitbucket Data Center

Select Setup for Bitbucket Data Center. Enter the Bitbucket Data Center Host, the token owner's Username for Git clone, and the Personal access token, then select Save Changes. The username field is required by the setup form. OAuth client credentials are optional for social login and account linking.

Confirm the connection shows Active, then check Assets and Scans. If a webhook warning appears, check both the token's Repository admin permission and its owner's access to the repository. For token creation and permission options, see Atlassian's HTTP access token documentation. Follow Connect a VCS for the complete setup and verification steps.

After connection

• Cysmiq syncs the connected organizations, groups, workspaces, and repositories.

• Cysmiq queues scans automatically for repositories it can access.

• You can verify the connection from Integrations, Assets, and Scans.

Which IP addresses should we allow for Cysmiq Cloud?

If your VCS restricts access by IP address, add 3.43.74.176/28 to its allowlist. This is the source IPv4 range for Cysmiq Cloud connections to your provider. See Cloud IP allowlisting for the address range and provider configuration links.

GitHub returns a 403 about an IP allowlist

GitHub can block repository discovery, branch fetches, and scans even when the authorization credentials are valid. Ask an organization owner to add the CIDR as an enabled entry in the applicable organization or enterprise allowlist. See GitHub organization IP allowlists. Allow a few minutes for the change to take effect, then retry the operation that failed.

For a GitHub App you manage, see Managing allowed IP addresses for a GitHub App. For self-hosted Cysmiq, allow the public outbound IP addresses of your own installation.

Canonical docs

For the maintained walkthrough, see Connect a VCS, Cloud IP allowlisting, and Integrations.

Contact support if

• You cannot authorize or save the integration.

• The connected organization, group, workspace, or repositories do not appear in Cysmiq.

• Scans do not appear after the integration is connected.

• GitHub still reports an IP allowlist error after the range is enabled.