Skip to content

Check Point Software Technologies Ltd.

Vulnerability disclosure program on security.txt checkpoint.com

Accepting reports security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Replies within 3 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No No monetary or other rewards are granted in connection with such reports.
Response
Within 3 days Within 3 business days, we will acknowledge that your report has been received.
Safe harbor
Partial Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing, unless specifically approved by Check Point in writing
Hall of fame
Yes Upon request and subject to our review, we may acknowledge individuals who report security vulnerabilities to us through sk142952 – Check Point Products Acknowledgments .

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 2 excluded.

Domains 2

  • checkpoint.com
  • check point’s owned domains (e.g. www.checkpoint.com)

Products and areas 1

  • Check Point Products
Out of scope (2)
  • Any service not expressly listed above, such as any connected services
  • vulnerabilities found in systems from our vendors

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Check Point Software Technologies Ltd.'s policy. "We" in these lines means the program, not this site.

While testing

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence.
  • Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Please keep the vulnerability confidential until we officially announce a resolution.
  • Do not submit a high volume of low-quality reports.

Not accepted

  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 3 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.