Configuring Patch

If you did not install Patch with the Apply Tanium recommended configurations, you must enable and configure certain features.

Configure global settings

You can configure the Tanium platform for optimal delivery of larger payloads, which are typically associated with patching activity.

  1. From the Main menu, go to Administration > Management > Global Settings.
  2. To increase the client cache size, click New Setting, provide the following information, and click Save.
    Setting Name: ClientCacheLimitInMB
    Setting Value: 2048
    Affects: Client
    Value TypeNumeric
  3. To increase the hot cache percentage, click New Setting, provide the following information, and click Save.
    Setting Name: HotCachePercentage
    Setting Value: 80
    AffectsClient
    Value TypeNumeric

Changes to global settings can take up to five hours to propagate to clients.

Install and configure Configure Tanium End-User Notifications

With the Tanium End-User Notifications solution, you can create a notification message with your deployment to notify the user that the system is going to restart, and give the user the option to postpone the restart.

For more information, see Tanium End-User Notifications User Guide: End-User Notifications overview.

Disable Windows Update restart prompts

The Windows Update Agent automatically prompts users to restart their machine when an update is installed from any user or source. The following Windows Local/Group Policies should be configured to allow Tanium End-User Notifications to control endpoint restarts.

  1. In the Windows Local Group Policy Editor, go to Computer Configuration > Administrative Templates > Windows Components > Windows Update.
  2. Enable the No auto-restart for scheduled Automatic Updates installations parameter.
  3. Disable the Re-prompt for restart with scheduled installations parameter.

Install and configure Configure Tanium Endpoint Configuration

Manage solution configurations with Tanium Endpoint Configuration

Tanium Endpoint Configuration delivers configuration information and required tools for Tanium Solutions to endpoints. Endpoint Configuration consolidates the configuration actions that traditionally accompany additional Tanium functionality and eliminates the potential for timing errors that occur between when a solution configuration is made and the time that configuration reaches an endpoint. Managing configuration in this way greatly reduces the time to install, configure, and use Tanium functionality, and improves the flexibility to target specific configurations to groups of endpoints.

Endpoint Configuration is installed as a part of Tanium Client Management. For more information, see the Tanium Client Management User Guide: Installing Client Management.

Additionally you can use Endpoint Configuration to manage configuration approval. For example, configuration changes are not deployed to endpoints until a user with approval permission approves the configuration changes in Endpoint Configuration. For more information about the roles and permissions that are required to approve configuration changes for Patch, see User role requirements.

To use Endpoint Configuration to manage approvals, you must enable configuration approvals.

  1. From the Main menu, go to Administration > Shared Services > Endpoint Configuration to open the Endpoint Configuration Overview page.
  2. Click Settings and click the Global tab.
  3. Select Enable configuration approvals, and click Save.

For more information about Endpoint Configuration, see Tanium Endpoint Configuration User Guide.

If you enabled configuration approvals, the following configuration changes must be approved in Endpoint Configuration before they deploy to endpoints:

  • Creating, updating, or deleting patch lists
  • Adding or removing enforcements
  • Removing all enforcements
  • Updating scan configuration priorities
  • Creating deployments
  • Stopping deployments
  • Adding targets to deployments
  • User-initiated actions, such as initializing endpoints, uploading custom field files, enabling Linux

Configure Patch

Configure service account

The service account is a user that runs several background processes for Patch. This user requires the Tanium Administrator or Patch Service Account role. If you installed Tanium Client Management, this This user requires the Endpoint Configuration Service Account role. Endpoint Configuration is installed as a part of Tanium Client Management. For more information about Patch permissions, see User role requirements.

  1. On the Patch Overview page, click Settings and then click Service Account if needed.
  2. Provide a user name and password, and then click Save.

Organize computer groups

One way to apply patches and view deployment results is by computer group. Create relevant computer groups to organize your endpoints. Some options include:

  • Endpoint type, such as servers or employee workstations
  • Endpoint location, such as by country or time zone
  • Endpoint priority, such as business-critical machines
  • Endpoint configuration needs, such as VDI machines

Manual computer groups are not supported in Patch. For more information, see Tanium Core Platform User Guide: Managing computer groups.

Organize computer groups by operating system generation for useful visibility and scan configuration targeting.

Computer group Filter Purpose
All Windows1 Is Windows equals True
  • Visibility
  • Patch action group
