Firing a General Over a Leak Misses the Real Rot in Secrecy

Firing a General Over a Leak Misses the Real Rot in Secrecy

When a senior US general gets fired over a classified leak, the standard playbook kicks in within twenty minutes. Pundits call it a betrayal of oath. Cable hosts debate treason. Officials demand harsher punishment and tighter locks.

It is theater. Comforting, tidy, and completely wrong.

Firing a four-star officer over an unauthorized disclosure does not fix a broken secrecy system. Usually, it lets the institution off the hook. A single rogue official makes a much cleaner villain than an over-classified bureaucracy that hoards information until pressure forces a valve open.

I have spent years watching organizations in high-stakes, security-obsessed environments burn millions on lock-down theater while ignoring the incentives that create leaks in the first place. Badges get revoked. Audits get launched. Access lists shrink for a week, then quietly expand again because nobody can actually do their job in the dark.

The real story is rarely just one bad actor with a thumb drive or a loose lip. Often, the real story is a system so bloated with secrets that people start treating truth as contraband.

Why the "Rogue General" Story Lets Everyone Else Off the Hook

The lazy consensus goes something like this: a high-ranking officer had access to sensitive material, violated trust, damaged national security, and had to go. Case closed. Clean line between loyalty and treason.

That framing is catnip for headlines. It gives readers a recognizable moral drama. Hero vs. traitor. Duty vs. ego.

In reality, senior officials rarely operate in a vacuum. By the time someone reaches general rank, they have spent decades inside a culture where classification is both a shield and a currency. When information is over-classified—stamped top secret to avoid embarrassment, protect turf, or dodge congressional scrutiny—it loses credibility with the very people sworn to guard it.

Let us define the terms cleanly before going further, because sloppy vocabulary ruins half these debates. Classification is a legal and administrative marking under executive authority to protect information whose unauthorized disclosure could reasonably be expected to cause identifiable harm to national security. Leaking is the unauthorized release of non-public, often classified information to outside parties, typically the press. Whistleblowing is a legally protected disclosure through authorized channels—or, in narrow statutory cases, to specific oversight bodies—reporting illegality, fraud, abuse, or gross mismanagement.

People mash those concepts together all the time. A leak is not automatically noble, and an official firing is not automatically justice. Yet treating every leak as a pure failure of personal character ignores the architecture that makes leaking predictable.

Consider what happens inside rigid command hierarchies. Bad news travels upward slowly, if at all. Dissent gets filtered out before it reaches decision-makers. When a senior leader feels—rightly or wrongly—that civilian or military leadership is ignoring reality, or that internal channels lead to career suicide, the temptation to bypass normal channels grows.

That does not excuse breaking classification rules. Rules exist for a reason. Still, firing the messenger while keeping the incentives intact is like replacing a blown fuse with a heavier nail. The light comes back on right before the wall catches fire.

The Questions Everyone Asks Instead of the Ones That Matter

Whenever a general gets ousted over classified material, search bars fill up with the same predictable questions. Most of them start from a flawed premise.

Did the leak actually harm national security?

Sometimes yes. Sometimes less than officials claim. Sometimes nobody outside a small circle can verify the damage because the very evidence of harm is itself classified.

That asymmetry is a trap. Government agencies routinely assert "grave damage" whenever a leak exposes an awkward policy debate, a strained alliance, or an operational misstep. Having spent time advising leadership teams through high-risk disclosures, I have seen plenty of instances where "national security" was doing heavy lifting for "institutional embarrassment."

Real harm happens when a leak exposes sources, methods, active operational timelines, or technical vulnerabilities an adversary can exploit immediately. Policy friction leaked to a reporter is rarely in the same category as handing an enemy a blueprint. Lumping both together under the same outrage machine blurs actual risk with bruised pride.

Should a senior general face harsher punishment than a junior analyst?

Accountability should scale with responsibility. A general has deeper visibility, broader authority, and a sharper obligation to uphold standards than a mid-level staffer.

Yet harsher punishment alone is a blunt instrument. History—from Daniel Ellsberg's analysis of the Pentagon Papers to decades of security reviews—shows that draconian penalties deter some people while failing to stop systemic leaks. Why? Because people who leak out of ideological conviction, desperation, or institutional frustration often calculate that the stakes of silence outweigh the risk of prosecution.

If leadership wants fewer leaks, punishment is step ten, not step one. Step one is asking why senior leaders felt compelled to go outside channels, or why sensitive material was sitting on vulnerable networks and in sprawling distribution lists in the first place.

