Skip to main content
Version: 0.9

LinkShadow applications (WIP)

Reads the logs LinkShadow's sensors write off the network and finds the applications in them: products servers announce, internal sites people reach by name, cloud services the organisation's endpoints use, and connections to databases and message brokers.

An agent on a server sees what is installed; the network sees what is used. This integration adds what an endpoint inventory cannot show: applications on hosts that run no agent, the URL people reach an application at, who uses it, when its certificate expires and what it depends on.

Type namelinkshadow_applications
CreatesApplications
Runs onA sensor with HTTPS reach to the LinkShadow console
Fields writtennames, type, hw_vendor, hw_product, application_hosts, app_url, app_hosting_model, app_depends_on_applications, and the lsapp_* fields

Where the evidence comes from​

Four sources, each switched on or off in the scan template. A source that cannot be read is skipped with a warning in the scan log; the others still run.

SourceWhat it showsShown as
Server bannersThe product a server announces on the wire, such as Microsoft-IIS/10.0 or Apache/2.4.37, with its version and portServer banner
Internal sitesSites clients reach by name on the organisation's servers: the TLS server name, the certificate's name, or the HTTP hostTLS, HTTP
Cloud servicesThe cloud services the organisation's endpoints reach, such as Microsoft 365, Salesforce or ChatGPTCloud service
Connections to data platformsWho connects to database and message broker portsConnections

Server banners are read over the Server banner look-back, 30 days by default: a sensor logs a server's banner when it first sees it, not on every connection.

TLS and HTTP traffic is too heavy to read whole, so it is sampled: two-minute slices spread over the Traffic window, six per hour by default, a fifth of the traffic. Connections to data platforms are read in full for the listed ports. Client counts from a sample are a floor, not a census.

What counts as an application​

As every integration does, this one creates an application when it is confident and otherwise adds what it saw to the application already registered.

Products in banners. A banner is judged by the same product catalogue the CrowdStrike applications integration uses, so IIS seen on the wire and IIS installed on a server are one Internet Information Services application. Most banners name a framework or an appliance (Microsoft-HTTPAPI, Kestrel, a load balancer), not an application, and are skipped.

Internal sites, in this order:

  1. A site on the port of a business product the server announces belongs to that product: portal.contoso.com on a SharePoint server is SharePoint's URL.
  2. A site on a host the register places exactly one business application on belongs to that application.
  3. Otherwise a site becomes a Web application of its own, named after the site, once at least Clients for a new site clients have reached it (1 by default).

These are not sites, and are skipped:

  • A name the server answers for among names of five or more unrelated domains: that server is a proxy.
  • A cloud service's name answered by an internal server: also a proxy.
  • A name on a management port (SSH, RDP, WinRM, LDAP, Kerberos, SMB, DNS): it is the host's own name.
  • A site named after its own host, such as srv01.contoso.local on SRV01: that is the host's management page.
  • Wildcards, addresses and names a device ships with, such as server.

Cloud services are recognised by their own domains: contoso.sharepoint.com and outlook.office365.com are Microsoft 365. Operating system telemetry, update and content delivery hosts are not cloud services anybody registers, and are skipped. A cloud service becomes an application once Endpoints for a new cloud service endpoints use it (2 by default), with its hosting model set to SaaS.

IT infrastructure (monitoring, backup and security products and cloud services, such as an EDR's cloud or a secure web gateway) runs the estate rather than the business, so it is skipped unless Include IT infrastructure is on.

Usage and dependencies​

The endpoints seen using an application are its clients. An application running on a client endpoint depends on what that endpoint uses: when the server running the payroll site connects to the database server's SQL Server port, Payroll depends on Microsoft SQL Server. Dependencies are added to Depends On Applications, and so appear on the other application's Used By.

  • Backup, monitoring and security tools reach everything as their job, so they depend on nothing here.
  • A web or application server is only where the application that depends runs, so the dependency is recorded on that application, not on IIS or Tomcat.
  • An application this run creates gets its dependants on the next run, once it is registered.

Fields​

FieldHolds
names, hw_productThe product or site, e.g. Internet Information Services or portal.contoso.com
hw_vendorThe vendor, when known
typeWhat kind of application it is, as for CrowdStrike applications, plus Web application
application_hostsThe endpoints it runs on
app_urlThe URLs clients reached it at
app_hosting_modelSaaS, for a cloud service
app_depends_on_applicationsWhat it depends on
lsapp_evidenceWhat showed it: Server banner, TLS, HTTP, Cloud service, Connections
lsapp_versions, lsapp_portsVersions from banners, and the ports it was seen on
lsapp_service_namesThe names clients reached it by
lsapp_host_count, lsapp_hostsThe hosts it was seen on, with versions and ports
lsapp_client_count, lsapp_clientsThe endpoints seen using it
lsapp_depends_onThe applications it was seen using
lsapp_cert_issuer, lsapp_cert_expiryThe certificate that expires first, and who issued it
lsapp_last_seenWhen it was last seen

type, hw_vendor, hw_product and the hosting model are written only when empty, so a correction made in the register stays. Hosts, URLs and dependencies are only ever added to, never removed: the network sees a sample, and the register or another integration may know more.

An application created by the CrowdStrike applications integration for the same product is enriched, not duplicated. An application someone created by hand under the same name is adopted.

Requirements​

Network access​

FromToProtocolPort
The sensor running the integrationThe LinkShadow consoleHTTPS over TCP443

Access in LinkShadow​

NeedWhy
A console user with access to Shadow360Every source is read through the raw-log search
Sensors writing the software, TLS, HTTP and flow logsThese are the logs searched. The connection test checks the software and TLS logs exist

In this deployment​

NeedWhy
A registered, healthy sensorThe integration runs on a sensor, on the platform's schedule. See Sensors
Endpoints with their IP addresses already discoveredServers and clients are matched to the tenant's endpoints by address. Schedule this after the endpoint integrations
A sensor sees only its own segments

LinkShadow sees the traffic its sensors are attached to. Traffic between servers in a segment no sensor sees, which is often where an application talks to its database, never shows. An application missing here may simply be out of sight.

Addresses

An address carried by two endpoints of the tenant is ignored, as is any address that is not an endpoint's. When one LinkShadow appliance serves several organisations, only the tenant's own endpoints' addresses count, which separates them only if each tenant's endpoint integrations import its own hosts and no others.

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
URLYesThe LinkShadow console, e.g. https://linkshadow.contoso.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 SSLNoSkips certificate validation
SensorYesSensor that will run the integration

Its scan template adds:

OptionDefaultEffect
Server bannersOnReads the products servers announce
Internal sitesOnFinds sites reached by name, from sampled TLS and HTTP
Cloud servicesOnFinds cloud services the tenant's endpoints use, from sampled TLS and HTTP
Connections to data platformsOnReads who connects to database and broker ports
Server banner look-back (days)30How far back banners are read, 1 to 90
Traffic window (hours)24How many hours of TLS, HTTP and connection logs each run reads, 1 to 168
Samples per hour6Two-minute TLS and HTTP samples per hour, 1 to 30
Data platform portsDatabase and broker portsComma-separated ports whose connections are read
Clients for a new site1Clients that must reach a site before it becomes an application
Endpoints for a new cloud service2Endpoints that must use a cloud service before it becomes an application
Include IT infrastructureOffAlso keeps monitoring, backup and security products and cloud services
Always includeEmptyComma-separated product names to keep whatever the catalogue makes of a banner holding one
Never includeEmptyComma-separated names to skip in banners, site names and cloud services

See also​