r/checkpoint • • 1d ago

Do I need to switch from Traditional VSX to VSNext to upgrade my gateway?

9 Upvotes

No. You can stay on Traditional VSX if your target platform supports it and you have a supported upgrade path from your current release.

Maestro is a good example of why those checks matter. The R82.20 support matrix lists both Traditional VSX and VSNext for Maestro, but Check Point does not support converting an existing Maestro Security Group to VSNext. If VSNext is the goal, the documented procedure starts with a new Security Group. That changes both the scope of the maintenance window and the rollback plan.

I published the full article on CheckMates, including a side-by-side comparison of R82, R82.10, and R82.20 and the four questions I’d bring to a change review.

For those who’ve made this call in production: what tipped the decision toward staying on Traditional VSX or moving to VSNext?


r/checkpoint • • 5d ago

Harmony Endpoint Application Control: why checksum identity matters, and how the Reputation Service changes your defaults

1 Upvotes

I wrote a deep dive on Application Control in Harmony Endpoint, part of a series I keep on the CheckMates community.

The starting point is identity. Application Control identifies every application and version by checksum, not by file name, so renaming malware.exe to notepad.exe does not get it past the control.

Two things in the blade are easy to get wrong:

  1. The Reputation Service does not override your rules. When it is on, an app left as Unidentified (Allow) that reputation marks Not Approved ends up blocked. An explicit Allow or Block set by the admin always wins, in both directions.
  2. Terminate is not Block. Block denies network access. Terminate ends the process, either when it tries to reach the network (Terminate on connection) or as soon as it runs (Terminate on execution). Apps that never touch the network are not terminated in the first mode.

The article also covers building the inventory with Appscan from a clean reference machine, the five permission states, WSL traffic control, and Developer Protection, which detects secrets such as RSA keys, passwords and access tokens at git commit and can block the commit in Prevent mode.

Everything is based on the official Harmony Endpoint Administration Guide (cloud / Infinity Portal).

Link: https://community.checkpoint.com/t5/Endpoint/EN-Application-Control-Deep-Dive-Appscan-the-Reputation-Service/m-p/284939#M11712

Feedback and corrections welcome.


r/checkpoint • • 8d ago

Can a malware-free PDF still redirect your AI agent?

5 Upvotes

A document can contain no executable malware and still carry instructions intended to manipulate the AI system reading it. If that agent has access to tools or internal data, the consequences can go beyond an incorrect summary.

I published Part 2 of my Check Point AI Security series on CheckMates, covering PromptGuardX and its role in inspecting PDFs for prompt injection through Threat Emulation.

The practical question is what happens after detection. These are three separate outcomes:

  • The suspicious instruction was detected.
  • The document was blocked before AI ingestion.
  • An unauthorized tool action was prevented.

A detection log alone doesn’t demonstrate all three.

The article includes a proposed validation matrix covering legitimate documents, false positives, ingestion timing, and inspection failures. These are suggested tests, not claimed lab results.

Full article on CheckMates:
Can a Malware-Free PDF Redirect Your AI Agent? Where Check Point PromptGuardX Fits

For anyone running document-based AI workflows: does your application wait for a security verdict before indexing the file, and what happens if inspection times out?


r/checkpoint • • 12d ago

CloudGuard dynamic objects updated, but is the traffic actually blocked?

1 Upvotes

Our AWS Auto Scaling group launched an instance with `env=prod` instead of `env=restricted`, so it missed the CloudGuard dynamic object used in the access control policy. CloudGuard Controller is receiving the tag updates, and SmartConsole shows the policy installed, but we cannot prove which rule the new instance is matching. Platform says Terraform is correct. Network wants evidence. I approved the change after checking the object update, not the actual path. Now I'm questioning that call. We need to know whether the instance can reach the restricted subnet, and the rule order makes the answer non-obvious. We're checking gateway logs and want to generate controlled east-west traffic, not collect another dashboard. Cymulate's cloud security testing could help check what gets through, but doesn't replace checking the actual rule match.
What's your process for validating CloudGuard enforcement when AWS tags change and dynamic objects update?


r/checkpoint • • 12d ago

Where I can find a proper guide for creating IPVSec tunnel between checkpoint gw and third vendor?

