r/checkpoint • • Mar 03 '26

CP FW Keygen

0 Upvotes

Hi, hope this is OK, understand if it isn't but I think sufficient years have passed...

Back in the early 00's or possible even late 90s there was a keygen that'd crank out keys for CPFW 3.0/4.x/NG.

Would anyone still have a copy, or a link to it?

E


r/checkpoint • • Oct 12 '25

Hello, we are looking for employees with Checkpoint CCSA CCSE certificates to work remotely.

0 Upvotes

Hello, we are looking for employees with Checkpoint CCSA CCSE certificates to work remotely. Pls dm


r/checkpoint • • Sep 15 '26

how often do you guys reboot your Check Point firewalls? 😂

0 Upvotes

Just reboot it and move on. It’s a feature 😂 not a bug


r/checkpoint • • Jun 13 '21

How do I completely remove Check Point from my system?

0 Upvotes

I want everything Check Point removed from my system. The Chrome extensions are causing endless headaches. The thing is constantly slowing down my system.

But I can't for the life of me find a way to get rid of it. It doesn't show up as an installed program to remove. There's no uninstallers. Chrome won't let me turn it off because it's made Chrome believe it's being managed by an administrator (which it isn't, as this is a home PC).

But I cannot find a way to kill this damn program and remove it from my system. Someone PLEASE help me.


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 • • 29d 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 • • 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.


r/checkpoint • • Aug 09 '26

Operational runbook (MHO + SGMs + traffic + VPN) with field commands

2 Upvotes

Maestro Troubleshooting in Practice

Operational runbook (MHO + SGMs + traffic + VPN) with field commands

If you run Quantum Maestro in production, you’ve probably seen the pattern: issues that “look like VPN” or “look like policy” often turn out to be Security Group health, a single divergent SGM, a physical/link problem (cable/port/optics), or an unstable uplink. The key to reducing MTTR is discipline: evidence + commands, without skipping layers.

Below is a practical “copy-and-run” runbook, with good vs bad interpretation.

 

1) Mental model 

  • MHO (Orchestrator): controls the Security Group (inventory, health, ports, fabric).

  • SGMs: run the dataplane (sessions, inspection, VPN, state).

  • Typical symptom patterns:

    • Unhealthy SG → everything becomes a symptom (policy/VPN/traffic).

    • Unhealthy single SGM → intermittent behavior (“sometimes it works”).

2) clish vs gclish (why this becomes a real incident)

clish

  • Local node context.

  • Useful for point inspection, but risky for configuration in Maestro because it can introduce drift (one member behaving differently).

gclish

  • Global Security Group context.

  • Operational rule:

    • use gclish when the intent is global consistency (uniform validation/collection/adjustment);

    • use clish only when you need to inspect/act on a specific member in a controlled way.

3) Fast triage start with the Security Group

3.1 Global Maestro / Security Group health

On the MHO:

orch_stat -all

What this proves:

  • whether all SGMs are present/operational

  • whether any member is degraded/missing

  • signals of port/fabric issues

Good: all members OK, stable links, no critical port down.
Bad: missing/degraded member, unstable links → fix the foundation before analyzing VPN/policy.

3.2 Security Group sanity check

asg diag verify

What this proves: high-level SG consistency and quick integrity checks.
Bad: critical alerts → return to orch_stat -all and isolate the failing member/port.

3.3 Capacity before taking member-level actions

asg perf -v

What this proves: whether the SG has enough headroom (CPU/memory) to absorb load during isolation/actions.
Bad: SG near its limits → avoid disruptive actions.

3.4 Reconcile state (use with care)

hcp -r all

Note: commonly used in playbooks to recover internal state/handshakes, but it should not be the first “blind” step.

 

4) Physical and link health (where most “bugs” actually start)

When you see intermittency, “traffic disappears,” or only some users/flows fail, first prove whether there is physical/L1–L2 instability.

4.1 Inventory/port-map quick reference

 

orch_stat -p

or

cat /etc/maestro.json

Use this to confirm interface/port mapping in the Maestro context.