All Windows Servers1 Windows OS Type equals Windows Server
  • Visibility
  • Scan configuration targeting
All Windows Servers - Physical Windows OS Type contains windows and Is Virual equals no Scan configuration targeting
All Windows Servers - Virtual Windows OS Type contains windows and Is Virual equals yes Scan configuration targeting
All Windows Workstations Windows OS Type equals Windows Workstation Scan configuration targeting
All Windows Workstations - Physical Windows OS Type contains windows workstation and Is Virtual equals no Scan configuration targeting
All Windows Workstations - Virtual Windows OS Type contains windows workstation and Is Virtual equals yes Scan configuration targeting
All CentOS 61 Operating System Generation equals CentOS 6
  • Visibility
  • Scan configuration targeting
All CentOS 71 Operating System Generation equals CentOS 7
  • Visibility
  • Scan configuration targeting
All Red Hat 61 Operating System Generation equals Red Hat Enterprise Linux 6
  • Visibility
  • Scan configuration targeting
All Red Hat 71 Operating System Generation equals Red Hat Enterprise Linux 7
  • Visibility
  • Scan configuration targeting
All Oracle 61 Operating System Generation equals Oracle Linux Server 6
  • Visibility
  • Scan configuration targeting
All Oracle 71 Operating System Generation equals Oracle Linux Server 7
  • Visibility
  • Scan configuration targeting
All Amazon1 Operating System Generation equals Amazon Linux
  • Visibility
  • Scan configuration targeting
All Amazon Linux 1 Operating System Generation equals Amazon Linux 1
  • Visibility
  • Scan configuration targeting
All Amazon Linux 2 Operating System Generation equals Amazon Linux 2
  • Visibility
  • Scan configuration targeting
Tanium Scan Supported Windows Windows OS Major Version > 6.0 and Tanium Client Version >= 7.2.314.3211
  • Visibility
  • Scan configuration targeting
All Supported Linux Operating System Generation matches "(Amazon Linux(1|2)|(Oracle Linux Server (6|7))|(Red Hat Enterprise Linux.*(6|7))|(CentOS (6|7))"
  • Visibility
  • Patch action group
1 Patch creates this computer group if you select the Apply Tanium recommended configurations option during installation on Tanium Core Platform 7.4.2 or later.This computer group is created by default.

Add computer groups to Patch action group

Importing the Patch module automatically creates an action group to target specific endpoints. Select the computer groups to include in the Patch action group. By default, Patch targets No Computers.

Deselect No Computers and ensure that all operating systems that are supported by Patch are included in the Patch action group.

  1. From the Main menu, go to Administration > Actions > Action Groups.
  2. Select Patch and then click Edit.
  3. Select the computer groups that you want to include in the action group and Click Save.
    If you select multiple computer groups, choose an operand (AND or OR) to combine the groups.

Enable and configure Configure Windows features

Before you can use certain Patch features for Windows endpoints, you must enable or configure them:

Enable and configure Tanium Scan for Windows

For more information about Tanium Scan for Windows, see Tanium Scan.

  1. From the Patch menu, go to Scan Management.
  2. Click Tanium Scan for Windows and then click Edit.
  3. Select Enable Tanium Scan for Windows and select a scan source.
  4. Click Synchronize Now to perform the required initial synchronization.
  5. If you want to synchronize daily, select Enable Daily Synchronization.
  6. Use the arrows to select products to include in scans.

    Synchronize all products, regardless of which products are present in the environment. Selectively choosing products can cause gaps in critical or important patches.

  7. Use the arrows to select update classifications to include in scans.

    Select Critical Updates, Security Updates, Service Packs, and Update Rollups.

  8. Click Submit.

    Click Synchronize Now after you make any changes.

Configure Tanium Scan for Windows

  1. From the Patch menu, go to Scan Management.
  2. Click Tanium Scan for Windows and then click Edit.
  3. Use the arrows to select products to include in scans.

    Synchronize all products, regardless of which products are present in the environment. Selectively choosing products can cause gaps in critical or important patches.

  4. Use the arrows to select update classifications to include in scans.

    Select Critical Updates, Security Updates, Service Packs, and Update Rollups.

  5. Click Submit.

    Click Synchronize Now after you make any changes.

