Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Often we get the question, “What is the impact of the Tanium agent on the endpoint?” Today we’re going to unpack that answer as part of a series on optimizing the Tanium agent for your environment. In this series we’re going to explore expectations for endpoint agent load, look at agent tuning, talk about proper anti-virus exclusions, what to consider for virtual infrastructure, and more. Today we’re going to focus on the baseline load of the Tanium agent on your endpoints: disk, memory, CPU, network.

How do I tune Tanium for virtual infrastructure like VMs and VDI? Many folks who have worked in IT ops are familiar with the struggle of keeping virtual infrastructure properly resourced with memory, disk, CPU, and network. Sometimes it’s a balancing act of hardware, budget, and virtual machines. Now you’re deploying a real time agent on every guest on those virtual hosts, so how can we make sure it doesn’t create a resource storm?

My endpoints have other agents beside Tanium. How do I get them to play well together? The onboarding checklist for every new Tanium customer includes a step on third party agent exclusions. Most IT shops have anywhere from 5 to 15 agents running on their servers and workstations, everything from antivirus to data loss prevention. So how can we make sure that Tanium functions well alongside those other agents? This is the next installment in our Tanium Agent FAQ series.