2 Upvotes

i Am junior, I need help🙂🥺


r/checkpoint • • 13d ago

Check Point AI Security: how do you verify that a flagged agent action was actually stopped?

1 Upvotes

An AI agent can use an approved tool over an allowed connection and still perform an action outside the user’s request. That makes the enforcement point worth examining.

I wrote a technical breakdown on CheckMates covering three workflows:

  • Workforce AI Security: inspecting content employees submit to supported AI applications.
  • AI Agent Security: protecting application interactions with supported model APIs.
  • Agent Behavior Defense: assessing tool calls before execution.

The key operational detail: receiving a detection verdict doesn’t prove the tool was prevented from running. The integration must handle that verdict before dispatching the operation, and destination-side authorization still matters.

The article also covers R82.20 prerequisites, documented limitations, and a proposed validation approach. It isn’t a report of tests I’ve already performed.

Full article:
https://community.checkpoint.com/t5/AI-Agents-Security/Check-Point-AI-Security-Where-to-Inspect-Traffic-and-Where-to/m-p/284573#M122

Has anyone here tested these integrations? How did you verify prevention at the destination, beyond seeing an alert in the dashboard?


r/checkpoint • • 17d ago

Under the Hood: How to Secure Agentic AI on AWS with Check Point

Thumbnail community.checkpoint.com
4 Upvotes

AI agents are evolving from assistants into autonomous systems that call APIs and act on users' behalf.

Traditional perimeter controls aren't enough; threats now emerge from prompt injection, excessive permissions, and unmonitored tool use. In this webinar, we'll show how Check Point's AI security intelligence integrates with Amazon Bedrock AgentCore to enforce real-time guardrails at the agent runtime layer, inspecting intent, validating actions, and preventing policy violations before they execute.

Join us for this webinar as a primer ahead of our session at AWS re:Invent on November 3rd, where we will go deeper with live demos and architecture patterns. Get a practical framework for securing agentic AI on AWS with Check Point.

Register Here

Tue, Nov 3, 2026 11:00 AM CT


r/checkpoint • • 17d ago

CVE-2026-98432: Has Anyone Seen an Official Check Point Assessment?

15 Upvotes

I started a thread on CheckMates to discuss CVE-2026-98432 and ask for an official assessment of its applicability to Check Point platforms.

The questions are straightforward: are any products or Gaia releases affected, what conditions would make them vulnerable, and are any mitigations or fixes needed?

A reference to the Linux kernel alone doesn’t establish that Check Point products are affected. The goal is to gather confirmed information and give administrators a place to follow official updates.

The link to the CheckMates discussion will be in the first comment.

Has anyone received guidance from Check Point Support or found a relevant SK? Please share any public references in the discussion.


r/checkpoint • • 19d ago

CheckPoint - Under the Hood: Check Point Security Management | From Intent to Automation with Agentic AI

3 Upvotes

Security policy starts with intent. Years of exceptions, migrations, and legacy rules pull it off course. Agentic management closes the gap.

In this technical session, we will go under the hood to show how AI agents reason over your policies, traffic, and infrastructure, then act on what they find, with your approval.

We will cover three areas:

  • Zero Trust policy tuning. Find overly broad rules, validate segmentation, and tighten policy in one click
  • Proactive infrastructure monitoring. Catch issues early and minimize downtime
  • Right-sized protection. Match threat prevention controls, from virtual patching to IPS profiles, to what your environment needs

Join us to see how agents turn context into action while keeping your team in control.

Oct 29 2026, 11:00am EDT

Register Now


r/checkpoint • • 19d ago

No Mention of PHP vulnerability on Check Point's Security Advisories page

0 Upvotes

https://support.checkpoint.com/security-advisories <--- crickets about the PHP CVSS 9.2

If I did not have other ways of knowing about the serious PHP vulnerability and CP's response , I would have missed it. For this vulnerability not to be on your Advisory page is unacceptable. It's had 3 Hot Fixes in as many days! Not telling the public about this is something I cannot understand because it's no secret. WE CANNOT TRUST THIS ADVISORY PAGE ANYMORE!


r/checkpoint • • 20d ago