4.2 Counters and drops (all members)

g_all netstat -ni

What to look for: increasing RX-ERR/TX-ERR/drops.
If these counters climb, they often explain VPN flapping, broken sessions, and “policy is OK but traffic fails.”

4.3 Per-interface physical errors (CRC/symbol errors)

ethtool -S <interfacename>

Good: no CRC/errors increasing.
Bad: CRC/symbol errors → treat as L1/L2 (cable/optics/port/switch) before focusing on VPN.

4.4 Real link flap (carrier)

asg_ifconfig | grep carrier | grep -v "carrier: 0"

Bad: carrier oscillation → intermittent behavior is highly likely.

4.5 Hardware health (sensors)

g_all cpstat -f sensors os

What this proves: thermal/power/fan conditions can lead to instability and erratic behavior.

4.6 Maestro port state

show maestro port <port>

Confirms the port’s state/configuration in the Maestro domain.

 

5) The turning point: “no log” — does the traffic exist in the SG dataplane?

This step quickly separates “problem before the gateway” from “problem inside the gateway.”

5.1 Prove the session/connection on the SG

Example (intentionally generic IPs):

asg search -v 10.10.40.25 \* 203.0.113.50 443 tcp

Interpretation:

  • No output: traffic likely is not reaching the SG (or it’s taking a different path). Return to L1/L2/L3 and capture at the correct point.

  • Output present: traffic exists in the dataplane; you now have a basis to correlate with NAT, routing, policy, and VPN.

6) Single-SGM failure: how to investigate and restore consistency

Typical symptom: intermittent failures, “some flows drop,” “works after some time.”

6.1 Controlled action to reintegrate a suspected member (when needed)

On the suspected SGM:

clusterXL_admin down
clusterXL_admin up

Risk: medium (sessions anchored to that member can be impacted).
Pre-condition: confirm headroom with asg perf -v.

6.2 Check state and drift indicators

cphaprob list
tail $FWDIR/log/blade_config

What to look for:

  • cphaprob list: HA/cluster participation/state signals and inconsistencies

  • blade_config: alerts and errors that indicate configuration drift

Closing

Maestro troubleshooting requires discipline: start with SG health, then prove traffic exists, then validate physical stability, and only then go deeper. If you follow this sequence with objective commands, “phantom incidents” drop sharply—and troubleshooting becomes engineering, not guesswork.


r/checkpoint • • Oct 07 '26

Maestro Dual Site: The Site Is Back. Why Hasn’t Traffic Returned?

0 Upvotes

After a failure at Site 1, Site 2 takes over traffic processing. Site 1’s infrastructure recovers, its members become available again, but Site 2 remains active.

This may be the expected behavior of your high availability configuration.

In Maestro Dual Site, understanding when traffic returns requires evaluating the HA mode, the quality grade, and the Security Group’s transition criteria.

Active Up and Primary Up

ModeBehavior after recovery
0 — Active UpThere is no primary site. The currently active site remains active; recovery of the other site alone does not trigger a return.
1 — Primary UpThis mode provides for a return to the primary site after recovery, subject to HA conditions.

In both modes, differences in quality grade can trigger a site transition. Therefore, Active Up does not mean that the current site remains active regardless of its health, and Primary Up should not be interpreted as an immediate return as soon as a device responds.

Being reachable does not mean the grade has recovered

The assessment considers monitored components and their assigned weight factors. Each component contributes according to:

Component grade = Unit weight × Number of components in the UP state

A site can regain administrative access while remaining degraded because members or interfaces are still unavailable. Additionally, the failover parameter defines the minimum grade differential that triggers a transition.

These HA factors differ from the traffic distribution weights assigned to SGMs. Changing member-weight is not equivalent to configuring site preference.

What to check in R82/R82.10

Run the following in Gaia gClish on the Security Group:

show cluster configuration high-availability mode
show cluster configuration high-availability failover
show cluster configuration high-availability freeze_interval
show cluster configuration high-availability factors member
show cluster configuration high-availability factors port bond
show cluster configuration high-availability mgmt-monitoring

