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
Book a demo
See your own findings.
Thirty minutes, your own environment, no slides. Tell us what to cover.
SOC 2 Type II · ISO 27001 · 1,400 security teams
- 1Stale admin accountLeft the company 212 days ago and is still a global adminHigh
- 2Leaked API keyFound in a public repository six hours agoCritical
- 3Contractor · MFA offSigns in to production with a password onlyHigh
- 4Laptop · 41 days unpatchedThree critical fixes are waiting to installMedium
Book a demo
See your own findings.
Thirty minutes, your own environment, no slides. Tell us what to cover.
SOC 2 Type II · ISO 27001 · 1,400 security teams
- 1Stale admin accountLeft the company 212 days ago and is still a global adminHigh
- 2Leaked API keyFound in a public repository six hours agoCritical
- 3Contractor · MFA offSigns in to production with a password onlyHigh
Book a demo
See your own findings.
Thirty minutes, your own environment, no slides. Tell us what to cover.
SOC 2 Type II · ISO 27001 · 1,400 security teams
- 1Stale admin accountLeft the company 212 days ago and is still a global adminHigh
- 2Leaked API keyFound in a public repository six hours agoCritical
- 3Contractor · MFA offSigns in to production with a password onlyHigh
- 4Laptop · 41 days unpatchedThree critical fixes are waiting to installMedium
The request
Tell us what to cover.
Tell us who you are and what to look at. No slides: the demo is a sweep of your own domain.
- 1
We read it the same day
A security engineer, not a sales queue.
- 2
30 minutes on a call
We connect one source read-only while you watch.
- 3
Your own findings
You leave with a ranked list for your domain, yours to keep.
- Office
- 14 Curtain Road, London EC2A 3NH
The request
Tell us what to cover.
Tell us who you are and what to look at. No slides: the demo is a sweep of your own domain.
- 1
We read it the same day
A security engineer, not a sales queue.
- 2
30 minutes on a call
We connect one source read-only while you watch.
- 3
Your own findings
You leave with a ranked list for your domain, yours to keep.
- Office
- 14 Curtain Road, London EC2A 3NH
The request
Tell us what to cover.
Tell us who you are and what to look at. No slides: the demo is a sweep of your own domain.
- 1
We read it the same day
A security engineer, not a sales queue.
- 2
30 minutes on a call
We connect one source read-only while you watch.
- 3
Your own findings
You leave with a ranked list for your domain, yours to keep.
- Office
- 14 Curtain Road, London EC2A 3NH
Before the call
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Connect your identity provider and most teams see their first findings in under an hour. Cloud accounts and device managers each add a few minutes. Nothing is installed on a server to get started.
Read-only access to every source. Fixes that change something, such as revoking a key or disabling an account, use a separate write permission that you grant per action and can remove at any time.
No. Palisade finds what is exposed before an attack and reads from the tools you already run. It sends findings to your SIEM and takes alerts from it, so the two work as one queue.
Each open finding carries a weight from its severity and from what it can reach. The score is the weighted share of your surface that is exposed, from 0 to 100. Closing a critical finding moves it more than closing ten low ones.
In the region you pick at sign-up: the EU, the UK or the US. Enterprise plans can use a private region. Data is encrypted in transit and at rest, and we keep findings, never the content of your files or mail.
Yes. Every finding has an owner taken from your directory or device manager. They get a message in Slack or email with the exact step, and the finding closes itself when the fix lands.
SOC 2, ISO 27001, GDPR and HIPAA out of the box, with each control mapped to live checks. You can add your own controls and map them to the same evidence.
One person in your directory. Service accounts, devices and cloud resources are not counted, however many you have. Yearly billing takes two months off the price.
Before the call
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Connect your identity provider and most teams see their first findings in under an hour. Cloud accounts and device managers each add a few minutes. Nothing is installed on a server to get started.
Read-only access to every source. Fixes that change something, such as revoking a key or disabling an account, use a separate write permission that you grant per action and can remove at any time.
No. Palisade finds what is exposed before an attack and reads from the tools you already run. It sends findings to your SIEM and takes alerts from it, so the two work as one queue.
Each open finding carries a weight from its severity and from what it can reach. The score is the weighted share of your surface that is exposed, from 0 to 100. Closing a critical finding moves it more than closing ten low ones.
In the region you pick at sign-up: the EU, the UK or the US. Enterprise plans can use a private region. Data is encrypted in transit and at rest, and we keep findings, never the content of your files or mail.
Yes. Every finding has an owner taken from your directory or device manager. They get a message in Slack or email with the exact step, and the finding closes itself when the fix lands.
SOC 2, ISO 27001, GDPR and HIPAA out of the box, with each control mapped to live checks. You can add your own controls and map them to the same evidence.
One person in your directory. Service accounts, devices and cloud resources are not counted, however many you have. Yearly billing takes two months off the price.
Before the call
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Connect your identity provider and most teams see their first findings in under an hour. Cloud accounts and device managers each add a few minutes. Nothing is installed on a server to get started.
Read-only access to every source. Fixes that change something, such as revoking a key or disabling an account, use a separate write permission that you grant per action and can remove at any time.
No. Palisade finds what is exposed before an attack and reads from the tools you already run. It sends findings to your SIEM and takes alerts from it, so the two work as one queue.
Each open finding carries a weight from its severity and from what it can reach. The score is the weighted share of your surface that is exposed, from 0 to 100. Closing a critical finding moves it more than closing ten low ones.
In the region you pick at sign-up: the EU, the UK or the US. Enterprise plans can use a private region. Data is encrypted in transit and at rest, and we keep findings, never the content of your files or mail.
Yes. Every finding has an owner taken from your directory or device manager. They get a message in Slack or email with the exact step, and the finding closes itself when the fix lands.
SOC 2, ISO 27001, GDPR and HIPAA out of the box, with each control mapped to live checks. You can add your own controls and map them to the same evidence.
One person in your directory. Service accounts, devices and cloud resources are not counted, however many you have. Yearly billing takes two months off the price.