This page explains how Ping2Prompt produces articles: where the facts come from, what the automation does and refuses to do, what the labels on an article mean, and how to tell us when we got something wrong. For who we are, see About.
Where stories come from
We watch primary sources first: CISA's Known Exploited Vulnerabilities catalogue, the National Vulnerability Database, GitHub security advisories, vendor advisories, project release notes and distribution security announcements. Community sources only add context; they never carry a claim on their own.
How a story is written
- New items are triaged against our product watchlist and clustered into one story per event.
- A research step extracts facts, each tied to the source URL it came from.
- A desk writer turns the facts into an article. The writer sees only the facts and their sources, never the raw pages.
- A separate fact-checker compares every sentence with the source it cites. A sentence that cannot be traced to a source is rewritten or removed.
- Code-enforced editorial rules check headlines, quotes, length, reading level and banned wording.
- A second set of checks, written as code and not run by a model, compares the structured facts in the text with what the sources contain: every CVE identifier, severity score and version number, any statement about exploitation, the links, the dates and the code blocks. A critical mismatch blocks the article. An uncertain one sends it to a person.
- A Short Ping is written from the finished article and checked against it (see below).
- Nothing publishes automatically unless the fact-check confidence is high, every claim has a source, a primary source is present, the image licence is verified and the day's publishing limits are not exceeded. Anything else waits for a person to approve it.
Series pieces (The Friday Footgun, Weekend Build and the others) never publish automatically. Each one is held until the editor has read and approved it.
The Short Ping
Every article opens with a Short Ping: a summary of about 35 words that says what happened, why it matters and what to do, so you can decide in seconds whether to read on. It is written from the finished, fact-checked article, never from the headline. Code then checks its length and confirms that every identifier, version, number and name in it appears in the article, and a separate check compares each sentence with the article. A Short Ping that fails is rewritten; if it still fails, the article waits for an editor. An editor can also write it by hand.
Exploitation status
Security articles state exploitation status as one of four things: confirmed exploitation, a public proof of concept, no exploitation reported by the vendor, or unknown. "Unknown" means the sources do not say. It does not mean safe, and we do not treat it as a reason to wait.
What the labels mean
A label under an article's headline states a fact about how that article was checked. An article without a label makes no such claim.
| Label | What it means |
|---|---|
| Automated source check | Software compared each claim with the listed sources before publication. This is the baseline for every article. |
| Source verified | A person checked the claims against the cited sources. The article says who and when. |
| Lab tested | The procedure was reproduced in a documented environment. The article gives the environment, the software versions, the date and the result. |
| Documentation reviewed | A guide whose steps and commands come from the cited vendor documentation. We have not run them. |
| Hypothetical scenario | A constructed attack path built from public vulnerability records. It is not a report of a real incident. A documented incident is reported as news and never carries this label. |
| Updated | The article was rewritten after publication because the sources changed or several reports of one release were merged. The dated update note in the text says what changed. |
| Correction issued | A factual correction was made after publication. The corrections log records what was wrong, what it says now and who or what approved the change. Copy edits such as typos are not listed. |
| Analysis / Opinion | The piece takes a position. The facts are sourced; the conclusion is ours. |
"Verified" on this site always means checked against the cited sources. It is not a security certification of any product, and it is not a promise that the sources themselves are right.
A model checking its own output never earns "Source verified" or "Lab tested". Approving an article for publication is an editorial decision, not a source check, and does not add a label. Guides and blueprints that carry only the automated label were assembled from documentation and have not been run by us: check commands against your own version before using them.
What we do not do
- We do not publish claims without a source, and we do not state as known what the sources leave open. Gaps are named in the article.
- We do not invent quotes, victims, benchmark numbers, versions or commands.
- We do not speculate about who is behind an attack.
- We do not write "we tested" unless a test was run and recorded.
Images
Every article carries a photograph chosen for relevance from licensed stock libraries (Unsplash, Pexels, Pixabay) or open archives (Openverse, Wikimedia Commons, NASA), with the licence checked at the moment we fetch it. Software has no photograph of its own, so the picture shows what the software does: a lock for a security tool, a computer for an operating system, connected networks for a web application. We do not use photos of identifiable people, and the only logo we use is that of the product the article is about. Photos are illustrative: they do not show the specific system or incident in the article. Every photo carries a credit line.
Corrections
When a source changes, for example a new fixed version or a revised severity score, the article gets a dated update line at the top and an entry on the corrections log. We do not silently rewrite published text.
Sponsors and affiliate links
Sponsor slots and affiliate links are labelled as such and carry rel="sponsored". Sponsors never see articles before publication and never influence what we cover.
Report an error
Email [email protected] with the article link and the source that contradicts it. Corrections are logged publicly.