Integrity Monitor requirements

Review the requirements before you install and use Integrity Monitor.

Tanium dependencies

In addition to a license for Integrity Monitor, make sure that your environment meets the following requirements.

Component Requirement
Tanium™ Core Platform 7.2 or later

If you are using an older version, contact your Technical Account Manager (TAM) before installing and using Integrity Monitor.

Tanium™ Client
  • Windows:
    • 7.2.314.3584 or later
    • 7.4.1.1955 or later
  • Linux:
    • 7.2.314.3211 or later
    • 7.4.1.1955 or later
  • AIX:
    • 6.0.314.1437 or later
    • 7.2.314.3584 or later
  • Solaris:
    • 6.0.314.1321 or later
    • 7.2.314.3584 or later
    • 7.4.1.1955 or later

For best results with AIX and Solaris endpoints, use version 7.2.314.3584 or later due to known issues with file handling in the 6.0 client that were fixed in later versions.

For more information about specific Tanium Client versions and supported operating system versions, see Tanium Client User Guide: Host system requirements.

For more information about deploying the Tanium Client to endpoints with different operating systems, see the Tanium Client User Guide.

Tanium products

If you clicked Install with Recommended Configurations when you installed Integrity Monitor, the Tanium Server automatically installed all your licensed modules at the same time. Otherwise, you must manually install the modules that Integrity Monitor requires to function, as described under Tanium Console User Guide: Manage Tanium modules.

The following modules are optional, but Integrity Monitor requires the specified minimum versions to work with them:

  • Tanium™ Connect 4.0 or later
  • Tanium™ Trends 2.4 or later
Computer groups (Tanium Core Platform 7.4.2 or later only) When you first log into the Tanium Console after installing the Tanium Server, the server automatically imports the computer groups that Integrity Monitor requires:
  • All Computers
  • All AIX
  • All Linux
  • All Solaris
  • All Mac
  • All Windows Server 2019
  • All Windows Server 2016
  • All Windows Server 2012 R2
  • All Windows Server 2012
  • All Windows Server 2008 R2

Manual computer groups are not supported in Integrity Monitor.

Endpoints

Supported operating systems

The following endpoint operating systems are supported with Integrity Monitor.

Operating System Version
Windows A minimum of Windows 7 or Windows Server 2008 R2 (with SP1) is required.
Linux Same as Tanium Client support. See Tanium Client User Guide: Host system requirements.
AIX Same as Tanium Client support. See Tanium Client User Guide: Host system requirements.
Solaris Same as Tanium Client support. See Tanium Client User Guide: Host system requirements.

Linux requirements

For Linux endpoints:

  • Install the most recent stable version of the audit daemon and audispd-plugins. For information on deprecated parameters in the audit daemon configuration, see Tanium Client Recorder Extension User Guide. See the specific operating system documentation for instructions.
  • Be aware that when using immutable "-e 2" mode, the recorder adds Tanium audit rules in front of the immutable flag. When using the -e 2 flag on Linux, the endpoint must be restarted after the recorder is enabled.
  • Be aware that when using the failure "-f 2" mode, the Linux kernel panics in the event that auditd message is lost. The recorder does not add audit rules if this configuration is detected.

Disk space requirements

By default, the endpoint database is 1 GB in size. There must be three times the maximum database size available in free disk space on the partition where the Tanium Client is installed.

CPU and memory requirements

The CPU demand on the endpoint averages less than 1%. For full-functionality a minimum of two CPUs per endpoint is required. The Tanium Client Recorder Extension cannot operate on less than 2 CPU cores.

A minimum of 4 GB RAM is recommended on each endpoint device.

Client Recorder Extension

Integrity Monitor uses the Tanium™ Client Recorder Extension to gather data from endpoints. For more information, see Client Recorder Extension User Guide.

Integrity Monitor 2.0 and later includes an upgrade to Client Recorder Extension 2.0 or later, commonly referred to as the recorder. Recorder 2.0 and later includes significant improvements to performance and interoperability between modules that use the recorder (Integrity Monitor, Tanium™ Threat Response, and Tanium™ Map).

