Editorial standards

How we decide what to publish, how we credit sources, and how we fix mistakes.

What we publish

RedTeamDaily covers security news: vulnerabilities, attacks, breaches, scams, privacy and the policy around them. We publish a story when a source we track reports it. We do not write original investigations, and we do not publish rumours that no source has reported.

Where stories come from

Every story is built from public feeds published by government agencies, vendors, researchers and news outlets. You can see the full list on our Sources page. We read only what a publisher puts in its feed: the headline, the link, the date and a short excerpt. We never copy whole articles, and every story links to the original reports.

Credit

Each story shows who reported it first among neutral reporters (government agencies, news outlets and researchers), and lists every other source that covered it. Vendors are credited for their own advisories, but a vendor's blog is not used as the byline for news about a competitor.

Severity

How serious a story is comes from data, not opinion: the CVSS score of the vulnerabilities involved, and whether CISA lists them as exploited in the wild. A story with no vulnerability data has no severity label.

People

We name people only when the sources do and it matters to the story, for example someone charged or sentenced. We do not publish personal details beyond what the sources reported.

Independence

Sponsors never decide which stories appear, in what order, or what they say. Sponsored cards are always labelled. RedTeamDaily is run by Codelivly; when a story is about Codelivly, we say so.

Mistakes

If we get something wrong, we fix it and record the fix on our Corrections page, with the date and what changed. Use "Wrong?" on any story to tell us, or email hello@redteamdaily.com.

Last updated 2 November 2026