RSA 2013: Suppliers need to prepare for new security vulnerability handling standards

Software makers and online service providers need to prepare for two ISO standards on vulnerability handling processes due by the end of 2013

Software makers and online service providers need to prepare for two new ISO standards on vulnerability handling processes that are due for publication by the end of 2013.

ISO 30111 covers all vulnerability handling processes, whether they are identified internally or are reported by an external source.

ISO 29147 covers vulnerability disclosures from external sources such as end users, security researchers and hackers.

Katie Moussouris, editor of the 30111 standard and senior security strategist lead at Microsoft, expects ISO 29147 to make it easier to report vulnerabilities in software and services.

“The standard will also make advisory notices on vulnerabilities more useful in assessing risk and applying remediation,” she told attendees of RSA Conference 2013 in San Francisco.

ISO 29147 provides guidelines for preparing to receive external vulnerability reports, and the first requirement is for suppliers to make is easy to make contact with the right people internally.

“Make it easy to find the front door; it must be obvious where to submit reports because if it is not, vulnerability finders may resort to other channels such as the media or online forums,” said Moussouris.

The next thing is to acknowledge receipt of the vulnerability report, which the standard says must be done within 7 calendar days.

Read More

Application vulnerability disclosures rise, Microsoft finds

Dutch government publishes security flaw disclosure guide

RSA 2011: Microsoft promotes co-ordinated vulnerability disclosure

Microsoft seeks true 'responsible' vulnerability disclosure

Is a full vulnerability disclosure strategy a responsible approach?

“This is not the same as acknowledging the vulnerability, so no investigation is required first,” said Moussouris.

An auto-reply is probably not a good idea, she said, adding that this is a good opportunity to get the relationship with the finder off to a good start and to find out as much information as possible about the vulnerability as this will save time later during the investigation.

Once the vulnerability has been verified, the next step is to send out an advisory. According to the ISO standard, advisory notices should include:

  1. Unique identifiers for the vulnerability and the advisory
  2. Enough information for users to determine the level of risk
  3. The platforms and/or services affected by the vulnerability
  4. How severe and exploit of the vulnerability could be
  5. Location of fixes or workaround documents

“It is also probably a good idea to give the finder of the vulnerability credit,” said Moussouris.

ISO 30111 provides guidelines and recommendations for investigating and remediating vulnerabilities:

  1. Have a process and organisational structure in place to support investigation and remediation
  2. Perform a root cause analysis to identify all products/services that could be affected
  3. If vulnerabilty affects multiple products/services, prioritise according to severity rating
  4. Balance speed with thoroughness –  if threat is high, consider immediate temporary fix
  5. Co-ordinate with other suppliers if appropriate

There are several possible exit conditions, said Moussouris. These are:

  1. An inability to reproduce the vulnerability
  2. The vulnerability is already under investigation
  3. The vulnerability affects only obsolete products
  4. Vulnerability is not exploitable
  5. Vulnerability is in a third-party product/service

An inability to reproduce the vulnerability will require further discussion with the finder, knowing whether a vulnerability is exploitable demands that suppliers keep up with latest hacking techniques, and in the case of a third-party vulnerability, that supplier should be notified, said Moussouris.

Once resolution security update has been designed, created and released through an advisory to users, there are several post-release activities set out by the ISO standard:

  1. Ongoing maintenance
  2. Feedback to security development lifecycle to ensure continual improvement
  3. Monitoring of the effectiveness off the security update
  4. Monitoring of the time taken between vulnerability report and resolution
  5. Ensuring confidentiality of details of vulnerability and any person information involved
  6. Communication with finder, product divisions, affected users and supply chain

Moussouris expects ISO 3011 to raise the level of investigations carried out by suppliers and to improve the speed and quality of remediation.



Read more on Regulatory compliance and standard requirements

Data Center
Data Management