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 name | crowdstrike_asset_owner |
| Creates | Nothing — enriches existing endpoints |
| Runs on | A sensor with outbound reach to the Falcon API |
| Fields written | asset_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.
| Source | What it gives | Score |
|---|---|---|
| LogScale logons | The days each account logged on, from UserLogon events, in one query for the whole fleet | 2 for the account with the majority of a host's logon days |
| Identity Protection | CrowdStrike's computed owner (OWNERSHIP), recent interactive logons (LOGIN) and the directory object owner (OBJECT_OWNER) of each endpoint, and whether it is shared | 3, 2 and 2 |
| Discover logins | Daily login history, usually going back further than LogScale | 2 for the account with the majority of a host's login days |
| Last logged-on user | The cs_last_login_user the CrowdStrike integration recorded | 1 |
How ownership is resolved
- 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.
- 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.
- 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.
- 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.
- 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.
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:
| Option | Effect |
|---|---|
| Never replace (default) | The conflict is logged and the host is skipped |
| Replace a disabled, excluded or shared owner | Also 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 owner | As above, and also replaces any owner when the new one has a score of 5 or more from two or more sources |
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
| 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, 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
| Need | Why |
|---|---|
| An account that can create API clients in the Falcon console | The credential is created under Support and resources → API clients and keys, which is admin-gated |
| A scope for each source you switch on | See Permissions in CrowdStrike; the connection test lists which sources the client can read |
In this deployment
| Need | Why |
|---|---|
| A registered, healthy sensor | The integration runs on a sensor, on the platform's schedule — see Sensors |
| Endpoints already discovered by CrowdStrike | This 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 criticality | The enrichment copies user_department and criticality from the owning user's record, so those fields need a user source such as Azure users |
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 |
| 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 |
Its scan template adds the source checkboxes, Workstations only, Skip shared
hosts, the existing-owner option, Minimum owner score, Owner majority
threshold (%), Minimum logon days, Maximum hosts per owner, Excluded logon
names, 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, which sets the host's
department from the owner's user_department and propagates criticality.
Naming conventions for administrator accounts differ per organisation; add yours to
Excluded logon names, for example *-adm or *L1-*.
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.
| Source | Scope | Access |
|---|---|---|
| LogScale logons | Investigate (LogScale) | Read |
| Identity Protection | Identity Protection GraphQL | Write: the GraphQL endpoint is a POST, so Falcon requires the write level even to read |
| Discover logins | Assets | Read |
See also
- CrowdStrike — the inventory source this depends on
- Elastic asset owner — the same idea using Elastic logs
- Integrations overview — the shared configuration model