Protocols Are Not Protection
The Washington Hilton claims it followed Secret Service protocols to the letter on the night of the attack. That is exactly the problem. When an organization hides behind "standard operating procedure" after a catastrophic failure, they aren't describing a defense; they are describing an alibi.
The lazy consensus suggests that if you check every box on a federal security checklist, the outcome is out of your hands. This is the Security Theater Fallacy. It is the comfort of the clipboard over the reality of the street. In the high-stakes world of executive protection and venue management, "following protocol" is often the very thing that creates the blind spot an attacker exploits. You might also find this similar story useful: The Berdegué Mandate and the High Stakes of Mexico's Broken Food System.
Protocols are static. Threats are liquid. When you freeze your defense into a set of pre-approved movements, you give the adversary a fixed map. The Washington Hilton’s defense—that they did what they were told—ignores the fundamental duty of a private entity hosting global power: the duty to think beyond the minimum viable requirement.
The Myth of the Perimeter
We need to stop talking about "secure zones" as if they are physical realities. They are psychological constructs. The competitor article leans heavily on the idea that the Secret Service owns the space. It treats the hotel as a passive vessel. As extensively documented in recent articles by Al Jazeera, the implications are widespread.
I have spent decades watching corporations and venues outsource their common sense to government agencies. Here is the brutal truth: The Secret Service is focused on the asset. The hotel should be focused on the environment. When those two goals don't mesh, you get a gap wide enough to drive a motorcade through—or a shooter.
Most people ask, "Was the perimeter breached?" The better question is, "Why did we assume the perimeter existed in the first place?"
A hotel is a sieve. It is designed for flow, for service, for hospitality. Trying to turn a luxury lobby into a fortress using government handbooks is like trying to use a sieve to carry water. You can move fast, but you're still going to lose the contents. The Hilton’s reliance on federal protocols is an admission that they prioritized administrative compliance over genuine situational awareness.
The Liability of Compliance
The industry treats compliance as a shield against lawsuits. In reality, it’s a trap.
If you only do what the Secret Service asks, you have effectively capped your security at the level of a federal budget and a bureaucrat's imagination. Real security requires redundancy and friction.
Imagine a scenario where a hotel manager notices a suspicious person in a "grey zone"—an area just outside the official Secret Service sweep. In a protocol-heavy environment, that manager often does nothing because they don't want to overstep or interfere with the "professionals." They wait for the agency to act. By the time the agency acts, the window of prevention has closed.
This is the Bystander Effect institutionalized. By claiming they followed protocol, the Hilton is inadvertently admitting they stayed in their lane while the car was heading for a cliff.
Human Capital vs. Hardware
The "Secret Service protocols" mentioned in the news usually involve physical hardware: magnetometers, barricades, and encrypted comms. This is the easy stuff. It’s the expensive toys that make stakeholders feel safe.
But hardware fails. Software is hacked. The only thing that actually works is human intuition, which protocols actively suppress. When you tell a security team to "follow the manual," you are telling them to stop looking at the room and start looking at the checklist.
I’ve seen venues spend millions on "cutting-edge" surveillance while paying their floor staff minimum wage and giving them zero training on behavioral detection. They want the optics of safety without the sweat of excellence.
The Transparency Trap
The hotel’s insistence on their adherence to protocol is a PR move, not a security one. It’s designed to settle the nerves of future event planners and shareholders.
But transparency in security is often a liability. By confirming exactly which protocols were in place, the industry provides a blueprint for the next attempt. We are obsessed with "demystifying" (to use a term I despise) the process, when we should be embracing the unpredictable.
A truly secure venue doesn't just follow the Secret Service’s lead. They layer their own, unpublished, idiosyncratic measures on top. They create a "black box" of security that an outsider cannot map. The Hilton did the opposite. They followed a known, predictable, and ultimately bypassable routine.
The Failure of "Standard" Professionalism
We are taught that "professionalism" means following the rules. In high-risk environments, professionalism means knowing when the rules are insufficient and having the stones to do more.
The Secret Service is a massive bureaucracy. It moves slowly. It has internal politics. It has budget cuts. If your entire defense strategy is anchored to the performance of a government agency, you aren't managing risk; you are gambling with it.
The Washington Hilton’s stance is a classic example of Responsibility Shifting. If they followed the rules and something went wrong, it’s the rules' fault. If they followed the rules and something went right, it’s their success. It is a win-win for the lawyers and a lose-lose for the people inside the building.
Stop Asking if They Followed the Rules
The media is obsessed with the wrong metric. They want to know if a specific gate was locked or if a specific ID was checked. They are looking for a singular point of failure.
Security is not a chain; it’s a web. When one strand breaks, the web should hold. If the Hilton’s defense is that they kept their strand intact while the Secret Service’s strand snapped, they are missing the point of being a partner in a high-profile event.
You don't get a pass for standing by while your partner fails. You are both in the web.
The Cost of the Alibi
The insistence on protocol over outcomes is a plague in the hospitality industry. It creates a culture of "not my job."
- "Did you see the man with the bag?" Not my job, the Secret Service handled that entrance.
- "Was the side door monitored?" The protocol didn't require a guard there.
- "Why was the response delayed?" We were waiting for official clearance.
This is how people die. They die in the gaps between protocols. They die because someone was more afraid of breaking a rule than they were of a threat.
The Washington Hilton's statement isn't a badge of honor. It is a confession of systemic passivity. They played their part in a scripted play while the real world was screaming off-book.
If you want to protect a President, or a CEO, or a guest, you have to stop acting like an extra in someone else's security theater. You have to own the space. You have to ignore the "standard" and pursue the "exceptional." Anything less is just waiting for the next headline.
The protocol didn't fail. The belief in the protocol did.
Stop looking for the checklist. Look for the threat.
