Init Checkpoint HEC SOAR content hub

[chkp-arvidb]

Required items, please complete

Change(s):

• Add Checkpoint Sentinel Content Hub solution that will contain DCR/DCE, custom table, analytics rules, and playbooks

Reason for Change(s):

• Solution does exist

Version Updated:

• No

Testing Completed:

• Yes

Checked that the validations are passing and have addressed any issues that are present:

• Need Help

[v-shukore]

Hi @chkp-arvidb,
Please accept CLA.
Please share running screenshots for the CCF data connector and azure functions.

Also, please address the failed validation checks.

To fix CodeQL validation update this branch with master and commit.

Please fix Arm-ttk failure it's giving unreferenced variable error as mentioned in screenshot below.

To resolve the KQL validation failures, ensure that:
All table schemas used in the content are also present in the below location.
https://github.com/Azure/Azure-Sentinel/tree/master/.script/tests/KqlvalidationsTests/CustomTables

All columns referenced in the queries are defined in the corresponding table schemas.

To fix Detectiontemplateschema validation, add the requiredDataConnectors property to the Analytic Rule.

It appears that the playbook images are missing from the Playbook folder. Kindly create images folder into Playbook folder and add images that demonstrate the playbook in action. You can refer to the structure used in the "CiscoUmbrella" solution in the GitHub repository.

Also, please ensure that the data file version is set to 3.0.0, and include a releasenotes.md file for this solution. You may refer to any existing solution in the repository as a reference.

Thanks!!

[v-shukore]

Hi @chkp-arvidb, any update on the above comment. Thanks!!

[v-shukore]

Hi @chkp-arvidb, any update on the above comment. Thanks!!

[chkp-arvidb]

@chkp-arvidb please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

1. **Definitions**.
   **“Code”** means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   **“Project”** means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative ([www.opensource.org](http://www.opensource.org)).
   **“Submit”** is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   **“Submission”** means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.

2. **Your Submission**. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.

3. **Originality of Work**. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.

4. **Your Employer**. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.

5. **Licenses**.


* **Copyright License**. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.

* **Patent License**. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.

* **Other Rights Reserved**. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.


6. **Representations and Warranties**. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

7. **Notice to Microsoft**. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.

8. **Information about Submissions**. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.

9. **Governing Law/Jurisdiction**. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.

10. **Entire Agreement/Assignment**. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="CheckPoint Software"

[chkp-christiang]

Hi @v-shukore, @chkp-arvidb had to take some time off.

Please share running screenshots for the CCF data connector and azure functions.

Can you please help me understand what are the expected screenshots here?, perhaps an example?. Thanks in advance.

[chkp-arvidb]

screenshot of the Connector, DCE, DCR and log table

[v-shukore]

Hi @chkp-arvidb, please resolve validations checks as mentioned in screenshots below. Thanks!

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds the initial Microsoft Sentinel Content Hub solution scaffolding for “Checkpoint Harmony Email and Collaboration”, including solution metadata/release notes, a SOAR playbook, analytic rule + hunting queries, and supporting Azure Functions code.

Changes:

• Added Solution metadata and ReleaseNotes for the new solution.
• Added a Quarantine playbook template and supporting Azure Functions (Quarantine/Restore + API clients).
• Added one scheduled analytic rule and five hunting queries targeting the custom CheckpointHEC_CL table.

Reviewed changes

Copilot reviewed 26 out of 29 changed files in this pull request and generated 19 comments.

Show a summary per file

File	Description
Solutions/Checkpoint Harmony Email and Collaboration/SolutionMetadata.json	Defines Content Hub metadata (publisher/offer/support/categories) for the solution
Solutions/Checkpoint Harmony Email and Collaboration/ReleaseNotes.md	Adds initial release notes entry for version 3.0.0
Solutions/Checkpoint Harmony Email and Collaboration/Playbooks/Quarantine/quarantine.json	Adds a Sentinel-incident-triggered playbook intended to quarantine emails via an Azure Function
Solutions/Checkpoint Harmony Email and Collaboration/Package/testParameters.json	Ignored per repo guidelines (Solutions//Package/)
Solutions/Checkpoint Harmony Email and Collaboration/Package/mainTemplate.json	Ignored per repo guidelines (Solutions//Package/)
Solutions/Checkpoint Harmony Email and Collaboration/Package/createUiDefinition.json	Ignored per repo guidelines (Solutions//Package/)
Solutions/Checkpoint Harmony Email and Collaboration/Hunting Queries/CheckpointPhishing.yaml	Adds hunting query for phishing counts
Solutions/Checkpoint Harmony Email and Collaboration/Hunting Queries/CheckpointHighConfidenceSpam.yaml	Adds hunting query for spam counts
Solutions/Checkpoint Harmony Email and Collaboration/Hunting Queries/CheckpointEventRecapLastDay.yaml	Adds hunting query summarizing events in last 24 hours
Solutions/Checkpoint Harmony Email and Collaboration/Hunting Queries/CheckpointEventPerUser.yaml	Adds hunting query pivoting event categories per user
Solutions/Checkpoint Harmony Email and Collaboration/Hunting Queries/CheckpointDLPEvent.yaml	Adds hunting query for DLP detections detail
Solutions/Checkpoint Harmony Email and Collaboration/Data/Solution_Checkpoint HEC.json	Declares solution package composition (data connector, rules, queries, playbook)
Solutions/Checkpoint Harmony Email and Collaboration/Data Connectors/CheckpointHEC_Table.json	Ignored per repo guidelines (Solutions//Data Connectors/)
Solutions/Checkpoint Harmony Email and Collaboration/Data Connectors/CheckpointHEC_PollingConfig.json	Ignored per repo guidelines (Solutions//Data Connectors/)
Solutions/Checkpoint Harmony Email and Collaboration/Data Connectors/CheckpointHEC_Definition.json	Ignored per repo guidelines (Solutions//Data Connectors/)
Solutions/Checkpoint Harmony Email and Collaboration/Data Connectors/CheckpointHEC_DCR.json	Ignored per repo guidelines (Solutions//Data Connectors/)
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/utils/client.py	Adds API clients used by Azure Functions for quarantine/restore actions
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/requirements.txt	Adds Python dependencies for the Azure Functions connector
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/local.settings.json	Adds local dev settings for Azure Functions
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/host.json	Adds Azure Functions host settings
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/Restore/function.json	Adds Restore HTTP-triggered function binding
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/Restore/init.py	Implements Restore action dispatcher
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/Quarantine/function.json	Adds Quarantine HTTP-triggered function binding
Solutions/Checkpoint Harmony Email and Collaboration/AzureFunctions/Quarantine/init.py	Implements Quarantine action dispatcher
Solutions/Checkpoint Harmony Email and Collaboration/Analytic Rules/CheckpointHECPhishingNotQuarantined.yaml	Adds a scheduled analytic rule for pending phishing emails
.script/tests/KqlvalidationsTests/CustomTables/CheckpointHEC_CL.json	Adds custom table schema for KQL validation tests

[v-shukore]

Hi @chkp-arvidb, please update suggested changes suggested by the copilot and commit the changes also validation is failing due to below error please do needful. Thanks!

[chkp-arvidb]

Hi @chkp-arvidb, please update suggested changes suggested by the copilot and commit the changes also validation is failing due to below error please do needful. Thanks!

Hey @v-shukore , how would i resolve this and get a unique ID for the connector