Skip to main content

Check Point XDR

This Integration is part of the Check Point XDR Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.10.0 and later.

Check Point XDR Integration#

The Check Point XDR (Extended Detection and Response) integration allows you to connect to Check Point's CloudInfra platform to fetch and manage incidents. This integration enables you to retrieve incidents from Check Point XDR, convert them into Cortex XSOAR format, and manage them effectively within your security operations workflows.

Key Features#

  • Authentication: Secure OAuth2-based authentication using Client ID and Access Key.
  • Incident Fetching: Retrieve incidents from Check Point XDR using flexible parameters such as timestamp and limit.
  • Data Mapping: Automatically map Check Point fields such as severity, status, summary, and insights into XSOAR incident fields.
  • Custom Fields Support: Includes mapping for MITRE ATT&CK techniques, assets, and alerts.
  • Pagination Support: Automatically fetches additional pages of incidents if the result size equals the max_fetch parameter.
  • Insights & Enrichment: Include related context such as associated users, endpoints, and threat intelligence.

Prerequisites#

  • A valid Check Point XDR account with API access enabled.
  • API credentials:
    • Client ID
    • Access Key
  • Cortex XSOAR version 6.10.0 or higher.

Use Cases#

  • Ingest Check Point XDR alerts and incidents into XSOAR for automated playbook-driven response.
  • Correlate assets, users, and threats across your SOC toolset.
  • Perform enrichment using insights and threat classifications included in the XDR data.
  • Monitor status and severity changes and trigger escalation or remediation workflows.

Setup Instructions#

    1. Navigate to Settings โ†’ Integrations โ†’ Servers & Services.

    2. Search for Check Point XDR and click Add instance.

    3. Configure the following parameters:

      ParameterDescription
      Base URLDefault: https://cloudinfra-gw.portal.checkpoint.com
      Client IDYour Check Point XDR API Client ID
      Access KeyYour Check Point XDR API Access Key
      First fetch timeFormat: 3 days, 2 hours, etc. Determines the starting point of the initial fetch.
      Max fetchMaximum number of incidents to fetch per API call (default recommended: 50-100)
      Fetch incidentsEnable to allow scheduled fetching of incidents
      Trust any certificateDisable SSL validation (not recommended for production environments)
      Use system proxyUse the system proxy defined in Cortex XSOAR settings
  1. Test the Integration:

    • Click the "Test" button to verify the connection and configuration.
  2. Fetch Incidents:

    • Enable the "Fetches incidents" option to allow the integration to periodically fetch incidents from Check Point XDR.

Commands#

fetch-incidents#


Fetches incidents from Check Point XDR and converts them into Cortex XSOAR format.

Base Command#

fetch-incidents

Input#

This command uses the parameters from the integration instance configuration:

  • First fetch time
  • Max fetch

Context Output#

PathTypeDescription
incident.namestringIncident name
incident.typestringIncident type
incident.severitynumberIncident severity
incident.occurreddateIncident timestamp
incident.xdrstatusstringIncident status
incident.xdridstringUnique ID of the incident
incident.insightsstringAssociated insights
incident.assetsstringAffected assets
incident.mitrestringMITRE TTPs

Human Readable Output#

โœ… Successfully fetched X incidents.


get-mapping-fields#


Returns the fields available for mapping incoming incidents to Cortex XSOAR fields.

Base Command#

get-mapping-fields

Input#

None

Context Output#

The fields available in XSOAR for incident mapping.

Command Example#

!get-mapping-fields

Human Readable Output#

Displays the supported incident fields for mapping from Check Point XDR.


update-remote-system#


Sends updates from Cortex XSOAR to the corresponding incident in Check Point XDR, such as status changes or ownership updates.

Base Command#

update-remote-system

Input#

Argument NameDescriptionRequired
remoteIdThe ID of the incident in Check Point XDR.True
dataThe fields to update (status, owner, etc).True
entriesEntries (comments, notes) to be pushed.Optional

Context Output#

There is no context output for this command.

Command Example#

!update-remote-system

Human Readable Output#

โœ… Remote incident successfully updated.


Incident Fields#

FieldDescription
xdridUnique identifier of the incident
xdrstatusCurrent status (e.g. New, In Progress, Resolved)
severityIncident severity mapped to XSOAR levels
summaryShort summary of the incident
insightsDetailed related alerts and context
assetsAffected hosts, users, and services
mitreAssociated MITRE ATT&CK tactics and techniques

Example Use Case#

  1. Authenticate with Check Point XDR using your client credentials.
  2. Fetch incidents from Check Point XDR based on the specified date and limit.
  3. Convert the incidents into Cortex XSOAR format, including custom fields for insights, alerts, and assets.
  4. Manage and respond to incidents directly within Cortex XSOAR.

Troubleshooting#

  • Authentication Errors: Ensure the Client ID and Access Key are correct and have the necessary permissions.
  • No Incidents Fetched:
  1. Verify the date range parameter is long enough (so there are incidents to fetch).
  2. Verify the limit parameter in the integration configuration is higher then 0.
  3. Verify your client Id and Access key are correct - copy them from the XDR portal under your settings.
  4. Verify the Fetch Incidents checkbox is cheked.
  • SSL Errors: If SSL verification is enabled, ensure the base URL uses a valid SSL certificate.

Additional Resources#

Support#

For support, please contact Check Point or your system administrator.