Check Point Endpoint

Name: Check Point Endpoint
Brand: Check Point Software Technologies
Rating: 4.5 (1293 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

MarketsSecurity Service Edge (SSE)Endpoint Security (EPP/EDR)Endpoint Management (UEM)

Platform CoversThreat Intelligence Platforms

Published Oct 15, 2026

01Common complaints

- If endpoint performance is a primary risk: public community reports describe performance degradation in certain versions and configurations; organizations that cannot tolerate such risk should prioritize vendors that demonstrate consistent performance in their own POC. - If transparent, self-serve pricing is a procurement requirement: the product is commonly sold via channel partners and may require partner engagement for firm pricing. - If minimizing component coupling is a priority: some protections depend on additional components that administrators may find unexpected. - If the organization is fully committed to a Microsoft-only stack and seeks cost optimization through bundled licensing: Microsoft Defender for Endpoint may offer simpler licensing justifications.

Deal disqualifiers (poor fit)

Organizations that require fully transparent, self-serve pricing with simple monthly contracts.
Environments where endpoint performance must meet strict SLAs (for example, engineering workstations or media production) and the organization cannot accept version-specific regressions.

Versioning and release cadence signals

The vendor publishes detailed release notes for endpoint clients (Windows and macOS). Buyers should review release notes and test upgrades prior to broad rollout.

Endpoint telemetry and data sharing considerations

Certain releases may enable anonymized incident-related telemetry sent to ThreatCloud by default; administrative controls and documentation describe how to disable telemetry where required by policy.

Cloud service availability terms

The vendor’s cloud terms include SLA language with availability definitions that are relevant for enterprise contracting; buyers should review contractual SLAs and exclusions.

Publicly discussed issues

Community reports have described audio/video desynchronization attributed to specific client versions and reported performance issues in sysadmin forums. These reports indicate the importance of validating client behavior in the buyer’s target environment.

02Why they buy

Product capabilities cited by the vendor and third-party summaries

Agent consolidation: the vendor presents a single-agent approach that includes endpoint protection, detection and response, and optional VPN and encryption capabilities; third-party summaries indicate encryption is offered in higher tiers.
Cloud management: community feedback indicates the Infinity cloud management portal represents an operational improvement compared with legacy on-prem endpoint management tools.

Where competitors may have advantages

Microsoft Defender: strong OS and identity integration and attractive bundling economics for organizations already invested in Microsoft 365.
Best-in-class EDR vendors: perceived strengths in EDR workflows, telemetry ingestion, and community-led playbooks; suitability depends on organizational priorities and POC outcomes.

03Field reports

Note on review access: some enterprise review platforms may gate full review text; this report relies on accessible community discussions and open review sources.

Review platforms (what is publicly visible)

G2 lists Harmony Endpoint and hosts user reviews.
PeerSpot publishes review summaries and mindshare metrics; PeerSpot published a small mindshare figure for Harmony Endpoint in the EPP category (PeerSpot methodology is proprietary and should not be treated as market share).
Editorial reviews from third-party outlets provide additional perspectives.

Positive customer sentiment (examples)

1) Improvement versus legacy on-prem management - A community contributor reported that cloud management via the Infinity Portal was a significant improvement compared with the older on-prem endpoint manager, which was described as tedious and buggy in that discussion. 2) Suite consolidation as a selection factor - Vendor materials claim a single agent that includes data security and remote access VPN; this capability is cited by some buyers as a reason to reduce the number of agents/vendors in their environment. 3) Vendor and community amplification of lab results - Community posts reference vendor-referenced third-party AV testing and analyst recognition; these references are primarily vendor- or community-amplified rather than independent editorial analysis in the accessible sources.

Negative customer sentiment / complaints (examples)

1) Performance degradation complaints - Community threads include reports of endpoint slowdowns and perceived severe performance impact for some versions and configurations. 2) Application side effects / browser media issues - Reports indicate audio/video desynchronization in Microsoft Edge attributed to specific client versions; removing the client was reported to resolve the symptom in at least one case. 3) Operational friction / unexpected component behavior - Reports describe components (for example, a browser protection module) repeatedly attempting to install; in some cases, certain protections require that component, which can surprise administrators. 4) Deployment and troubleshooting complexity - Community guidance directs administrators to specific logs and configuration files to diagnose VPN or policy inconsistencies; this suggests a nontrivial troubleshooting process typical of enterprise endpoint agents.

Why customers reported choosing this product over alternatives

Agent consolidation: preference for one agent that can provide multiple functions (EDR + VPN + encryption) instead of stacking multiple endpoint products.
Existing Check Point footprint: organizations standardized on Check Point may choose the endpoint product for operational consolidation within the same vendor ecosystem.

Why some customers leave or avoid

Reported endpoint performance issues or disruptive application conflicts.
Pricing and channel complexity that can reduce clarity compared with more transparent SaaS vendors.
Complexity of policy blades and inter-component dependencies.

Example: TopRx customer case study (vendor-published)

