InfoSec Relations publishes analytical work that most security and geopolitics publications cannot accommodate because they sit on one side of the technical-policy divide and rarely cross it. Our readership spans CISOs and threat intelligence analysts on one side, and defense analysts, government officials, and policy researchers on the other. The people whose insight we need most are the ones who have spent careers moving between those two worlds, and this page is addressed to them.
We operate two distinct editorial tracks. The InfoSec Relations track covers the geopolitical, policy, and strategic dimensions of cybersecurity. The Offensive Engineering track covers the technical mechanics of offensive and defensive security as experienced by practitioners. Contributions, interviews, and hosted conversations are commissioned and published separately under each track to serve their respective audiences with the depth each deserves.
What We Cover
The topics below define the scope of both tracks. We do not cover basic security hygiene, vendor product comparisons, or content that serves a marketing objective. Every piece we publish must be analytically grounded, sourced from direct expertise, and useful to a senior professional audience that already possesses significant domain knowledge.
InfoSec Relations Track
State-sponsored cyber operations and attribution, including the technical evidence base and geopolitical context behind major campaigns. Nation-state strategy and the use of digital operations as instruments of foreign policy, coercion, and signalling. Offensive cyber doctrine and how governments develop, deploy, and constrain their digital capabilities. Critical infrastructure as a strategic target, including energy, financial, and telecommunications systems operating under active threat. International law and norms governing cyber conflict, including the evolving application of international humanitarian law to digital operations. Intelligence community operations and how signals intelligence, cyber, and human intelligence functions intersect in practice. Historical cyber conflict case studies including Stuxnet, SolarWinds, NotPetya, and the APT campaign ecosystem, treated as empirical foundations for current strategic analysis. Regulatory and legal frameworks with direct national security implications, including NIS2, the EU AI Act, CHIPS Act export controls, and data sovereignty regimes. Technical explainers written for policymakers who need operational grounding to draft legislation, negotiate agreements, or make resource allocation decisions. Policy analysis written for engineering teams who must translate regulatory requirements into architectural decisions.
Offensive Engineering Track
Adversary simulation and red team tradecraft, including how enterprise environments are mapped, traversed, and compromised in practice. Identity attack paths and the abuse of authentication infrastructure, including Active Directory, Entra ID, and federated identity systems. Offensive tooling development, evasion techniques, and the engineering of post-exploitation capabilities. Cloud and infrastructure security from an attacker's perspective, including misconfiguration exploitation and lateral movement across distributed environments. Threat intelligence tradecraft, including how analysts attribute campaigns, track infrastructure, and connect technical indicators to operational intent. Incident response from the perspective of teams who have worked live intrusions against sophisticated threat actors. AI and autonomous systems as both attack surface and offensive capability, including agentic threat models and adversarial machine learning. Hardware and firmware security, supply chain integrity, and the exploitation of embedded systems in critical environments.
Ways to Contribute
Contributed Analysis
A developed analytical piece of 800 to 2,500 words anchored in your direct professional experience or primary research. This is not a blog post or an opinion column. A successful contribution presents a specific argument, supports it with named primary sources, and delivers insight that a senior practitioner or policy professional cannot find elsewhere. We work closely with contributors through editing and review, and we preserve your voice and your language throughout. Contributed pieces carry your full byline, title, employer, and a short author profile that links back to your professional presence.
Interview Guest
A conducted conversation of 45 to 60 minutes with one of our editorial team members or volunteer hosts, exploring a topic where your direct experience produces insight that cannot be generated any other way. Interviews are recorded, transcribed, edited carefully, and reviewed with you before publication to ensure factual accuracy and faithful representation of your analysis. You retain the right to request corrections to any factual claim prior to publication. Interviews are published as standalone features or integrated into longer analytical pieces, depending on the editorial context.
Volunteer Interview Host
We maintain a team of volunteer hosts who conduct interviews on behalf of InfoSec Relations across both editorial tracks. Hosts are practitioners with genuine domain knowledge in the subject area they are covering. You do not need a journalism background or on-camera experience to host for us. What you need is the professional depth to ask the questions that actually matter to practitioners and policy professionals in your field, and the credibility to draw substantive answers from senior guests.
We provide every volunteer host with the full editorial and production infrastructure they need to get started. This includes a detailed run-of-show document prepared specifically for each recording, background research on the guest and their work, a structured question framework developed collaboratively with you before the session, StreamYard access and technical setup, production support throughout the recording, and post-production editing handled by our team. Your role is to show up with domain knowledge and intellectual curiosity. We handle everything else.
Hosts are credited on every episode and piece they produce for the publication, with their title, affiliation, and author profile. Contributing hosts who develop a consistent body of work become part of the publication's editorial identity in a visible way.
Editorial Standards That Apply to All Contributions
Every piece published under the InfoSec Relations name must meet the same editorial standard regardless of format or track. Factual claims must be traceable to a named primary source. Vendor marketing, product promotion, and commercially motivated framing are not acceptable in any form. Analysis must serve both the technical and the policy reader where the topic permits, or serve one audience with genuine depth where a dual framing would dilute the argument. AI tools may assist your research and drafting process, but every claim must be manually verified by a human author before submission. We reserve the right to decline or substantially revise contributions that do not meet these standards after editorial review.
For a full statement of our sourcing requirements, corrections process, and editorial independence policy, see our Editorial Policy at infosecrelations.com/editorial-policy.
A Note on Compensation
Contributions to InfoSec Relations, including writing, interview hosting, and expert participation, are unpaid volunteer roles. We are an independent publication committed to editorial integrity, and our model depends on practitioners and experts who contribute because they believe the work matters, not because of financial incentive.
On rare occasions, we may offer an honorarium to hosts or guests for interviews that we specifically commissioned and that demonstrate exceptional performance by our readership metrics. These decisions are made at our editorial discretion and are not guaranteed under any standard contribution arrangement. We will communicate this clearly at the point of commissioning when it applies.
How to Get in Touch
Send us a brief note with your current or most recent professional role, the editorial track you are interested in contributing to, whether you are proposing a written piece, offering to participate as a guest, or interested in joining our volunteer host team, and a short description of the specific angle, argument, or expertise you want to develop. We respond to all contribution inquiries within five business days.
For written and guest contributions, write to editor @ infosecrelations.com. For volunteer host inquiries, write to editor @ infosecrelations.com with the subject line "Volunteer Host."