These queries identify the mode, grade differential, stabilization interval, and factors relevant to the decision.

To inspect component states and weights:

asg stat -v

This command remains documented for this purpose in the R82.10 guide. Correlate its output with the HA configuration before concluding that failback is malfunctioning.

Pay attention to freeze_interval

This mechanism prevents another transition before the applicable interval expires, allowing the grade to stabilize. The R82.10 guide documents effective default intervals of 30 seconds in Active Up and 150 seconds in Primary Up.

There is an important operational detail: when configuring the interval in Primary Up, the documentation instructs you to enter a value five times smaller than the desired duration. Therefore, do not interpret or change this parameter assuming a universal 1:1 relationship between the configured value and the effective duration.

Before forcing traffic back, answer these questions:

  • Is the Security Group configured for Active Up or Primary Up?

  • Has the recovered site reached its expected grade?

  • Does the grade differential meet the configured criterion?

  • Has the stabilization interval expired?

Recovery testing should also validate the failback behavior defined in the design. A site remaining Standby after recovery may demonstrate that the HA policy is working exactly as configured.


r/checkpoint • • Sep 09 '26

Harmony Endpoint on VDI: how the Shared Signature Server fixes stale signatures on non-persistent desktops

0 Upvotes

If you run Check Point Harmony Endpoint on VMware Horizon or Citrix, you have probably hit one of these two problems.

Scan storms first. A bunch of virtual desktops on the same host all start an anti-malware scan around the same time and the disk and CPU tank for everyone on that host. The fix in VDI is usually to just disable the periodic scan, since a non-persistent desktop is wiped clean on every logout anyway. If you have to keep it, at least randomize the scan time so it spreads across the week.

The second one is stale signatures. Every non-persistent desktop boots from the Golden Image, and the signatures inside that image are frozen at the time you built it. So every morning you get a fresh machine with old signatures, and downloading full signatures on every boot on every desktop would kill the WAN.

The Shared Signature Server is how Check Point handles that. It is a normal Endpoint client running on a persistent VM that becomes a signature server through policy. It keeps the latest anti-malware signatures in a read only shared folder and the non-persistent clients read from it over UNC. If that server goes down, the clients quietly fall back to the Golden Image signatures, so protection keeps running, it just ages until the server is back.

Two things that trip people up. The signature server has to be on a persistent VM, and every endpoint reading from it has to be in the same domain. And not every blade works on non-persistent desktops, FDE is not supported there at all.

I wrote a full deep dive with the cloud Web Management config and the blade support matrix per desktop type, here:

https://community.checkpoint.com/t5/Endpoint/EN-Harmony-Endpoint-in-VDI-Scan-Storms-amp-the-Shared-Signature/m-p/281970


r/checkpoint • • Nov 21 '23

Smaller Tires?

0 Upvotes

Hey guys, my checkpoint is being built by the body shop and I was wondering your thoughts on narrower tires. I will be using this bike on the road 90% of the time in NYC and would like to keep up on road rides


r/checkpoint • • Nov 02 '22

How to uninstall?

0 Upvotes

Can someone pleae help me uninstall checkpoint and all its fucking extensions.I just downloaded the zone alarm program and now i have to deal with this


r/checkpoint • • Oct 31 '19

IP address in URL regex

0 Upvotes

Hi guys,

i want to block IP address in url. Do anyone have good regex which match the IP address in 2 format, ipv4 and ipv6

Thanks!!!!!!


r/checkpoint • • 18d 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 • • Jun 03 '24

Thanks for the downplay

0 Upvotes

r/checkpoint • • Aug 07 '26

Quantum SD-WAN (Check Point) Deeper Technical View of Steering, Policy Matching, and Enforcement

3 Upvotes

Quantum SD-WAN is often introduced as “dynamic WAN link selection.” Technically, it’s closer to a policy-controlled, measurement-driven path selection engine that influences per-connection egress and VPN transport without requiring dynamic routing for the decision itself.

Below is a more technical  walkthrough: what is computed, what is installed, what is enforced, and why “policy looks right” can still produce unexpected paths.

