The Common Vulnerability Scoring System (CVSS) is an industry standard for assigning a score to computer system security vulnerabilities in an enterprise, the score being typically based on base score, environmental score metrics and temporal score metrics. These metrics are typically aggregated manually by a researcher.
The present disclosure will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:
The Common Vulnerability Scoring System (CVSS) is an industry standard for assigning a score to computer system security vulnerabilities in an enterprise, the score being based on the following metrics:
base score metrics which are inherent to a vulnerability, such as, for example, the complexity of the vulnerability, the impact of the vulnerability on confidentiality of information affected by the vulnerability, and the impact of the vulnerability on the integrity of information affected by the vulnerability;
environmental score metrics which evaluate the effect of a vulnerability within a particular enterprise, such as, for example, a percentage of enterprise assets which are vulnerable to the vulnerability and the percentage of enterprise data which may potentially be lost as a result of exploitation by the vulnerability; and
temporal score metrics which evaluate vulnerability properties which typically change over time, such as, for example, the availability of an implementation of the vulnerability as an exploitation which may affect the enterprise, the type of remedy available against the vulnerability, and the level of verification that an implementation of the vulnerability exists.
It is appreciated that the metrics which comprise a CVSS score are typically aggregated manually by a researcher. While base score metrics are typically objective metrics which are inherent to a vulnerability and environmental score metrics are typically subjective metrics which are inherent to a particular enterprise, temporal score metrics typically change over time. Therefore, for a CVSS score to remain accurate over time, the temporal score metrics should be periodically updated. The present disclosure seeks to provide an automatic update mechanism for temporal score metrics comprised in a CVSS score by automatically analyzing vulnerability information which is commonly available on the internet.
Reference is now made to
System 100 is preferably operative to analyze preexisting vulnerability information, the preexisting vulnerability information relating to at least one of at least one vulnerability and at least one attack vector thereof. The at least one vulnerability can have a preexisting CVSS score, the preexisting CVSS score being based at least partially on the preexisting vulnerability information.
Responsive to analyzing preexisting vulnerability information, system 100 is also preferably operative to extract new vulnerability information relating to the at least one of the at least one vulnerability and the at least one attack vector thereof. System 100 is also operative to employ the new vulnerability information to update the preexisting CVSS score, as will be described hereinbelow.
As shown in the example of
As shown in step A of the example of
Responsive to retrieving the industry-standard vulnerability identification code from vulnerability record 122, system 100 preferably utilizes the industry-standard vulnerability identification code to access a publicly available vulnerability information web page 126 which comprises publicly available information pertaining to vulnerability 122. The publicly available information may comprise, inter alia, a description of vulnerability 122, attack vectors of vulnerability 122, and a list of sources of vulnerability advisory information relating to vulnerability 122 and to attack vectors thereof in the form of one or more URLs 130, each of URLs 130 linking to a particular source of vulnerability advisory information.
It is a particular feature of the example of
As shown in step B of the example of
It is a particular feature of the example of
In the example of
It is a particular feature of the example of
In the example of
CVSS score record 124 also preferably includes an overall CVSS score which is based at least on the base score, the environmental score and the temporal score. In the example of
As shown in step C of
In the example of
Reference is now made to
Responsive to analyzing the preexisting vulnerability information, new vulnerability information relating to at least one of the vulnerability and the at least one attack vector thereof is then extracted (202). As described hereinabove with reference to
Thereafter, the new vulnerability information is employed to update the preexisting CVSS score (204).
Reference is now made to
As shown in
System 100 preferably includes vulnerability database 120 comprising a collection of vulnerability records 122 and a collection of CVSS score records 124, each of which vulnerability records 122 preferably comprising information pertaining to a particular vulnerability relevant to the enterprise, each of which vulnerability records 122 preferably having a corresponding CVSS score record 124.
System 100 also can include vulnerability information analyzing functionality 300 operative to analyze preexisting vulnerability information which relates to at least one of at least one vulnerability and at least one attack vector thereof, the at least one vulnerability having a preexisting CVSS score, the preexisting CVSS score being based at least partially on the preexisting vulnerability information.
System 100 further can include vulnerability information extraction functionality 302, which is operative, responsive to analyzing preexisting vulnerability information by vulnerability information analyzing functionality 300, to extract new vulnerability information relating to the at least one of the at least one vulnerability and the at least one attack vector thereof.
System 100 yet further preferably includes CVSS score updating functionality 304 operative to employ the new vulnerability information extracted by vulnerability information extraction functionality 302 to update the preexisting CVSS score. Each of the functionality may include, for example, hardware devices including electronic circuitry for implementing the functionality described herein. In addition or as an alternative, each of the functionality may be implemented as a series of instructions encoded on a machine-readable storage medium of a computing device and executable by a processor. It should be noted that, in some embodiments, some of the functionality are implemented as hardware devices, while other functionality are implemented as executable instructions.
It will be appreciated by persons skilled in the art that the present disclosure is not limited by what has been particularly shown and described hereinabove. Rather the scope of the present disclosure includes both combinations and subcombinations of the various features described hereinabove as well as modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not in the prior art.
Number | Name | Date | Kind |
---|---|---|---|
8095984 | McFarlane et al. | Jan 2012 | B2 |
20020147803 | Dodd et al. | Oct 2002 | A1 |
20040010571 | Hutchinson et al. | Jan 2004 | A1 |
20050015622 | Williams et al. | Jan 2005 | A1 |
20070143827 | Nicodemus et al. | Jun 2007 | A1 |
20070169199 | Quinnell et al. | Jul 2007 | A1 |
20090024663 | McGovern | Jan 2009 | A1 |
20090030751 | Barve et al. | Jan 2009 | A1 |
20110277034 | Hanson | Nov 2011 | A1 |
20110307957 | Barcelo et al. | Dec 2011 | A1 |
20120102543 | Kohli et al. | Apr 2012 | A1 |
20120232679 | Abercrombie et al. | Sep 2012 | A1 |
20120304300 | LaBumbard | Nov 2012 | A1 |
20130239167 | Sreenivas et al. | Sep 2013 | A1 |
20130253978 | Adachi et al. | Sep 2013 | A1 |
20140007241 | Gula et al. | Jan 2014 | A1 |
Entry |
---|
“McAfee Vulnerability Manager”; < http://www.mcafee.com/in/products/vulnerability-manager.aspx >, Retrieved Jan. 8, 2013. |
“RandomStorm announces new vulnerability management platform”, < http://www.randomstorm.com/news-randomstorm-new-scanning.php >, Oct. 16, 2012. |
“Started Trial of Automated Collection of Vulnerability Countermeasure Information Released by Product Developers”, < http://www.ipa.go.jp/security/english/vuln/JVNiPedia2009q1—en.html >, May 2009. |
Neuhaus, et al.; “Security Trend Analysis with CVE Topic Models”, < http://dspace.ucalgary.ca/bitstream/1880/48066/1/2010-970-19.pdf >, Nov. 1-4, 2010. |
Seville, “Common Vulnerability Scoring System (CVSS-SIG)”, < http://www.first.org/cvss >, Jun. 20, 2007. |
Number | Date | Country | |
---|---|---|---|
20140215629 A1 | Jul 2014 | US |