Washington DC: Where Encryption Meets Federal Complexity

The DC environment

Unlike a typical city with one municipal police force, DC operates with a dense stack of overlapping agencies:

• Metropolitan Police Department (MPD): The District's primary law enforcement agency
• US Capitol Police: Protecting the Capitol complex and members of Congress
• US Secret Service: White House and presidential protection
• US Park Police: Federal parks and monuments
• FBI: Federal investigations and national security
• Multiple federal protective services: Each with their own security details and radio infrastructure

Every agency operates on separate radio systems with different encryption policies. The result is a patchwork that complicates both inter-agency coordination and any form of public oversight.

January 6, 2021: communication failures

The Capitol attack surfaced the consequences of DC's fragmented, encrypted radio environment. Radio communication breakdowns were a documented factor in the delayed response.

Congressional investigators identified these failures as a contributing factor in the delayed response. The combination of agencies unable to talk to each other, and a public unable to monitor any of it, prolonged the crisis.

The information gap

During major DC events—inaugurations, protests, security incidents—encrypted radio creates a one-sided information environment:

Protest coverage

DC draws more protests than any other American city. Before 2011, scanner access served concrete functions during demonstrations:

• Journalist safety — knowing where police lines are forming and where arrests are happening
• Protester safety — understanding police movements before confrontations occur
• Legal observers documenting police actions for civil rights cases
• Independent verification of what officials claim happened

Encrypted radio eliminates all of it. Reporters, legal observers, and the public now depend entirely on statements from the departments they are trying to hold accountable.

The interoperability problem

DC's multi-agency environment creates real technical problems that encryption makes worse:

These problems appeared on January 6 and have been documented in after-action reports from other DC events. Encryption adds to the complexity without providing measurable safety benefits.

How DC compares

DC's approach is not the only option among government capitals:

• London's Metropolitan Police operates with more transparency; scanner access is more available than in DC.
• Many US state capitals maintain open access to routine police communications.
• Other federal districts vary by jurisdiction and agency.

DC's near-total encryption across all major agencies makes it one of the most closed police communications environments among democracies.

A path forward

Security concerns are real; full blackout is not the only answer

DC's role as the seat of federal government creates security considerations that most cities don't face. But the current approach—full encryption with no public access alternative—removes accountability precisely when it matters most:

• When police respond to political protests
• When federal agencies deploy force
• When national events unfold that affect the whole country
• When Congress needs information about security operations affecting its own members

What DC could do

• Establish a journalist access program along the lines of San Francisco's media credentialing model—a workable minimum step.
• Invest in interoperability so agencies can communicate during emergencies without the failures January 6 exposed.
• Create open or media-accessible channels for major public events.
• Give congressional oversight bodies real-time communications access during security incidents affecting Congress.
• Release communications records from significant events after a defined delay.
• Establish a civilian oversight body with access to communications records.