1) What Quantum SD-WAN does (technical thesis)

Quantum SD-WAN enables a Security Gateway / Cluster to select an egress ISP interface or VPN transport per connection based on:

  • Classification (source/destination/identity + service/application)

  • Measured link quality (latency/jitter/loss, optionally utilization)

  • Rule steering intent (prioritization / link aggregation / breakout vs overlay/backhaul)

What it is not: a replacement for routing protocols. Routing still provides reachability; SD-WAN provides path selection logic layered on top of reachability.

Operational implication: you don’t “route to ISP1/ISP2”; you steer sessions to a link/transport chosen by the SD-WAN engine.

 

 

 

 

2) Control plane vs data plane (what owns what)

A useful separation:

Control plane (steering decision + state distribution)

  • SD-WAN policy definition (Infinity Portal)

  • WAN link objects, thresholds, measurement targets

  • SD-WAN steering computation (probes → eligibility → selection)

  • Installation of steering state for enforcement (tables/state on the gateway)

  • Telemetry/event publication (iNext/Nano + cpview)

 

Data plane (packet forwarding + VPN encapsulation)

  • Connection setup and forwarding decisions

  • NAT, access control, IPS/Threat Prevention enforcement

  • VPN encapsulation and transport selection for overlay/backhaul

  • Failover behavior at runtime (within allowed/preferred sets)

Key rule: SD-WAN steering decisions are only applied after Security Policy allows the traffic. SD-WAN cannot “force” a denied flow to go out a different ISP.

3) Simple use case (but with the missing details)

Two ISPs at a branch:

  • Zoom → ISP #1

  • Microsoft 365 → ISP #2

 

What’s happening under the hood is not “PBR in the classical sense,” but:

  • session classification (app/service/identity)

  • link health evaluation against thresholds

  • selection of eligible ISP(s)

  • installation of that choice so the connection setup pipeline uses the correct egress interface

If a failover happens and your policy uses aggregation, per-flow path choice can change due to hashing, even with the same rule.

4) SD-WAN actions (Breakout vs Overlay vs Backhaul) — deeper technical split

A) Local Breakout (Internet egress steering)

  • Goal: choose the best ISP interface for direct Internet traffic.

  • Enforcement point: firewall connection handling chooses a WAN interface based on steering state.

Common failure pattern: app classification ambiguity → wrong rule match → wrong ISP.

B) Overlay (VPN steering between peers)

  • Goal: for each VPN peer pair, select the best VPN transport (underlay link/interface) to carry encrypted traffic.

  • Enforcement point: VPN subsystem chooses the transport for the tunnel/session based on steering state.

Common failure pattern: peers/transport eligibility not installed correctly → VPN uses a default or “last known good” path.

C) Backhaul (branch Internet via HQ over VPN)

  • Composite pipeline:

    • Branch → HQ: overlay transport selection (VPN)

    • HQ → Internet: breakout selection (ISP egress)

  • Troubleshooting must split both legs. People often debug only one side.

5) SD-WAN Policy matching (the real classification mechanics)

An SD-WAN policy is an ordered rulebase. Each connection is evaluated against:

5.1 Source/Destination dimensions

  • IP address / network objects

  • Identity (User / Computer Identity)

  • Destination objects (including Updatable Objects)

5.2 Service/Application dimensions

  • Service ports (HTTPS, FTP, etc.)

  • Application signatures (e.g., Zoom/Teams categories, depending on what is supported and enabled)

5.3 The “first packet problem”

A critical nuance: application identification on the first packet is not always deterministic.
Examples:

  • multiple SaaS apps behind the same IP/CDN

  • TLS where SNI is missing/obfuscated early

  • traffic patterns that require more packets for confident classification

Why this matters: steering is ideally decided at/near connection setup; if classification matures later, you can see:

  • initial steering based on coarse match (destination/service)

  • then “it looks like the app is X” but the session is already pinned to an ISP/transport

 

Best practice (technical reasoning): use Updatable Objects in Destination whenever possible. This increases the chance that the rule matches accurately early (even when application classification is ambiguous).

