Skip to main content
Version: 0.9

CrowdStrike identities (WIP)

Imports the CrowdStrike Falcon Identity Protection inventory as user assets. Identity Protection keeps one entity per identity, built from the directories Falcon is joined to, so one person's Active Directory account and Entra ID or SSO account arrive together as a single identity. Each one shows whether the account is enabled, locked out or has a password that never expires, whether it is a person or a service account, its privileged roles, its risk score and when it last authenticated.

Type namecrowdstrike_identities
CreatesUsers
Runs onA sensor with outbound reach to the Falcon API
Fields writtencsi_*, plus names, distinguished_name, user_username, user_full_name, user_email, user_department, user_title and criticality

How it reads Identity Protection​

Identity Protection has no REST listing: everything comes from its GraphQL endpoint, POST /identity-protection/combined/graphql/v1. Each run only queries; nothing is changed in CrowdStrike.

  • The query fits the tenant. The fields Identity Protection offers differ between subscriptions and product builds, and a query naming a field the tenant does not have is rejected whole. The sensor therefore reads the tenant's own schema first and asks only for what it offers. Where the schema cannot be read, it sends a conservative query and drops any field the server objects to, retrying a few times.
  • Only user entities. Identity Protection also holds endpoint entities; those are left to the CrowdStrike integration and are never imported here.
  • Filters run at the source where possible. Account status, archived state and risk are sent as query filters. A filter the tenant's schema does not offer is applied by the sensor to the records it receives instead, so the result is the same either way.
  • Accounts are folded into the identity. An identity is enabled when any of its accounts is. Account facts (UPN, logon name, domain, distinguished name, department, title, flags) are taken from the first account that carries them.
  • Nothing is lost. The whole entity as Identity Protection returned it is kept on the asset in csi_raw_entity, so a field nothing maps yet is still visible.

Timestamps Identity Protection uses for "never" (year 1 and year 1601) are discarded, so an account that has never logged on shows no last activity rather than a date in the past.

What it writes​

FieldHolds
csi_existsPresence flag: Identity Protection knows this identity
csi_entity_id, csi_entity_typeIdentity Protection's own key for the identity, and its kind
csi_primary_display_name, csi_secondary_display_nameThe names the Falcon console shows
csi_upn, csi_sam_account_name, csi_domain, csi_object_sidThe directory account
csi_email, csi_email_addressesThe first e-mail address, and all of them
csi_distinguished_name, csi_organizational_unitWhere the account sits in the directory
csi_department, csi_job_title, csi_descriptionDirectory attributes
csi_service_principal_namesThe account's SPNs, typical of service accounts
csi_account_enabled, csi_account_locked, csi_password_never_expiresThe account's standing
csi_account_flagsActive Directory account control flags by name, decoded when the tenant reports a bitmask
csi_archived, csi_learned, csi_watched, csi_sharedIdentity Protection's own markers
csi_is_human, csi_is_programmatic, csi_is_admin, csi_has_domain_admin_roleHow Identity Protection classifies the identity
csi_last_activityLast authentication. Decommissioning evidence
csi_created, csi_password_last_change, csi_account_expiry, csi_last_update, csi_earliest_seen_trafficAccount dates
csi_risk_score, csi_risk_severity, csi_risk_factors, csi_risk_factor_countIdentity Protection's risk view
csi_rolesPrivileged roles, as Identity Protection classifies them
csi_open_incident_count, csi_open_incident_typesOpen incidents, when Fetch open incidents is on
csi_associated_entities, csi_associated_entity_countAssociated endpoints and identities, when Fetch associated entities is on
csi_account_sources, csi_account_countThe kinds of account behind the identity, and how many
csi_raw_entityThe untouched entity

The shared fields are filled so other integrations and correlation can use them:

