Skip to main content

Outline

Introduction

The CrowdStrike Exposure Management (EM) integration in SAFE is a consolidated integration that ingests data across the following modules using CrowdStrike APIs:

  • Falcon EDR (Endpoint Detection & Response)
  • Spotlight VM (Vulnerability Management)
  • Discover (Asset Inventory & Software Visibility)

Safe automatically identifies which of these modules are licensed and accessible based on your API credentials and permissions, streamlining the onboarding process.

Note: Discover ingestion is currently triggered only when vulnerability data from Spotlight is not fetched (for example, due to insufficient permissions or module unavailability). If Spotlight vulnerability ingestion runs successfully, Discover data is not ingested in the same cycle.

What SAFE Imports from CrowdStrike

SAFE imports the following security data from CrowdStrike.

Source Data Ingested
Falcon Hostname, IP, MAC, OS and kernel, BIOS version and vendor, serial number, manufacturer and model, platform, asset type (Server / Workstation / Domain Controller), Falcon sensor version, first/last seen, Active Directory domain, tags (Falcon tags, site, host group, OU, policy and sensor states, AD domain).
Spotlight CVE, severity, status, first/last detected, affected software (name, vendor, version), CrowdStrike's recommended remediation and fix version, end-of-life flag for software CrowdStrike reports as unsupported.
Discover Installed software name, vendor, version (only when Spotlight is unavailable).

Prerequisites and Permissions

You need the following connection details to establish the SAFE-CrowdStrike connection.

  • CrowdStrike URL

  • Client ID

  • Client Secret

Note: To create API clients and secrets, you must have a Falcon Administrator role in CrowdStrike. The API client secret value is only shown when a new API client is created or while resetting it.

Generate Connection Details

Follow the below step-by-step procedure to get the connection details:

  1. Login to your CrowdStrike instance.

  2. Navigate to the Support and resources > API Clients and Keys (Under Resources and tools).

  3. Under OAuth2 API clients, click the Create API Client. It opens an API scope view.

  4. Enter the details Client Name and Description.

  5. Select the Read and/or Write boxes next to a scope to enable access to its endpoints.

  6. At least one scope must be assigned.

  7. Select the scopes as read:hosts, read:vulnerabilities, and read:discover.

  8. Click the Create button.

  9. The system displays the connection details (URL, Client ID, and Client Secret). Copy connection details somewhere, it will be needed at the time configuring connector in Safe Platform.

Permissions
Permissions

Configure Crowdstrike Integration in SAFE

After completing the prerequisites, follow these steps to configure Crowdstrike connector into Safe Platform.

  1. Login to SAFE as admin and navigate to Knowledge Graph > First Party > Integrations.

  2. Click on the + icon and search for Crowdstrike Exposure Management.

  3. Click the Crowdstrike Exposure Management card.

  4. Enter a unique name for the integration.

  5. Enter the CrowdStrikeURL, Client ID, and Client Secret.

  6. Enter the API Filter in CrowdStrike FQL format. Example, product_type_desc:['Server'], product_type_desc:'Workstation'.

  7. Enter a value in days for the Asset Last seen days filter field. This is the maximum allowed age of assets (in days) while populating the data from the source.

  8. Click the Test Connection.

  9. Once the connection is verified, click Save.

  10. Click the Sync Now to trigger an on-demand sync.

Configuration page

View Result

To view the assets and the assessment result:

  1. From the Integrations page, Click on Crowdstrike card.

  2. A page with “Finding View” and “Asset View” tabs will open up.

  3. Finding view will contain all the findings pulled from Crowdstrike.

  4. Asset view will list all the assets pulled/updated from Crowdstrike.

How CrowdStrike Data Appears in SAFE

SAFE integrates with CrowdStrike to provide visibility into assets, vulnerabilities, software, and other security-related information. The following sections explain how CrowdStrike data is displayed and managed in SAFE.

Asset Identification

  • SAFE imports assets that have at least one valid identifier: hostname, IPv4 address, or MAC address.

  • Assets without a valid identifier are dropped from SAFE.

  • IP-based names, such as ip-10-0-0-1, are not considered valid hostnames.

Vulnerability Severity

  • The Severity displayed in SAFE represents SAFE's risk-based finding score rather than the original CrowdStrike severity.

Remediation Availability

  • The Fix Available field displays Yes when CrowdStrike provides remediation information for a vulnerability.

Falcon Sensor Information

  • The CrowdStrike Falcon sensor is listed as CrowdStrike Falcon in the asset's Software tab.

  • The installed sensor version is also displayed.

Cloud Asset Classification

  • Assets imported from CrowdStrike are not automatically classified as cloud resources.

  • Cloud resource classification is determined through SAFE's cloud integrations.

Active Directory Domain Tagging

  • For assets joined to an Active Directory (AD) domain, SAFE automatically assigns a tag in the following format: AD_DOMAIN: <domain>Example: AD_DOMAIN: corp.example.com. The domain value is retrieved from the Active directory domain field in CrowdStrike Falcon.

  • Assets that are not joined to an AD domain do not receive this tag.

  • Using AD Domain Tags in SAFE:  You can use AD domain tags to:

  • > Filter assets and findings using the Asset Tags filter.

  • > Create Smart Groups based on AD domain membership.

  • > Organize and report on assets by business domain, such as Corporate, Store, or Digital.

End-of-Life Software Identification

  • When CrowdStrike Spotlight identifies software as Unsupported software, SAFE marks the corresponding software as End Of Life in the asset's Software tab.

  • You can identify these assets using the Software Patch State = End of Life filter.

  • SAFE does not generate a separate End-of-Life (EOL) finding for this software because the existing CrowdStrike Unsupported software finding already represents the issue.

API Details

Fetching Inventory details from CS requires two step:

  1. Fetch resources
  2. Fetch inventory for each resource id got from fetch resources response.
API Method Endpoint
Resources GET /devices/queries/devices-scroll/v1
Inventory POST /devices/entities/devices/v2
Vulnerabilities GET /spotlight/combined/vulnerabilities/v1

FAQs

Q: How frequently does SAFE sync data from Crowdstrike?
A: Sync frequency depends on the auto sync frequency.

Q: What happens if API rate limits are exceeded?
A: SAFE automatically manages rate limits by pausing and retrying API calls after the designated wait time.

Q: How are duplicate assets or findings handled?
A: Assets are deduplicated based on unique identifiers.

Q: Can historical data be re-ingested?
A: Yes, historical data can be re-ingested by re-running the integration.

Did this article help?

Let us know by leaving a star rating at the top of this article.