Editorial standards
These are the rules the Blast Radius newsroom uses. They apply to the daily briefing, weekly recaps, the month-in-review, and every story page.
What we publish
We cover cybersecurity that a reader would want to know about that day: threats and malware, breaches, vulnerabilities, ransomware, policy and regulation, and the security industry. A story does not need to be the biggest event in the world to be worth a briefing. It does need a source a reader can open.
We do not publish rumors with no source. We do not publish a story whose only basis is a private tip we cannot point to. Tips are welcome at editors@blastradius.news. A tip is a starting point, not a finished story.
Sources
Every story lists the sources it relies on, with links. We use the names and descriptions those sources use. We do not add a fact that is not in the cited material, and we do not put words in a person's mouth. If a figure, a date, or a quotation appears in a story, it comes from the sources on that page.
When a story has more than one source, each one is listed. When two sources disagree, the story says so.
Verified and unverified
A story marked verified has been checked by a person against its sources. When the segment names the person who checked it, the story says so.
A story marked Unverified rests on a single source, or the newsroom has not confirmed it yet. The label is there so you can see that limit before you rely on the item. An unverified item can still be worth knowing. It is not the same thing as a confirmed account.
Status can change. When a later briefing confirms an item, the story is updated and the label comes off. If a material detail changes, we add a correction on the story.
Corrections
We correct factual errors. A correction names what was wrong and what the record is now, and it stays on the story. We do not quietly rewrite the past.
If you see an error, write to editors@blastradius.news. Include the page address, the line you believe is wrong, and a source for the correction. We read every correction request. When we change a story, the correction note shows the date of the change.
Typos that do not change the meaning may be fixed without a note. Anything that changes a fact, a name, a number, or a quotation gets a note.
How stories are prepared
People in the newsroom decide what runs. Staff may use software tools, including tools that draft or organize text, to gather public reporting and prepare a first pass. A person compares the story with its cited sources before it is marked verified. Software is not the reporter, and it is not the byline.
We do not present generated text as a quotation from a person. We do not invent sources, scenes, or numbers to fill a gap. If a fact is missing, the story says less, or it waits.
Independence
Coverage is not for sale. MCCoE may have a business relationship with an organization that later appears in a story. That relationship is not a reason to publish, and it is not a reason to hold back. Where a story is about MCCoE itself, we say so in plain language.
What this site is not
Blast Radius is a news site. It is not professional security advice, legal advice, or an incident-response service. Read the disclaimer before you act on something you read here.