Jan 2, 2019 · 37m · a16z
a16z Podcast | The Fundamentals of Security and the Story of Tanium’s Growth
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In an Andreessen Horowitz podcast episode, a16z co-founder Ben Horowitz interviews Tanium co-founder Orion Hindawi about the flaws in legacy enterprise cybersecurity, the critical importance of basic security hygiene, and how Tanium built a real-time endpoint management platform to secure complex corporate networks.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
speaking balance: gold is the host, purple is the guest (3 minute bins)
Orion directly rejects the argument of point solution vendors, asserting they intentionally make simple problems sound complicated merely to validate their commercial existence.
Hardest push from the host ▶ 2:37 Challenging 5-year R&D durationBen refuses to passively accept scale as a justification for a 5-year R&D cycle, pointing out that Orion's team had already built a similar product at BigFix.
Biggest teaching moment ▶ 11:38 Exposing 1,500 hidden network exitsOrion educates the host on perimeter security blind spots by recounting how a telecom client boasting 22 heavily guarded entry points actually had 1,500 unmanaged exits built by employees.
The host holds their own ▶ 9:46 Framing IBM's incumbent disadvantageBen demonstrates sharp industry acumen by recognizing that Orion's chief competitor, IBM, is disadvantaged because it sells software Orion himself designed as an 18-year-old.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The host as informed peer | Guest teaching | Guest disagreement | The host pushing back | Why |
|---|---|---|---|---|---|---|
| Architectural Flaws of Legacy Hub-and-Spoke Models | 5 | 5 | 1 | 3 | Ben Horowitz pushes on why building Tanium required five years of R&D when the team had already built BigFix, prompting Orion to explain the edge cases of refactoring topology for decentralized encryption. Ben demonstrates domain familiarity with enterprise software scale and development complexity. | |
| Endpoint Visibility in High-Profile Cyber Breaches | 3 | 5 | 2 | 1 | Orion gently reframes Ben's specific question about Home Depot to discuss breach post-mortems generally, explaining how Tanium bridges the gap between security urgency and operational ROI. | |
| Competing Against Legacy Tech and Market Incumbents | 6 | 6 | 2 | 2 | Ben highlights the M&M security metaphor and IBM's legacy tech monetization. Orion educates on perimeter failures, referencing a major telco that thought it had 22 entrances but had 1,500 unmanaged internet paths. | |
| Prioritizing Basic Cybersecurity Hygiene Over Cloak-and-Dagger | 4 | 5 | 2 | 1 | Ben asks why the industry over-indexes on perimeter defense over endpoint hygiene. Orion criticizes fluffy analytics tools and explains that security founders prefer sexier spy-thriller problems over basic patch management. | |
| Pilot Deployments and Uncovering Unused Software Savings | 4 | 4 | 1 | 1 | Orion details how pilot deployments uncover unused software licenses, allowing customers to self-fund Tanium from operational savings. Ben quickly grasps the economic model, quipping that it is great for customers but bad for Microsoft. | |
| Real-Time Detection and Reducing Attacker Dwell Time | 4 | 6 | 2 | 2 | Ben asks whether Tanium can prevent all malware from entering. Orion clarifies that total prevention is an illusion against modern targeted attacks, shifting the goal to reducing attacker dwell time to seconds. | |
| Balancing System Performance and Eliminating Professional Services | 5 | 5 | 2 | 1 | Ben notes that Orion's zero-services strategy crashes IBM's enterprise software business model. Orion details why professional services create a moral hazard by incentivizing buggy and complex software. | |
| Expanding Addressable Market Through Platform Extensibility | 5 | 5 | 3 | 3 | Ben plays devil's advocate for point-solution vendors that claim deep specialization. Orion sharply rejects their premise, stating point vendors inflate complexity to justify their existence when platform modules can solve the same problems with far less code. | |
| Audience Q&A: Mobile Device Management and Hardware Integration | 3 | 6 | 2 | 1 | During audience Q&A, Orion breaks down why Mobile Device Management is flawed due to Apple's consumer-focused sandbox philosophy, explaining Tanium's strategy to integrate direct chip-level management with Intel and Qualcomm. |