Solving the dilemma of vulnerability exploitation disclosure
by Zeljka Zorz - Managing Editor - Tuesday, 15 October 2013.
The subject of software and hardware vulnerability disclosure has been debate time and time again, and most agree that, if possible, vulnerabilities should first be disclosed to the manufacturer / developer, then ultimately to the public if they are too slow to react or decide not to patch it for whatever reason.

But what about disclosure of information about the fact that vulnerabilities that are being exploited in the wild? What is the responsible thing to do then?

In this podcast recorded at the Virus Bulletin 2013, Tom Cross from Lancope shares some insight into the things you should take into consideration when deciding on the best course of action.



Tom Cross is Director of Security Research at Lancope. He has over a decade of experience as a security researcher and thought leader. He is credited with discovering a number of critical security vulnerabilities in enterprise-class software, and frequently speaks on security issues at conferences around the world.

Spotlight

Black hole routing: Not a silver bullet for DDoS protection

As ISPs, hosting providers and online enterprises around the world continue suffering the effects of DDoS attacks, often the discussions that follow are, “What is the best way to defend our networks and our customers against an attack?”


Weekly newsletter

Reading our newsletter every Monday will keep you up-to-date with security news.
  



Daily digest

Receive a daily digest of the latest security news.
  
DON'T
MISS

Mon, Mar 2nd
    COPYRIGHT 1998-2015 BY HELP NET SECURITY.   // READ OUR PRIVACY POLICY // ABOUT US // ADVERTISE //