InfoSec Relations is an analytical publication operated by Ebenworks Private Limited (CIN: U62099DL2026PTC461045), New Delhi, India. This Editorial Policy governs every piece of content published on infosecrelations.com, in the Offensive Engineering newsletter at offensive.infosecrelations.com, and across all associated distribution channels including LinkedIn and YouTube.
This policy exists to make our editorial standards transparent to readers, contributors, sources, and the platforms that index our work. It is not aspirational. Every standard described here is actively enforced across our content operation.
Editorial Independence
InfoSec Relations maintains strict editorial independence from all commercial, governmental, and institutional interests. Editorial decisions, including what topics we cover, which experts we feature, which conclusions we draw, and which stories we decline to publish, are made exclusively by our editorial team on the basis of analytical merit and reader value.
No advertiser, sponsor, investor, or external organisation has any influence over our editorial agenda, our coverage decisions, or the conclusions reached in our published analysis. Sponsored or partner content, if introduced in the future, will be clearly and prominently labelled as such and will be produced and reviewed separately from our editorial content pipeline. It will never appear under an author byline that implies it is independent editorial work.
Our editorial team does not accept gifts, paid travel, complimentary access to products or services, or any other form of compensation from organisations that are or may become subjects of our coverage.
What We Cover and Why
InfoSec Relations covers the intersection of cybersecurity and geopolitics. Our core editorial premise is that cyber operations are instruments of statecraft and must be analysed within that frame. We cover state-sponsored threat activity, the policy and legal dimensions of offensive cyber operations, critical infrastructure security, AI and emerging technology as strategic tools, and the decisions made by security leaders operating inside these dynamics.
We do not cover product launches, vendor marketing narratives, or technical content that serves commercial interests rather than analytical ones. We do not publish content designed to drive traffic through sensationalism, fear, or manufactured urgency. A piece that will not hold analytical value two years from the date of publication does not meet our editorial standard.
Source Standards
Every factual claim, every statistic, and every assertion about the behaviour of specific threat actors or the provisions of specific policies must be traceable to a primary source. Our source hierarchy is as follows.
First-party sources take precedence above all others. These are original interviews and commissioned analysis from identifiable expert practitioners, conducted and published by InfoSec Relations directly.
Primary external sources are the only acceptable second tier. These include government reports and official statements, academic research published in peer-reviewed journals or by established research institutions, official threat intelligence reports with named authorship, congressional testimony and legislative records, and first-party documentation from the organisations being reported on.
Secondary or aggregated sources are not acceptable as the basis for factual claims. This includes blog aggregators, unattributed summaries, and content that cannot be traced to an identifiable primary author and institutional affiliation.
All citations include the author name, source name, publication date, and a working URL where one exists. Citations are formatted as inline anchor text within the body of the article, not appended as footnotes.
Authorship and Contributor Transparency
Every article published on InfoSec Relations carries a named author or, in the case of editorial staff pieces, a clear publication byline. Anonymous sourcing is not used for factual claims. Where a source requests anonymity for safety or professional reasons in an interview context, we will describe the nature of their expertise and institutional affiliation at the level of detail consistent with protecting their identity, and we will note explicitly in the piece that the source requested anonymity and why.
Guest contributors and interview subjects are identified by their current professional title, employer or affiliation, and the date their contribution was recorded or submitted. We do not retroactively alter author attribution after publication except to correct a factual error in the attribution itself.
Use of AI Tools
InfoSec Relations uses AI tools to assist with research, synthesis, structural outlining, and copyediting. AI tools do not replace human editorial judgment on any factual claim, analytical conclusion, or sourcing decision. No content is published solely on the basis of AI-generated output. Every fact, every claim, and every conclusion in a published piece has been manually verified by a human editor against a primary source before publication.
We do not use AI tools to generate quotations, fabricate expert perspectives, or produce analysis that is attributed to a named human contributor who did not produce it. All quoted material from interview subjects is drawn from recorded and transcribed conversations and is not edited beyond minor grammatical correction with the contributor's approval.
Corrections Policy
We take factual accuracy seriously and we correct errors promptly and transparently.
When we identify or are notified of a factual error in a published piece, we investigate the claim against our primary source documentation. If the error is confirmed, we correct the article and add a correction notice at the top of the piece that states the original claim, the corrected information, and the date the correction was made. We do not silently edit errors without disclosure.
Corrections are distinguished from updates. Where new developments in a story warrant adding context to an existing piece without changing a prior claim, we add an editor's note at the top or bottom of the article noting the date and nature of the update.
To submit a correction, write to editor @ infosecrelations.com with the subject line "Correction Request," the URL of the article in question, the specific claim you believe to be inaccurate, and the primary source you believe contradicts it. We aim to acknowledge correction requests within 48 hours and resolve them within seven days.
Conflicts of Interest
Members of our editorial team and contributors are required to disclose any financial relationship, professional affiliation, or personal connection to any organisation or individual they are writing about. Undisclosed conflicts of interest are grounds for removal of a contributor from the publication.
Where a disclosed conflict exists, the relevant contributor will not be assigned to cover the organisation or individual to which the conflict applies. If a conflict emerges during the reporting or production of a piece already in progress, that contributor will be recused from the piece and it will be reassigned or reviewed by an independent editor.
InfoSec Relations does not accept payment from any organisation in exchange for editorial coverage, positive or otherwise.
Expert Contributors and Interview Subjects
Expert contributors and interview subjects featured in InfoSec Relations are selected on the basis of professional expertise, institutional credibility, and the analytical value they bring to our readership. We do not charge contributors or interview subjects for coverage, and we do not offer payment to contributors in exchange for positive or favourable treatment of their employers or affiliated organisations.
When we feature a contributor who works for a vendor, government agency, think tank, or other institution, that institutional affiliation is disclosed in the piece. Readers should be aware that expert contributors speak from within their professional context, and that institutional affiliation is a relevant factor in evaluating any expert perspective.
Editorial Complaints
Readers who have concerns about the accuracy, fairness, or editorial standards of a published piece that go beyond a factual correction request are invited to write to editor @ infosecrelations.com with the subject line "Editorial Complaint." We review all complaints seriously and will respond within 14 days with our assessment of the concern raised.
Governing Standards
InfoSec Relations models its editorial standards on those of established analytical journalism, with particular reference to practices common to serious policy and security publications. We are committed to the principles of factual accuracy, transparency of sourcing, editorial independence, named authorship, and prompt and disclosed correction of errors.
Contact
For editorial queries, correction requests, contribution proposals, or complaints, contact us at:
Editorial Team, InfoSec Relations Ebenworks Private Limited with registered office in New Delhi, India CIN: U62099DL2026PTC461045 Email: editor @ infosecrelations.com Website: infosecrelations.com