Configure WSUS Scan

  1. Add the WSUS Server URL.
    1. On the Patch Overview page, click Settings and then click Configuration Settings if needed.
    2. In the WSUS Server Configuration section, enter the URL and click Submit. A regular expression for the URL is generated and added.
    3. Click View Allowed URLs, or go to Administration > Management > Allowed URLs to view the entry that was added.
  2. On the WSUS server, change the following settings:
    1. Set the intranet URL for detecting updates and the statistics server to: http://<WSUS server URL>:<port>.
    2. Disable the Configure Automatic Updates setting.

Enable direct patch downloads from Microsoft

For Windows scan configurations, you can enable direct patch downloads from Microsoft to isolated remote endpoints. This option reduces the impact on network resources. If the direct download fails, the endpoint downloads patches from the Tanium Server.

Cautions and considerations

Endpoints must be in a list of virtual private network (VPN) subnets or allowed Zone Servers that you configure. Configure VPN ranges only where clients have a direct path to the Microsoft URLs that are listed in Internet URLs . The following configurations are recommended:

  • Define the IP address ranges that are used by endpoints that connect to Tanium over a split-tunnel VPN. Use for split-tunnel VPN ranges with a separate route to download patches from the Internet. Isolated endpoints within the defined ranges attempt to download patches directly from Microsoft.
  • Define the public IP addresses or Internet-resolvable fully qualified domain names of Internet-facing Zone Servers. Isolated Tanium Clients that are connected to these Zone Servers attempt to download patches directly from Microsoft.

Do not specify the following VPNs or Zone Servers:

  • Split-tunnel VPNs where endpoints still send traffic bound for Microsoft URLs through the internal corporate network
  • Full-tunnel VPNs
  • Zone Servers that are used in an internal security zone

Clients that use WSUS scan configurations leverage the location that is defined by WSUS. Unless the WSUS server is configured to download patches from Microsoft instead of storing them locally, do not enable direct downloads for a WSUS Scan configuration. For more information about how to specify where updates are stored, see Microsoft article Update storage options.

  1. On the Patch Overview page, click Settings and then click Configuration Settings if needed.
  2. In the Patch Direct Downloads section, specify network information:
    1. Select VPN Networks, Zone Servers, or both.
    2. Add one or more networks or servers, or, if previously created, choose from the list.
  3. Click Save.

Tracking direct download status

Review current and past patch downloads directly from Microsoft over the Internet.

  1. In Interact, ask the Get Patch - Direct Downloads Statuses from all machines question.
  2. Choose the time period in hours; for example, downloads in the last three hours.
  3. Choose whether to include in-progress downloads in the results.
  4. Choose whether to include failed downloads in the results.
  5. Click Ask Question.

The results grid shows a row for each download attempt and its status.

Enable and configure Configure Linux features

Before you can use certain Patch features for Linux endpoints, you must enable or configure them:

Enable Patch for Linux endpoints

Before you begin, ensure that you meet the prerequisites listed Tanium dependencies.

  1. On the Patch Overview page, click Settings .
  2. In the Operating Systems tab, select Linux: RedHat, CentOS, Oracle, Amazon and click Save.

    After you enable this option, you cannot disable it.

  3. (Optional) Add any custom Yum repositories.

    You can also edit existing Yum repositories by clicking Edit .

    1. From the Patch menu, go to Scan Management and then click Yum Repositories.
    2. Click Add Repository, provide the requested information, and then click Submit.

      Enable GPG Check and Repo GPG Check to confirm authenticity by verifying GPG signatures.

  4. (Optional) Create snapshots of Yum repositories. For more information, see Manage Linux repository snapshots.

(Red Hat endpoints) Configuring TDownloader to use certification authentication

For Tanium as a Service, Contact Tanium Support to configure TDownloader to use certificate authentication for downloads from the Red Hat Satellite server.

To use Patch on Red Hat Linux endpoints, you must configure Tanium Downloader (TDownloader) to use certificate authentication for downloads from the Red Hat Satellite server. Obtain a valid SSL client certificate and private key and the SSL certificate authority (CA) certificate of the satellite server from the Red Hat, Inc. website. For more information, see Creating a Red Hat certificate for Tanium downloads (login required) and Reference: TDownloader (login required).

