@SushiDude @mroytman @raesene @VZDBIR while poking in the 2005 time frame, seemed like little change or update
-
-
@attritionorg@sushidude@mroytman@raesene So, can you folks provide data/input for next year? Def appreciate your veracity. -
@hrbrmstr@sushidude@mroytman@raesene can certainly give input re: the vuln side of things before it goes to press, sure. -
@attritionorg@sushidude@mroytman@raesene very much appreciated. I'll follow up eoQ3 as we start prep for next year. +100 -
@hrbrmstr@sushidude@mroytman@raesene in mean time, encourage sec vendors to use better data for vuln scanning/signatures -
@attritionorg@SushiDude@mroytman@raesene now *that* I can do. Prepping a VZ sec blog post for next week and I'll def include it. -
@hrbrmstr@SushiDude@mroytman@raesene remember, those may be 'top attacks' because you aren't looking for so many others -
@attritionorg possible bias from tool false pos, 1 org's results dominating others, 1 noisy attacker?@hrbrmstr@mroytman@raesene -
@SushiDude@attritionorg@hrbrmstr@raesene that's a good question id like to include@jaimeblascob on - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.