Shared fieldValueMode
namesThe identity's name, display name, logon name and the UPN without its domainAdded to existing values
distinguished_nameThe account's distinguished nameAdded to existing values
user_usernameThe UPNAdded to existing values
user_full_name, user_email, user_department, user_titleDisplay name, e-mail, department, job titleOnly when empty
criticalityCritical, for an identity with a domain administrator roleOnly when empty
Criticality is set once, never overwritten

A domain administrator is marked Critical only when the asset has no criticality yet. A value set by hand, or by another integration, is left alone.

Matching​

An identity is matched to an existing user asset by, strongest first:

  1. Its Identity Protection entity ID, which survives a rename.
  2. Its distinguished name, which is where it meets the user that Active Directory users or another directory integration created for the same account.
  3. Its UPN, on csi_upn, then on user_username.
  4. Its e-mail address.
  5. Its UPN among the asset's names.
  6. Its logon name (sAMAccountName).
  7. Its display name, only on an asset that holds no different e-mail, UPN or logon name.

Rules 3 to 7 match a name rather than an identifier, and a name is unique only within one directory domain. Where both the identity and the asset carry a distinguished name, those rules also require the two to be in the same domain, so j.smith in one forest is never merged with j.smith in another.

An identity with no name at all (no UPN, logon name, e-mail, display name or entity ID) is skipped.

Requirements​

The integration is outbound-only: nothing is installed on the CrowdStrike side and nothing has to reach into the deployment.

Network access​

FromToProtocolPort
The sensor running the integrationThe Falcon API host for your region, e.g. api.us-2.crowdstrike.comHTTPS over TCP443

The token request and every GraphQL query go to that one host. Credentials issued in one Falcon cloud do not authenticate against another, so use your region's host. If the sensor reaches the internet through a proxy, set Proxy settings rather than opening direct egress.

Access in CrowdStrike​

NeedWhy
A Falcon Identity Protection subscriptionWithout it there is no identity inventory to read
An API client with the Identity Protection GraphQL scope at WriteThe GraphQL endpoint is a POST, so Falcon requires the write level even to read. The Identity Protection read scopes do not cover it

A scope added to an existing client takes effect only on a token issued after the change. The connection test asks Identity Protection for one identity, so it tells a missing scope or subscription apart from a wrong secret.

In this deployment​

NeedWhy
A registered, healthy sensorThe integration runs on a sensor, on the platform's schedule. See Sensors

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
API URLYesRegion-specific Falcon API base, e.g. https://api.us-2.crowdstrike.com
Client IDYesFalcon API client ID with the Identity Protection GraphQL: Write scope
Client SecretYesFalcon API client secret
Proxy settingsNohttp://host:port
SensorYesSensor that will run the integration
Ignore SSLNoSkips certificate validation. Off by default

Its scan template replaces the shared offline setting and adds:

OptionDefaultEffect
Account statusAllAll, Enabled only or Disabled only
Include peopleOnImports identities classified as human
Include service accountsOnImports identities classified as programmatic
Include archived identitiesOffImports identities the directory no longer holds
Only identities active withinNoneSkips identities whose last authentication is older than this. An identity with no recorded activity is always imported
Ignore archived identities older than90 daysWith archived identities included, skips one whose last activity is older than this. An archived identity with no recorded activity is kept, and a live account is never skipped for being idle
Minimum risk scoreNone0 to 1, e.g. 0.5
Minimum risk severityAllLow and above, Medium and above, High and above or Critical only
Fetch open incidentsOffAdds each identity's open incidents to the query
Fetch associated entitiesOffAdds the endpoints and identities associated with each one
Page size100Identities per request, 1 to 1000
Identity limit0Imports at most this many identities after filtering; 0 for no limit

An identity Identity Protection has not classified as either a person or a service account is always imported.

Dormant accounts are the point

Neither the activity window nor the archived cut-off removes an enabled account that has simply not been used. Those are exactly what an identity review looks for, so they stay in the inventory.

The basic and action settings are the shared ones; see the configuration model.

See also​