This upgrade does not require you to update all three modules at the same time, but conditional logic is applied to determine whether to upgrade the recorder component from version 1.x to 2.x when more than one of these modules is deployed to an endpoint. The recorder updates on an endpoint as follows:

  • If Integrity Monitor is the only module installed that uses the recorder, the endpoint updates to the new recorder when you upgrade to Integrity Monitor 2.0 or later.
  • If Threat Response 1.4.2 or earlier is installed along with Integrity Monitor 2.0 or later, the previous version of the recorder is used on the endpoint until you upgrade to Threat Response 2.0 or later.
  • If Map 1.2.2 or earlier is installed along with Integrity Monitor 2.0 or later and Threat Response 2.0 or later, the endpoint updates to the new recorder. Map will not function as expected until you upgrade to Map 2.0.

Integrity Monitor 2.5 and later includes an upgrade to Recorder 2.2 or later. Recorder 2.2 or later is required for Windows registry monitoring.

Integrity Monitor does not use the Client Recorder Extension for Solaris and AIX endpoints.

Tanium Event Recorder Driver

Use the Tanium Event Recorder Driver to record registry events on supported Windows endpoints. For more information, see Tanium Client Recorder Extension User Guide: Installing the Tanium Event Recorder Driver.

The Tanium Event Recorder Driver is installed by default when you deploy a monitor that is configured to use it. For more information, see Create a new monitor.

If you need to troubleshoot an issue with the Tanium Event Recorder Driver, see Manually install the Tanium Event Recorder Driver.

Third-party software

For integrating Integrity Monitor with an IT workflow in ServiceNow Change Management, the Madrid or later release of ServiceNow is required.

Host and network security requirements

Specific processes are needed to run Integrity Monitor.

Security exclusions

If security software is in use in the environment to monitor and block unknown host system processes, your security administrator must create exclusions to allow the Tanium processes to run without interference.

Table 1:   Integrity Monitor security exclusions
Target Device Notes Process
Tanium Module Server   <Module Server>\services\integrity-monitor-service\node.exe
Tanium Zone Server   <Zone Server>\proxy\node.exe
Windows x86 and x64 endpoints   <Tanium Client>\Tools\EPI\TaniumExecWrapper.exe
  <Tanium Client>\Tools\EPI\TaniumEndpointIndex.exe
  <Tanium Client>\Tools\IM\TaniumSQLiteQuery.exe
  <Tanium Client>\Tools\IM\TaniumExecWrapper.exe
  <Tanium Client>\extensions\TaniumRecorder.dll
  <Tanium Client>\extensions\TaniumRecorder.dll.sig
  <Tanium Client>\extensions\recorder\proc.bin
  <Tanium Client>\extensions\recorder\recorder.db
  <Tanium Client>\extensions\recorder\recorder.db-shm
  <Tanium Client>\extensions\recorder\recorder.db-wal
  <Tanium Client>\extensions\core\libTaniumPythonCx.dll
  <Tanium Client>\extensions\core\libTaniumPythonCx.dll.sig
  <Tanium Client>\TaniumClientExtensions.dll
  <Tanium Client>\TaniumClientExtensions.dll.sig
7.2.x clients <Tanium Client>\Python27\TPython.exe
7.4.x clients <Tanium Client>\Python38\TPython.exe
7.4.x clients <Tanium Client>\Python38\*.dll
  <Tanium Client>\TaniumCX.exe
Linux x86 and x64 endpoints   <Tanium Client>/TaniumAuditPipe
  <Tanium Client>/Tools/Trace/recorder
  <Tanium Client>/Tools/EPI/TaniumEndpointIndex
  <Tanium Client>/Tools/EPI/TaniumExecWrapper
  <Tanium Client>/Tools/IM/TaniumExecWrapper
