A new security publication owes its readers an explanation. Here is ours: what we are for, how we check things, and what happens when we get them wrong.
Written for people who have to act
There is no shortage of security news. There is a shortage of security news that tells you what to do on Tuesday morning. Cyber-Threat.net is written for the analyst triaging an advisory, the engineer turning it into a detection and the manager explaining both to a board. If a piece does not help one of them, it has not earned its place.
We cover threats and vulnerabilities, Hunt Lab detection content, horizon scanning, regulation and standards, AI security, OT cyber, and reviews and events. We would rather be useful than first. When a story is still forming, we say so, and we come back when it has settled.
Sourcing
We work from primary sources wherever they exist: vendor advisories, CVE records, government guidance and the legislation itself. We link to them, so you can check our reading against theirs. We quote exactly, or not at all. We separate what is confirmed from what is claimed, and when we say something is being exploited, we tell you who says so. Our reviews say how we reached a view; if we have read the documentation rather than run the tool, we say that too.
Corrections
We will get things wrong. When we do, we would rather hear about it than not. Email newsletter@cyber-threat.net with “Correction” in the subject line. Significant errors are corrected with a dated note at the foot of the article. Where security advice was wrong, the correction goes at the top of the article. We do not quietly delete articles. The full rules are in our editorial policy.
Each of our main sections has its own page, with a short list of where to start: Threats & Vulnerabilities, Hunt Lab, Regulation & Standards and OT Cyber.
Hunt Lab
Reading about an attack is not the same as finding it in your own logs. Hunt Lab publishes detection and hunting queries you can lift into your own tooling, kept in a public repository at github.com/CyberThreatNet/hunt-lab where you can read, test and improve them. Test them in your own environment first. Every network is unusual in its own way.
Welcome. Tell us what we can do better.