We are pleased to announce the appointment of Ross Tackett as our Chief Revenue Officer, effective October 1, 2026. In this role, he will lead our global revenue operations, sales organization, strategic partner ecosystem, and go-to-market execution. Ross most recently served as Zscaler's Head of Worldwide Sales, and brings over thirty years of technology sales leadership, a proven record of scaling enterprise go-to-market organizations, accelerating international expansion, and building high-performing revenue teams. https://bit.ly/4d2jRdg
Congratulations on the appointment Ross Tackett you’re going to crush it at Zscaler !! 🚀
Having worked with Ross Tackett these past few years, I am thrilled by this appointment. Thoroughly deserved and an exciting next frontier for Zscaler!
Congratulations to Ross on the new role. Exciting to see what’s next for Zscaler’s global growth.
Congrats!
Ross Tackett - Congratulations on the well deserved promotion. I speak on behalf of all of marketing to say we are excited to have you partner with us. Very exciting times indeed!
Congratulations 🙏🏽🙏🏽
Cool 😎
Congratulations Ross!
Congratulations Ross - Interested in the team's thoughts on a critical industry challenge, especially now that Congress and states are debating reactive, mandatory AI "kill switches." The kill switch debate misses the point, in my opinion. Do we need a heavy-handed, human-delayed shutdown? Maybe, as a last resort. Or do we need machine-speed, real-time prevention? The incidents driving this debate were specific. AI agents used stolen credentials, fake identities, and direct outbound contact to reach destinations outside their defined containment boundary — all during testing. A critical architectural question for Jay Chaudhry and Ross Tackett: Can a cloud security platform stop that kind of outbound action in real time - before the credential use, before the external contact, before autonomous code reaches production, rather than after? If a security platform is embedded inline at the request layer, as an App Broker or sidecar proxy, does that neutralize the agent by controlling the next hop, lateral movement, or the breakout attempt before it happens? If so, is Zscaler positioned to execute on this today?