In a Tanium™ deployment, content refers to sensors, packages, saved questions, dashboards, categories, filter groups, and plugins. Tanium provides predefined content through content packs
You cannot create custom sensors in a Tanium as a Service deployment.
Content developers require the following knowledge and experience:
- Understand the Tanium platform
- Expert knowledge of the endpoint operating system
- Experience writing and testing scripts written in VBScript (Windows), shell script (non-Windows), or Python
Your team might include content developers who create saved questions that you can reissue at scheduled intervals or that you can associate with packages for deploying actions. These content developers do not necessarily write scripts, but they must be aware of the systems and processes running on endpoints, understand the impact that scheduled questions and actions might have on endpoints, and make any necessary adjustments. Most customers leverage the content provided in Tanium content packs and solution modules as much as possible, and work with Tanium Support (see Contact Tanium Support) on customizations and new use cases.
When developing content for the Tanium Core Platform, examine the content in the Tanium content packs as examples of code and settings that were tested for best results. Use the tested
Another best practice is to develop and test custom content in your lab environment before distributing the content to the production servers in your Tanium Core Platform deployment. You can use the Tanium Console to export and import content between Tanium Servers: see Manage Tanium shared services and content.
Tanium might deliver package files from third-party providers. For more information on each package, please refer to the README.txt file that is referenced with the package.
All content is assigned to content sets. To grant users access to the content sets, you specify content set permissions in advanced and module roles, and then assign those roles to users and user groups. For details, see Managing content sets.
By default, users own the content that they create, but you can transfer ownership from a non-active user when necessary. For details, see Delete, disable, or transfer ownership for the content of a non-active user.
Last updated: 10/15/2020 11:18 AM | Feedback