Guest posts

Who can contribute

People with first-hand experience of the subject: IT administrators, security engineers, auditors, incident responders and those who run managed services. A guest article carries the contributor's real name, role and employer, and a short biography with a link to their own public profile.

What we publish

• Original articles that have not appeared elsewhere.
• Practical accounts: how something was set up, what went wrong, what the logs showed.
• Explanations of a rule or standard, with the clause cited.

What we do not publish

• Product promotion, or an article whose point is a link.
• Lists that rank the contributor's own product or employer.
• Text produced by an AI tool and not checked by the named author.
• Articles on topics outside security for small and mid-size organisations.

Editing

Every submission is edited by us and held to the same standards as our own articles: a direct answer at the top, sources linked and dated, no claims of testing without published evidence. We may decline a submission or ask for changes, and the final text is ours to approve.

Links, payment and disclosure

• Links to other sites are marked nofollow. We do not sell links that pass ranking credit.
• If a fee is paid for publication, the article is labelled as a paid post and its links are marked sponsored.
• A contributor writing about their employer's field must say so. The article states the connection near the top.

How to pitch

Email [email protected] with a two-line summary, the sources or evidence you would draw on, and your public profile. Send the idea before the article. We reply to pitches we can use.