CheckPointXDR

Fetch and manage incidents from Check Point XDR.

Analytics & SIEM · Check Point XDR

Details

IDCheckPointXDR
ProviderCheckPoint Software Technologies
CategoryAnalytics & SIEM
From Version6.10.0
Docker Imagedemisto/python3:3.12.13.10116658

README

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.
1. Navigate to SettingsIntegrationsServers & Services.
2. Search for Check Point XDR and click Add instance.
3. Configure the following parameters:

| **Parameter**         | **Description**                                                                                |
|-----------------------|-----------------------------------------------------------------------------------------------|
| Base URL              | Default: `https://cloudinfra-gw.portal.checkpoint.com`                                        |
| Client ID             | Your Check Point XDR API Client ID                                                            |
| Access Key            | Your Check Point XDR API Access Key                                                           |
| First fetch time      | Format: `3 days`, `2 hours`, etc. Determines the starting point of the initial fetch.         |
| Max fetch             | Maximum number of incidents to fetch per API call (default recommended: 50-100)              |
| Fetch incidents       | Enable to allow scheduled fetching of incidents                                               |
| Trust any certificate | Disable SSL validation (not recommended for production environments)                          |
| Use system proxy      | Use 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

Path Type Description
incident.name string Incident name
incident.type string Incident type
incident.severity number Incident severity
incident.occurred date Incident timestamp
incident.xdrstatus string Incident status
incident.xdrid string Unique ID of the incident
incident.insights string Associated insights
incident.assets string Affected assets
incident.mitre string MITRE 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 Name Description Required
remoteId The ID of the incident in Check Point XDR. True
data The fields to update (status, owner, etc). True
entries Entries (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

Field Description
xdrid Unique identifier of the incident
xdrstatus Current status (e.g. New, In Progress, Resolved)
severity Incident severity mapped to XSOAR levels
summary Short summary of the incident
insights Detailed related alerts and context
assets Affected hosts, users, and services
mitre Associated 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.

Configuration parameters

  • url — Infinity XDR API URL (required)
  • credentials — Client ID (required)
  • insecure — Trust any certificate (not secure)
  • proxy — Use system proxy settings
  • first_fetch — First fetch time
  • isFetch — Fetch incidents
  • incidentFetchInterval — Incidents Fetch Interval
  • incidentType — Incident type
  • max_fetch — Maximum number of incidents per fetch
  • close_out — Close Mirrored XDR Incidents
  • mirror_direction — Incident Mirroring Direction

Commands (1)

  • get-mapping-fields

    Returns the list of fields to map in outgoing mirroring. This command is only used for debugging purposes.

category: Analytics & SIEM
provider: CheckPoint Software Technologies
sectionorder:
- Connect
- Collect
commonfields:
  id: CheckPointXDR
  version: -1
configuration:
- section: Connect
  display: Infinity XDR API URL
  name: url
  defaultvalue: "https://cloudinfra-gw.portal.checkpoint.com"
  type: 0
  required: true
- section: Connect
  display: Client ID
  displaypassword: Access Key
  name: credentials
  type: 9
  required: true
- section: Connect
  advanced: true
  display: Trust any certificate (not secure)
  name: insecure
  type: 8
  required: false
- section: Connect
  advanced: true
  display: Use system proxy settings
  name: proxy
  type: 8
  required: false
- section: Collect
  display: First fetch time
  additionalinfo: First insight updated date to fetch. e.g., "24 hours", "7 days", "1 month"
  name: first_fetch
  defaultvalue: 3 days
  type: 0
  required: false
- section: Collect
  advanced: true
  display: Fetch incidents
  name: isFetch
  defaultvalue: 'true'
  type: 8
  required: false
- section: Collect
  display: Incidents Fetch Interval
  name: incidentFetchInterval
  defaultvalue: "10"
  type: 19
  required: false
- section: Collect
  display: Incident type
  name: incidentType
  required: false
  type: 13
  defaultvalue: "Check Point XDR Incident"
- section: Collect
  display: Maximum number of incidents per fetch
  name: max_fetch
  defaultvalue: "1000"
  type: 0
  required: false
- additionalinfo: Outgoing Mirroring - when selected, closing the Cortex XSOAR incident is mirrored in XDR.
  defaultvalue: 'false'
  display: Close Mirrored XDR Incidents
  name: close_out
  type: 8
  section: Collect
  advanced: true
  required: false
- additionalinfo: 'Choose the direction to mirror the incident: Incoming (from XDR to Cortex XSOAR) - currently not supported, Outgoing (from Cortex XSOAR to XDR), or Incoming and Outgoing (Incoming currently not supported).'
  defaultvalue: None
  display: Incident Mirroring Direction
  name: mirror_direction
  options:
  - None
  - Incoming
  - Outgoing
  - Incoming And Outgoing
  type: 15
  hidden:
  - marketplacev2
  required: false
  section: Collect
description: Fetch and manage incidents from Check Point XDR.
display: 'Check Point XDR'
name: CheckPointXDR
script:
  commands:
  - arguments: []
    deprecated: false
    description: Returns the list of fields to map in outgoing mirroring. This command is only used for debugging purposes.
    execution: false
    name: get-mapping-fields
  isfetch: true
  script: '-'
  subtype: python3
  type: python
  ismappable: true
  isremotesyncin: true
  isremotesyncout: true
  dockerimage: demisto/python3:3.12.13.10116658
defaultmapperin: CheckPointXDR_Incoming_Mapper
defaultmapperout: CheckPointXDR_Out_Mapper
fromversion: 6.10.0
tests:
- No tests (auto formatted)