Version: 9
restore

Contents


What is Tachyon Agent Historic Data Capture?

On Tachyon Windows Agent devices Tachyon continuously captures events, which enables Tachyon to capture all significant events as they happen. This should be contrasted with polling, which to a certain degree relies on luck to capture conditions that are brief enough to fall between polls. In this way Tachyon Agent Historic Data Capture compares with the Windows Task Manager or Perfmon. Tachyon captures the data to a compressed and encrypted database to ensure that it has a very low impact on device performance and security.

The data is captured and stored to a local, encrypted persistent store and then periodically aggregated according to an ongoing daily, weekly, monthly window. This means that the data is held securely and the amount of data is minimized while still maintaining its usefulness.

Configuration options for each capture source are described in the public documentation reference for Tachyon Agent configuration properties.

What are the data capture sources?

The table below lists currently supported capture sources, and on which OS they are supported.

The Agent has two key mechanisms of knowing when an event occurs that is of interest - event-based and polling-based

  • Event-based relies on a source external to the Agent (normally the operating system) providing a notification to indicate that something has happened
  • Polling-based is where the Agent will periodically check a source of data and work out what has changed by looking at differences in the data returned

The Windows Agent can be configured to use polling instead of ETW for individual capture sources.

Historic data source

Description

Windows
MacOS
Linux
Solaris
Android
DNS resolutions

The Agent captures whenever a DNS address is resolved.

When using the polling method, the polling interval is every 30 seconds.

  • ETW on Windows 8.1 and above

  • Polling on Windows 8 and below

PollingNot yet availableNot yet availableNot yet available
Process executions

The Agent captures whenever a process starts on the device.

When using the polling method, the polling interval is every 30 seconds.

  • ETW on Windows Vista and above
  • Polling on Windows XP
PollingPollingPollingNot yet available
Software installations

The Agent captures which software is present on a device, and when it is installed and uninstalled.

Software polling is every 120 seconds.

  • Polling on on all versions
PollingPollingPollingNot yet available
Outbound TCP connections

The Agent captures whenever an outbound TCP connection is made.

When using the polling method, the polling interval is every 30 seconds.

  • ETW on Windows Vista and above
  • Polling on Windows XP
PollingPollingNot yet availableNot yet available

How do I retrieve the data from the Tachyon Agent devices?

Live and aggregated historic data is available in inventory tables. 

Historic data source
Live tables
Hourly tables
Daily tables
Monthly tables
DNS resolutions$DNS_Live$DNS_Hourly$DNS_Daily$DNS_Monthly
Process executions$Process_Live$Process_Hourly$Process_Daily$Process_Monthly
Software installations$Software_Live$Software_Hourly$Software_Daily$Software_Monthly
Outbound TCP connections$TCP_Live$TCP_Hourly$TCP_Daily$TCP_Monthly
Example - querying historic captured data
/* Sum the number of connections made per process today */
SELECT    SUM(ConnectionCount) AS Connections
,         ProcessName
FROM      $TCP_Daily
WHERE     TS = DATETRUNC(STRFTIME("%s", "now"), "day")
GROUP BY  ProcessName;
Example - querying historic captured data
SELECT * FROM $Process_Live WHERE ProcessName = "chrome.exe"

Note that because the inventory tables are not created with COLLATE NOCASE, they need to be queried in a case-sensitive fashion. So the example above won't match "Chrome.exe" or "chrome.EXE" - to work around this, you can use WHERE ProcessName LIKE "chrome.exe"

How is the data managed?

The Tachyon Agent automatically aggregates and grooms data in each inventory table, according to aggregation intervals and data retention settings which are configurable in the Agent configuration file.  

  • Default aggregation cycle interval is every 60 seconds, therefore it may take up to a minute before an event appears in an aggregated table
  • Default retention for live tables is 5000 entries provided at least 3 aggregation cycles have occurred (older entries are deleted to make room for new entries)
  • Default retention for hourly tables is a rolling 24 hours.
  • Default retention for daily tables is a rolling 31 days.
  • Default retention for monthly tables is a rolling 12 months.

Each aggregated table is built from the live table, and does not have a dependency on other aggregated tables. For example, Monthly is fed by Live, not fed by Daily. This allows retention settings to be configured independently for each table.

Data is stored in a local, encrypted persistent store, which persists during an Agent upgrade, uninstall and re-installation, unless specifically deleted.

