Other versions

Managing content sets

A content set is a group of sensors, saved questions, dashboards, categories, and packages to which a permission applies. You create a content set when the nature of the content requires fine-grained assignment of permissions.

Role requirements

You must have the Administrator role or Content Set Administrator role to see and use the Content Set configuration page.

Special content sets

  • You cannot move content to or from the Reserved content set. This content set includes fundamental sensors used by the system.
  • Tanium solution modules might lock down module-defined content sets in a manner similar to reserved content sets. In other words, they have been designed to limit end users from moving content into or out of the module-designed content set.

Create content sets

  1. Go to Permissions > Content Sets.
  2. Click New Content Set.
  3. Specify a configuration name and description. Click Save.
  4. Click Preview to Save to display a diff of the changes.
  5. Review the changes and then click Confirm & Save.

Move content to a content set

  1. Go to Permissions > Content Sets.
  2. Browse the content set configuration and select the objects you want to move.

    Use the Filter by text box to filter the items displayed.

  3. Click Move to and select the target content set.
  4. Click Save.
  5. Click Preview to Save to display a diff of the changes.
  6. Review the changes and then click Confirm & Save.

Move content to a content set from the Authoring pages

On the Authoring pages, you can move content from one content set to another. On the Sensors page, for example, when you select one or more rows in the configuration table, the Move to Content Set button appears in the buttons above the table. You can use this feature to move selected configurations to a target content set. It is equally as effective as the preceding procedure.

Figure  1:  Changing content sets from the Authoring pages

You can move saved questions, sensors, or packages between content sets for which you have Write permission. Users with the Administrator or Content Set Administrator reserved role can move content between any content sets.

The Authoring pages have descriptions of the sensors, packages, and saved questions, so you might find it helpful to do this procedure from the Authoring pages when you are unfamiliar with the content and want to become familiar with it before moving it.

Specify a content set when you create content

When you create content (sensors, packages, saved questions, dashboards, and categories), you specify the content set to which the content belongs. The content set drop-down list includes the content sets for which you have Write permission. For example, if you have Write Sensor permission on three content sets, the drop-down list includes those three.

Figure  2:  Content Set field

When modifying a configuration, users can move saved questions, sensors, or packages between content sets for which they have write permissions. Users with the Administrator or Content Set Administrator reserved role can move content between any content sets.

Review users with permissions to a content set

  1. Go to Permissions > Content Sets.
  2. Browse the content set configuration to find an object you want to review (a sensor, for example).
  3. Click the icon to view user permissions and the icon to view user group permissions.
  4. Click OK to dismiss the dialog box.

Import/export the content sets and roles configuration

We recommend that you test content sets and roles in your lab before importing the configuration into your production environment.

Role requirements

Users with the Administrator and Content Set Administrator reserved roles can export and import the content sets and roles configuration.

Export

  1. From any Authoring, Content Sets, or Roles page, click the Export to XML link in the top right.
  2. In the Export Content selection box, select the Content Sets and Roles item and click Export.
  3. Enter a file name or use the default and click OK.

The exported configuration is an XML file that specifies the configuration names and settings. The content set section of the file includes the content set configuration names but not the content set assignments. Those assignments are contained in the content object configuration. To export those settings, you must also select the content items (sensors, packages, saved actions, categories, and dashboards) in the Export Content selection box.

Import

  1. From any Authoring, Content Sets, or Roles page, click the Import from XML link in the top right.
  2. Browse to and select the configuration file and click Import.
  3. When you import an XML configuration, an element in the XML might have the same object name as an existing object. If a conflict occurs, you can view the conflicts in the Import XML dialog box.

  4. Review the summary. Select Overwrite to resolve the conflict in favor of the imported settings or select Skip to resolve the conflict in favor of the current settings.
  5. Click Proceed with Import.

You must use KeyUtility.exe to sign XML files before you import them. You must also copy the public key for the key that signed the XML file to the Tanium Server keys folder. When you import content, the Tanium Server verifies the signature on the imported content against its store of content signing key files. See Signing content XML files.

Delete a content set

A content set configuration must be empty to be deleted.

Align content for modules

In some cases, Tanium solution modules require module-created sensors, packages, and saved questions to remain in special module-created content sets. If content is moved, the solution module workflow might not work as expected.

Modules report misaligned content to the Tanium Console Content Alignment page.

Role requirements

You must have the Administrator role or Content Set Administrator role to see and use the Content Alignment page.

Align module content to module requirements

  1. Go to Authoring > Content Alignment.
  2. Review the list.
  3. Click Align All Content.

Last updated: 5/16/2018 1:12 PM | Feedback