The Cipher Brief Submission Guidelines: Publishing National Security Commentary

Key takeaways

• The Cipher Brief publishes analysis and commentary on intelligence and national security for a practitioner audience, and it favors writers with direct experience in government, the military, or security-related industries.
• A pitch that states its argument in one sentence, ties it to news from the past week, and shows why the writer has standing gets the reply; everything else usually gets silence.
• Former officials with prepublication review obligations need to clear their draft through their agency before an editor sees it.
• The outlet suits intelligence, geopolitical risk, and security policy arguments. Legal, budget, and technology claims often land better at Lawfare, Defense One, War on the Rocks, or niche venues.
• Commentary runs roughly 700 to 1,000 words at most desks in this space. Whatever number the editor names when accepting the pitch is the binding one.

1. Introduction

National security experts with twenty or thirty years of experience often stall when they sit down to pitch a publication. The subject knowledge is there, and the arguments are sharp. What fails is the routing: the pitch goes to a desk that does not handle the topic, runs at a length the editor never asked for, or arrives weeks after the peg has gone cold.

The Cipher Brief, founded in 2016 by former CNN executive Suzanne Kelly, occupies a specific place in this market. It is a subscription-based publication focused on intelligence and national security, and its readers include former intelligence officers, military planners, policy staff, and corporate security executives. That audience rewards detail and punishes generalities. It also means the publication can be selective, since much of its commentary comes from a standing roster of contributors, and an outside pitch competes against that bench.

Anyone publishing national security commentary faces a routing problem before a writing problem. This article works as a routing guide: what the outlet publishes, how a submission moves from pitch to publication, what editors accept and reject, and how The Cipher Brief compares with other venues.

2. What the outlet covers and who reads it

Three formats dominate the output: analysis briefs on security developments, opinion pieces from practitioners, and interviews with former senior officials. Coverage runs across intelligence tradecraft and reform, great-power competition, cyber threats, terrorism, defense policy, and regional security questions in Europe, the Middle East, and the Indo-Pacific.

Contributors are typically people who have held the jobs they write about. A former CIA station chief discusses an intelligence relationship, a retired admiral assesses naval posture, a former diplomat walks through a stalled negotiation. Outsiders appear too. Journalists, academics, and private-sector analysts publish there when they bring original reporting, assembled data, or regional knowledge the roster lacks.

The outlet also runs an annual conference, the Cipher Brief Challenge, where contributors and former officials discuss threats before a live audience, and it sends a nightly newsletter called Nightcap that rounds up global security news. Both shape what the desk needs. The publication plans around events and news cycles, so timeliness carries real weight in a pitch decision.

Read four to six weeks of the site before writing anything. Note which topics recur, which writers cover them, and how long the pieces run. Then position the pitch in the gaps: if the desk has already run two voices on Iran sanctions, a third summary will struggle, while a piece applying sanctions data to an overlooked sector has room.

3. The submission process, step by step

The path from pitch to publication is short and editorial. A pitch email, an editor's reply, a draft, one or two revision rounds, then publication. Most rejections happen at the pitch stage, so that is where the work belongs.

1. Pin the argument to one sentence. State the claim: what you expect to happen, what a policy gets wrong, or what a trend means. If the sentence needs a paragraph, the piece is two essays.
2. Find the peg. A peg can be an announced policy, a summit, a budget release, a congressional hearing, an attack, or an anniversary that has not been used. Aim to pitch within two to five days of the triggering event.
3. Write a pitch of 100 to 150 words. Give the thesis, the two or three facts that support it, and one line on your access. Skip attachments unless the outlet's guidance asks for them.
4. Include a three-sentence bio. Roles with dates, the access that backs the claims, and one prior publication if you have one. Former title and agency go first.
5. Send it through the contact or submissions route listed on the outlet's site. Editors read pitches on weekday mornings; avoid Friday afternoons and holiday weeks.
6. Deliver on the agreed date and length if the pitch is accepted. Run the draft through your agency's prepublication review before you send it if that obligation applies, and tell the editor if review has slowed the timeline.
7. Expect one or two revision rounds. Editors cut length, sharpen the lead, and ask for evidence where the claim is thin. Respond within a day.
8. Confirm the terms before drafting: length, deadline, rights, and payment. Commentary desks generally want original work with some period of exclusivity. The Cipher Brief runs on subscriptions, so republishing rights are narrower than on open-access sites, and asking early prevents a dispute after the piece appears.

