Editorial policy
How we research and publish cybersecurity content.
This policy explains the standards behind the articles, guides, and glossary entries on this site. It also explains why work is published under a studio byline instead of an individual name.
Authorship
Why articles use the Infosec Writing Studio editorial team byline
The studio currently publishes under a role based byline. This protects contributor privacy while giving readers one consistent place to inspect the standards applied to the work.
The byline does not represent a fictional person. We do not attach invented credentials, employment history, client work, or personal profiles to it. Individual contributors and reviewers will be named only with their consent.
Evidence
Research starts with primary and authoritative sources
Articles should cite the source beside the claim it supports. Preferred sources include standards bodies, government agencies, research papers, official technical documentation, public datasets, and direct product documentation.
Vendor material can explain a product's own features or stated position. It should not be used as independent proof of broad market claims. If evidence is limited, the wording should state that limit or the claim should be removed.
Review
Published work passes a defined editorial review
Review checks the direct answer, terminology, factual support, links, headings, metadata, internal links, and readability. Technical claims are compared with their cited source before publication.
A page should answer its stated search question without relying on a service pitch. Glossary entries receive a separate reference-first review so definitions stay neutral and useful.
AI tools
AI output is not treated as a factual source
Research, drafting, source selection, and final editorial judgment remain human-led. AI tools may assist with mechanical checks, such as finding repeated words or broken formatting, but their output is not accepted as evidence.
A human editor remains responsible for every claim, citation, and correction that appears on this site.
Maintenance
Corrections and substantive updates change the page record
A publication date records the first public release. The updated date changes after a factual correction, source refresh, or substantive revision. Cosmetic edits do not receive a new update date.
Readers can report an error by emailing contact@infosec-content.online. The report should include the page URL, the disputed text, and a supporting source where possible.
Independence
Reference content stays separate from commercial pages
The site contains both commercial service pages and reference material. Glossary definitions are written to explain the term, not to sell a service or favor a vendor.
If sponsorship, payment, or another material relationship affects an editorial page, that
relationship is disclosed clearly on the page. Paid links use rel="sponsored" or
rel="nofollow", and payment does not determine definitions, evidence, source
selection, or editorial conclusions. No sponsored editorial content is currently published
on this site.