6) Steering behavior objects (what a rule really controls)

A steering rule is not just “send app X to ISP Y.” It defines:

  1. Measurement targets What is probed to represent “Internet quality” or “reachability” per link.

  2. Quality criteria + thresholds Latency, jitter, loss (and potentially utilization) thresholds that determine link eligibility.

  3. Selection method

    • Prioritization: pick the best/priority candidate among eligible links/transports

    • Link aggregation: mark multiple candidates as eligible; per-flow selection may be done by hashing/aggregation method

Important: eligibility comes first. If all links fail thresholds, the result can be “no eligible ISP/transport,” which is often misread as “SD-WAN is broken” when it is behaving correctly.

7) Steering criteria (deeper look)

Latency / jitter / loss

  • Typically measured via active probing (quality check) to one or more targets.

  • Decision is per rule: different apps can have different thresholds.

WAN utilization (when used)

  • Adds a capacity dimension: a link could be “healthy” but saturated, so it becomes less preferred.

  • This is often where teams need to align with business intent: latency-sensitive apps vs bulk traffic.

Quality Check configuration (where mistakes happen)

Even with a perfect policy, poor probing design causes bad decisions:

  • probing targets not representative (e.g., a single target that’s sometimes rate-limited)

  • too infrequent probing → slow reaction

  • too aggressive probing → noise/false degradation

  • thresholds that don’t match realistic ISP behavior

8)Enablement workflow (what must exist where) — more explicit

To have deterministic steering, you need consistency across four planes:

8.1 Gateway / Cluster members

  • SD-WAN interfaces configured consistently on all members

  • correct WAN link binding (interface mapping)

  • Nano Agent + SD-WAN services healthy (where applicable)

  • consistent reachability (routing) for probe targets and peer endpoints

8.2 SmartConsole / Security Policy

  • Access Control must allow the traffic that you expect SD-WAN to steer

  • NAT rules must not accidentally “force” an egress path (e.g., implicit NAT assumptions)

  • VPN domain/topology must align with overlay/backhaul design

8.3 Smart-1 Cloud (objects/management integration)

  • objects exist and are synchronized correctly (depending on architecture)

8.4 Infinity Portal (SD-WAN policy plane)

  • WAN links, thresholds, measurement targets

  • SD-WAN Policy ordering and steering objects

  • consistent gateway membership / profile assignment

Takeaway: “policy is correct” is meaningless unless:

  • the gateway installed it

  • probing data exists

  • steering state is installed and consumed by enforcement

9) Practical validation checklist (technical, not UI-based)

When you get “wrong ISP / wrong overlay path,” validate in this order:

  1. Traffic classification

    • What rule is actually matching (source/dest/service/app/identity)?

    • Is first-packet ambiguity likely?

  2. Probing and thresholds

    • Do you have current probe results for the relevant decision?

    • Are links eligible under the rule thresholds?

  3. Selection mode

    • Prioritization vs link aggregation changes expectations.

    • With aggregation, per-flow hash choice can look “random” to operators.

  4. Enforcement pipeline alignment

    • Breakout: FW chooses ISP from steering state

    • Overlay/backhaul: VPN chooses transport from steering state

  5. State/telemetry consistency

    • Portal events (iNext/Nano) should align with gateway telemetry (cpview) and observed behavior.

10) Common pitfalls (why steering “looks wrong”)

  • Thresholds too strict → all links disallowed → fallback behavior or failure

  • Single probe target bias → false positives/negatives on link health

  • Rule ordering mistakes → coarse rule matches before specific one

  • Application detection timing → session pinned before app becomes known

  • Aggregation misunderstanding → multiple links eligible, hash decides per-flow

  • Backhaul confusion → people troubleshoot HQ egress while the problem is branch→HQ overlay (or vice-versa)

Fontes: Quantum SD-WAN - Technical | eLearning https://checkpointpartners.litmoseu.com/course/1588097 , 

Admin Guide:  https://support.checkpoint.com/results/sk/sk180605

