Check Point SASE

Name: Check Point SASE
Brand: Check Point Software Technologies
Rating: 4.5 (624 reviews)

Leader

Customers rely on Lakera for real-time security that doesn’t slow down their GenAI applications.

Est 1993|Valuation $13.7B|Raised $1.8B

LinkedIn 11K|Website|Web traffic 2.0M|FTEs 6,825|HQ San Francisco, CA

MarketsFirewalls Security Service Edge (SSE)

Published Oct 15, 2026

01Common complaints

- If the organization requires a very simple deployment with minimal security engineering: multiple reviews cite setup and policy configuration complexity. - If pricing transparency is a strict procurement requirement: Check Point SASE procurement appears to be sales-led and negotiated. - If the organization cannot tolerate cloud service performance variability: community discussions about degraded performance indicate the need to validate regional gateway performance and service status history during a PoC. - If the organization prefers best-of-breed single-category components over a consolidated suite: some buyers choose specialized SWG, CASB, or ZTNA products instead of a unified SASE offering.

Deal disqualifiers (poor fit)

Very small teams seeking minimal policy work and a plug-and-play solution
Organizations requiring fully transparent, self-serve pricing and instant procurement
Environments with extremely complex application segmentation requirements but limited engineering bandwidth

Known limitations from customer feedback (observed)

Complex initial configuration and policy design requirements
Reporting and dashboard usability friction
Edition and feature discoverability or entitlement confusion (e.g., Essentials vs Essentials+)

Roadmap / future features

Public roadmap details and delivery dates were not consistently available in the sources reviewed. Procurement should ask for roadmap commitments during contract negotiations where relevant.

Scale limits

No public hard limits for users, tunnels, connectors, or log retention were found in the reviewed sources. Request documented scale and performance limits during technical evaluation.

Security / compliance gaps

While vendor materials reference SOC 2 Type 2 and ISO 27001, buyers should verify:
- That the SOC 2 report scope includes the specific SASE services required
- That data residency and contractual controls meet the organization’s requirements
- Availability of security artifacts such as SOC 2 reports under NDA and pen-test summaries

02Why they buy

Evidence-supported differentiators (partially validated)

Compliance posture references: vendor materials reference SOC 2 Type 2 and ISO 27001 certificates for relevant services.
Consolidation: multiple reviewers and community comments reference value from having policies and features consolidated in a single vendor offering.

Differentiation that requires validation

Vendor performance and deployment speed claims (for example, claims about significant speed improvements) are marketing statements that should be substantiated via PoC and third-party benchmarks.

Where competitors have advantages

Zscaler: market maturity and enterprise referenceability in the SSE space.
Palo Alto: integration with Palo Alto product families for organizations that have an existing investment in that stack.

Why customers chose it (recurring themes)

Recurring selection drivers across reviews and community discussion include:

Consolidation of tools and policies
Check Point brand and threat prevention experience
Vendor messaging around performance and backbone architecture

03Field reports

Review-platform sentiment (G2)

G2 lists Check Point SASE with a high aggregate score across available reviews (e.g., very favorable with a moderate review footprint), and the listing shows an implementation timeframe reported by users. Positive example (G2, mid-market user): > “A more secure experience when connecting users and applications… everything on a single platform… real-time protection without impacting performance.” Negative / critical examples (G2): > “Initial setup and policy configuration can be complex.” > “Report generation could also be more intuitive…” Interpretation: review-platform feedback aligns with a common SASE pattern — buyers value consolidation and security outcomes, but deployment and reporting friction are recurring notes.

Gartner Peer Insights (access notes)

Gartner Peer Insights has an entry for Check Point Harmony SASE in the Security Service Edge market. Access to full reviews and gated content may require a Gartner account; organizations with such access should extract both positive and negative reviews for a fuller perspective.

Community / social sentiment (Reddit)

Reddit discussions include operational notes, licensing confusion, and reliability questions. Outage / degraded performance discussion: - Threads reference an outage or degraded performance event in the context of US data residency. Packaging / licensing confusion (MSSP context): - Community threads discuss Essentials vs Essentials+ and report difficulty locating expected features in the SASE console, suggesting possible packaging ambiguity or entitlement/configuration gaps. Competitive shortlisting: - Networking-focused discussions show Check Point SASE included alongside Prisma and Cato when organizations discuss replacing separate SD-WAN and security stacks.

Why some customers hesitate or leave (recurring themes)

Recurring concerns include:

Setup and policy configuration complexity during initial deployment
Reporting and dashboard usability issues
Edition clarity and entitlement concerns
Reliability concerns based on isolated outage or degraded performance discussions

Vendor collateral and success claims