- Check Point hosts a vendor-published customer story titled "TopRx customer case study." Vendor-published case studies provide examples of deployments and outcomes. Critical evaluation: - Vendor-published material is inherently promotional; metrics and outcomes should be treated as directional unless independently validated. - Procurement questions to validate vendor claims: What was the baseline? Over what time window were results measured? Which controls were enabled? How were incidents counted?

Product/competitive briefs (vendor-published)

Vendor competitive briefs sometimes present specific detection claims (for example, stated detection metrics from controlled simulations).

Critical evaluation:

Competitive briefs are biased by design; test conditions, dataset selection, and scoring may favor the publisher’s product. For objective evaluation, prefer independent lab reports and conduct a controlled proof of concept (POC).

04Best fit

Company size

Typical organizational fit: mid-market to enterprise organizations where centralized security operations, standardized endpoint images, and incident response processes exist.
The product can also be deployed by managed service providers for mid-market customers depending on licensing and channel arrangements.

Industries

Regulated or IP-sensitive sectors (finance, healthcare, professional services, manufacturing) where endpoint encryption, device control and VPN are valued.

Roles/personas

Decision makers: Chief Information Security Officer, VP Security, IT Director.
Evaluators: SOC manager, endpoint engineering lead, network security architect.
End-user impact areas: knowledge workers and developers where performance and application compatibility are critical.

Pain points addressed

Reducing vendor sprawl by consolidating endpoint agents.
Preventing ransomware and commodity malware.
Combining remote access with endpoint security under a single vendor when that is a procurement objective.

Qualification criteria (good fit)

Organizations that already operate Check Point network or security infrastructure and seek operational consolidation.
Organizations that require a combined VPN, endpoint security, and encryption capability managed within a single management model.
Buyers willing to run a structured proof of concept that includes performance baselining.

05The pitch

What the product does (core value proposition)

Check Point Endpoint (marketed primarily today as Harmony Endpoint) is an endpoint protection platform (EPP) and endpoint detection & response (EDR) product line designed to consolidate endpoint security controls into a single agent. The agent can provide malware prevention, behavioral protections, anti-ransomware, device/media controls and, in some packages, full disk/media encryption and remote access VPN. Check Point describes the product as "prevention-first" endpoint security that also supports detection/response and integrates with the broader Check Point Infinity platform and ThreatCloud intelligence. Key suite positioning themes noted in official materials: - Unified endpoint security under the Harmony brand (EPP + EDR + management) and integrations with other Check Point controls. - A single agent that can include data security and remote access VPN; this is presented by the vendor as a capability not present in some EDR-only agents.

Target market and market positioning

- Mid-market to enterprise organizations seeking centralized endpoint policy and telemetry plus optional add-ons such as encryption and VPN under a single vendor. - Organizations already using Check Point network security (Quantum gateways / Infinity ecosystem) and seeking consolidated operations. - Environments with endpoint compliance and posture requirements; Windows release notes reference "Posture Automatic Deployment" support, indicating endpoint posture workflows are a roadmap area.

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

Download full report →

Published Oct 15, 2026

01Common complaints

If endpoint performance is a primary risk: public community reports describe performance degradation in certain versions and configurations; organizations that cannot tolerate such risk should prioritize vendors that demonstrate consistent performance in their own POC.
If transparent, self-serve pricing is a procurement requirement: the product is commonly sold via channel partners and may require partner engagement for firm pricing.
If minimizing component coupling is a priority: some protections depend on additional components that administrators may find unexpected.
If the organization is fully committed to a Microsoft-only stack and seeks cost optimization through bundled licensing: Microsoft Defender for Endpoint may offer simpler licensing justifications.

Deal disqualifiers (poor fit)

Organizations that require fully transparent, self-serve pricing with simple monthly contracts.
Environments where endpoint performance must meet strict SLAs (for example, engineering workstations or media production) and the organization cannot accept version-specific regressions.

Versioning and release cadence signals

The vendor publishes detailed release notes for endpoint clients (Windows and macOS). Buyers should review release notes and test upgrades prior to broad rollout.

Endpoint telemetry and data sharing considerations

Certain releases may enable anonymized incident-related telemetry sent to ThreatCloud by default; administrative controls and documentation describe how to disable telemetry where required by policy.

Cloud service availability terms

The vendor’s cloud terms include SLA language with availability definitions that are relevant for enterprise contracting; buyers should review contractual SLAs and exclusions.

Publicly discussed issues

Community reports have described audio/video desynchronization attributed to specific client versions and reported performance issues in sysadmin forums. These reports indicate the importance of validating client behavior in the buyer’s target environment.

02Why they buy

Product capabilities cited by the vendor and third-party summaries

Agent consolidation: the vendor presents a single-agent approach that includes endpoint protection, detection and response, and optional VPN and encryption capabilities; third-party summaries indicate encryption is offered in higher tiers.
Cloud management: community feedback indicates the Infinity cloud management portal represents an operational improvement compared with legacy on-prem endpoint management tools.

Where competitors may have advantages