Demo Point: SD-WAN https://usercenter.checkpoint.com/ucapps/techpoint/demo-point


r/checkpoint • • Aug 07 '26

VIDEO: Complete Check Point Hardware Diagnostic Execution

2 Upvotes

If you find this useful, please consider giving the original CheckMates post a like! 😊
Full post: https://community.checkpoint.com/t5/Firewall-and-Security-Management/VIDEO-Complete-Check-Point-Hardware-Diagnostic-Execution/m-p/280847#M106475

I believe many people have already run the Hardware Diagnostic, but I also believe many have never done it. Since I was performing a complete Hardware Diagnostic on a Quantum Force 9800 cluster that I will be deploying, I decided to record this video to help others by going beyond what is covered in the official guide.

In this video, I demonstrate the complete Hardware Diagnostic process using loopback connectors, show what happens if something is done incorrectly, and explain the entire procedure step by step.

ISSUE FOUNDED TO SAVE HW LOG: I also present an issue that I have observed on recent Quantum Force versions. I have installed Quantum Force 9000, 19000, and 29000 firewalls, and none of them have been able to save the Hardware Diagnostic results to the USB drive at the end of the test, even when using a FAT32-formatted USB drive as described in the documentation.

I hope this video is helpful. I used all of my English for it (haha), so if you find it useful, please leave a like on the video and give this post a Kudos to encourage me to continue creating and sharing this kind of content.


r/checkpoint • • Jul 04 '22

Is there a reason why most deployments I've come across have Drop TCP Out-of-state disabled?

0 Upvotes

From my understanding, this is checked to drop any TCP packets that does not match to any session (first non-SYN), which is caused by possible asymmetric routing in the network.

This is the default behaviour for stateful firewalls. However, for most Check Point ClusterXL and Maestro Hyperscale deployment I've come across, have this disabled in production.

I've never seen a good reason to this, for other vendors (Palo Alto, FortiGate and even the open source -sense). Even Check Point has this enabled by default.


r/checkpoint • • Oct 21 '25

Checkpoint for individual

0 Upvotes

Do individuals can purchase Checkpoint infinity portal? I'm not talking about evaluation license.

Looking to configure my testing lab using CP mxdr aswell.

Please let me know the way. Been trying for a while without success.

Would appreciate the help :)


r/checkpoint • • Apr 25 '25

ClusterXL in load sharing mode is not supported with IPsec VpN

Post image
0 Upvotes

Hi team, any workaround to fix this


r/checkpoint • • Jun 12 '26

Harmony SASE client issue with 3rd party clients

0 Upvotes

Hello everyone,

Has anyone experienced client issues (such as frequent "Reconnecting" events) when using third-party clients in parallel, such as WatchGuard? That's the client currently causing me some problems.

Do you have any solutions or ideas, other than the usual "it's by design" explanation?

Thanks!


r/checkpoint • • Feb 01 '24

Friends, does anyone have the latest firmware for checkpoint utm-1 (edge ​​1)x, n, w?

0 Upvotes

r/checkpoint • • Jun 14 '24

Appliance 1600 unreachable

0 Upvotes

Hello everyone, Here is my appliance 1600. Unreachable After configuring user-awareness. Can i have your help please ?


r/checkpoint • • Jun 22 '22

Check Point Cloud Design

0 Upvotes

Hi Guys,

So my sister company planning shifting some apps on cloud, and decided using between GCP or AWS.

If i used Check Point firewall as Perimeter Firewall on GCP or AWS as SSLVPN and authentication using LDAP (which is on premise), is it still possible?

The problem is, i dont have direct communication (ipsec is not available) from cloud to onprem solution to integrated LDAP with Check Point firewall. Do you guys any suggestion?

Tl;dr :

  • User --SSLVPN--> Checkpoint on GCP/AWS --> Access local resource on cloud.

  • Auth for SSLVPN using LDAP which is on onprem area

  • how to connected CP with onprem LDAP?

Merci!


r/checkpoint • • Apr 26 '19

Checklist

0 Upvotes

Dear all,

can we create auto checklist of all the firewalls??