Vendor collateral emphasizes performance and compliance and includes marketing claims of substantially faster secure internet access and very rapid deployment timeframes cited in marketing. These are vendor-asserted claims and should be validated. Critical evaluation: - Vendor performance and deployment claims typically depend on baseline comparisons, network geography, last-mile conditions, and the specific scope of what is included in "deployment" (IdP integration, application onboarding, segmentation design, logging/SIEM integration, and endpoint rollout). - No independent, methodologically transparent benchmark supporting the vendor's pronounced performance claim was identified in the reviewed sources.

What procurement should validate in a PoC (to assess ROI claims)

Before/after network performance: page-load times, tunnel throughput, packet loss, latency by region
Administrative workflows: policy change workflow timing and admin UX comparisons
Reporting completeness: required reports and export capabilities to SIEMs
Incident handling drills: exercise malware/phishing/DLP scenarios and measure mean time to detect and investigate

04Best fit

Company size

Likely fit: mid-market to enterprise organizations with distributed users and multiple sites (typically hundreds to thousands of employees).
Also relevant: MSPs/MSSPs serving SMB-to-mid-market customers, though edition entitlements and console feature visibility should be verified.

Industries

Cross-industry applicability; vendor materials reference regulated sectors (e.g., government, education) and compliance alignment as part of the value proposition.

Roles / personas

Decision makers: CISO, Head of Network/Security Engineering, IT Director
Implementers: network engineers, security engineers, identity engineers, endpoint management teams
Operational users: helpdesk/service desk and SOC analysts

Pain points addressed

VPN complexity and security gaps
Fragmented SWG / ZTNA / CASB tooling
Need for consistent policy enforcement for remote users

Qualification criteria (good fit)

Willingness to conduct a structured PoC and invest in policy design and integration
Need for SOC 2 / ISO-aligned vendor posture
Desire to consolidate security tooling within the Check Point ecosystem

05The pitch

What the product does (core value proposition)

Check Point SASE (marketed as Harmony SASE, and integrated with the Perimeter 81 platform) is a cloud-delivered Secure Access Service Edge (SASE) / Security Service Edge (SSE) offering that consolidates secure internet access, zero-trust private access (ZTNA), and related security controls into a single service for remote users, branch connectivity, and SaaS access. Vendor positioning highlights a single-vendor approach, threat prevention capabilities, and a private backbone with local/on-device inspection intended to affect user experience and performance. Key solution components commonly presented under the suite include: - Internet access / secure web gateway (web/DNS filtering, malware protection, etc.) - Private access (ZTNA) with identity-centric policy enforcement - SaaS security (visibility / shadow SaaS discovery, monitoring integrations) - Supporting features such as device posture, agent-based connectivity, and management dashboards (These capabilities are described across Check Point SASE web properties and vendor materials.)

Target market and positioning

- Primary target: mid-market to enterprise organizations modernizing remote access and branch security, especially those seeking vendor consolidation within the broader Check Point ecosystem. - Secondary target: MSP/MSSP-managed deployments (some materials and community discussion suggest MSSP bundles/editions and feature packaging can be confusing in practice). - Positioning themes reported by the vendor include speed, simplified onboarding, consolidated features, and prevention-focused security.

Get a comprehensive analysis of Check Point SASE including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

If the organization requires a very simple deployment with minimal security engineering: multiple reviews cite setup and policy configuration complexity.
If pricing transparency is a strict procurement requirement: Check Point SASE procurement appears to be sales-led and negotiated.
If the organization cannot tolerate cloud service performance variability: community discussions about degraded performance indicate the need to validate regional gateway performance and service status history during a PoC.
If the organization prefers best-of-breed single-category components over a consolidated suite: some buyers choose specialized SWG, CASB, or ZTNA products instead of a unified SASE offering.

Deal disqualifiers (poor fit)

Very small teams seeking minimal policy work and a plug-and-play solution
Organizations requiring fully transparent, self-serve pricing and instant procurement
Environments with extremely complex application segmentation requirements but limited engineering bandwidth

Known limitations from customer feedback (observed)

Complex initial configuration and policy design requirements
Reporting and dashboard usability friction
Edition and feature discoverability or entitlement confusion (e.g., Essentials vs Essentials+)

Roadmap / future features

Public roadmap details and delivery dates were not consistently available in the sources reviewed. Procurement should ask for roadmap commitments during contract negotiations where relevant.

Scale limits

No public hard limits for users, tunnels, connectors, or log retention were found in the reviewed sources. Request documented scale and performance limits during technical evaluation.

Security / compliance gaps

While vendor materials reference SOC 2 Type 2 and ISO 27001, buyers should verify:
- That the SOC 2 report scope includes the specific SASE services required
- That data residency and contractual controls meet the organization’s requirements
- Availability of security artifacts such as SOC 2 reports under NDA and pen-test summaries

02Why they buy