Microsoft Defender: strong OS and identity integration and attractive bundling economics for organizations already invested in Microsoft 365.
Best-in-class EDR vendors: perceived strengths in EDR workflows, telemetry ingestion, and community-led playbooks; suitability depends on organizational priorities and POC outcomes.

03Field reports

Note on review access: some enterprise review platforms may gate full review text; this report relies on accessible community discussions and open review sources.

Review platforms (what is publicly visible)

G2 lists Harmony Endpoint and hosts user reviews.
PeerSpot publishes review summaries and mindshare metrics; PeerSpot published a small mindshare figure for Harmony Endpoint in the EPP category (PeerSpot methodology is proprietary and should not be treated as market share).
Editorial reviews from third-party outlets provide additional perspectives.

Positive customer sentiment (examples)

Improvement versus legacy on-prem management

A community contributor reported that cloud management via the Infinity Portal was a significant improvement compared with the older on-prem endpoint manager, which was described as tedious and buggy in that discussion.

Suite consolidation as a selection factor

Vendor materials claim a single agent that includes data security and remote access VPN; this capability is cited by some buyers as a reason to reduce the number of agents/vendors in their environment.

Vendor and community amplification of lab results

Community posts reference vendor-referenced third-party AV testing and analyst recognition; these references are primarily vendor- or community-amplified rather than independent editorial analysis in the accessible sources.

Negative customer sentiment / complaints (examples)

Performance degradation complaints

Community threads include reports of endpoint slowdowns and perceived severe performance impact for some versions and configurations.

Application side effects / browser media issues

Reports indicate audio/video desynchronization in Microsoft Edge attributed to specific client versions; removing the client was reported to resolve the symptom in at least one case.

Operational friction / unexpected component behavior

Reports describe components (for example, a browser protection module) repeatedly attempting to install; in some cases, certain protections require that component, which can surprise administrators.

Deployment and troubleshooting complexity

Community guidance directs administrators to specific logs and configuration files to diagnose VPN or policy inconsistencies; this suggests a nontrivial troubleshooting process typical of enterprise endpoint agents.

Why customers reported choosing this product over alternatives

Agent consolidation: preference for one agent that can provide multiple functions (EDR + VPN + encryption) instead of stacking multiple endpoint products.
Existing Check Point footprint: organizations standardized on Check Point may choose the endpoint product for operational consolidation within the same vendor ecosystem.

Why some customers leave or avoid

Reported endpoint performance issues or disruptive application conflicts.
Pricing and channel complexity that can reduce clarity compared with more transparent SaaS vendors.
Complexity of policy blades and inter-component dependencies.

Example: TopRx customer case study (vendor-published)

Check Point hosts a vendor-published customer story titled "TopRx customer case study." Vendor-published case studies provide examples of deployments and outcomes.

Critical evaluation:

Vendor-published material is inherently promotional; metrics and outcomes should be treated as directional unless independently validated.
Procurement questions to validate vendor claims: What was the baseline? Over what time window were results measured? Which controls were enabled? How were incidents counted?

Product/competitive briefs (vendor-published)

Vendor competitive briefs sometimes present specific detection claims (for example, stated detection metrics from controlled simulations).

Critical evaluation:

Competitive briefs are biased by design; test conditions, dataset selection, and scoring may favor the publisher’s product. For objective evaluation, prefer independent lab reports and conduct a controlled proof of concept (POC).

04Best fit

Company size

Typical organizational fit: mid-market to enterprise organizations where centralized security operations, standardized endpoint images, and incident response processes exist.
The product can also be deployed by managed service providers for mid-market customers depending on licensing and channel arrangements.

Industries

Regulated or IP-sensitive sectors (finance, healthcare, professional services, manufacturing) where endpoint encryption, device control and VPN are valued.

Roles/personas

Decision makers: Chief Information Security Officer, VP Security, IT Director.
Evaluators: SOC manager, endpoint engineering lead, network security architect.
End-user impact areas: knowledge workers and developers where performance and application compatibility are critical.

Pain points addressed

Reducing vendor sprawl by consolidating endpoint agents.
Preventing ransomware and commodity malware.
Combining remote access with endpoint security under a single vendor when that is a procurement objective.

Qualification criteria (good fit)

Organizations that already operate Check Point network or security infrastructure and seek operational consolidation.
Organizations that require a combined VPN, endpoint security, and encryption capability managed within a single management model.
Buyers willing to run a structured proof of concept that includes performance baselining.

05The pitch

What the product does (core value proposition)

Key suite positioning themes noted in official materials:

Unified endpoint security under the Harmony brand (EPP + EDR + management) and integrations with other Check Point controls.
A single agent that can include data security and remote access VPN; this is presented by the vendor as a capability not present in some EDR-only agents.

Target market and market positioning

Mid-market to enterprise organizations seeking centralized endpoint policy and telemetry plus optional add-ons such as encryption and VPN under a single vendor.
Organizations already using Check Point network security (Quantum gateways / Infinity ecosystem) and seeking consolidated operations.
Environments with endpoint compliance and posture requirements; Windows release notes reference "Posture Automatic Deployment" support, indicating endpoint posture workflows are a roadmap area.

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

Download full report →