Skip to main content

Understand the monitored perimeter

Overview#

Your perimeter page has two main objectives:

  1. Identify which of your sources are at risk
  2. Ensure that your entire perimeter is well protected by GitGuardian

Perimeter page

In the bottom of the right-hand side panel, the scope section gives you a quick summary of the different integrations (VCS types) that have been integrated with GitGuardian, alongside with a breakdown of sources per integration.

Perimeter scope

Differences between historical scanning and real-time protection#

Real-time monitoring#

The first protection and the most effective one for secrets remediation is the real-time monitoring. Within your list of sources, under the protection column, the blue shield icon indicates that a given source is being monitored in real-time.

real-time protection

As you may have read in our How GitGuardian works section, real-time monitoring means that every single push event (and its commits) are scanned for secrets as soon as they arrive on your VCS server (post-receive hooks).

We then alert you instantly, which will save you time in the remediation process. Indeed, the longer a secret is exposed, the harder the remediation gets.

On the right-hand side panel, we indicate the percentage of sources covered, based on the number of sources you integrated with GitGuardian. Note that some sources may not be eligible to being monitored because of plan restriction.

real-time protection coverage

Historical scanning#

The second type of protection offered is the ability to scan the commit history of all the sources you integrated with GitGuardian.

Size limitations apply to historical scans, depending on your plan:

  • Free: you can scan sources up to 1GB,
  • Business and trial: you can scan sources up to 12 GB.

How can I add new sources to my protected perimeter?#

GitHub#

Go to integration guide.

GitHub Enterprise#

Go to integration guide.

GitLab#

Go to integration guide.

Bitbucket server/data center#

Go to integration guide.

Troubleshooting connectivity problems#

Most often, connectivity problems arise because a firewall, proxy server, corporate network, or other network is configured in a way that blocks GitGuardian.

In case you need to authorize incoming/outgoing connections to/from the SAAS application, here are the main information you need to know.

Allowing GitGuardian's IP addresses#

GitGuardian serves the application from the following IP addresses:

  • 44.231.207.147/32
  • 44.224.13.10/32
  • 35.163.105.95/32
  • 54.212.233.107/32
  • 35.83.131.170/32
  • 35.161.89.114/32

These IP addresses are used for:

  • VCS integrations (eg: GitHub, GitLab)
  • Alerting integrations (eg: Slack)

Allowing GitGuardian's domains#

The following domains are used to expose the application:

  • dashboard.gitguardian.com
  • hook.gitguardian.com
  • api.gitguardian.com

Note: HTTP is only used to redirect to HTTPS.