7.2.x clients <Tanium Client>/python27/python
7.4.x clients <Tanium Client>/python38/python
  <Tanium Client>/libTaniumClientExtensions.so
  <Tanium Client>/libTaniumClientExtensions.so.sig
  <Tanium Client>/extensions/recorder/proc.bin
  <Tanium Client>/extensions/recorder/recorder.db
  <Tanium Client>/extensions/recorder/recorder.db-shm
  <Tanium Client>/extensions/recorder/recorder.db-wal
  <Tanium Client>/extensions/recorder/recorder.auditpipe
  <Tanium Client>/extensions/core/libTaniumPythonCx.so
  <Tanium Client>/extensions/core/libTaniumPythonCx.so.sig
  <Tanium Client>/TaniumCX
Table 2:   Integrity Monitor security exclusions
Target Device Notes Process
Windows x86 and x64 endpoints   <Tanium Client>\Tools\EPI\TaniumExecWrapper.exe
  <Tanium Client>\Tools\EPI\TaniumEndpointIndex.exe
  <Tanium Client>\Tools\IM\TaniumSQLiteQuery.exe
  <Tanium Client>\Tools\IM\TaniumExecWrapper.exe
  <Tanium Client>\extensions\TaniumRecorder.dll
  <Tanium Client>\extensions\TaniumRecorder.dll.sig
  <Tanium Client>\extensions\recorder\proc.bin
  <Tanium Client>\extensions\recorder\recorder.db
  <Tanium Client>\extensions\recorder\recorder.db-shm
  <Tanium Client>\extensions\recorder\recorder.db-wal
  <Tanium Client>\extensions\core\libTaniumPythonCx.dll
  <Tanium Client>\extensions\core\libTaniumPythonCx.dll.sig
  <Tanium Client>\TaniumClientExtensions.dll
  <Tanium Client>\TaniumClientExtensions.dll.sig
7.4.x clients <Tanium Client>\Python38\TPython.exe
7.4.x clients <Tanium Client>\Python38\*.dll
  <Tanium Client>\TaniumCX.exe
Linux x86 and x64 endpoints   <Tanium Client>/TaniumAuditPipe
  <Tanium Client>/Tools/Trace/recorder
  <Tanium Client>/Tools/EPI/TaniumEndpointIndex
  <Tanium Client>/Tools/EPI/TaniumExecWrapper
  <Tanium Client>/Tools/IM/TaniumExecWrapper
7.4.x clients <Tanium Client>/python38/python
  <Tanium Client>/libTaniumClientExtensions.so
  <Tanium Client>/libTaniumClientExtensions.so.sig
  <Tanium Client>/extensions/recorder/proc.bin
  <Tanium Client>/extensions/recorder/recorder.db
  <Tanium Client>/extensions/recorder/recorder.db-shm
  <Tanium Client>/extensions/recorder/recorder.db-wal
  <Tanium Client>/extensions/recorder/recorder.auditpipe
  <Tanium Client>/extensions/core/libTaniumPythonCx.so
  <Tanium Client>/extensions/core/libTaniumPythonCx.so.sig
  <Tanium Client>/TaniumCX

Service account user

The Integrity Monitor service account requires certain privileges to run background jobs which include gathering endpoint statistics, sending labels to Connect, and evaluating rules. See Installing Integrity Monitor to create a service account user and configure the service account within Integrity Monitor.

User role requirements

Integrity Monitor 1.2.1 introduced role-based access control (RBAC) permissions that control access to Integrity Monitor functions.

Table 3:   Integrity Monitor user role privileges for Tanium 7.1.314.3071 or later
Privilege Integrity Monitor Administrator Integrity Monitor Operator Integrity Monitor Author Integrity Monitor User Integrity Monitor Read Only User Integrity Monitor Service Account

Show Integrity Monitor

View the Integrity Monitor workbench.

Integrity Monitor Use API

1 1 1 1 1 1

Integrity Monitor Monitor Event Labels Read

View monitor event labels.

1 1 1 1

Integrity Monitor Watchlists Read

View watchlists.

1 1 1

Integrity Monitor Rules Read

View rules.

1 1 1 1

Integrity Monitor Monitor Events Read

View monitor events.

1 1 1 1

Integrity Monitor Monitors Read

View monitors. View and download reports.

1 1 1

Integrity Monitor Settings Read