Evidence-supported differentiators (partially validated)

Compliance posture references: vendor materials reference SOC 2 Type 2 and ISO 27001 certificates for relevant services.
Consolidation: multiple reviewers and community comments reference value from having policies and features consolidated in a single vendor offering.

Differentiation that requires validation

Vendor performance and deployment speed claims (for example, claims about significant speed improvements) are marketing statements that should be substantiated via PoC and third-party benchmarks.

Where competitors have advantages

Zscaler: market maturity and enterprise referenceability in the SSE space.
Palo Alto: integration with Palo Alto product families for organizations that have an existing investment in that stack.

Why customers chose it (recurring themes)

Recurring selection drivers across reviews and community discussion include:

Consolidation of tools and policies
Check Point brand and threat prevention experience
Vendor messaging around performance and backbone architecture

03Field reports

Review-platform sentiment (G2)

Positive example (G2, mid-market user):

“A more secure experience when connecting users and applications… everything on a single platform… real-time protection without impacting performance.”

Negative / critical examples (G2):

“Initial setup and policy configuration can be complex.” “Report generation could also be more intuitive…”

Interpretation: review-platform feedback aligns with a common SASE pattern — buyers value consolidation and security outcomes, but deployment and reporting friction are recurring notes.

Gartner Peer Insights (access notes)

Community / social sentiment (Reddit)

Reddit discussions include operational notes, licensing confusion, and reliability questions.

Outage / degraded performance discussion:

Threads reference an outage or degraded performance event in the context of US data residency.

Packaging / licensing confusion (MSSP context):

Community threads discuss Essentials vs Essentials+ and report difficulty locating expected features in the SASE console, suggesting possible packaging ambiguity or entitlement/configuration gaps.

Competitive shortlisting:

Networking-focused discussions show Check Point SASE included alongside Prisma and Cato when organizations discuss replacing separate SD-WAN and security stacks.

Why some customers hesitate or leave (recurring themes)

Recurring concerns include:

Setup and policy configuration complexity during initial deployment
Reporting and dashboard usability issues
Edition clarity and entitlement concerns
Reliability concerns based on isolated outage or degraded performance discussions

Vendor collateral and success claims

Critical evaluation:

Vendor performance and deployment claims typically depend on baseline comparisons, network geography, last-mile conditions, and the specific scope of what is included in "deployment" (IdP integration, application onboarding, segmentation design, logging/SIEM integration, and endpoint rollout).
No independent, methodologically transparent benchmark supporting the vendor's pronounced performance claim was identified in the reviewed sources.

What procurement should validate in a PoC (to assess ROI claims)

Before/after network performance: page-load times, tunnel throughput, packet loss, latency by region
Administrative workflows: policy change workflow timing and admin UX comparisons
Reporting completeness: required reports and export capabilities to SIEMs
Incident handling drills: exercise malware/phishing/DLP scenarios and measure mean time to detect and investigate

04Best fit

Company size

Likely fit: mid-market to enterprise organizations with distributed users and multiple sites (typically hundreds to thousands of employees).
Also relevant: MSPs/MSSPs serving SMB-to-mid-market customers, though edition entitlements and console feature visibility should be verified.

Industries

Cross-industry applicability; vendor materials reference regulated sectors (e.g., government, education) and compliance alignment as part of the value proposition.

Roles / personas

Decision makers: CISO, Head of Network/Security Engineering, IT Director
Implementers: network engineers, security engineers, identity engineers, endpoint management teams
Operational users: helpdesk/service desk and SOC analysts

Pain points addressed

VPN complexity and security gaps
Fragmented SWG / ZTNA / CASB tooling
Need for consistent policy enforcement for remote users

Qualification criteria (good fit)

Willingness to conduct a structured PoC and invest in policy design and integration
Need for SOC 2 / ISO-aligned vendor posture
Desire to consolidate security tooling within the Check Point ecosystem

05The pitch

What the product does (core value proposition)

Key solution components commonly presented under the suite include:

Internet access / secure web gateway (web/DNS filtering, malware protection, etc.)
Private access (ZTNA) with identity-centric policy enforcement
SaaS security (visibility / shadow SaaS discovery, monitoring integrations)
Supporting features such as device posture, agent-based connectivity, and management dashboards

(These capabilities are described across Check Point SASE web properties and vendor materials.)

Target market and positioning

Primary target: mid-market to enterprise organizations modernizing remote access and branch security, especially those seeking vendor consolidation within the broader Check Point ecosystem.
Secondary target: MSP/MSSP-managed deployments (some materials and community discussion suggest MSSP bundles/editions and feature packaging can be confusing in practice).
Positioning themes reported by the vendor include speed, simplified onboarding, consolidated features, and prevention-focused security.

Get a comprehensive analysis of Check Point SASE including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →