About The Perimeter Site
A daily security desk: what was attacked, what was exploited, and what it means.
The Perimeter Site follows the security news cycle and turns it into something readable. Every day brings breaches, ransomware, exploited vulnerabilities and regulatory action; most of it is reported once, in isolation, and then buried. This site collects that flow, classifies it, and keeps a running answer to the questions people actually ask — who got hacked today, what is being exploited right now, and which sectors are being hit.
What is here
- The Desk — longer pieces: post-mortems of significant incidents, vulnerability analysis, sector watch and patch priorities.
- The Wire — the stream of security headlines as they are assessed, newest first, each with a severity rating and the categories it falls into.
- Hacked Today and Data Center Security — continuously updated views of recent incidents and the infrastructure they hit.
Where the reporting comes from
Source material is public security reporting, vendor advisories, and disclosures from affected organisations and the researchers who found the issues. Every item on the wire links back to the original report, so you can read the primary source rather than take this site's word for it.
How severity is judged
Each headline is assessed on a five-point severity scale and tagged by category — data breach, ransomware, supply chain, exploited-in-the-wild and so on. That assessment is a triage aid, not a risk rating for your organisation. A SEV 5 that does not touch your stack matters less to you than a SEV 3 that does. Use it to sort your reading, not to size your response.
Limits worth stating plainly
Security news moves faster than confirmation does. Early reports are frequently wrong about scale, cause and attribution, and this site inherits those errors. Nothing here is security, legal or compliance advice, and no item should be treated as confirmation that a named organisation was breached — follow the link, read the primary source, and verify before acting. Corrections are welcome and made quickly; see contact.
Related
For the vulnerability side of the same story — which CVEs are confirmed exploited in the wild, and what the resulting breaches have cost UK organisations at the regulator — see Hazard.