@daviottenheimer most of the site-specific vulns (our term, rather than SaaS) are not added but we have a list going
-
-
Replying to @attritionorg
@attritionorg but i'm talking more than outage. bypass, disclosure, loss1 reply 0 retweets 0 likes -
Replying to @daviottenheimer
@daviottenheimer outage is the primary thing we have been tracking decently. site-specific vulns (any kind) is next goal1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg that's what need to see entered. tracking SaaS breaches where attackers suck data out1 reply 0 retweets 0 likes -
Replying to @daviottenheimer
@daviottenheimer@Datalossdb tracks the breaches. we want association between site-specific vulns, which led to breaches, and more.1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg@datalossdb where would microsoft SaaS (office 365) token disclosure flaw "icedagger" end up? http://www.adallom.com/blog/severe-office-365-token-disclosure-vulnerability-research-and-analysis/ …1 reply 0 retweets 0 likes -
Replying to @daviottenheimer
@daviottenheimer that is Cloutage, site/service specific vuln1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg ok, will get it entered there. thanks!1 reply 0 retweets 0 likes -
Replying to @daviottenheimer
@daviottenheimer as mentioned, we have a list of 100+ site-specific (the bigger ones) just not entered. our steward has been sick1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg let me know if i can help. we'll enter them in1 reply 0 retweets 0 likes
@daviottenheimer mail me please, jericho@ twitter handle
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.