In a Tanium™ deployment, content refers to sensors, packages, saved questions, dashboards, categories
- 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 their Technical Account Manager (TAM) 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 sensors and packages as a models for your custom content. As a best practice, do not edit content that is provided through Tanium content packs; create custom content instead. For details, see Tip 4: Limit customizations to Tanium content. 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 deployment.
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 for which you configure permissions according to the role-based access control (RBAC) setup of your Tanium deployment. For details, see Managing content sets.
Last updated: 4/2/2020 7:12 PM | Feedback