INFORMATION TECHNOLOGY ISSUE SCORING AND VERSION RECOMMENDATION
In examples, vulnerability information is obtained from vendors/manufacturers and/or centralized data sources and processed to extract information about associated issues. Additionally, one or more scores (e.g., a confidentiality score, an availability score, and/or an integrity score) may be generated for hardware and/or software based on a set of associated issues. A score may be version-specific, such that different versions of software may each have different associated scores. A set of generated scores may each be used as a score component to generate an aggregated score for the hardware and/or software (e.g., by weighting security and/or operational issues differently). In some instances, an organization may prioritize confidentiality over availability or vice versa, such that an aggregated score reflects a user-configured weighting. Aggregated scores for multiple hardware and/or software versions may be ranked or presented to a user, thereby enabling a user to determine whether one version is preferable to another version.
1 . A system comprising:
at least one processor; and
memory storing instructions that, when executed by the at least one processor, causes the system to perform a set of operations, the set of operations comprising:
obtaining customer information indicating at least one of hardware or software, wherein the hardware or software has a corresponding version;
identifying a set of issues associated with the version, wherein the set of issues includes two or more of a confidentiality issue, an integrity issue, and an availability issue;
generating an aggregated score for the version based on the set of issues; and
providing an indication of the aggregated score for the version.
2 . The system of claim 1 , wherein providing the indication of the aggregated score further comprises providing an indication of at least one issue of the identified set of issues.
3 . The system of claim 1 , wherein the aggregated score is generated based on one or more of:
a confidentiality score component for the confidentiality issue;
an integrity score component for the integrity issue; and
an availability score component for the availability issue.
4 . The system of claim 3 , wherein the aggregated score is generated based on a set of user-configured weights including at least one of:
a first weight for the confidentiality score component;
a second weight for the integrity score component; and
a third weight for the availability score component.
5 . The system of claim 1 , wherein the set of issues relates to at least one of:
a vulnerability for the version; or
an operational defect for the version.
6 . The system of claim 1 , wherein the aggregated score is generated based on information obtained from at least one of:
a vendor of the hardware or the software;
a centralized data source; or
a crowd-sourced data source.
7 . The system of claim 1 , wherein:
the customer information is obtained as part of a request, from a computing device, for an issue score associated with the at least one of hardware or software; and
the set of operations further comprises providing the indication of the aggregated score for the version to the computing device in response to the request.
8 . A system comprising:
at least one processor; and
memory storing instructions that, when executed by the at least one processor, causes the system to perform a set of operations, the set of operations comprising:
receiving a recommendation request comprising an indication of at least one of computer software or computer hardware;
identifying, based on the recommendation request, a set of versions;
generating, for each version of the set of versions, an aggregated score;
ranking the set of versions based on an associated aggregated score for each version; and
providing an indication of a highest-ranked version from the ranked set of versions.
9 . The system of claim 8 , wherein providing the indication of the highest-ranked version further comprises providing an indication of an aggregated score for the highest ranked version.
10 . The system of claim 8 , wherein providing the indication of the highest-ranked version further comprises providing an indication of a set of score components used to generate the aggregated score for the highest-ranked version.
11 . The system of claim 8 , wherein generating the aggregated score for each version comprises:
determining set of score components comprising two or more of:
a confidentiality score component for the version;
an integrity score component for the version; and
an availability score component for the version; and
generating the aggregated score based on a set of user-configurable weights, wherein each weight of the set of user-configurable weights corresponds to a score component of the set of score components.
12 . The system of claim 8 , wherein the set of operations further comprises:
receiving an indication to perform an action based on the provided indication; and
in response to the indication, performing at least one action of:
patching an instance of software;
upgrading an instance of software;
downgrading an instance of software;
disabling a service;
generating a knowledge article in a known error database comprising an indication to avoid functionality; or
moving a workload to a different computing device.
13 . The system of claim 12 , wherein the at least on action is performed in response to receiving approval from a user to perform the at least one action.
14 . A method for managing at least one of hardware or software of an environment, the method comprising:
receiving, from a computing device, a score request for at least one of hardware or software of the environment, wherein the hardware or software has a corresponding version;
identifying a set of issues associated with the version, wherein the set of issues includes two or more of a confidentiality issue, an integrity issue, and an availability issue;
generating an aggregated score for the version based on the set of issues; and
providing, to the computing device in response to the score request, an indication of the aggregated score for the version.
15 . The method of claim 14 , wherein providing the indication of the aggregated score further comprises providing an indication of at least one issue of the identified set of issues.
16 . The method of claim 14 , wherein the aggregated score is generated based on one or more of:
a confidentiality score component for the confidentiality issue;
an integrity score component for the integrity issue; and
an availability score component for the availability issue.
17 . The method of claim 16 , wherein the aggregated score is generated based on a set of user-configured weights including at least one of:
a first weight for the confidentiality score component;
a second weight for the integrity score component; and
a third weight for the availability score component.
18 . The method of claim 14 , wherein the set of issues relates to at least one of:
a vulnerability for the version; or
an operational defect for the version.
19 . The method of claim 14 , wherein the aggregated score is generated based on information obtained from at least one of:
a vendor of the hardware or the software;
a centralized data source; or
a crowd-sourced data source.
20 . The method of claim 14 , wherein the score request is received as part of a change management process corresponding to the environment.