Cisco Talos
cited as evidence in 56 · CNA assigner on 2 (independent) · credited finder on 1 of 59 known-exploited records. Every aggregate on this page is recomputed from the records listed below — each one already cited to its public source.
blog.talosintelligence.com ↗ · home of the cited advisories
Roles across the work
— find / fix / exploit / catalog, computed per record from credit type, the vendor-self-CNA gate, and the linked public exploit catalogStands alone with its own profile — the research arm of Cisco; successor to sourcefire. Related, but credited in its own right (soft link, not a rollup).
Each dimension is a count of the listed records where this contributor did that job. A CNA row is fix only when the affected product is the assigner’s own; registries, coordinators, platforms, intel and research houses read as catalog, never fix. Exploit counts records where this contributor is credited as author of a public exploit / detection template in a linked catalog — we link the catalog, never host a payload.
Known for
— recomputed from this contributor’s own recordsNarrative reach
— how far this contributor’s records carry an attacker, front door → lights outFurthest any of these records carries an attacker: 5 · Lights out. 10 of 54 narrative-framed records reach data-at-risk or lights-out. (furthest-position idiom, reused from the landing map; the stage mapping is a model output over cited evidence.)
Recent highlights
— this contributor’s newest known-exploited recordsEvery record they’re cited in
— all 59, each linked to its cited sourceThis is the evidence behind every number above. Sorted ransomware-first, then by modeled exploit probability.