most conferences sell you a look at where the industry has been. Black Hat does the opposite. The research that lands on its stage in August tends to become the thing your security team is dealing with by the following spring, which is why people who run enterprise technology read the program like a weather report. This year is my first time in the room, and I have been looking forward to it for months.

The timing is the reason.

Artificial intelligence has moved into real work faster than any technology I have watched in twenty-five years. Teams are shipping AI into customer service, into code, into the browser your staff uses all day, and they are doing it quicker than anyone can write the rules for keeping it safe. A show built around the people who find the weak spots, before the rest of us feel them, could not be better timed.

The value is in the room, not just on the stage

Black Hat USA runs its 29th year at the Mandalay Bay Convention Center in Las Vegas. The two days that matter to me are the Briefings on August 5 and 6, where researchers present work that a board of more than a hundred experts has already picked apart before it goes live (Black Hat, 2026). That vetting is what separates this from a vendor showcase. Nobody gets the stage on a marketing budget.

What has me most excited, though, is the calendar. I already have a run of one-on-one meetings lined up with security companies across the two days.

Scanning the sponsor list, I keep running into names I know. People I have talked with over the years, teams I have watched build. Once word got around that I was coming, a good number of them reached out to grab time. That welcome means a lot to a first-timer, and it says something about how much this community shows up for each other.

The stage tells you what the researchers found. The meeting room tells you what the companies are going to do about it. Both halves are the story, and getting to sit across the table from the teams building the defenses is the part I would not trade.

What I want to bring home for the people who read this

I cover this for chief information officers and chief technology officers, the leaders who have to decide what to trust and what to hold off on. They do not need me to relay a product pitch. They need to know which of the coming worries are real and which are noise.

So I am going in with one plain question, and I will be asking it in every meeting. When one of these AI systems gets tricked into doing the wrong thing, what stops it before the damage is done? A clear answer to that is worth more than any slide deck, and I plan to come home with a few.

If you are going to be in Vegas, find me. I would rather learn this alongside the people living it than read about it after.