IdentitiesOpenWatching
Identity
Every account, human or machine, and what it can reach.
- Sources
- Okta, Entra ID, Google Workspace
- First findings
- under 1 hour
- Fix
- one click or a ticket
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
Cybersecurity platform
See every exposure before an attacker does.
Palisade watches every identity, device and key your company runs on, finds what is exposed and closes it before it turns into a breach.
SOC 2 Type II · ISO 27001 · 1,400 security teams
Risk score7 open
01234567890123456789/100
Risk score 82. 7 openSample findings, demo data
Cybersecurity platform
See every exposure before an attacker does.
Palisade watches every identity, device and key your company runs on, finds what is exposed and closes it before it turns into a breach.
Risk score7 open
01234567890123456789/100
Risk score 82. 7 open- ·Waiting for the sweep
- ·Waiting for the sweep
- ·Waiting for the sweep
SOC 2 Type II · ISO 27001 · 1,400 security teams — Sample findings, demo data
Cybersecurity platform
See every exposure before an attacker does.
Palisade watches every identity, device and key your company runs on, finds what is exposed and closes it before it turns into a breach.
Risk score7 open
01234567890123456789/100
Risk score 82. 7 open- ·Waiting for the sweep
- ·Waiting for the sweep
- ·Waiting for the sweep
SOC 2 Type II · ISO 27001 · 1,400 security teams — Sample findings, demo data
Liveexposures closed today
18,402
Across every customer workspace, counted as each one is verified closed.
Trusted by 1,400 security teams
Read their stories- Northwind FreightVerified
- Lumen PayVerified
- Harbour & ValeVerified
- Calder StaffingVerified
- Osprey HealthVerified
- TessellateVerified
- Brightwater EnergyVerified
- Kestrel LabsVerified
Compliance
- SOC 2 Type II
- ISO 27001
- GDPR
- HIPAA
Liveexposures closed today
18,402
Across every customer workspace, counted as each one is verified closed.
Trusted by 1,400 security teams
Read their stories- Northwind FreightVerified
- Lumen PayVerified
- Harbour & ValeVerified
- Calder StaffingVerified
- Osprey HealthVerified
- TessellateVerified
- Brightwater EnergyVerified
- Kestrel LabsVerified
Compliance
- SOC 2 Type II
- ISO 27001
- GDPR
- HIPAA
Liveexposures closed today
18,402
Across every customer workspace, counted as each one is verified closed.
Trusted by 1,400 security teams
Read their stories- Northwind FreightVerified
- Lumen PayVerified
- Harbour & ValeVerified
- Calder StaffingVerified
- Osprey HealthVerified
- TessellateVerified
- Brightwater EnergyVerified
- Kestrel LabsVerified
Compliance
- SOC 2 Type II
- ISO 27001
- GDPR
- HIPAA
Live findings
Found at 09:41. Closed at 09:45.
Palisade does not hand you a list to work through. Each finding arrives with its owner, its fix and a clock, and most are closed before anyone opens a ticket.
- Median time to close: 4 min
- 92 % closed without a ticket
- Every fix is logged and reversible
LiveFindings · all workspaces
1 open5 Secured
TimeFindingKindState
- 09:41Stale admin accountLeft the company 212 days ago and is still a global adminIdentityHighsecured in 5 min
- 09:38Leaked API keyFound in a public repository six hours agoSecretCriticalsecured in 2 min
- 09:35Contractor · MFA offSigns in to production with a password onlyIdentityHighsecured in 4 min
- 09:32Laptop · 41 days unpatchedThree critical fixes are waiting to installEndpointMediumsecured in 6 min
- 09:29Shared admin passwordUsed by nine people and last changed in 2023IdentityHighsecured in 3 min
- 09:26Open RDP portPort 3389 answers to the whole internetNetworkCriticalsecured in 5 min
Sample findings, demo data
Live findings
Found at 09:41. Closed at 09:45.
Palisade does not hand you a list to work through. Each finding arrives with its owner, its fix and a clock, and most are closed before anyone opens a ticket.
- Median time to close: 4 min
- 92 % closed without a ticket
- Every fix is logged and reversible
LiveFindings · all workspaces
1 open3 Secured
TimeFindingKindState
- 09:41Stale admin accountLeft the company 212 days ago and is still a global adminIdentityHighsecured in 5 min
- 09:38Leaked API keyFound in a public repository six hours agoSecretCriticalsecured in 2 min
- 09:35Contractor · MFA offSigns in to production with a password onlyIdentityHighsecured in 4 min
- 09:32Laptop · 41 days unpatchedThree critical fixes are waiting to installEndpointMediumsecured in 6 min
Sample findings, demo data
Live findings
Found at 09:41. Closed at 09:45.
Palisade does not hand you a list to work through. Each finding arrives with its owner, its fix and a clock, and most are closed before anyone opens a ticket.
- Median time to close: 4 min
- 92 % closed without a ticket
- Every fix is logged and reversible
LiveFindings · all workspaces
1 open5 Secured
TimeFindingKindState
- 09:41Stale admin accountLeft the company 212 days ago and is still a global adminIdentityHighsecured in 5 min
- 09:38Leaked API keyFound in a public repository six hours agoSecretCriticalsecured in 2 min
- 09:35Contractor · MFA offSigns in to production with a password onlyIdentityHighsecured in 4 min
- 09:32Laptop · 41 days unpatchedThree critical fixes are waiting to installEndpointMediumsecured in 6 min
- 09:29Shared admin passwordUsed by nine people and last changed in 2023IdentityHighsecured in 3 min
- 09:26Open RDP portPort 3389 answers to the whole internetNetworkCriticalsecured in 5 min
Sample findings, demo data
Coverage
Four surfaces. One watch.
Every employee, contractor and service account, with what each can reach and when it was last used.
- Stale accounts
- MFA gaps
- Shared passwords
- Admin sprawl
Each device that touches company data, managed or not, with its patch level and lock state.
- Missing patches
- Disk encryption
- Screen lock
- Unknown devices
Buckets, databases, ports and roles across AWS, Azure and Google Cloud, checked against what should be public.
- Public storage
- Open ports
- Over-wide roles
- Idle resources
Keys, tokens and passwords in code, build logs and chat, matched to the system they unlock.
- Leaked keys
- Secrets in logs
- Risky dependencies
- Unsigned builds
IdentityHighContractor · MFA offIdentityHighStale admin accountIdentityMediumShared admin password
EndpointMediumLaptop · 41 days unpatchedEndpointLowBadge left on a desk
CloudCriticalPublic storage bucketNetworkCriticalOpen RDP portCloudMediumIdle database · no owner
SecretCriticalLeaked API keySecretHighPassword on the whiteboardSecretHighToken in a build logCoverage
Four surfaces. One watch.
- 12301 / 04
1,284 people and service accounts3 open
Identities
Every employee, contractor and service account, with what each can reach and when it was last used.
- 1Contractor · MFA offHigh
- 2Stale admin accountHigh
- 3Shared admin passwordMedium
- Stale accounts
- MFA gaps
- Shared passwords
- Admin sprawl
- 1202 / 04
2,031 laptops, phones and servers2 open
Devices
Each device that touches company data, managed or not, with its patch level and lock state.
- 1Laptop · 41 days unpatchedMedium
- 2Badge left on a deskLow
- Missing patches
- Disk encryption
- Screen lock
- Unknown devices
- 12303 / 04
3 clouds, 46 accounts3 open
Cloud
Buckets, databases, ports and roles across AWS, Azure and Google Cloud, checked against what should be public.
- 1Public storage bucketCritical
- 2Open RDP portCritical
- 3Idle database · no ownerMedium
- Public storage
- Open ports
- Over-wide roles
- Idle resources
- 12304 / 04
412 repositories3 open
Code & secrets
Keys, tokens and passwords in code, build logs and chat, matched to the system they unlock.
- 1Leaked API keyCritical
- 2Password on the whiteboardHigh
- 3Token in a build logHigh
- Leaked keys
- Secrets in logs
- Risky dependencies
- Unsigned builds
Coverage
Four surfaces. One watch.
- 12301 / 04
1,284 people and service accounts3 open
Identities
Every employee, contractor and service account, with what each can reach and when it was last used.
- 1Contractor · MFA offHigh
- 2Stale admin accountHigh
- 3Shared admin passwordMedium
- Stale accounts
- MFA gaps
- Shared passwords
- Admin sprawl
- 1202 / 04
2,031 laptops, phones and servers2 open
Devices
Each device that touches company data, managed or not, with its patch level and lock state.
- 1Laptop · 41 days unpatchedMedium
- 2Badge left on a deskLow
- Missing patches
- Disk encryption
- Screen lock
- Unknown devices
- 12303 / 04
3 clouds, 46 accounts3 open
Cloud
Buckets, databases, ports and roles across AWS, Azure and Google Cloud, checked against what should be public.
- 1Public storage bucketCritical
- 2Open RDP portCritical
- 3Idle database · no ownerMedium
- Public storage
- Open ports
- Over-wide roles
- Idle resources
- 12304 / 04
412 repositories3 open
Code & secrets
Keys, tokens and passwords in code, build logs and chat, matched to the system they unlock.
- 1Leaked API keyCritical
- 2Password on the whiteboardHigh
- 3Token in a build logHigh
- Leaked keys
- Secrets in logs
- Risky dependencies
- Unsigned builds
Products
Five products, one list of what is exposed.
Start with the surface that worries you most. Every product writes into the same findings list, so nothing has to be stitched together later.
2DevicesOpenWatching
Endpoint
Laptops, phones and servers that have fallen behind.
- Sources
- Jamf, Intune, agent
- Platforms
- macOS, Windows, Linux, iOS, Android
- Agent footprint
- 38 MB
CloudOpenWatching
Cloud
Buckets, ports and roles that answer to the whole internet.
- Sources
- AWS, Azure, Google Cloud
- Access
- read-only role
- Checks
- 640 and growing
Code & secretsOpenWatching
Secrets
Keys and tokens before they leave the building.
- Sources
- GitHub, GitLab, Slack, Jira
- Detectors
- 310 key types
- Median time to revoke
- 4 minutes
Detection & responseOpenWatching
Respond
One timeline from first signal to closed.
- Alerts
- Slack, PagerDuty, email
- Median time to contain
- 4 minutes
- Retention
- 13 months
Products
Five products, one list of what is exposed.
Start with the surface that worries you most. Every product writes into the same findings list, so nothing has to be stitched together later.
1IdentitiesOpenWatching
Identity
Every account, human or machine, and what it can reach.
- Sources
- Okta, Entra ID, Google Workspace
- First findings
- under 1 hour
- Fix
- one click or a ticket
- 2
DevicesOpenWatching
Endpoint
Laptops, phones and servers that have fallen behind.
- Sources
- Jamf, Intune, agent
- Platforms
- macOS, Windows, Linux, iOS, Android
- Agent footprint
- 38 MB
CloudOpenWatching
Cloud
Buckets, ports and roles that answer to the whole internet.
- Sources
- AWS, Azure, Google Cloud
- Access
- read-only role
- Checks
- 640 and growing
Code & secretsOpenWatching
Secrets
Keys and tokens before they leave the building.
- Sources
- GitHub, GitLab, Slack, Jira
- Detectors
- 310 key types
- Median time to revoke
- 4 minutes
Detection & responseOpenWatching
Respond
One timeline from first signal to closed.
- Alerts
- Slack, PagerDuty, email
- Median time to contain
- 4 minutes
- Retention
- 13 months
Products
Five products, one list of what is exposed.
Start with the surface that worries you most. Every product writes into the same findings list, so nothing has to be stitched together later.
- 1
IdentitiesOpenWatching
Identity
Every account, human or machine, and what it can reach.
- Sources
- Okta, Entra ID, Google Workspace
- First findings
- under 1 hour
- Fix
- one click or a ticket
- 2
DevicesOpenWatching
Endpoint
Laptops, phones and servers that have fallen behind.
- Sources
- Jamf, Intune, agent
- Platforms
- macOS, Windows, Linux, iOS, Android
- Agent footprint
- 38 MB
CloudOpenWatching
Cloud
Buckets, ports and roles that answer to the whole internet.
- Sources
- AWS, Azure, Google Cloud
- Access
- read-only role
- Checks
- 640 and growing
Code & secretsOpenWatching
Secrets
Keys and tokens before they leave the building.
- Sources
- GitHub, GitLab, Slack, Jira
- Detectors
- 310 key types
- Median time to revoke
- 4 minutes
Detection & responseOpenWatching
Respond
One timeline from first signal to closed.
- Alerts
- Slack, PagerDuty, email
- Median time to contain
- 4 minutes
- Retention
- 13 months
One incident, two endings
The same leaked key. Two very different endings.
A cloud key is pushed to a public repository on a Tuesday afternoon. What happens next depends on whether anyone is watching.
0days before anyone noticed
Without Palisade: Day 212. Found by a customer. Found on day 212
Without Palisade
Found on day 212- Day 0Key pushed to a public repoA deploy script with a live cloud key lands in a public repository.
- Day 3Copied by a scraperAutomated scanners pick the key up. Nobody is told.
- Day 41First quiet loginThe key is used from a new country to list storage buckets.
- Day 130Customer records copied1.2 million rows leave over nine nights.
- Day 212Found by a customerA customer reports their data for sale. The clock starts now.
With Palisade
Closed in 4 min- 0:00Key pushed to a public repo
- 0:40Finding opened
- 1:30Owner paged
- 3:10Key revoked
- 4:00Closed
One incident, two endings
The same leaked key. Two very different endings.
A cloud key is pushed to a public repository on a Tuesday afternoon. What happens next depends on whether anyone is watching.
0days before anyone noticed
Without Palisade: Day 212. Found by a customer. Found on day 212
Without Palisade
Found on day 212- Day 0Key pushed to a public repoA deploy script with a live cloud key lands in a public repository.
- Day 3Copied by a scraperAutomated scanners pick the key up. Nobody is told.
- Day 41First quiet loginThe key is used from a new country to list storage buckets.
- Day 130Customer records copied1.2 million rows leave over nine nights.
- Day 212Found by a customerA customer reports their data for sale. The clock starts now.
With Palisade
Closed in 4 min- 0:00Key pushed to a public repo
- 0:40Finding opened
- 1:30Owner paged
- 3:10Key revoked
- 4:00Closed
One incident, two endings
The same leaked key. Two very different endings.
A cloud key is pushed to a public repository on a Tuesday afternoon. What happens next depends on whether anyone is watching.
0days before anyone noticed
Without Palisade: Day 212. Found by a customer. Found on day 212
Without Palisade
Found on day 212- Day 0Key pushed to a public repoA deploy script with a live cloud key lands in a public repository.
- Day 3Copied by a scraperAutomated scanners pick the key up. Nobody is told.
- Day 41First quiet loginThe key is used from a new country to list storage buckets.
- Day 130Customer records copied1.2 million rows leave over nine nights.
- Day 212Found by a customerA customer reports their data for sale. The clock starts now.
With Palisade
Closed in 4 min- 0:00Key pushed to a public repo
- 0:40Finding opened
- 1:30Owner paged
- 3:10Key revoked
- 4:00Closed
Integrations
Connects to what you already run.
Read-only access, no agents to roll out for the first findings. Most teams connect their identity provider and one cloud account in the first hour.
0 / 12 connected· Read-only by default · no credentials stored
- IdentityOktaUsers, groups, admin roles and sign-in policyNot connected
- IdentityEntra IDDirectory roles, conditional access and guestsNot connected
- IdentityGoogle WorkspaceAccounts, super admins and third-party app grantsNot connected
- CloudAWSAccounts, IAM roles, storage and network rulesNot connected
- CloudAzureSubscriptions, role assignments and exposed servicesNot connected
- CloudGoogle CloudProjects, service accounts and public resourcesNot connected
- CodeGitHubSecret scanning on every push and pull requestNot connected
- CodeGitLabPipelines, tokens and repository visibilityNot connected
- DevicesJamfPatch level, encryption and screen lock on Apple devicesNot connected
- DevicesIntuneCompliance state for Windows and mobile devicesNot connected
- AlertsSlackFindings sent to the owner, fixes confirmed in threadNot connected
- TicketsJiraIssues opened with the fix and closed when it landsNot connected
Integrations
Connects to what you already run.
Read-only access, no agents to roll out for the first findings. Most teams connect their identity provider and one cloud account in the first hour.
0 / 12 connected· Read-only by default · no credentials stored
- IdentityOktaUsers, groups, admin roles and sign-in policyNot connected
- IdentityEntra IDDirectory roles, conditional access and guestsNot connected
- IdentityGoogle WorkspaceAccounts, super admins and third-party app grantsNot connected
- CloudAWSAccounts, IAM roles, storage and network rulesNot connected
- CloudAzureSubscriptions, role assignments and exposed servicesNot connected
- CloudGoogle CloudProjects, service accounts and public resourcesNot connected
- CodeGitHubSecret scanning on every push and pull requestNot connected
- CodeGitLabPipelines, tokens and repository visibilityNot connected
- DevicesJamfPatch level, encryption and screen lock on Apple devicesNot connected
- DevicesIntuneCompliance state for Windows and mobile devicesNot connected
- AlertsSlackFindings sent to the owner, fixes confirmed in threadNot connected
- TicketsJiraIssues opened with the fix and closed when it landsNot connected
Integrations
Connects to what you already run.
Read-only access, no agents to roll out for the first findings. Most teams connect their identity provider and one cloud account in the first hour.
0 / 12 connected· Read-only by default · no credentials stored
- IdentityOktaUsers, groups, admin roles and sign-in policyNot connected
- IdentityEntra IDDirectory roles, conditional access and guestsNot connected
- IdentityGoogle WorkspaceAccounts, super admins and third-party app grantsNot connected
- CloudAWSAccounts, IAM roles, storage and network rulesNot connected
- CloudAzureSubscriptions, role assignments and exposed servicesNot connected
- CloudGoogle CloudProjects, service accounts and public resourcesNot connected
- CodeGitHubSecret scanning on every push and pull requestNot connected
- CodeGitLabPipelines, tokens and repository visibilityNot connected
- DevicesJamfPatch level, encryption and screen lock on Apple devicesNot connected
- DevicesIntuneCompliance state for Windows and mobile devicesNot connected
- AlertsSlackFindings sent to the owner, fixes confirmed in threadNot connected
- TicketsJiraIssues opened with the fix and closed when it landsNot connected
In numbers
What gets measured gets closed.
Averages across every customer over the last twelve months. Your own numbers sit on the first screen of the product.
- Mean time to detect
- 4 min
- From the moment something is exposed to the moment its owner is told.
- Measuring
- Findings closed
- 1.28M
- Closed by the person who owns the asset, not parked in a queue.
- Measuring
- Coverage
- 99.2%
- Of identities, devices, cloud accounts and repositories under watch.
- Measuring
- Security teams
- 1,400
- From ten-person start-ups to regulated groups in 31 countries.
- Measuring
Figures are sample data for this template
In numbers
What gets measured gets closed.
Averages across every customer over the last twelve months. Your own numbers sit on the first screen of the product.
- Mean time to detect
- 4 min
- From the moment something is exposed to the moment its owner is told.
- Measuring
- Findings closed
- 1.28M
- Closed by the person who owns the asset, not parked in a queue.
- Measuring
- Coverage
- 99.2%
- Of identities, devices, cloud accounts and repositories under watch.
- Measuring
- Security teams
- 1,400
- From ten-person start-ups to regulated groups in 31 countries.
- Measuring
Figures are sample data for this template
In numbers
What gets measured gets closed.
Averages across every customer over the last twelve months. Your own numbers sit on the first screen of the product.
- Mean time to detect
- 4 min
- From the moment something is exposed to the moment its owner is told.
- Measuring
- Findings closed
- 1.28M
- Closed by the person who owns the asset, not parked in a queue.
- Measuring
- Coverage
- 99.2%
- Of identities, devices, cloud accounts and repositories under watch.
- Measuring
- Security teams
- 1,400
- From ten-person start-ups to regulated groups in 31 countries.
- Measuring
Figures are sample data for this template
Customers
Closed cases, in their own numbers.
Four teams, four different problems. Each one started with a sweep and a list they did not expect.
- Case 01 · StaffingCalder StaffingWe found 340 accounts that belonged to nobody.Imogen Hartley · Head of ITRead the story
- Case 02 · LogisticsNorthwind FreightPatch lag went from 41 days to three.Darius Okafor · Infrastructure LeadRead the story
- Case 03 · HospitalityHarbour & ValeAn open port, closed before breakfast.Sofia Marchetti · Group IT DirectorRead the story
- Case 04 · FintechLumen PaySOC 2 in eleven weeks, with a team of two.Tomás Reyes · CTORead the story
Closed340orphaned accounts closed in week one
Closed3days from patch release to installed
Closed4minutes from alert to contained
Closed11weeks to a clean SOC 2 Type II reportCustomers
Closed cases, in their own numbers.
Four teams, four different problems. Each one started with a sweep and a list they did not expect.
- Closed340orphaned accounts closed in week oneCase 01 · StaffingCalder StaffingWe found 340 accounts that belonged to nobody.Imogen Hartley · Head of ITRead the story
- Closed3days from patch release to installedCase 02 · LogisticsNorthwind FreightPatch lag went from 41 days to three.Darius Okafor · Infrastructure LeadRead the story
- Closed4minutes from alert to containedCase 03 · HospitalityHarbour & ValeAn open port, closed before breakfast.Sofia Marchetti · Group IT DirectorRead the story
- Closed11weeks to a clean SOC 2 Type II reportCase 04 · FintechLumen PaySOC 2 in eleven weeks, with a team of two.Tomás Reyes · CTORead the story
Customers
Closed cases, in their own numbers.
Four teams, four different problems. Each one started with a sweep and a list they did not expect.
- Closed340orphaned accounts closed in week oneCase 01 · StaffingCalder StaffingWe found 340 accounts that belonged to nobody.Imogen Hartley · Head of ITRead the story
- Closed3days from patch release to installedCase 02 · LogisticsNorthwind FreightPatch lag went from 41 days to three.Darius Okafor · Infrastructure LeadRead the story
- Closed4minutes from alert to containedCase 03 · HospitalityHarbour & ValeAn open port, closed before breakfast.Sofia Marchetti · Group IT DirectorRead the story
- Closed11weeks to a clean SOC 2 Type II reportCase 04 · FintechLumen PaySOC 2 in eleven weeks, with a team of two.Tomás Reyes · CTORead the story
Pricing
One price per seat. Nothing hidden.
Move the slider to your headcount. Every plan covers every identity and device those people use.
BillingTwo months free
Team
For companies getting their first clear picture.
$600per month
$5 per seat / month · billed yearly
- Identity and Endpoint
- Daily sweep
- Slack and email alerts
- 90 days of history
- Community support
Business
Most chosenFor teams that have to prove it to an auditor.
$1,080per month
$9 per seat / month · billed yearly
- Everything in Team
- Cloud and Secrets
- Continuous sweep
- Jira and PagerDuty
- SOC 2 and ISO 27001 evidence
- 13 months of history
Enterprise
For regulated companies with their own security team.
$1,800per month
$15 per seat / month · billed yearly
- Everything in Business
- Respond with custom playbooks
- Single sign-on and SCIM
- Private data region
- Named engineer and 1-hour response
More than 1,000 people, or a private data region? Talk to sales
Pricing
One price per seat. Nothing hidden.
Move the slider to your headcount. Every plan covers every identity and device those people use.
BillingTwo months free
Team
For companies getting their first clear picture.
$600per month
$5 per seat / month · billed yearly
- Identity and Endpoint
- Daily sweep
- Slack and email alerts
- 90 days of history
- Community support
Business
Most chosenFor teams that have to prove it to an auditor.
$1,080per month
$9 per seat / month · billed yearly
- Everything in Team
- Cloud and Secrets
- Continuous sweep
- Jira and PagerDuty
- SOC 2 and ISO 27001 evidence
- 13 months of history
Enterprise
For regulated companies with their own security team.
$1,800per month
$15 per seat / month · billed yearly
- Everything in Business
- Respond with custom playbooks
- Single sign-on and SCIM
- Private data region
- Named engineer and 1-hour response
More than 1,000 people, or a private data region? Talk to sales
Pricing
One price per seat. Nothing hidden.
Move the slider to your headcount. Every plan covers every identity and device those people use.
BillingTwo months free
Team
For companies getting their first clear picture.
$600per month
$5 per seat / month · billed yearly
- Identity and Endpoint
- Daily sweep
- Slack and email alerts
- 90 days of history
- Community support
Business
Most chosenFor teams that have to prove it to an auditor.
$1,080per month
$9 per seat / month · billed yearly
- Everything in Team
- Cloud and Secrets
- Continuous sweep
- Jira and PagerDuty
- SOC 2 and ISO 27001 evidence
- 13 months of history
Enterprise
For regulated companies with their own security team.
$1,800per month
$15 per seat / month · billed yearly
- Everything in Business
- Respond with custom playbooks
- Single sign-on and SCIM
- Private data region
- Named engineer and 1-hour response
More than 1,000 people, or a private data region? Talk to sales
What teams say
The first sweep usually pays for the year.
Security and IT leads on what turned up in week one, and what they stopped worrying about after.
01 of 05
Closed01
“The first sweep found a global admin who had left the company seven months earlier. That one finding paid for the year.”
Closed02
“It ranks by what an attacker would do next. My team stopped arguing about severity and started closing things.”
Closed03
“Our auditor logged in, read the evidence and left. No screenshots, no spreadsheet, no three-week scramble.”
Closed04
“A key hit a public repository at 2 am. Palisade had it revoked before I had found my glasses.”
Closed05
“Depot managers fix their own devices now, because the message tells them exactly what to press.”
What teams say
The first sweep usually pays for the year.
Security and IT leads on what turned up in week one, and what they stopped worrying about after.
01 of 05
Closed01
“The first sweep found a global admin who had left the company seven months earlier. That one finding paid for the year.”
Closed02
“It ranks by what an attacker would do next. My team stopped arguing about severity and started closing things.”
Closed03
“Our auditor logged in, read the evidence and left. No screenshots, no spreadsheet, no three-week scramble.”
Closed04
“A key hit a public repository at 2 am. Palisade had it revoked before I had found my glasses.”
Closed05
“Depot managers fix their own devices now, because the message tells them exactly what to press.”
What teams say
The first sweep usually pays for the year.
Security and IT leads on what turned up in week one, and what they stopped worrying about after.
01 of 05
Closed01
“The first sweep found a global admin who had left the company seven months earlier. That one finding paid for the year.”
Closed02
“It ranks by what an attacker would do next. My team stopped arguing about severity and started closing things.”
Closed03
“Our auditor logged in, read the evidence and left. No screenshots, no spreadsheet, no three-week scramble.”
Closed04
“A key hit a public repository at 2 am. Palisade had it revoked before I had found my glasses.”
Closed05
“Depot managers fix their own devices now, because the message tells them exactly what to press.”
Questions
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Answered.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Questions
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Answered.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Questions
Asked before every rollout.
What security and IT teams want to know before they connect the first source.
Answered.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
Open.
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.
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