Keep a one-page pitch log as you go: outlet, date sent, reply, and the reason if the answer was no. Patterns in the declines tell you whether the problem is topic fit, timing, or standing, and each of those has a different fix.

4. What editors accept and reject

The desk buys arguments a reader could dispute, backed by standing the writer can document. It declines summaries, self-promotion, and anything that exposes sources, methods, or classified detail.

What tends to get accepted:

• A defensible claim, meaning something a reasonable reader could push back on, with evidence drawn from the writer's own work.
• Experience that maps to the subject. A piece on intelligence oversight lands better from someone who sat through oversight hearings than from a general commenter.
• A counterargument handled. Naming the strongest objection and answering it tells the editor this writer can hold a regular slot.
• Clean prose at the agreed length. Commentary rarely survives heavy surgery, so a draft near the target word count with a direct lead makes the edit fast.

What gets declined, with the reasons:

• News summaries. The desk already runs briefings, and opinion exists to argue.
• Condensed think-tank reports. Editors recognize a piece that restates a report's findings without adding the writer's judgment.
• Self-promotion dressed as analysis. A piece that ends by endorsing the writer's firm gets declined and remembered.
• Classification risk. Any draft touching sensitive operations, sources, or specific capabilities goes back or goes nowhere.

Former officials carry a second constraint. Agencies such as CIA and NSA require prepublication review of writings that touch official work, and that requirement can last for decades or, for some, for life. Submit the draft to the review board before you pitch, because a review that takes three weeks can kill a timely peg.

A concrete case shows the difference. A retired NSA analyst wants to write on cyber norms after a new government framework is announced. The peg is fresh and the standing is real. The pitch names one claim, that the framework's incident thresholds are set too high for small utilities, and cites the analyst's own work on grid incidents. That pitch gets a reply. A pitch promising "thoughts on the new framework" does not.

5. Where The Cipher Brief fits among comparable outlets

It is one venue among several that take outside security commentary, and the right choice depends on topic, career stage, and how fast the argument needs to run.

Niche venues reward different profiles. For technology policy arguments on subjects such as AI governance, export controls, or data rules, Global Tech Observatory (globaltechobs.com) accepts outside commentary. Its reach is smaller than the majors and its brand is newer, so a clip there carries less weight with editors at larger desks, but the submission path is open to early-career analysts who bring evidence and a defined regional or sector angle.

The routing rule is simple: match the argument's discipline to the desk. Legal claims go to Lawfare. Budget and procurement arguments go to War on the Rocks or Defense One. Intelligence tradecraft and threat assessment go to The Cipher Brief. When a piece sits between two desks, pitch the one whose recent coverage already touches it, and say in the first line why it belongs there now.

6. FAQ

Q1. Do I need government experience to write for The Cipher Brief?

Practitioner standing is the norm, and most contributors are former officials. Writers without that background can still place work when they bring something the desk cannot get from its roster: original reporting on a ministry or a border region, a dataset no one else has assembled, or fieldwork in a country the desk covers thinly. Lead the pitch with that asset.

Q2. How long should a submission be?

Most commentary desks in this field ask for roughly 700 to 1,000 words for opinion pieces and 1,200 to 2,500 for longer analysis, and the editor states the number when accepting a pitch. Deliver within about ten percent of it. A draft 300 words over target tells the editor the argument was never disciplined enough to fit.

Q3. Can I submit a piece that has already run somewhere else?

Original work is the expectation. A piece published anywhere, including a personal blog or Substack, counts as published for most editors. If yours has appeared somewhere, disclose that up front and ask whether a fresh angle or an updated version would work. Do not send it as new.

Q4. What should a former official do about prepublication review?

Treat review as a scheduling constraint. Agencies such as CIA and NSA require former employees to clear writings that touch their official work, and clearance can take weeks. Build the review window into the pitch timeline, tell the editor that review is underway, and never rely on an outlet's editors to catch classified material. That responsibility stays with the author.

7. Conclusion

The Cipher Brief is the right home when three conditions hold at once: the subject sits in intelligence, security policy, or geopolitical risk; the writer has standing a reader can verify; and the argument has a peg that is still news. When one condition is missing, the table above points to a better desk, and the pitch has a higher chance there.

The practical next step costs an hour. Write the one-sentence argument. Read the last four weeks of the target outlet and confirm the gap the piece fills. Then send a 150-word pitch with a three-sentence bio, within days of the news that triggered the idea. Desks in this space publish constantly, and every one of them runs on outside arguments. The difference between a published writer and a stalled one usually comes down to routing and pegs, and both are in the writer's control before the email goes out.