Editorial Policy

1. Mission & Editorial Independence

Our mission is to provide security professionals with high-quality, actionable threat intelligence. Our editorial decisions are made independently of commercial considerations. Advertisers have no influence over the content we publish, the stories we choose to cover, or our analytical conclusions.

We do not accept payment for positive coverage of any product, vendor, or service. Sponsored content, when published, is always clearly labelled as such and separated from our editorial content.

2. Source Standards & Verification

We rely on multiple, independent primary sources before publishing claims about specific incidents, attributions, or technical details. Our sources include:

• Official vendor security advisories and CVE disclosures
• Government CERT and CISA advisories
• Published security research from peer-reviewed and reputable sources
• Dark web and threat actor monitoring (publicly accessible forums and channels)
• Independent security researchers and practitioners
• Court documents, legal filings, and regulatory disclosures
• First-party disclosures from affected organisations

We do not publish claims from a single unverified anonymous source as established fact. Unverified claims are clearly labelled as unverified or “claimed.”

3. AI-Assisted Research — Transparency Disclosure

We are transparent about this practice because we believe readers deserve to know how content is produced. Our use of AI tools does not replace editorial judgement — it augments our ability to cover more incidents faster while maintaining analytical depth.

What AI tools do NOT do in our process:

• Make editorial decisions about what to publish or not publish
• Fabricate sources, quotes, or statistics
• Publish content without human review and editorial oversight
• Attribute events to threat actors without supporting evidence

4. Accuracy & Corrections Policy

We strive for accuracy in all reporting. Despite our verification processes, errors can occur. When we identify or are informed of a factual error:

• We correct the error promptly, typically within 24 hours of confirmation
• Significant corrections are noted at the top or bottom of the article with an “Editor’s Note” explaining what was changed and why
• We do not silently alter published articles without notation
• For minor typos or grammatical corrections, a notation is not required

To submit a correction request, email us at contact@quantnest.in with “Correction Request” in the subject line. Include the article URL, the specific claim in question, and the correct information with supporting evidence.

5. Responsible Disclosure

We follow industry responsible disclosure norms when reporting on vulnerabilities and security research:

• We do not publish fully functional proof-of-concept exploits for unpatched vulnerabilities
• We may withhold specific technical details at the request of researchers or vendors during an active disclosure period
• When a patch or mitigation is available, we prioritise publishing that information prominently
• We may report on the existence of vulnerabilities before patches are available when public awareness is in the interest of defenders

If you are a security researcher who wants to work with us on responsible disclosure, please contact contact@quantnest.in.

6. Attribution & Threat Actor Claims

We apply conservative standards to threat actor attribution claims. Attributing a cyberattack to a specific nation-state, group, or individual has significant real-world consequences. Our approach:

• We clearly distinguish between confirmed attribution (from official government bodies or the victim organisation) and assessed attribution (from security researchers)
• We use hedging language (“assessed to be,” “attributed to by researchers”) when attribution is analytical rather than confirmed
• We note when multiple attributions exist or when attribution is contested
• We do not name private individuals alleged to be threat actors without substantial, publicly available evidence

7. Reader Tips & Community Submissions

We welcome tips, leads, and submissions from the security community. Our handling of tips:

• Tipsters may request to remain anonymous; we will not reveal sources who request confidentiality
• We independently verify tip-based claims before publishing
• Submission of a tip does not guarantee publication
• We will not use information shared “off the record” without explicit consent

Send tips to: contact@quantnest.in