If the Agent is unable to write to storage (out of disk space or other file-system problems), it will fail but continue monitoring in the hope this situation will improve later.

Historic data capture inventory schema

The following table shows the fields which exist only in the Live and Aggregated (Hourly, Daily, Monthly) tables.

Historic data source
Fields that only exist in Live tables
Fields that only exist in Aggregated tables
DNS resolutionsn/aLookupCount
Process executionsCommandLine, ProcessId, ParentProcessIdExecutionCount
Software installationsIsUninstallInstallCount, UninstallCount
Outbound TCP connectionsProcessIdConnectionCount

Timestamps

The timestamp column (TS) in each table is stored in Unix Epoch format. Defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. 

 To convert to a readable format use DATETIME(TS, "unixepoch").

Timestamps are truncated in the aggregated tables.

  • Hourly - time is truncated to each hour - so an event that occurred at 2017-01-27 18:03:54 would be included in the summary for 2017-01-27 18:00:00
  • Daily - time is truncated to midnight on each day - so an event that occurred at 2017-01-27 18:03:54 would be included in the summary for 2017-01-27 00:00:00
  • Monthly - time is truncated to midnight on the first day of each month - so an event that occurred at 2017-01-27 18:03:54 would be included in the summary for 2017-01-01 00:00:00

DNS resolutions

ETWPollingNot supported
  • Windows 8.1 and above
  • Windows 8 and below
  • MacOS
  • Linux
  • Solaris
  • Android
FieldDatatypeDescriptionSample valueTables
FqdnstringThe FQDN which is being resolved.

client-office365-tas.msedge.net

All

LookupCountintegerSum of resolutions per FQDN within the hour, day, month.1234
  • $DNS_Hourly
  • $DNS_Daily
  • $DNS_Monthly
TSintegerSee Agent Historic Data Capture.1500756083

All

The Agent attempts to capture DNS queries at the point that they are made, although on non-Windows platforms (and pre-Win 8.1 - see below), this is not presently possible and instead the local DNS cache is queried through polling.

When the Agent captures DNS queries, it captures the query, not the result of that query. That is, the Agent will capture a request to resolve an FQDN which may ultimately not be resolvable.

When using ETW, the Agent will not perform an initial scan to establish the contents of the DNS cache. When polling, the Agent will capture all unique FQDNs available in the DNS cache; new entries that appear in the cache are deemed to correspond to resolutions.

Process executions

ETWPollingNot supported
  • Windows Vista and above
  • Windows XP
  • MacOS
  • Linux
  • Solaris
  • Android
FieldDatatypeDescriptionSample valueTables
CommandLinestring

The full command-line of the process, including (on Windows) the executable name.

Sometimes the executable name part of the command-line is quoted, sometimes it's not - it's arbitrary based however the parent process launched the child; so you may see a mix of command-lines like...

  • "C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE" 
  • \??\C:\Windows\system32\conhost.exe 0x4
  • C:\Windows\system32\svchost.exe -k UnistackSvcGroup
"C:\Windows\system32\VmConnect.exe" "1EUKDEVWKS1231" "TCH-CLI-WXPX86" -G "B2C72520-BBC6-4736-BBBC-5CCF50FE6666" -C "0"
  • $Process_Live
ExecutableHashstring

The MD5 hash of the process executable.

dae0bb0a7b2041115cfd9b27d73e0391All
ExecutableNamestringThe filename (including extension) of the process executable.vmconnect.exe

All

ExecutablePathstring

The path and filename of the process executable.

On Windows, this is the NT-device format version of the path (as a process does not necessarily need to have been launched from a device which has a drive-letter mapping).

\device\harddiskvolume8\windows\system32\vmconnect.exeAll
ExecutionCountintegerSum of executions per executable within the hour, day, month.1234
  • $Process_Hourly
  • $Process_Daily
  • $Process_Monthly
ParentExecutableNamestringThe filename (including extension) of the executable of the process which spawned this one.mmc.exeAll
ParentProcessIdintegerThe process ID of the process which spawned this one.2088
  • $Process_Live
ProcessIdintegerOperating-system dependent process ID.178
  • $Process_Live
TSintegerSee Agent Historic Data Capture.1500756083

All

UserNamestringThe account name of the user who launched the process (or blank if it is a system-launched process).1E\bill.gatesAll