Is the military's classification system too secretive?

Yes. Almost everyone who works inside or alongside it admits this privately, even while defending it publicly.

Former senior officials—from intelligence chiefs like Michael Hayden and Robert Gates to legal scholars like Jack Goldsmith—have long warned that over-classification erodes both security and public trust. When millions of documents get classified every year, nothing feels truly sacred. Security clearances turn into a bureaucratic tide. Attention spreads thin.

Imagine a scenario where a command marks ninety percent of its daily reporting as restricted to protect itself from bad press. Analysts stop treating the stamp as a serious warning. Junior staff copy-paste old headers onto new memos out of habit. When a genuinely sensitive operational plan comes along, it sits in the same mental bucket as routine administrative chatter.

That is not a hypothetical stretch. It is the daily grind of over-classification.

What Actually Drives Leaks Inside High-Command Culture

Leaks rarely happen because someone wakes up one morning and decides to be chaotic for fun. They cluster around specific structural pressures.

Pressure Point Conventional Diagnosis Structural Reality Practical Consequence
Over-classification Employees lack discipline Too much mundane data is marked sensitive Real secrets lose distinct protection
Echo-chamber leadership Subordinates are timid Dissent is punished or ignored upstairs Insiders seek outside leverage
Sprawling access One person went rogue Large groups hold overlapping clearances Accountability diffuses across teams
Political crossfire Pure military misconduct Policy disputes spill into civil-military friction Leaks become weapons in turf wars

Look at that fourth row. Civil-military tension sits right underneath many high-profile security scandals.

Senior generals live at the intersection of uniformed service and civilian politics. They brief lawmakers. They manage coalitions. They watch administrations shift priorities while troops carry out orders on the ground. When friction builds between uniformed leaders and civilian policymakers, information becomes leverage. One side leaks to frame a narrative; the other fires someone to reassert control.

Sometimes the general is guilty of reckless indiscretion. Sometimes they are caught in a crossfire they helped start. Either way, a single dismissal rarely settles the underlying clash over strategy, oversight, or candor.

The Uncomfortable Trade-Offs of My Own Argument

Let us be straight about the blind spots here. Pushing back on knee-jerk firings has real risks, and pretending otherwise would make me just another loud voice selling easy answers.

First, excusing or minimizing unauthorized disclosures weakens the rule of law. If senior officers can decide for themselves which classified rules are worth following, discipline frays. A military cannot function if every commander treats classification guidelines as optional suggestions based on personal judgment.

Second, public skepticism of official damage assessments can go too far. Sometimes an agency really cannot explain why a leak hurt operations without revealing more secrets. Assuming bad faith every time an official warns of harm is just as lazy as believing every warning blindly.

Third, transparency has costs. Intelligence sources are fragile. Alliances rely on quiet assurances that private conversations will stay private. If partners stop trusting Washington—or any major institution—with sensitive information because leaks keep happening, real strategic damage follows.

So no, I am not arguing for a free-for-all where classified files become open reading material. I am arguing that firing a general without fixing the system is a distraction disguised as action.

How Serious Leaders Actually Fix the Problem

If you run a high-stakes organization—whether a defense command, a corporate security team, or a regulated enterprise—waiting for a scandal to enforce discipline is a losing strategy. Real reform takes unglamorous work.

  1. Audit access before adding security theater. Strip default permissions. Review who actually needs sensitive material today, not who held a title three years ago. Fewer eyes on sensitive data means fewer leak vectors and cleaner audit trails.
  2. Create real internal pressure valves. If people have no credible, safe way to challenge bad assumptions or surface misconduct internally, they look for outside megaphones. Protect candid debate inside the room so nobody feels forced to take it to the press.
  3. Cut classification bloat ruthlessly. Stop hiding routine coordination, awkward memos, and political spin behind high-level secrecy labels. When secrecy is reserved for genuine operational and source protection, compliance goes up because the rationale is obvious.
  4. Separate personal misconduct from systemic failure. Hold individuals accountable when they break rules knowingly or recklessly. At the exact same time, examine what workflow, culture, or incentive made the breach possible. Fix both tracks or watch the same movie repeat next year.

A firing makes a clean headline. Fixing how secrets are generated, shared, and contested takes years of grit nobody wants to applaud.

The general is gone, the outrage will fade, and the same secret-stuffed machine will keep humming until someone finally has the nerve to fix the pipes.

MJ

Miguel Johnson

Drawing on years of industry experience, Miguel Johnson provides thoughtful commentary and well-sourced reporting on the issues that shape our world.