View general settings, templates, and default labels.

1 1

Integrity Monitor Monitor Event Labels Write

Create and edit monitor event labels and label notes.
Send labeled events to Connect manually.2

1 1

Integrity Monitor Watchlists Write

Create and edit watchlists.

Integrity Monitor Rules Write

Create and edit rules.

Integrity Monitor Monitors Write

Create and edit monitors.
Enable, disable, or delete reports for a monitor.

Integrity Monitor Settings Write

Update general settings, templates, and default labels.

Integrity Monitor Monitor Event Labels Delete

Delete monitor event labels and notes.

Integrity Monitor Execute Scheduled Task

Execute tasks in the IM service via the IM schedule plugin, including sending labeled events to Connect via a background scheduled task and scheduling the weekly day and time to generate reports.
Execute and apply rules to events.

Integrity Monitor Deploy Monitors

Deploy monitors.

Integrity Monitor Deploy Rules

Deploy rules.

Trends Integration Service Account

Provides access for module service accounts to read and write data, and to define sources and boards.

Integrity Monitor Troubleshooting

Create, check the status of, and download the troubleshooting archive.

Integrity Monitor Admin Settings Write

Set the service account and log level.

Integrity Monitor Integrations Admin

Create, edit, and schedule integrations with IT workflows.

1 Denotes a provided permission.

2To send labeled events to Tanium Connect, you must have Connect installed. You must also have the Integrity Monitor Monitor Event Labels Write permission and the Tanium Connect Connect Event Write permission, which is provided through the Connect roles. The least privileged Connect role that an Administrator can assign to grant this privilege is Connect User.




Table 4:   Provided Integrity Monitor Advanced user role permissions for Tanium 7.1.314.3071 or later
Permission Content Set for Permission Integrity Monitor Administrator Integrity Monitor Operator Integrity Monitor Author Integrity Monitor User Integrity Monitor Read Only User Integrity Monitor Service Account
Execute plugin Integrity Monitor Events
Execute plugin Integrity Monitor
Execute plugin Connect
Execute plugin Trends
Read action Integrity Monitor Deployment
Read action Integrity Monitor Troubleshooting
Read filter group Reserved
Read filter group Default Filter Groups
Read filter group Integrity Monitor
Read filter group Integrity Monitor Deployment
Read saved question Integrity Monitor
Read saved question Integrity Monitor Events
Read sensor Reserved
Read sensor Base
Read sensor Integrity Monitor
Read sensor Integrity Monitor Deployment
Read sensor Integrity Monitor Events
Write action Integrity Monitor Deployment
Write action Integrity Monitor Troubleshooting
Write package Integrity Monitor Deployment
Write package Integrity Monitor Troubleshooting
Write saved question Integrity Monitor
Write saved question Integrity Monitor Events

Permission recording

Linux

To monitor permission event types, there are no special requirements for Linux endpoints.

Windows

To monitor permission event types, you must configure the Audit File System permission under Local Security Policy on the endpoint.

You can check to see if this permission is already configured by asking the question Get Integrity Monitor Endpoint Tools Status and Computer name from all machines in Tanium™ Interact. If the permission is not configured, endpoints report the following, depending on the version of Client Recorder Extension that is installed: Recorder - Error: File permission auditing is disabled.

Client Recorder Extension Version Error Messages
Client Recorder Extension 1.0

Audit Policy for File System auditing is configured for: No Auditing

or

Audit Policy for File System auditing is configured for: Failure

followed by

Error: Audit Policy for File System auditing is not properly configured

Client Recorder Extension 2.0

Recorder - Error: File permission auditing is disabled

To configure the Audit File System permission, complete the following steps. (This procedure is based on Windows 10 and might vary for different versions of Windows.)

  1. Open Local Security Policy, usually found in the Administrative Tools folder.
  2. Expand Advanced Audit Policy Configuration under Security Settings.
  3. Expand System Audit Policies - Local Group Policy Object.
  4. Double click Object Access.
  5. Double click Audit File System.
  6. Select Configure the following audit events: and then select Success.
  7. Click Apply and then click OK.