Skip to main content
Version: 0.10

CrowdStrike asset owner (WIP)

Works out who uses each CrowdStrike-managed host from every owner source the Falcon API offers, and names an owner only when the sources agree well enough. It creates no assets — it fills in asset_owner on the ones you already have.

Type namecrowdstrike_asset_owner
CreatesNothing — enriches existing endpoints
Runs onA sensor with outbound reach to the Falcon API
Fields writtenasset_owner, optionally department and criticality

Sources​

Each source is a checkbox on the scan template, all on by default. A source the API client is not entitled to is skipped with a warning on the task; the scan fails only when no source can be read.

SourceWhat it givesScore
LogScale logonsThe days each account logged on, from UserLogon events, in one query for the whole fleet2 for the account with the majority of a host's logon days
Identity ProtectionCrowdStrike's computed owner (OWNERSHIP), recent interactive logons (LOGIN) and the directory object owner (OBJECT_OWNER) of each endpoint, and whether it is shared3, 2 and 2
Discover loginsDaily login history, usually going back further than LogScale2 for the account with the majority of a host's login days
Last logged-on userThe cs_last_login_user the CrowdStrike integration recorded1

How ownership is resolved​

  1. Every account each source reports is matched to a user asset: by domain SID, then by UPN, then by logon name, and only then by the local part of an e-mail address, and that only when exactly one enabled account carries it. Where several user assets answer, an enabled account beats a disabled copy, and an account in the logon's own domain beats one in another.
  2. Accounts that are never a person are dropped: Windows principals (anything but a domain SID), local Windows accounts, the excluded logon names, and trust accounts. An account in use on more hosts than Maximum hosts per owner is treated as shared and never named an owner.
  3. For LogScale and Discover, an account counts when it holds more than the owner majority threshold of the host's distinct logon days, over at least minimum logon days.
  4. The scores of each account's sources are added up. The highest wins if it beats the runner-up and reaches the minimum owner score, 3 by default: Identity Protection ownership on its own is enough, a LogScale majority on its own is not.
  5. The winner's user asset ID is written to the host's asset_owner. Nothing is written when the host already has that owner.

Hosts are matched to the evidence by their Falcon sensor ID. A sensor the CrowdStrike integration has not synchronised yet falls back to its hostname, but only onto a single endpoint that carries no sensor ID.

Ownership is a link, not a string

asset_owner holds the ID of a user asset. A person with no user asset cannot be assigned as an owner, so import identities first with Active Directory users, CrowdStrike identities or Azure users.

Logon history​

LogScale usually keeps only 7 days of endpoint telemetry, whatever the look-back says; the task shows a warning when it holds less than the look-back. The logon days of every run are therefore kept by the platform and combined with the next run's, so a scan that runs at least weekly covers the whole look-back window: a laptop that was switched off all week keeps the owner it had the weeks before.

Workstations and shared hosts​

With Workstations only on (the default), servers and domain controllers get no owner: whoever logged on last is an administrator, not the owner. The host type comes from CrowdStrike's product type, then Identity Protection, then the asset's type; a host none of them describes is treated as a workstation. With Skip shared hosts on, a host Identity Protection marks as shared gets no owner either.

Existing owners​

When the host already has another owner decides what happens to an owner that is already set:

OptionEffect
Never replace (default)The conflict is logged and the host is skipped
Replace a disabled, excluded or shared ownerAlso replaces an owner that is a disabled account, an excluded or shared account, or no longer in the user inventory
Replace with a high-confidence ownerAs above, and also replaces any owner when the new one has a score of 5 or more from two or more sources
Replacing applies to manual assignments too

The integration cannot tell an owner set by hand from one it set itself. Keep Never replace where owners are maintained manually.

Requirements​

The integration is outbound-only: it is a scheduled API client, so nothing is installed on the CrowdStrike side, nothing runs on the endpoints themselves, 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, the host enumeration and the LogScale query jobs all go to that same host, so one egress rule covers the whole integration. Open it for your region's host — credentials issued in one Falcon cloud do not authenticate against another — and if the sensor reaches the internet through a proxy, point Proxy settings at it rather than opening direct egress.

Access in CrowdStrike​

NeedWhy
An account that can create API clients in the Falcon consoleThe credential is created under Support and resources → API clients and keys, which is admin-gated
A scope for each source you switch onSee Permissions in CrowdStrike; the connection test lists which sources the client can read

In this deployment​

NeedWhy
A registered, healthy sensorThe integration runs on a sensor, on the platform's schedule — see Sensors
Endpoints already discovered by CrowdStrikeThis integration creates nothing — it writes asset_owner onto hosts that already exist, matched by their Falcon sensor ID. Schedule it after the CrowdStrike scan
Users in the inventory, for department and criticalityThe enrichment copies user_department and criticality from the owning user's record, so those fields need a user source such as Azure users

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
Client SecretYesFalcon API client secret. Write-only: once saved it shows as a locked box with Replace, and is sent only to the sensor
Proxy settingsNohttp://host:port
SensorYesSensor that will run the integration
Ignore SSLYesA checkbox; ticked, it skips certificate validation

Test connection probes LogScale, Identity Protection and Discover logins one by one. It passes when at least one is readable and lists the ones that are not.

Its scan template adds the source checkboxes (Use LogScale logons, Use Identity Protection, Use Discover logins, Use last logged-on user), Workstations only, Skip shared hosts, When the host already has another owner, Minimum owner score (3), Owner majority threshold (%) (50), Minimum logon days (2), Maximum hosts per owner (10; 0 switches the check off), Excluded logon names (empty uses the built-in list), a Look-back window (45 days), the Logon types that count (2 interactive, 7 unlock, 10 remote interactive, 11 cached), and an Enrich host information by asset owner checkbox, on by default. It sets the host's department from the owner's user_department and its criticality from the owner's, where the host has none yet; when the owner is replaced, both are taken from the new owner.

Naming conventions for administrator accounts differ per organisation; add yours to Excluded logon names, for example *-adm or *L1-*.

Enrichment is how departments get onto hosts

Nothing else in the catalogue can tell you which department a laptop belongs to. Resolving the owner and inheriting their department is what turns an inventory into something you can report on by business unit.

Permissions in CrowdStrike​

Grant the API client the scope of each source you switch on. A scope added to an existing client takes effect only on a token minted after the change.

SourceScopeAccess
LogScale logonsInvestigate (LogScale)Read
Identity ProtectionIdentity Protection GraphQLWrite: the GraphQL endpoint is a POST, so Falcon requires the write level even to read. Also needs a Falcon Identity Protection subscription
Discover loginsAssetsRead

See also​