Skip to content

Tanium Sensor Repository

Custom Tanium sensors, with the script source and the console settings needed to recreate each one.

A sensor answers a question in Interact. It runs on every targeted endpoint each time the question is asked, so it has to return in seconds. Anything slower belongs in a package.

Sensor What it answers Platform Updated
.NET App Dependencies Which apps use each .NET runtime, which version they really load, and which carry their own copy? Windows 2026-11-05
Certificate Expiration Which machine certificates expire soon, or have already expired? Windows, Linux, macOS 2026-09-24
Find File by Name Does this file exist in these folders, and when was it last modified? Windows 2026-09-18
IIS - PHP Usage Which IIS sites still run PHP, which version, and is anyone requesting their pages? Windows 2026-11-05
Java - Install Usage - Prefetch Which Java on this machine actually runs, and which never has? Windows 2026-11-06
Java - Last Run - Prefetch Has Java run on this machine recently, and when? Replaced by Java - Install Usage - Prefetch Windows 2026-11-03
Java - Runtime Inventory - Dependencies Which Java runtimes are installed, and what uses each one? Windows, Linux 2026-09-25
Java - Scheduled Tasks Does any scheduled task launch Java? Windows 2026-11-03
Running Processes - Paths - Hashes Which programs are running, from which path, and with what file hash? Windows, Linux 2026-11-04
Scheduled Tasks - By Command Which scheduled tasks run a given program, path, or script? Windows 2026-11-03

Conventions used here

  • Naming: short and plain, since the name becomes part of every question typed in Interact. Avoid brackets, quotes, and |, which Interact uses for parameters and column splitting. Avoid reserved words such as and as well: the console warns that a name containing one must be wrapped in quotation marks in questions.
  • Parameters are read through placeholders such as ||FileName||. The parameter Key in the console must match the placeholder exactly, including capitalization.
  • Parameters arrive URL-encoded. Tanium passes *.pst to the script as %2a%2epst. Every script that takes a parameter decodes it before use.
  • Multi-column results use | as the delimiter, with the columns defined in the sensor settings.
  • Time budget. Each script stops itself before the sensor timeout and returns a status line instead of being killed mid-run. Set the sensor timeout above that internal limit.
  • One sensor, one script per platform. Windows, Linux, and Mac scripts live in the same sensor instead of separate sensors per OS.
  • Status results are never empty: None when nothing matches, Not Applicable when the feature is not on that endpoint, and Error: <reason> on failure. The reasons come from a fixed list, so you can filter the results. Find File by Name is older than this rule and still uses NOT FOUND style text.
  • Read-only. Sensors never change anything on the endpoint.

Before creating a sensor

  1. Replace the ||Parameter|| placeholders with real values in a test copy, then run it locally to confirm it works and to measure the run time.
  2. Compare that run time against the sensor timeout. A sensor is re-run on every question, so anything close to the limit will hurt at scale.
  3. Check the Max Sensor Age. Tanium uses saved results for this time before the script runs again.