On Windows, the Agent runs as LOCAL SYSTEM, therefore details of almost every process will be available; however some processes may not be accessible because of permissions.

The Agent captures process starts; it does not track how long the process has been running, or how much CPU-time (or user/kernel/active time) the process has used.

Each time the Tachyon Agent starts it does an initial scan of processes before it starts capturing. To prevent double-counting a persistent storage setting called "Inventory.ProcessesLastScan" records the last time the Agent checked for processes. This corresponds to the last time the Agent polled, or if ETW is used it is the time when the Agent inventory module was last terminated.

Software installations

ETWPollingNot supported
  • n/a
  • Windows
  • MacOS
  • Linux
  • Solaris
  • Android
FieldDatatypeDescriptionSample valueTables
ArchitecturestringThe platform architecture of the software product.x64All
InstallCountinteger

Sum of installs per software product version within the hour, day, month.

0 if uninstalled, or present but not detected as installed.

1234
  • $Software_Hourly
  • $Software_Daily
  • $Software_Monthly
IsUninstallinteger0 = install, 1 = uninstall.0
  •  $Software_Live
Productstring

The title of the software product that was installed/uninstalled.

Google Chrome

All
PublisherstringThe publisher of the software product that was installed/uninstalled.Google Inc.All
TSinteger

See Agent Historic Data Capture.

The Agent assumes a "new" installation/uninstallation occurred at the point of polling.

1500756083

All

UninstallCountinteger

Sum of uninstalls per software product version within the hour, day, month.

0 if installed, or present but not detected as installed.

1233
  • $Software_Hourly
  • $Software_Daily
  • $Software_Monthly
VersionstringThe version of the software that was installed/uninstalled.55.0.2883.87All

Each time the Tachyon Agent starts it does an initial scan of install software before it starts capturing. To prevent double-counting persistent storage settings called "Inventory.SoftwareInstallations" and "Inventory.SoftwareInstallationsLastScan" records the results of the last scan by the Agent.  If these settings are present, the Agent will, on start-up, attempt to identify installs/uninstalls which occurred while the Agent was not capturing data. Since the Agent has no way of knowing when this install/uninstall happened, it will mark the event as having occurred "now".

On Windows, software installations are read from the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

Per-user installations are not yet supported.

Linux does not distinguish between O/S packages (even the kernel) and application packages; they are all software.

Outbound TCP connections

ETWPollingNot supported
  • Windows Vista and above
  • Windows XP
  • MacOS
  • Linux
  • Solaris
  • Android
FieldDatatypeDescriptionSample valueTables
ConnectionCountintegerSum of connections to an IP Address and Port by a process within the hour, day, month.123
  • $TCP_Hourly
  • $TCP_Daily
  • $TCP_Monthly
IpAddressstring

The target remote IP address of the connection, either an IPv4 or IPv6 address.

Windows support for IPV6 is limited; the Agent will capture the connections, but the format used to represent the target IPV6 may differ slightly depending on the mechanism used, and may be subject to change in future versions of the Windows Agent.

132.245.77.18

[2001:4860:4860::8888]

All
PortintegerThe target remote port of the connection.443All
ProcessIdinteger

The operating-system specific identifier of the process which instigated the connection.

Not supported for Mac OSX  earlier than Mac OSX Lion (10.7).

11828
  • $TCP_Live
ProcessNamestring

The executable filename of the process which instigated the connection

Connections originated from system-oriented processes are captured as "(system)"

chrome.exeAll
TSinteger

See Agent Historic Data Capture.

The Agent assumes a "new" installation/uninstallation has occurred at the point of polling.

1500756083

All

The Agent captures TCP connections, not UDP connections - as UDP is inherently connectionless (each packet sent is effectively a new connection).

Each time the Tachyon Agent starts it does an initial scan of connections before it starts capturing. A limitation of the Windows API is means that all established TCP connections, whether inbound or outbound, are captured; there is no way to distinguish between the two. This means that it is possible for the Agent to double-capture a connection if that connection was established before the Agent stops monitoring, and still exists when the Agent starts monitoring again, for example between Agent restarts. Unlike other capture sources, there is no persistent storage setting to prevent double-counting.

The Agent captures initial "connect" requests, not just successful connection establishment. This means that an attempt to perform a connection will be captured, even if that connection does not complete, for example, because of a timeout, or the server-side does not permit the connection.