Editorial standards
A security wire is only worth what it is credible for. These are our rules, identical in both languages.
1. Every claim has a source
Each story lists its sources at the bottom: a researcher's disclosure, a vendor advisory, a regulator filing, an official statement or established press coverage. A rumor stays a rumor, and the text says so.
2. Two sources to accuse
Attributing an attack to a group or an actor takes more than a post. Without solid public evidence we write "attribution unconfirmed" and name what is missing.
3. No how-to for attacking
We describe techniques so defenders understand the risk. We do not publish operational step-by-steps, victim lists or stolen data.
4. Vendor statements are labeled
Software publishers and security vendors are stakeholders. Their numbers and claims are presented with their origin marked.
5. Visible corrections
Factual errors are fixed in the text, followed by a dated note stating what changed. Corrections can come from readers: write to us.
6. Independence
No story is written at a vendor's request. Any affiliate link is flagged. Sponsored content, if it ever appears, will be labeled.