Credit: Jen Anderson
Bit9's Chris Lord talks about disclosure, bounty programs, and vulnerability marketing with CSO, in the first of a series of topical discussions with industry leaders and experts.
Hacked Opinions is an ongoing series of Q&As with industry leaders and experts on a number of topics that impact the security community. The first set of discussions focus on disclosure and how pending regulation could impact it. In addition, we asked about marketed vulnerabilities such as Heartbleed and bounty programs, do they make sense?
CSO encourages everyone to take part in the Hacked Opinions series. If you would like to participate, email Steve Ragan with your answers to the questions presented in this Q&A, or feel free to suggest topics for future consideration.
Where do you stand: Full Disclosure, Responsible Disclosure, or somewhere in the middle?
Chris Lord, Senior Director of R&D, Bit9 + Carbon Black (CL): The middle, but definitely leaning more toward responsible or coordinated disclosure. Overall, I'm more concerned about nondisclosure when the vulnerabilities that get reported through side channels or internally in a company never see the light of day. Responsible disclosure applies even when there aren't other parties to take it public.
If a researcher chooses to follow responsible/coordinated disclosure and the vendor goes silent - or CERT stops responding to them - is Full Disclosure proper at this point? If not, why not?
CL: I'd love to follow my kneejerk reaction and say "yes," but full disclosure of a vulnerability must consider who carries the risk and seek first to mitigate that risk. And when those who should be partners go dark, the responsibility falls on the researcher.
It isn't like disclosures around food, safety or health where the agent of harm is what is revealed. With vulnerabilities, the agent of harm only comes to exist in a significant way following disclosure.
If full disclosure leaves millions of people exposed and opens the practical exploitability to a broad group of actors, then we've not done the research community or the public a service.
When responsible disclosure is no longer an option, it's better to aim for the slow reveal: put the mitigation and remediation out early and share the exploitable details later. Ultimately, it all needs to be out.
Bug Bounty programs are becoming more common, but sometimes the reward being offered is far less than the perceived value of the bug/exploit. What do you think can be done to make it worth the researcher's time and effort to work with a vendor directly?
CL: As a vendor, I work with researchers on reported vulnerabilities. It's really about partnership. Bounties can't match the value of a vulnerability to actors with malicious intent. Nor can they match the potential loss to a company.
Sign up for Computerworld eNewsletters.