Skip to main content
Version: 0.10

LinkShadow users (WIP)

Reads LinkShadow's identity inventory and creates or enriches a user for every account in it. LinkShadow builds that inventory from the directories it is joined to, not from traffic, so the unit is the account and its username identifies it.

What this adds beyond another copy of the directory is each account's standing: whether it is enabled, locked out or protected as privileged, whether its password never expires or is not required, which groups it is in and which machines it signs in from. A dormant account whose password never expires shows as one. Optionally, it also imports the usernames LinkShadow has only seen authenticating on the network.

Type namelinkshadow_users
CreatesUsers
Runs onA sensor with HTTPS reach to the LinkShadow console
Fields writtenuser_username, names, user_full_name, user_email, user_department, user_title, distinguished_name, sam_account_name, phone_number, criticality, updated_at, and the ls_user_* fields (presence flag ls_user_exists)

How it reads LinkShadow​

Everything is read from the console's identity API. Nothing is changed in LinkShadow.

WhatEndpointWhen
The account listing/fastapi/user/usersEvery run, paged to the end
The name index/fastapi/user/user-list/Every run
One account's detail record/fastapi/user/user-detailsWith Fetch user details, and for every account the listing omits
One account's manager, peers and Azure groups/fastapi/user/peer-usersWith Fetch peers and manager
Usernames seen only on the network/fastapi/user/non-ad-usersWith Include network-observed logins

The listing does not always return the whole population: an account can be in the name index and still be left out of the listing. Each such account is fetched one by one from the detail endpoint, whatever the scan template says, so the import is complete.

Account standing comes from the detail record. LinkShadow reports the directory's userAccountControl word there, and the integration reads its bits: enabled or disabled, locked out, password never expires, password not required, Kerberos pre-authentication not required, trusted for delegation. An account with adminCount set is marked Admin Protected. The detail record also brings the directory attributes, group membership, primary group, account type and the devices the account signs in from. Binary attributes such as photographs and certificates are dropped.

The detail and peer requests cost one request per account each. They run in parallel (User detail workers, 8 by default) and, if capped by User detail account limit, spend the budget on the most recently active accounts first. One account that cannot be read is skipped with a warning; the run continues.

Without user details, the account flags are not known

The enabled, locked-out, password and delegation flags come only from the detail record. With Fetch user details off, Account Enabled is empty and the other flags read No because nothing was reported, not because the directory says so. Check LinkShadow Details Fetched before relying on them.

Network-observed logins are RADIUS, NTLM, FTP and HTTP usernames with no directory account behind them. Some are not people at all, such as a MAC address used as a RADIUS identity. They are marked Directory Account: No. One request of up to 2,000 sightings is read per run; anything beyond that is logged and not collected.

What it writes​

Matching​

A LinkShadow account is matched to an existing user by the first of these that finds one:

  1. The same LinkShadow username (ls_user_username).
  2. The same distinguished name, as Active Directory users, LDAP users and CrowdStrike identities write it. This is what joins an account to the user another directory integration created, on the first run.
  3. The same logon name in user_username.
  4. The same e-mail address, in ls_user_email and then in user_email. This is how a user from Azure users is usually reached.
  5. The username in sam_account_name. This is how a network login, which carries no domain, is reached.
  6. The same sAMAccountName.
  7. The same full name, only on a user carrying no different e-mail address, LinkShadow username or sAMAccountName. A display name is not an identity, so this is the last resort.

A match on more than one user goes to the approval queue.

Fields​

FieldWritten how
ls_user_*Replaced on every run: LinkShadow's own view of the account
user_usernameAdded to: the username as LinkShadow reports it and, when it carries a domain, the bare name
namesAdded to: the display name only
distinguished_name, sam_account_name, phone_numberAdded to, never replacing what another integration wrote. phone_number holds the mobile and every number in the directory record
user_full_name, user_email, user_department, user_titleWritten only when empty
criticalitySet to Critical when LinkShadow flags the account as critical, only when empty

The asset's last seen is the account's last logon as LinkShadow reports it, and LinkShadow Last Logon counts as decommissioning evidence. A network-observed login has no logon time, so it does not move the asset's last seen; its own sighting is in LinkShadow Last Seen.

Directory accounts are never dropped for being idle: a dormant account is what an identity review looks for. Ignore network logins older than applies only to network-observed logins.

Requirements​

Network access​

FromToProtocolPort
The sensor running the integrationThe LinkShadow consoleHTTPS over TCP443

Access in LinkShadow​

NeedWhy
A console user with access to Identity IntelligenceEvery source is read through the identity API
LinkShadow joined to the directoryThe inventory is LinkShadow's copy of the directory; accounts it has not read are not here

In this deployment​

NeedWhy
A registered, healthy sensorThe integration runs on a sensor, on the platform's schedule. See Sensors
A long first run with details on

With Fetch user details and Fetch peers and manager both on, a directory of a few thousand accounts costs two requests per account. Use User detail account limit to try it on the most active accounts first.

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
URLYesThe LinkShadow console, e.g. https://linkshadow.example.com
UsernameYesConsole user the collection runs as
PasswordNoLeave empty when the session is carried by the Cookies field
CookiesNoFor a console behind an access gateway or SSO: name=value; name2=value2
Proxy settingsNohttp://host:port
Ignore SSLNoOn by default. Skips certificate validation
SensorYesSensor that will run the integration

Password and Cookies are secrets: once saved, the console shows them as a locked box with Replace and Remove, never shows them back, and sends them only to the sensor.

TODO

Confirm the cookie-only sign-in. Username is required, and the sensor always signs in with the username and password when a username is set, so an empty password fails the sign-in even when the Cookies field carries a session. Only with no username does the sensor use a sessionid cookie from the Cookies field as the session.

Its scan template adds, alongside the shared options:

OptionDefaultEffect
Ignore network logins older than90 daysDrops network-observed logins not seen within this time. Directory accounts are always imported
Fetch user detailsOffReads each account's detail record: account flags, directory attributes, groups and devices. One request per account
Fetch peers and managerOffReads each account's manager, peers and Azure groups. A second request per account
Include network-observed loginsOnAlso imports usernames seen authenticating on the network with no directory account
User detail workers8Detail requests in flight at once, 1 to 16
User detail account limit0Enrich at most this many accounts, most recently active first. 0 for all

See also​