Configure TDownloader on Taniumâ„¢ Appliance

  1. Upload the SSL client private key and client certificate to your Tanium Appliance. Use SFTP with the tancopy account and copy the files to the /incoming folder.
  2. Using the TanOS menu, verify that the Tanium Server can reach cdn.redhat.com or the Red Hat Satellite server by name:
    1. Enter 3 to go to the Tanium Support menu.
    2. Enter 4 to go to the Run Network Diagnostics menu.
    3. Enter 1 to select the Ping Remote System option.
  3. On each Tanium Server, add the CA root certificate for the Red Hat Satellite or content delivery network (CDN) server:
    1. Enter 2 to go to the Tanium Operations menu.
    2. Enter 2 to go to the Tanium Configuration Settings menu.
    3. Enter 13 to go to the Control RedHat CA Cert menu.
    4. Enter 2 to select the Install redhat-uep.pem option.
  4. On each Tanium Server, add the Red Hat Entitlement client certificate and key:
    1. Enter 2 to go to the Tanium Operations menu.
    2. Enter 2 to go to the Tanium Configuration Settings menu.
    3. Enter 4 to select the Add Tanium Server TDL Auth Cert option.
    4. Enter the URL (https://cdn.redhat.com or the Red Hat Satellite server), client certificate file name, and the SSL client private key file name at each prompt.
    5. At the #Line Content display, enter R to return to the previous menu.

For more information, see Tanium Appliance Deployment Guide: Manage authentication certificates for Tanium Patch connections with Red Hat.

Configure TDownloader on Windows

  1. Copy the SSL client private key, client certificate, and satellite server certificate to your Tanium Server.
  2. Ensure that the Tanium Server can reach cdn.redhat.com or the Red Hat Satellite server by name.
    Example:
    ping cdn.redhat.com
  3. On each Tanium Server, configure TDownloader to use certificate authentication for downloads to the Red Hat Satellite server.
    Example:
    cmd-prompt>TDownloader.exe add-auth-cert --url https://cdn.redhat.com --cert C:\client-certificate.pem --key C:\client-key.pem
    where:
    • https://cdn.redhat.com is the URL prefix for the satellite server download URLs
    • C:\client-certficate.pem is the client certificate
    • C:\client-key.pem is the client certificate private key
  4. Check the TDownloader config to see that your certificate has been configured.
    cmd-prompt>TDownloader.exe config list
    Keys:
      - Auth:
    - Auth.0:
    - Auth.0.Certificate: -----BEGIN CERTIFICATE----- MIIFPTCCBCWgAwIBAgIIbY/mIdQbgMowDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNV BAYTAlVTMRcwFQYDVQQIDA5Ob3J0aCBDYXJvbGluYTEQMA4GA1UEBwwHUmFsZWln aDEQMA4GA1UECgwHS2F0ZWxsbzEUMBIGA1UECwwLU29tZU9yZ1VuaXQxKjAoBgNV BAMMIXJoZWxwYXRjaHNhdGVsbGl0ZTAxLnByb2RxYS5sb2NhbDAeFw0xODA0MjAw NDAwMDBaFw0xOTA0MjAwMzU5NTlaMEYxGTAXBgNVBAoMEHRhbml1bV9wYXRjaF9k ZXYxKTAnBgNVBAMTIDBjYjk4NjcyZjBhNTQ0MDJhNzIzYmNjOGI5ODFjYTg3MIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtXPySC20fPzMreenmX+4mUhS s/cdArQZOeeKliCdXI7Q/ZW0ZrhsgmMZTL+BNbZKUp72e0L3GF3yj0wx/8LWRLVC S9AaZdbXmJRK7B5mwpQaLtfuE93bJIkmBbzKA49jiwFdDE0J6v+wj0NgBZ3hr0NH V2O1hAwar2xkzz9fCTwyAR6d2I9Dpcfua8nH0ybO5kR8v1Epp70vw9/uMmGM3PCe YFX81ll3wxStbHj/DznUzQ/vFE0SZxLXh9LyWy9Nq+obLaFeDxJ0DT7iXotwVqWs Qow/upQ60vuYpAT57JM5tkrP+rKcct+TVVJNS/QmJC3yOwZWf8rIISRH4cb+GQID AQABo4IB5jCCAeIwEQYJYIZIAYb4QgEBBAQDAgWgMAsGA1UdDwQEAwIEsDCBwQYD VR0jBIG5MIG2gBRNdbtnITo9NxbcUdarkRIJv464dqGBkqSBjzCBjDELMAkGA1UE BhMCVVMxFzAVBgNVBAgMDk5vcnRoIENhcm9saW5hMRAwDgYDVQQHDAdSYWxlaWdo MRAwDgYDVQQKDAdLYXRlbGxvMRQwEgYDVQQLDAtTb21lT3JnVW5pdDEqMCgGA1UE AwwhcmhlbHBhdGNoc2F0ZWxsaXRlMDEucHJvZHFhLmxvY2FsggkAx2ndp2OhmcYw HQYDVR0OBBYEFHX7IDsUYNAZdI5dBxckm5a8y60aMBMGA1UdJQQMMAoGCCsGAQUF BwMCMBIGCSsGAQQBkggJBgQFDAMzLjMwFAYJKwYBBAGSCAkIBAcMBUJhc2ljMIGd BgkrBgEEAZIICQcEgY8EgYx42i2MMQrDMBAE9zFukyYgfyJdHmDO8oIEis7cXYz9 e8ck1UwxjNM2GsbXj1bYsFQP6BpVuzRk7cEeSP8kYYRL3EK1OZ51NrED6f5ASK+f 97RK5DIt3KAO7mHiGIyN4rwGw/wVsVxwAp4aKvUSzZXb1epTaC96MJ25BX5rmucc vyYlbSe9CpomkcWhADANBgkqhkiG9w0BAQUFAAOCAQEAubxqAqH/IQqIODQwaX9x NrIuJp3qWIUFjxZ1Vby4lEg2xmwfBtvNKminJBWNwOMZjq40xrEz0C2sxqkr/npv cbI4MMdQX1rdxMwsntgUZK8ApRR/pPwyxqAoa8IjahVBHNdFoA4+BBjcLcvzA1PB PReiXo0GS2gQQAb8U7d/jBTG1gm3ZpJFBxv7NBM9tEey3DwzP5LWPnZZmstRrlfx 7sb5J/2zLvWuMG+dMJ5jkgUKTuNdccdBP9PEVrAKiDuoLCl4UqnP0YzMJd+e9Ktx FC1QCICFUQLhZ/QVAhh8hIw0jSxIcGN+KVJF52BGdzUxvoidfqtMsjc/8NSTRk+T /g== -----END CERTIFICATE-----
    - Auth.0.PrivateKey: (protected) - Auth.0.URL: https://rhelpatchsatellite01.prodqa.local - LogVerbosityLevel: 41 - ProxyPassword: - ProxyPort: - ProxyServer: - ProxyType: NONE - ProxyUserid: - TrustedCertPath: C:\Program Files\Tanium\Tanium Server\Certs\installedcacert.crt - TrustedHostList: localhost,tanium.local,win-2012-r2
  5. To configure TDownloader to work with the Red Hat CDN, use a text editor to append the PEM-encoded certificate for cdn.redhat.com to the end of the certificate file as referenced by the TrustedCertPath value from the previous step (Example: C:\Program Files\Tanium\Tanium Server\Certs\installedcacert.crt).
    ClosedExpand this section to view the certificate.

Manage Linux repository snapshots

Repository snapshots have the following requirements:

  • Minimum Patch version:
    • For deployments to Red Hat and CentOS Linux endpoints, Patch 2.4.1.
    • For deployments to Oracle Linux endpoints, Patch 2.4.3.
  • The Patch process must be running on all Linux endpoints. For more information, see Patch process is not running.
  • Patch must be enabled for Linux endpoints. For more information, see Enable Patch for Linux endpoints.
  • You must use the Tanium Scan for Linux scan method. For more information, see Tanium Scan.
  • You must create a scan configuration with the Use deployment snapshots for deployment option enabled. For more information, see Create a scan configuration.
  1. From the Patch menu, go to Scan Management and then click Yum Repositories.
  2. To create a snapshot, select a repository and then click Create Snapshot. Name the snapshot and click Confirm.
  3. To rename a snapshot, expand a repository and then click Rename Snapshot . Provide a new name and click Confirm.
  4. To permanently remove unneeded snapshots, click Delete Snapshot .
  5. To remove failed snapshots across all repositories; for example, those for which the environment was not properly set up, click Delete Failed Snapshots.

Initialize Patch endpoints

Patch installs a set of tools on each endpoint that you have targeted. Initializing or reinitializing Patch is a common troubleshooting step.

  1. On the Patch Overview page, click Help and then click Support if needed.
  2. Click Initialize Endpoints to start the Patch service and begin distributing these tools to your endpoints.