CrowdStrike Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

CrowdStrike is cloud-delivered endpoint protection. CrowdStrike Falcon unifies next-generation antivirus, endpoint detection and response (EDR), and a 24/7 threat-hunting service — all delivered via a single lightweight agent.

Tip: For more information on how third-party integrations work, see Connectors.

Connector Details

Tenable Exposure Management ingests CrowdStrike devices and vulnerabilities through API.

Details Description

Supported products

CrowdStrike Falcon

Category

Endpoint Security

Ingested data Assets and Findings

Ingested Asset Classes

Device

Integration type

UNI directional (data is transferred from the connector to Tenable Exposure Management in one direction)

Supported version and type

SaaS (latest)

Prerequisites and User Permissions

Before you begin configuring the connector, make sure you have the following:

Generate Credentials

Some CrowdStrike accounts are divided into multiple customers, with multiple CIDs, each customer has its own CID. The CIDs are arranged in a parent/child (member) hierarchy. A parent CID has access to all of the account's hosts, including those associated with its child CIDs. Only the child CID has access to its own host groups and vulnerabilities.

Note: Ensure you create the API Client using the appropriate user.

To generate API and Secret keys:

  1. Navigate to the CrowdStrike console.

  2. Click Menu > Support and resources.

  3. In the Support and resources menu, select API clients and keys.

  4. In the upper-right corner of the page, click Add new API client.

  5. In the Client name and description section, type the appropriate information.

  6. In the API Scopes section, configure the following permissions (if available):

    • Hosts: Read

    • Hosts groups: Read

    • Spotlight vulnerabilities: (read)

  7. Click Add.

    Crowdstrike generates the API client information.

  8. Copy and save the CLIENT ID, SECRET and BASE URL.

Add a Connector

To add a new connector:

  1. In the left navigation menu, click Connectors.

    The Connectors page appears.

  2. In the upper-right corner, click Add new connector.

    The Connector Library appears.

  3. In the search box, type the name of the connector.

  4. On the tile for the connector, click Connect.

    The connector configuration options appear.

Configure the Connector

To configure the connector:

  1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

  2. In the API Url section, select the radio button for the URL that matches your Base URL.

    • EU_1 — api.eu-1.crowdstrike.com

    • US_1 — api.crowdstrike.com

    • US_2 — api.us-2.crowdstrike.com

    • US_GOV_1 — api.laggar.gcw.crowdstrike.com

  3. In the Client ID and Client Secret text boxes, enter the credentials you generated earlier.

  4. Data pulling configuration: This configuration has dynamic settings tailored to the specific connector and integration type. Below are the configurations relevant to this connector.

    • From the Crowdstrike product type fetching drop-down, select the product type you want to fetch data from.

    • For the "Fetch Spotlight vulnerability information" checkbox, consider the following:

      • If your CrowdStrike subscription does not include Spotlight, make sure to clear this checkbox. Enabling it without Spotlight access may result in incomplete or failed data ingestion.

      • If you own both EDR and Spotlight, leave the checkbox selected to include vulnerability data from Spotlight.

    • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

      Tip: For more information, see Asset Retention.

  5. In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.

    • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.

    • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.

  6. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

    Tip: For more information, see Connector Scheduling

  7. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.

  8. To confirm the sync is complete, do the following:

Crowdstrike in Tenable Exposure Management

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

  1. In Tenable Exposure Management, navigate to the Assets page.

  2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

    The asset list updates to show only assets from the selected connector.

  3. Click on any asset to view Asset Details.

Locate Connector Weaknesses in Tenable Exposure Management

As the connector discovers weaknesses, Tenable Exposure Management ingests those weaknesses for reporting.

To view weaknesses by connector: 

  1. In Tenable Exposure Management, navigate to the Weaknesses page.

  2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view weaknesses.

    The weaknesses list updates to show only weaknesses from the selected connector.

  3. Click on any weakness to view Weakness Details.

Locate Connector Findings in Tenable Exposure Management

As the connector discovers individual findings, Tenable Exposure Management ingests those findings for reporting.

To view findings by connector:

  1. In Tenable Exposure Management, navigate to the Findings page.

  2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view findings

    The findings list updates to show only assets from the selected connector.

  3. Click on any asset to view Finding Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Device Mapping

Tenable Exposure Management UI Field

CrowdStrike Field
Unique Identifier device_id

Asset - External Identifier or

Asset - Provider Identifier

 instance_id
Asset - Name hostname or ip
Class Host

Asset - IPv4 Adresses

