This documentation includes content for releases that might not be available on-premises. For the latest on-premises Trends documentation, see the PDF version of Tanium™ Trends User Guide version 3.9.324.
Gaining organizational effectiveness
The three key organizational governance steps to maximizing the value that is delivered by Trends are as follows:
- Develop a dedicated change management process. See Change management.
- Validate cross-functional alignment. See Organizational alignment.
- Track operational maturity. See Operational metrics.
Develop a tailored, dedicated change management process for data visualizations, taking into account the new capabilities provided by Tanium.
- Update SLAs with elevated expectations, including data visualization configuration and maintenance.
- Identify key resources in the organization to review and approve changes to data visualizations to ensure minimal unexpected or unapproved changes.
- Identify maintenance windows for various data visualization scenarios to maximize uptime.
- Create a Tanium steering group (TSG) for data visualization activities, to expedite reviews and approvals of processes that align with SLAs.
Successful organizations use Tanium across functional silos as a common platform for high-fidelity endpoint data and unified endpoint management. Tanium provides a common data schema that enables security, operations, and risk/compliance teams to assure that they are acting on a common set of facts that are delivered by a unified platform.
In the absence of cross-functional alignment, functional silos often spend time and effort in litigating data quality instead of making decisions to increase awareness of data visualizations at all levels of the organization.
Managing data visualizations successfully includes operationalization of the technology and measuring success through key benchmarking metrics. The four key processes to measure and guide operational maturity of your Tanium Trends program are as follows:
|Usage||How and when Tanium Trends is used in your organization|
|Automation||How automated Tanium Trends is|
|Functional Integration||How integrated Tanium Trends is, across IT security, IT operations, and IT risk/compliance teams|
|Reporting||How automated Tanium Trends is and who the audience of data visualizations is|
Use the following table to determine the maturity level for Tanium Trends in your organization.
|Process||Usage||Tanium Core Platform and Trends installed||Trends boards, panels, and sources created and in use||Tanium administrators rely on Trends boards to monitor health of environment, investigate and take action||
Multiple boards in use to track organization key performance indicators, set goals, and strategic initiatives
New sources created as standard operating procedure to important upgrades, vulnerabilities, events, and incidents
Custom sensors or modify an existing sensor specifically for use as a Trends source are in use
Custom RBAC roles and content sets to restrict access to boards and sources
|Automation||Tanium module boards automatically imported into Trends||Creating sources to track key results and metrics over time||Use Connect to periodically publish and email Trends boards to major stakeholders||Conditional and advanced formatting to prioritize further investigation and action||Conditional and advanced formatting to prioritize further investigation and action|
|Functional integration||Trends is functionally siloed within Operations and Security||Utilizing Trends for basic reporting and actions||Exporting to internal systems for reporting and actions; end-users access to Trends to access dashboards||Utilizing Trends imports and exports to move boards, panels, and sources between Tanium environments||Utilize Trends API to publish Trends boards to an internal portal (optional)|
|Reporting||Unused||Ad hoc; Tanium administrators||Consistent; Reporting tailored to stakeholders on cadence||Automated; Reporting tailored to stakeholders ranging from Operator to Executive||Automated; Reporting tailored to stakeholders ranging from Operator to Executive|
Last updated: 5/30/2023 3:49 PM | Feedback