Editorial Policy

Threat Vectr runs an automated editorial pipeline. It continuously monitors a curated set of established security news outlets and official sources — vendor advisories, CERT bulletins, CVE records, regulator announcements — for developments that matter to defenders.

When something newsworthy surfaces, our pipeline rewrites, condenses, and contextualizes that reporting using AI, and publishes the result under the ThreatVectr Newsdesk byline. Every story credits and links the source it is based on, and links the primary materials — advisories, CVE records, regulator filings — wherever they exist, so you can always read the original for yourself.

Human operators oversee the system: they choose and curate the sources the pipeline monitors, tune how it works, review its output over time, and handle corrections. Individual stories are machine-drafted; the system that produces them is run by people.

Editorial responsibility for this site rests with Lee Brown, of Imicus Group in Brisbane, Australia. Questions about a story, and requests to correct one, reach a named person.

Our pipeline only draws from sources we have deliberately added to it:

• Established security press — recognised cybersecurity news outlets with their own editorial standards.
• Official and primary sources — vendor security advisories, CVE/NVD records, CERT and government agency bulletins, and regulator filings and announcements.

We do not ingest anonymous paste sites, unverified social-media claims, or content farms. Every published story names its originating source with a visible credit and link, and we link primary sources directly whenever they are available — if a story is about a CVE, we link the CVE record; if it's about an advisory, we link the advisory.

Security news moves fast and early details are often wrong or incomplete — in the original reporting and, therefore, sometimes in ours. When we learn a story is inaccurate, we correct it and mark it as updated. Our full policy, including how to report an error, is on the corrections page.

To be completely plain about it: the copy you read on Threat Vectr is drafted by AI. Humans operate and oversee the automated system, curate the sources it reads, monitor its output, and handle corrections — but the writing itself is machine-generated, rewritten from the credited source material. If that division of labour matters to you (we think it should), now you know exactly where the line sits.

Every story is marked AI-assisted next to its byline and carries a short note on how it was made. Story pictures are illustrations made by an image model, never photographs of the events described: each one is captioned as such, and the picture file itself carries the standard IPTC “trained algorithmic media” label.

Threat Vectr is operated by Imicus Group, an Australian company that also builds security products. The site is funded by advertising — including house ads for sister products such as Train2Secure and Scan2Secure. Advertising never influences which stories the pipeline covers or how they are written.

Questions about this policy, our sources, or how a story was produced? Reach us via the contact page — a human reads and answers every message.