Hope @CloudFlare can make a statement about this: http://zeroscience.mk/files/wafreport2013.pdf … (http://news.ycombinator.com/item?id=5306519 ) - I'm pretty annoyed as a paying customer.
@eastdakota @bluetidepro @CloudFlare @mikedamm Don't need history refresher. Your WAF didn't stop 48 known attacks. You claim it "works".
-
-
@attritionorg@bluetidepro@CloudFlare@mikedamm server response sometimes better indication of vulnerability than request. -
@eastdakota@bluetidepro@CloudFlare@mikedamm "sometimes", so why bother filtering known bad attacks? doesn't seem like a good strategy
End of conversation
New conversation -
-
-
@attritionorg@bluetidepro@CloudFlare@mikedamm they weren't attacks. They were tests. The underlying site wasn't vulnerable. We detect. -
@eastdakota@attritionorg@bluetidepro@CloudFlare@mikedamm Ultimate goal is to detect Web attacks without requiring awareness of vulns. - End of conversation
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.