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
GitHub + Palisade
Secret scanning on every push and pull request.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Live keys in historyOpen
- 2Keys in new pull requestsOpen
- 3Public repositories that should be privateOpen
- 4Deploy keys with write accessOpen
What Palisade reads
The Palisade app checks every push and pull request for 310 kinds of key and sweeps the full history once. A found key is revoked at the provider from the same comment.
Set up in minutes
- 1Step 1. Install the GitHub app on the organisation
- 2Step 2. Choose all or selected repositories
- 3Step 3. Turn on the pull request check
- 4Step 4. Let the history sweep finish
What it feeds
- Live keys in history
- Keys in new pull requests
- Public repositories that should be private
- Deploy keys with write access
Code
GitHub + Palisade
Secret scanning on every push and pull request.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Live keys in historyOpen
- 2Keys in new pull requestsOpen
- 3Public repositories that should be privateOpen
- 4Deploy keys with write accessOpen
What Palisade reads
The Palisade app checks every push and pull request for 310 kinds of key and sweeps the full history once. A found key is revoked at the provider from the same comment.
Set up in minutes
- 1Step 1. Install the GitHub app on the organisation
- 2Step 2. Choose all or selected repositories
- 3Step 3. Turn on the pull request check
- 4Step 4. Let the history sweep finish
What it feeds
- Live keys in history
- Keys in new pull requests
- Public repositories that should be private
- Deploy keys with write access
Code
GitHub + Palisade
Secret scanning on every push and pull request.
Read-only role · no credentials stored · remove it at any time
Not connected· Read-only
First findings 0 of 4
- 1Live keys in historyOpen
- 2Keys in new pull requestsOpen
- 3Public repositories that should be privateOpen
- 4Deploy keys with write accessOpen
What Palisade reads
The Palisade app checks every push and pull request for 310 kinds of key and sweeps the full history once. A found key is revoked at the provider from the same comment.
Set up in minutes
- 1Step 1. Install the GitHub app on the organisation
- 2Step 2. Choose all or selected repositories
- 3Step 3. Turn on the pull request check
- 4Step 4. Let the history sweep finish
What it feeds
- Live keys in history
- Keys in new pull requests
- Public repositories that should be private
- Deploy keys with write access
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