The Washington Post Internal Security reporters operate at the intersection of federal law enforcement, surveillance, and domestic threat policy — a beat where documents beat adjectives.

This guide distills how to earn a response, what to lead with, and where most pitches die on arrival.

Internal security at The Post spans domestic extremism, FBI and DHS operations, counterintelligence, border and immigration enforcement, and civil-liberties friction around surveillance.

Expect scrutiny framing: oversight failures, institutional accountability, and the gap between official statements and internal records.

• Core territory: FBI, DHS, CISA, Secret Service, state fusion centers, extremist movements, election security.
• Adjacent territory: Justice Department prosecutions, congressional oversight hearings, FOIA litigation outcomes.
• Off-territory: Pure foreign policy, general crime blotter, corporate cybersecurity product news.

The beat is staffed thinly — our directory lists 1+ active journalists, so precision matters far more than volume.

Amy Argetsinger appears as a representative name in our directory; verify current assignment before sending, since Post beat lines shift with newsroom restructuring.

Build your own working The Washington Post Internal Security reporters list by cross-referencing bylines across National, National Security, and Justice desks over a rolling 90 days.

• Track bylines, not job titles — the byline is the beat.
• Note who co-bylines on breaking threat stories; those pairings reveal the real desk map.
• Flag reporters who publish FOIA-driven accountability pieces — they're your highest-yield targets.

Matching Your Pitch to The Washington Post Internal Security Journalists

Different reporters on this beat want different things. Misalignment is the most common reason a good story gets silence.

The Post rewards pitches that expose a gap between what an agency says and what it does. Build your angle around that delta.

Strongest recurring angles:

• Oversight gaps: missing audits, expired authorizations, unreported use of surveillance tools.
• Scale and cost: how many people, how much money, how long — quantified.
• Civil-liberties friction: who is affected, with a concrete case, not a hypothetical.
• Local proof of a national pattern: a single jurisdiction's records that reveal systemic practice.

Weakest angles: broad "the threat is growing" framing, unsourced forecasts, and anything that reads like marketing for a security vendor.

Treat The Washington Post Internal Security journalists contacts as privileged infrastructure: verified, current, and used sparingly.

• Email first; use official Post addresses or the newsroom tip line rather than social DMs.
• Offer secure transfer (Signal, SecureDrop) for sensitive documents — say so in one line.
• Never blast a press release; send one tailored pitch per reporter, one follow-up after 72 hours.
• State embargo terms plainly and honor them without renegotiation.
• Assume everything you send may be published; never send material you can't defend.

For anything sensitive, ask before sending: "Can I share documents via your preferred secure channel?" Reporters on this beat respect the question.

Run this before hitting send.

• Is there a document, filing, or dataset attached or offered?
• Does the first sentence name the agency and the consequence?
• Is the news peg within 72 hours of a hearing, report, or filing?
• Have you confirmed the reporter actually covers this beat right now?
• Is the pitch under 200 words and free of jargon?
• Have you stated exclusivity or embargo explicitly?
• Can every factual claim survive a hostile read?

Nail those seven and you are pitching at the standard The Washington Post Internal Security reporters expect. Miss two, and you are background noise.