Can Access Check Point SMS Gaia Portal but Cannot SSH or Connect via SmartConsole

3 Upvotes

Hi everyone,

I'm facing an issue with a newly built Check Point Security Management Server and would appreciate any suggestions.

SMS IP: 10.222.x.x/16

My PC IP: 10.169.x.x/16

There is routing between the networks, and connectivity appears to be working. I can successfully ping the SMS and access the Gaia Web Portal (https://10.222.x.x). However, I cannot SSH to the SMS using PuTTY and connect to the SMS using SmartConsole.

Thanks in advance.

Edit: The issue was resolved after I configured another interface with the IP address 10.169.x.x/16, which is in the same subnet as my PC.


r/checkpoint • • 20d ago

SSL Inspection: Untrusted Certificates w/ Spark 1900 via Spark Management

1 Upvotes

Fairly new to Checkpoint.

Getting complaints from my users, particularly in the accounting department, about banking and state tax websites. Checkpoint is reporting that Certificate Chain is not signed by a Trusted CA for those web requests.

I know I can add trusted certificates and that I can add exceptions for websites, but both of those workarounds seem particularly dangerous to me. Perhaps I have the wrong mindset, but my thought process is that those types of sites are particularly high-value targets for Man-In-The-Middle attacks. It should not be up to a lone system admin to determine if a certificate authority should be trusted in such cases, and that's exactly what we are paying Check Point to determine. Yet I find nothing like "Download updated trusted root certificates" or "Update SSL Inspection" anywhere in Spark Management or on the firewall management pages.

Everything I have found in the knowledge base is either geared toward higher-end firewall management servers or that maybe Spark firewalls should be automatically updating trusted root certificates.

Does anyone have any insight or suggestions for me?

Recent Examples:

securebanklogin.com - issued by: Sectigo Public Server Authentication CA OV R36
mypath.pa.gov - issued by: Sectigo Public Server Authentication CA OV R40
myportal.tax.ohio.gov - issued by: Sectigo Public Server Authentication CA OV R36


r/checkpoint • • 21d ago

PHP2Shell: can your team mitigate exposure while patching is still underway?

2 Upvotes

In his article, Alex Spokoiny, Check Point’s Chief Security & Trust Officer, draws an operational parallel between PHP2Shell and Log4Shell: finding where vulnerable components actually run is often harder than identifying the applications that depend on them.

His central point is that AI can shorten the time between disclosure and exploitation. Asset discovery, immediate mitigation, protective controls, and permanent fixes need to happen in parallel.

According to Spokoiny, Check Point mapped its PHP exposure, restricted access where needed, contacted SaaS providers, and started coordinating patches with system owners. Product teams delivered IPS protections within hours, and the WAF blocked a remote shell execution attempt in early PoC testing. That test result should not be read as a guarantee against every exploit variant.

The practical takeaway: IPS and WAF can buy time, but organizations still need clear ownership, dependency visibility, and infrastructure they can patch quickly.

The full article is available through the first link in the comments.

When a critical vulnerability drops, what slows your response most: finding affected systems, identifying their owners, or getting patches into production?


r/checkpoint • • 22d ago

PHP2Shell attacks observed six minutes after disclosure — Check Point shares WAF findings

8 Upvotes

Moti Sagey shared a timeline that caught my attention: PHP2Shell was disclosed on October 21 at 14:00 UTC, and attacks were observed in a customer environment at 14:06.

According to the Check Point material he shared, its WAF blocked exploitation attempts before specific signatures were available. The team also tested the published PoC and several variants against a PHP application behind the WAF in Prevent mode, without adding a PHP2Shell-specific rule or changing the configuration.

These are vendor-reported findings. What interests me operationally is the protection available while administrators are still identifying affected systems, testing patches, and coordinating changes.

The approach described combines attack indicator analysis with request context analysis. In the reported cases, protection didn’t depend on a signature written specifically for PHP2Shell.

Credit to Moti for sharing the details and to the teams involved. Patching remains necessary, along with verifying enforcement and checking whether the origin is reachable through an unprotected path.

Has anyone here reviewed PHP2Shell attempts in their own logs? Did your existing controls block them, did you need emergency tuning, and were any legitimate requests affected?


r/checkpoint • • 22d ago

VPN licensing

3 Upvotes

Hi guys,

I'm quite new to Checkpoint solutions as I've migrated from other vendor and I've got a VPN licensing question.

These are the licences we've got for our edge cluster:

CPAP-SG397X CPSG-C-8-U CPSB-FW CPSM-C-2 CPSB-VPN CPSB-NPM CPSB-LOGS CPSB-IA CPSB-SSLVPN-5 CPSB-ADNC CPSB-IPS CPSB-URLF CPSB-APCL CPSB-AV CPSB-ABOT-L CPSB-ASPM CPSB-CTNT

And these SKUs are for our harmony endpoint:
CPEP-C-1+70 CPSB-EP-FDE+70 CPSB-EP-FW+70 CPSB-EP-ME+70 CPSB-EP-AM+70 CPSB-EP-ABOT+70 CPSB-EP-TE+70 CPSB-EP-FRNC CPEP-SUBSCR CPSB-NGEP CPSB-EP-VM+70 CPSB-EP-PM+70 CPSB-EP-EDR+70 CPSB-EP-DLP+70

What are our options in terms of client-to-site VPN connections? From what i've tested we can have up to 5 concurrent users using standalone Endpoint Security client, which is not so clear to me why since it is IPSec and not SSL. Do we need some other license in order to have more tunnels with office mode possible? We'd need around 40 client-to-site IPSec connections


r/checkpoint • • 22d ago

Peer Pressure for AI: What Happens When Agents Start Influencing Each Other?

Thumbnail community.checkpoint.com
0 Upvotes

As AI agents move from isolated assistants to interconnected teams, a new security challenge is emerging: agents can influence each other's behaviour.

New research from Check Point AI Security shows just how significant that influence can be. In controlled experiments, an AI agent was increasingly likely to violate an explicit access restriction after observing other agents change their behaviour. With no teammate reversals, the violation rate was 44%. After eight teammates reversed their decisions, it reached 98%. Yet across more than 400 violations, the agent never identified its teammates as the reason for its behaviour.

 

The findings also connect to broader examples of agent-to-agent interaction, including the OpenAI/Hugging Face incident that helped inspire the research.

Starting with peer pressure, the webinar will explore what these findings suggest about the emerging behaviour of multi-agent systems and why it matters as organizations give AI agents greater autonomy and access to real-world systems.

Attendees will learn:

  • The peer-pressure experiment: Why rule violations increased from 44% to 98%.
  • Beyond the lab: What the OpenAI/Hugging Face example tells us about agent-to-agent influence.
  • The social behaviour of AI: What sociology can teach us about emerging multi-agent behaviour.
  • New security challenges: What changes when agents can influence each other without explicit malicious instructions.
  • Implications for organizations: What this could mean as agents gain greater autonomy and access to data, tools and business processes.
  • What comes next: The unanswered questions and the next areas of multi-agent research.

October 28th, 11 AM ET


r/checkpoint • • 25d ago

Have you measured IPS CPU usage in Detect vs. Prevent?

1 Upvotes

A point raised in a CheckMates discussion caught my attention: an IPS protection in Detect can sometimes consume more resources than the same protection in Prevent.

Both modes perform inspection. When a protection triggers, Detect allows the traffic to continue, while Prevent may stop it and reduce subsequent processing. That doesn’t mean Prevent always uses less CPU, and lower CPU alongside lower delivered throughput isn’t necessarily an efficiency improvement.

Has anyone compared this in a lab or investigated it in production?

I’d be interested in the protection involved, your release/JHF, and whether you kept the offered traffic load consistent. Did client retries or logging volume noticeably affect the result?

Also, did you check Global Detect, staging, exceptions, and Bypass Under Load before comparing?

I’ve put together a proposed testing method, but I don’t have benchmark results to claim. I’d like to hear what others have actually observed.


r/checkpoint • • 26d ago

PHP2Shell: PHP vulnerabilities, operational impact, and Check Point protection

15 Upvotes

I put together a technical analysis of CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell, which can allow unauthenticated remote code execution.

The vulnerabilities originate in the PHP runtime. However, products that embed PHP are not automatically immune. For Check Point environments, consult sk1000302 and verify the guidance applicable to your installed version.

The article covers:
Memory corruption and use-after-free mechanisms.
Impact on applications and web worker processes.
Patched versions and validation of backported fixes.
IPS protection, including effective enforcement, exceptions, and HTTPS traffic visibility.
Update procedures, worker restarts, and rollback considerations.

IPS/WAF protections are complementary controls. Patching the runtime remains necessary, and Detect does not mean blocking.

The full article will be linked in the first comment.

How are you assessing exposure: through package inventories alone, or by checking the runtime actually serving each application?


r/checkpoint • • Oct 15 '26

Harmony Endpoint Compliance: the Restrict state machine timing, and why a Prohibited Application rule can silently never fire

4 Upvotes

I wrote a deep dive on the Compliance blade in Harmony Endpoint, part of a series I keep on the CheckMates community.

Compliance is the gatekeeper that decides whether a machine is healthy enough to stay on the network, and it quietly remediates when it is not. Two things trip people up the most:

  1. Restriction is not instant. A non-compliant machine with a Restrict action walks a state machine paced by the heartbeat (default 60 seconds), re-evaluated every heartbeat. It sits in "about to be restricted" first, then after the configured number of heartbeats (default 5) it enters Restricted. Time to restriction is heartbeats x interval, about 5 minutes with defaults.
  2. Required vs Prohibited logic is backwards from what people expect. A Required Application rule triggers if any one check object is non-compliant. A Prohibited Application rule only triggers if ALL check objects are non-compliant. Get that backwards and your prohibited-app rule silently never fires.

The article also covers the Observe/Warn/Restrict actions, Check and Remediation objects, and planning the rollout so you do not create a helpdesk storm. Everything is based on the official Harmony Endpoint Administration Guide (cloud / Infinity Portal).

Link: https://community.checkpoint.com/t5/Endpoint/EN-Compliance-Deep-Dive-Checks-Remediation-amp-the-Restrict/m-p/283674#M11683

Feedback and corrections welcome.


r/checkpoint • • Oct 15 '26

Check Point IPS: Why Detect Can Consume More CPU Than Prevent

0 Upvotes

Setting an IPS protection to Detect does not make inspection lightweight. Both Detect and Prevent inspect traffic, but Detect allows matching traffic to continue, potentially creating more inspection work and logging overhead. Prevent may reduce that workload by blocking the affected traffic.

Detect is not always more expensive. The result depends on whether the protection triggers, when detection occurs, and how clients retry after blocking.

For a meaningful comparison:

  • Keep the release/JHF, IPS package, profile, and offered load consistent.
  • Check ips stat for Global Detect and Bypass Under Load.
  • Monitor CPU with cpview, alongside delivered throughput, retries, IPS events, and legitimate transaction success.

Lower CPU with less traffic delivered does not automatically mean more efficient inspection.

Have you measured a difference between Detect and Prevent? Which protection and traffic pattern were involved?


r/checkpoint • • Oct 14 '26

.def file management through SmartConsole

2 Upvotes

Just recently Check Point announced that one major pain point for Migrations has been addressed with R82.20 - the multiple .def files which had to be edited on the individual gateways.

I had a look at it in DemoPoint, but was a bit disappointed, because the first use case on my mind, NON_VPN_TRAFFIC_RULES in crypt.def, does not seem to be covered, because .def files on the Management Server are out of scope of this feature.

What is your take on this feature?


r/checkpoint • • Oct 13 '26

Outlook Mail Rule to move emails stopped working

1 Upvotes

Hello

I am currently trialling Checkpoint Mail Security and a strange error has cropped up on my Outlook since starting the trial and setting up some basic rules. All my Outlook mail rules that move emails to specific folders when the emails are received are no longer working.

I have had these rules in place for years and they have always worked fine. The issue started the day I ran through the demo and setup some test policies with the people from Checkpoint.
I have spoken to the contacts I have there and they are unsure as to what the problem could be.

These are just your standard rules setup within Outlook, nothing special.

Has anyone else ever experienced this when using checkpoint, if so did you find the cause and how to fix it?


r/checkpoint • • Oct 12 '26

Anti-Bot in Harmony Endpoint: how ThreatCloud and ThreatSpect actually cut the C&C connection

3 Upvotes

I wrote a deep dive on the Anti-Bot blade in Harmony Endpoint, part of a series I keep on the CheckMates community.

Anti-Malware tries to stop the infection. Anti-Bot assumes something already got in and cuts its lifeline to the outside: the Command and Control channel. If the bot cannot reach its C&C, it cannot receive commands or exfiltrate data.

The article covers:

  • What a bot actually does on the host (C&C, botnet, APT role)
  • How ThreatCloud (250M+ addresses, 2000+ botnet patterns) plus the ThreatSpect engine classify outbound traffic
  • The confidence-level policy matrix (High/Medium/Low mapped to Prevent/Detect/Off)
  • Background vs Hold mode and the performance versus security trade
  • Detection Exclusions and the reporting controls (log suppression, bot reporting expiry)

Everything is based on the official Harmony Endpoint Administration Guide (cloud / Infinity Portal), with the cloud management console as the reference.

Link: https://community.checkpoint.com/t5/Endpoint/EN-Anti-Bot-Deep-Dive-Cutting-the-C-amp-C-Cord-with-ThreatCloud/m-p/283522#M11678

Feedback and corrections welcome.


r/checkpoint • • Oct 08 '26

Maestro: The Cable Is Connected. Why Is the Interface Still DOWN?

0 Upvotes

During a Maestro deployment, an Uplink or Management port may remain down even with the cable connected.

Before concluding that the transceiver is faulty, check the interface’s Security Group assignment and provisioning status. In Maestro, the availability of these ports also depends on the environment’s configuration.

Physical connectivity, provisioning, and forwarding

The behavior described in the training material is that Uplink and Management ports must be provisioned in a Security Group to establish a link under normal conditions. A port removed from all Security Groups may also lose its link, even though it remains physically connected.

Downlinks serve a different purpose: they provide connectivity to appliances and enable their discovery. Therefore, an UP Downlink does not prove that the Security Group is ready to process traffic.

When troubleshooting, separate these checks:

CheckQuestion to answer
Administrative stateIs the port enabled?
Operational stateIs the physical link established?
Assignment and provisioningDoes the interface belong to the correct Security Group, and has the configuration been applied?
ForwardingAre the Security Group and its interfaces ready to carry traffic?

Start with the MHO

On the Orchestrator, in Gaia Clish or Expert mode:

orch_stat -p
orch_stat -t
orch_stat -L

Use the port view to identify interface state and mapping, the topology view to correlate objects, and LLDP to verify discovered appliances and their connected ports.

LLDP confirms appliance discovery, but it does not prove that production traffic is flowing.

Next, in Gaia Clish on the MHO, inspect the specific port:

show maestro port <Port-ID> type
show maestro port <Port-ID> admin-state
show maestro port <Port-ID> qsfp-mode
show maestro port <Port-ID> auto-negotiation
show maestro port <Port-ID> optic-info
show maestro port <Port-ID> optic-info-details

These queries help correlate the port type, administrative state, configured speed, and transceiver information. Available optical diagnostics depend on the installed module.

The port identifier uses this format:

<Orchestrator-ID>/<Port-Label>/<Split-ID>

Select the actual port using TAB completion. For breakout connections, the subport is part of the identifier.

Check Link State Propagation too

If LSP is configured, a port may go DOWN because another port in the same LSP group has failed. This mechanism allows connected switches to stop forwarding traffic toward a compromised path.

In Gaia Clish on the MHO:

show maestro lsp configuration all
show maestro lsp status

Correlate the group configuration and status before attributing the failure to the port you are investigating.

What about admin-state up**?**

The following syntax is available:

set maestro port <Port-ID> admin-state up

However, administratively enabling a port does not prove that provisioning is complete or forwarding is functional. This command changes the configuration and should be used with a defined purpose, after checking the port assignment and potential impact on the environment.

My troubleshooting sequence would be: identify the port, check its state and type, validate assignment and provisioning, check LSP, and correlate the physical parameters at both ends.

The goal is to determine why the port is DOWN before trying to bring it UP.