S4 Call For Papers
AAA  AAA 

Vulnerability Disclosure

There has been a lot of talk about disclosure of control system vulnerabilities. We have been laying low on this issue and letting it percolate after disclosing to US-CERT the initial control system vulnerabilities and kicking the issue off at PCSF two years ago.

With another PCSF annual meeting and disclosure panel coming up next week in San Diego, it is time to reengage. So take a look at our narrated 20 slides, 20 seconds each Pecha Kucha presentation on the topic.

If you can’t spend 6′40″, I’ll sum it up in 4 sentences. Fighting over the ‘proper’ control system vulnerability disclosure procedure and putting up new organizations is a waste of time because the decisions of vendors, asset owners, academia, government, and coordination center do not matter. The only policy that matters is the policy of the person or organization that finds the vulnerability, and many will not play ball with all these new proposed methods and organizations. I know Digital Bond wouldn’t, because we are happy with the results of our policy to disclose to US-CERT. [and we are quite conservative compared to most vuln discoverers] Instead the community, especially vendors but also asset owners, should be focused on how they will process the inevitable vulnerabilities as they arise in increasing numbers.

Comments

Comment from Ralph Langner
Time: August 20, 2008, 4:06 pm

There is a problem with vulnerability disclosure to CERT, Dale. People from the office IT world tend to think of vulnerabilities as bugs. The vulnerabilities that matter most in the control system world, however, are features, not bugs.

There was an interesting response on Matt’s original blog post (within the FranzBlog) that started the current stream of vuln-disclosure related discussion. The respondent talked about disclosing the default vendor accounts and passwords for popular control system products — an excellent example for a vulnerability that matters, but which would leave CERT without an answer. I could go on with other examples, but we don’t want to get the attention of the guys with the hat here. I don’t advocate security by obscurity, but I’m afraid there are some hot topics within the vulnerability landscape where CERT can’t help. How do we handle these?

Write a comment