Contribute
Become a Founding Contributor
The Cyber Standard is an independent Australian cybersecurity masthead. We publish practitioner writing in plain English for the people who answer for cyber risk — boards, CISOs, CTOs, assessors and operators.
These standards apply to every piece we publish: staff writing, guest contributions, sourced commentary we turn into features, and republished contributor drafts. If a piece cannot meet this bar, we do not run it.
01AI-generated content is not accepted
The Cyber Standard does not accept content written by generative AI. That means we will not publish articles, pitches, quotes, bios, captions or social copy that were drafted, rewritten, expanded or substantially generated by ChatGPT, Claude, Gemini, Copilot, Jasper, or any similar tool. If the machine wrote the sentences, it is not for us.
What is banned
- Submitting AI-drafted copy and lightly editing it
- Using AI to “polish”, paraphrase or expand a thin outline into publishable prose
- AI-generated quotes attributed to a real person
- AI-written case studies, timelines or “analysis” presented as the author’s own work
- Pitch replies that read as generic AI paste
What is allowed
- The author thinking and writing in their own words
- Spellcheck, grammar checkers and dictionary tools that do not invent new content
- Transcription tools for interviews the author conducted (the author still writes the piece)
- Search and research tools used to find sources the author then reads and verifies
Author certification. Every contributor must confirm, before we edit: “I wrote this myself. No generative AI drafted, rewrote or generated this piece.” We may ask for working notes, source files or a short call to test that they can defend every claim. Refusal or evasion is a reject.
If we discover AI use after acceptance, we kill the piece before publish, or issue a correction and take it down if it already ran. Repeat offenders are barred from contributing.
Editors and staff. The same rule applies in-house. Editors may use AI for admin tasks but not to write or rewrite journalism that carries a Cyber Standard byline.
02What we publish
We run original analysis, practitioner explainers, incident and sector deep-dives, interviews, and clearly labelled opinion. Pieces should teach something a working CISO, CTO or board member can use — we do not regurgitate a press release.
We do not run: product pitches dressed as journalism; unattributed speculation; confidential client detail; personal attacks; or anything that fails the AI rule above.
Typical length is 600–1,500 words unless the Editor of Record agrees otherwise. Every piece needs a clear headline claim, a named byline with a real bio, and sources the author can defend.
03Voice and style
Write like a sharp practitioner talking to peers — plain Australian English, short sentences, concrete examples. No corporate fluff, no buzzword stacks, no “in today’s rapidly evolving threat landscape”. Prefer active voice. Define acronyms on first use. Australian spelling (organisation, defence, licence) unless quoting a US source.
Headlines should say what happened or what the reader should do — not tease. Subheads break long pieces into scannable sections.
04Accuracy and sourcing
Facts must be checkable. Name the source for numbers, incident claims and product assertions. Link primary sources where they exist (advisories, judgments, standards, filings). Distinguish reported fact from the author’s judgment. If something is alleged or unconfirmed, say so.
Authors keep notes and source links for at least 12 months after publish so we can answer challenges. Editors fact-check before publish; anything that cannot be verified comes out or is labelled clearly.
05Independence and conflicts
Editorial decisions sit with the Editor of Record, Dean White, and the publishing team. Sponsored or partner content, if we ever run it, must be labelled Sponsored or Partner — never as news or analysis.
Authors disclose any financial, employment or vendor relationship that touches the subject of their piece. If they work for a vendor named in the story, we either kill the piece or label it clearly as contributor opinion from that vendor.
06Commercial and product pitches
We do not publish vendor white papers, feature lists or “why our product wins” essays as editorial. A practitioner may name tools they actually use if the piece is about a method or incident — not a sales funnel. Unsolicited product pitches go to media@thecyberstandard.com.au and are declined unless they meet the editorial bar above (and the AI ban).
07Contributor process
Pitch or submit to media@thecyberstandard.com.au. Include: working title, a 2–3 sentence angle, why you are the right author, and the AI certification in section 1.
We edit for clarity, length and house style. We may ask for rewrites. Acceptance is not a guarantee of a publish date. Contributors keep copyright in their name unless otherwise agreed; The Cyber Standard gets a royalty-free licence to publish and promote the piece on the site and socials.
Full contributor kit (bio, portrait, deadlines) is issued separately once a pitch is accepted.
08Corrections
Significant errors get a correction note at the top or foot of the piece, with the date. We do not silently rewrite history. Retractions are rare and decided by the Editor of Record.
09Contact
Editorial and contributor queries: media@thecyberstandard.com.au
Editor of Record: Dean White