SOC 2 Type II · ISO 27001 · 1,400 security teams
SOC 2 Type II · ISO 27001 · 1,400 security teams
Palisade
Palisade
Risk score82/100open
Next page/
Home
Code
GitLab + Palisade
Pipelines, tokens and repository visibility.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Keys in merge requestsOpen
- 2Long-lived access tokensOpen
- 3Public projectsOpen
- 4Runners shared across groupsOpen
What Palisade reads
Pipelines, tokens and repository visibility are read through a group access token. Checks appear on the merge request, where the engineer already is.
Set up in minutes
- 1Step 1. Create a group access token with read scopes
- 2Step 2. Add the pipeline check
- 3Step 3. Choose protected branches
- 4Step 4. Review token age
What it feeds
- Keys in merge requests
- Long-lived access tokens
- Public projects
- Runners shared across groups
Code
GitLab + Palisade
Pipelines, tokens and repository visibility.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Keys in merge requestsOpen
- 2Long-lived access tokensOpen
- 3Public projectsOpen
- 4Runners shared across groupsOpen
What Palisade reads
Pipelines, tokens and repository visibility are read through a group access token. Checks appear on the merge request, where the engineer already is.
Set up in minutes
- 1Step 1. Create a group access token with read scopes
- 2Step 2. Add the pipeline check
- 3Step 3. Choose protected branches
- 4Step 4. Review token age
What it feeds
- Keys in merge requests
- Long-lived access tokens
- Public projects
- Runners shared across groups
Code
GitLab + Palisade
Pipelines, tokens and repository visibility.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Keys in merge requestsOpen
- 2Long-lived access tokensOpen
- 3Public projectsOpen
- 4Runners shared across groupsOpen
What Palisade reads
Pipelines, tokens and repository visibility are read through a group access token. Checks appear on the merge request, where the engineer already is.
Set up in minutes
- 1Step 1. Create a group access token with read scopes
- 2Step 2. Add the pipeline check
- 3Step 3. Choose protected branches
- 4Step 4. Review token age
What it feeds
- Keys in merge requests
- Long-lived access tokens
- Public projects
- Runners shared across groups
Start here
Run the sweep on your domain.
Tell us where to look. We set up a read-only connection with you on a short call, and you see your own findings the same day.
We will sweep
- Identity providerNot connected
- Cloud accountsNot connected
- DevicesNot connected
- Code repositoriesNot connected
Start here
Run the sweep on your domain.
Tell us where to look. We set up a read-only connection with you on a short call, and you see your own findings the same day.
We will sweep
- Identity providerNot connected
- Cloud accountsNot connected
- DevicesNot connected
- Code repositoriesNot connected
Start here
Run the sweep on your domain.
Tell us where to look. We set up a read-only connection with you on a short call, and you see your own findings the same day.
We will sweep
- Identity providerNot connected
- Cloud accountsNot connected
- DevicesNot connected
- Code repositoriesNot connected