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 name | crowdstrike_identities |
| Creates | Users |
| Runs on | A sensor with outbound reach to the Falcon API |
| Fields written | csi_*, 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
| Field | Holds |
|---|---|
csi_exists | Presence flag: Identity Protection knows this identity |
csi_entity_id, csi_entity_type | Identity Protection's own key for the identity, and its kind |
csi_primary_display_name, csi_secondary_display_name | The names the Falcon console shows |
csi_upn, csi_sam_account_name, csi_domain, csi_object_sid | The directory account |
csi_email, csi_email_addresses | The first e-mail address, and all of them |
csi_distinguished_name, csi_organizational_unit | Where the account sits in the directory |
csi_department, csi_job_title, csi_description | Directory attributes |
csi_service_principal_names | The account's SPNs, typical of service accounts |
csi_account_enabled, csi_account_locked, csi_password_never_expires | The account's standing |
csi_account_flags | Active Directory account control flags by name, decoded when the tenant reports a bitmask |
csi_archived, csi_learned, csi_watched, csi_shared | Identity Protection's own markers |
csi_is_human, csi_is_programmatic, csi_is_admin, csi_has_domain_admin_role | How Identity Protection classifies the identity |
csi_last_activity | Last authentication. Decommissioning evidence |
csi_created, csi_password_last_change, csi_account_expiry, csi_last_update, csi_earliest_seen_traffic | Account dates |
csi_risk_score, csi_risk_severity, csi_risk_factors, csi_risk_factor_count | Identity Protection's risk view |
csi_roles | Privileged roles, as Identity Protection classifies them |
csi_open_incident_count, csi_open_incident_types | Open incidents, when Fetch open incidents is on |
csi_associated_entities, csi_associated_entity_count | Associated endpoints and identities, when Fetch associated entities is on |
csi_account_sources, csi_account_count | The kinds of account behind the identity, and how many |
csi_raw_entity | The untouched entity |
The shared fields are filled so other integrations and correlation can use them:
| Shared field | Value | Mode |
|---|---|---|
names | The identity's name, display name, logon name and the UPN without its domain | Added to existing values |
distinguished_name | The account's distinguished name | Added to existing values |
user_username | The UPN | Added to existing values |
user_full_name, user_email, user_department, user_title | Display name, e-mail, department, job title | Only when empty |
criticality | Critical, for an identity with a domain administrator role | Only when empty |
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:
- Its Identity Protection entity ID, which survives a rename.
- Its distinguished name, which is where it meets the user that Active Directory users or another directory integration created for the same account.
- Its UPN, on
csi_upn, then onuser_username. - Its e-mail address.
- Its UPN among the asset's
names. - Its logon name (sAMAccountName).
- 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
| From | To | Protocol | Port |
|---|---|---|---|
| The sensor running the integration | The Falcon API host for your region, e.g. api.us-2.crowdstrike.com | HTTPS over TCP | 443 |
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
| Need | Why |
|---|---|
| A Falcon Identity Protection subscription | Without it there is no identity inventory to read |
| An API client with the Identity Protection GraphQL scope at Write | The 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
| Need | Why |
|---|---|
| A registered, healthy sensor | The integration runs on a sensor, on the platform's schedule. See Sensors |
Configuration
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Label for this instance |
| API URL | Yes | Region-specific Falcon API base, e.g. https://api.us-2.crowdstrike.com |
| Client ID | Yes | Falcon API client ID with the Identity Protection GraphQL: Write scope |
| Client Secret | Yes | Falcon API client secret |
| Proxy settings | No | http://host:port |
| Sensor | Yes | Sensor that will run the integration |
| Ignore SSL | No | Skips certificate validation. Off by default |
Its scan template replaces the shared offline setting and adds:
| Option | Default | Effect |
|---|---|---|
| Account status | All | All, Enabled only or Disabled only |
| Include people | On | Imports identities classified as human |
| Include service accounts | On | Imports identities classified as programmatic |
| Include archived identities | Off | Imports identities the directory no longer holds |
| Only identities active within | None | Skips identities whose last authentication is older than this. An identity with no recorded activity is always imported |
| Ignore archived identities older than | 90 days | With 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 score | None | 0 to 1, e.g. 0.5 |
| Minimum risk severity | All | Low and above, Medium and above, High and above or Critical only |
| Fetch open incidents | Off | Adds each identity's open incidents to the query |
| Fetch associated entities | Off | Adds the endpoints and identities associated with each one |
| Page size | 100 | Identities per request, 1 to 1000 |
| Identity limit | 0 | Imports 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.
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
- CrowdStrike: the endpoint inventory from the same Falcon tenant
- CrowdStrike asset owner: links hosts to the user assets this integration creates
- Active Directory users: the directory view of the same accounts
- Assets: how fields from several sources land on one asset
- Integrations overview: the shared configuration model