Contributor guidelines
We publish practitioners who can defend their claims. Neither title runs contributed work that reads like marketing, and nothing publishes without an editing pass. Pick the title your experience fits, then send one paragraph.
Launching January 2027 — pitches open now
Write for The Agent Perimeter
The control plane for autonomous action
Who we want to hear from
Security practitioners, researchers, and technical leaders with real experience in agent identity, tool and data access, runtime behavior, or AI governance. Analysts and others who track how these projects actually play out, or who understand standards impact, are welcome too. If you've done the work or watched it closely enough to have real insight, not just surface-level takes, we want to hear from you.
What we publish
Perspective pieces (800–1,000 words)
A clear point of view on a trend, framework, or debate. Not a product pitch.
Technical explainers (1,000–1,200 words)
Break down a standard, framework, or technical concept for a security leadership audience.
Permission Slip (600–800 words)
A teardown of one real agent permission or tool-access failure mode.
Standards Watch (600–800 words)
A plain-English read on a relevant standards effort.
What we don't publish
- Anything that reads like a press release. Send vendor news to our news desk instead.
- AI-generated drafts with no real editing pass. We can tell, and it costs us trust with readers.
- Anything under NDA without written permission to publish.
If you work for a vendor
Fine, some of the best technical writing comes from practitioners. Just disclose your employer and role in your byline, and make sure the piece stands on its own without being built around your product. We'll tell you if something's crossed into advertising territory, that's a sponsored-content conversation, not a contributed piece.
How to pitch
One paragraph: which column you're pitching (Perspective, Technical Explainer, Permission Slip, or Standards Watch), the angle, why it matters now, and why you're the right person to write it. Send it to carm@signalandnoisemedia.com. Expect a response within two weeks. If it's a fit, we'll send back format, length, and a deadline.
What happens after
We edit for clarity and length, and you see the edit before it runs. This is unpaid, byline and platform, so we're upfront about that from the pitch stage on. Original work only; if it's been published elsewhere, tell us upfront.
In development — pitches collected ahead of launch, no launch date yet
Write for The Quantum Line
The operational transition to post-quantum cryptography
Who we want to hear from
Cryptography and PKI leaders, security architects, and technical leaders with real experience in PQC migration, crypto inventory, or compliance implementation. Analysts and others who track how these migrations actually play out, or who understand standards impact, are welcome too. If you've done the work or watched it closely enough to have real insight, not just surface-level takes, we want to hear from you.
What we publish
Perspective pieces (800–1,000 words)
A clear point of view on a trend, framework, or debate. Not a product pitch.
Technical explainers (1,000–1,200 words)
Break down a standard, framework, or technical concept for a security leadership audience.
Migration Ledger (600–800 words)
A real implementation milestone, vendor capability, or procurement signal worth tracking.
Crypto Inventory Clinic (600–800 words)
A practical read on discovery, prioritization, certificate issues, key management, or hybrid deployment.
What we don't publish
- Anything that reads like a press release. Send vendor news to our news desk instead.
- AI-generated drafts with no real editing pass. We can tell, and it costs us trust with readers.
- Anything under NDA without written permission to publish.
If you work for a vendor
Fine, some of the best technical writing comes from practitioners. Just disclose your employer and role in your byline, and make sure the piece stands on its own without being built around your product. We'll tell you if something's crossed into advertising territory, that's a sponsored-content conversation, not a contributed piece.
How to pitch
One paragraph: which column you're pitching (Perspective, Technical Explainer, Migration Ledger, or Crypto Inventory Clinic), the angle, why it matters now, and why you're the right person to write it. Send it to carm@signalandnoisemedia.com. Expect a response within two weeks. If it's a fit, we'll send back format, length, and a deadline.
What happens after
We edit for clarity and length, and you see the edit before it runs. This is unpaid, byline and platform, so we're upfront about that from the pitch stage on. Original work only; if it's been published elsewhere, tell us upfront.
Contributed work is held to the same editorial standard as staff work. Read The Standard.