Asset - IPv6 Adresses

external_ip

local_ip
Asset - First Observation Date first_seen
Asset - Last Observed At last_seen
Asset - MAC Addresses mac_address

Asset - External Tags

tags

cid

product_type_desc

machine_domain
Asset Custom Attributes

major_version.minor_version

containment_status

device_id

os_build

kernel_version

Findings Mapping

Tenable Exposure Management UI Field

CrowdStrike Field
Unique Identifier id
Finding Name cve.id
CVEs cve.id
CWEs cve.cwe
Severity Driver cve.base_score or cve.severity
Description cve.description
Finding Custom Attributes

cve.vector

cve.exprt_rating

cid

aid

id

cve.severity

cve.references

cve.vendor_advisory
First Seen created_timestamp
Last seen (Observed) updated_timestamp

Finding Severity Mapping

Tenable Exposure Management Severity

[Connector] Score

Critical

CVSS: 9.0 - 10.0

Severity: Critical

High

CVSS: 7.0 - 8.9

Severity: High

Medium

CVSS: 4.0 - 6.9

Severity: Medium

Low

CVSS: 1-3.9

Severity:Low

None

CVSS:0

Severtity: Information

Note:For CrowdStrike, Tenable uses the cve.base_score field to determine severity. If cve.base_score is not available, Tenable uses the cve.severity field from the connector, if provided.

Finding Status Mapping

Tenable Exposure Management Status

CrowdStrike Status

Active

open

reopen

Fixed

closed

is_suppressed

expired

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

Update Type in Exposure Management

Mechanism (When?)

Archiving Assets

  • Asset that appears in Tenable Exposure Management and isn't returned on the next connector's sync.

Change a Finding status from "Active" to "Fixed"

  • Finding status changes to closed on the vendor's side
Note: Updates on the vendor side are reflected in Tenable Exposure Management only when the next scheduled connector sync time is complete (once a day).

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip: To learn more about data deduplication and uniqueness criteria, See Third-Party Data Deduplication in Tenable Exposure Management

The uniqueness criteria for this connector are as follows:

Data

Uniqueness Criteria

Asset

device_id

Detection SecAlerts

Finding

id

API Endpoints in Use

API

Use in Tenable Exposure Management

Permissions required

https://{api_url}/oauth2/token

Generate access tokens for running other APIs

None

https://{api_url}/devices/queries/devices/v1

Collect host IDs for running other APIs

Hosts (read)

https://{api_url}/devices/entities/devices/v2

Assets (Devices)

Hosts (read)

https://{api_url}/devices/combined/host-groups/v1

Asset enrichment

Hosts groups (read)

https://{api_url}/devices/queries/host-group-members/v1

Asset enrichment

Hosts groups (read)

https://{api_url}/spotlight/combined/vulnerabilities/v1

Detections and solutions

Spotlight vulnerabilities (read)

Data Validation

This section shows how to validate and compare data between Tenable Exposure Management and the CrowdStrike platform.

Asset Data Validation

Objective: Ensure the number of endpoints (devices) in CrowdStrike aligns with the number of devices displayed in Tenable Exposure Management. Every managed asset in Crowdstrike should appear as a device in Exposure Management.

In CrowdStrike:

  1. Navigate to the Managed Assets tab.

    Note the number of assets.

In Tenable Exposure Management:

  1. Locate your connector assets.

  2. Compare the total number of assets between CrowdStrike and Tenable Exposure Management.

Expected outcome: The total numbers returned in CrowdStrike and Exposure Management should match.

If an asset is not visible in Exposure Management, check the following conditions:

  • The asset was archived because it did not return in the connector's last sync.

    Tip: To learn more on how assets are archived and findings change status, see Status Update Mechanisms.

Finding Data Validation

Objective: Ensure the number of vulnerabilities in CrowdStrike aligns with the number of findings in Tenable Exposure Management.

In CrowdStrike:

  1. Navigate to Vulnerabilities.

    Note the number of vulnerabilities.


In Tenable Exposure Management:

  1. Locate your connector findings.

  2. Compare the total number of findings between CrowdStrike and Tenable Exposure Management.

Expected outcome: The total numbers returned in CrowdStrike and Exposure Management should match

If a finding is missing from Exposure Management or no longer active, check the following conditions:

  • The finding is marked as Fixed and appears under the Fixed state on the Findings screen

  • The finding no longer appears because its related asset was archived.

    Tip: To learn more on how assets are archived and findings change status, see Status Update Mechanisms.