CloudDefense.AI
  • Connect Repositories
    • Scan a Github/Gitlab
    • Scan an Azure DevOps repository
    • Scan a Bitbucket repository
  • Scans
    • Written code Scan (SAST)
    • Open Source Libraries Scan (SCA)
    • Secrets Scan
    • DAST Scans
    • API Scan from CloudDefense UI
  • CI/CD
    • GitHub Enterprise Actions
    • Methods for CI/CD integration with CLI
    • CI/CD Policies
    • Jenkins integration with cdefence
  • Integration
    • IaC on GCR Scan
    • IaC on Amazon ECR Scan
    • IaC on Docker Hub Scan
    • Integration with ServiceNow
    • Integration with Jira
    • SSO Okta App Integration
    • Set up CloudDefense Single Sign-On (SSO)
    • SIEM
      • Azure Sentinel
      • IBM Qradar
      • Micro Focus ArcSight Logger
  • Features
    • Sharing Integration
    • How to Enable Multi-Factor Authentication
    • AUTO PR
    • Remediation using SAST Recommendations
    • Global Allowed List and Local allowed list - Documentation
    • File Exclude
  • CloudDefense CLI
    • Cloud Defense CLI
  • On-Prem Installation
    • Install CloudDefense Helm on a Kubernetes Cluster
    • Install CloudDefense suite on a Kubernetes cluster
  • Others
    • Team Management
    • User Management
    • App Management
    • LogIn/Signup process
Powered by GitBook
On this page
  • Prerequisites
  • 1. Github/Gitlab Cloud
  • 2. Github/Gitlab Enterprise
  1. Connect Repositories

Scan a Github/Gitlab

NextScan an Azure DevOps repository

Last updated 2 years ago

Prerequisites

  • You must have a valid Github/Gitlab/Azure account

1. Github/Gitlab Cloud

Step 1: Sign in or Integrate Github/Gitlab

Sign in with Github or Gitlab (or integrate them from the integration page if you are signing up by email or with any other IDP)

Step 2: Scan Repositories

If you are logged in with a GitHub/Gitlab account or integrate the accounts, it will redirect you to the Github/Gitlab Scan Page where you will see all of your repositories (both public and private). You can select any repository (or multiple) and run the scans.

Step 3: Scan any public repository.

You can scan any public Github or Gitlab repository using the input form (check below). Scan your public GitLab repositories in the marked option

2. Github/Gitlab Enterprise

Step 1: Contact CD Support to enable

By default, the option for Github/Gitlab enterprise is disabled. You need to contact CloudDefense support at support@clouddefense.ai to enable the option. Please email us with these details:

  • Organization Name

  • Account email address

How to Get GitHub Enterprise link and Generate Access Token:

  1. Enterprise Token:

2. Access token

After creating an access token, the user must copy and paste it into the enterprise access token field.

Step 2: Configure

Once your account is ready for integration, you will see the options to provide details as below:

  1. Enterprise Link

  2. Enterprise Access Token of Github and Gitlab

How to Get Gitlab Enterprise link and Generate Access Token:

  1. Enterprise link :

2. Access token:

To integrate Gitlab enterprise users need access tokens. To find access token user need to go from profile dropdown Preference > Access token

Once you provide the required information, click configure.

To integrate GitHub enterprise users must have an enterprise account. If the user have an enterprise account user can see all enterprises here

Clicking on the enterprise user will get an enterprise link. If the user doesn't have a GitHub enterprise, the user can easily open an enterprise account from the link below.

To integrate GitHub enterprise users need access tokens. To find the access token user need to go to Setting > tokens Here is the URL :

To integrate Gitlab enterprise users must have an enterprise account. If the user have an enterprise account user can see all enterprises/groups here

Clicking on the enterprise user will get an enterprise link. If the user doesn't have any Gitlab enterprise, the user can easily open an enterprise account from the link below.

Here is the URL : After creating the access token users need to copy that and paste it to the enterprise access token field.

https://github.com/settings/enterprises
https://github.com/enterprise
https://github.com/settings/tokens
https://gitlab.com/dashboard/groups
https://github.com/enterprise
https://gitlab.com/-/profile/personal_access_tokens