Analyzing target software for security vulnerabilities

US2016110549A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016110549-A1
Application numberUS-201314787863-A
CountryUS
Kind codeA1
Filing dateJul 12, 2013
Priority dateJul 12, 2013
Publication dateApr 21, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method of analyzing target software for security vulnerabilities comprises, with a processor, scanning a codebase of a target software using a static analysis scan to identify a number of security flaws, and calculating a number of code metrics of the codebase of the target software for a number of iterations over a period of time to obtain a number of historical scans.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method of analyzing target software for security vulnerabilities comprising, with a processor: scanning a codebase of a target software using a static analysis scan to identify a number of security flaws, and calculating a number of code metrics of the codebase of the target software for a number of iterations over a period of time to obtain a number of historical scans; and analyzing a number of correlations between security flaw evolution and a number of the code metrics. 2 . The method of claim 1 , in which scanning the codebase of the target software further comprises obtaining runtime security information from the runtime environment of a version of the target software for a number of iterations over a period of time to obtain a number of additional historical scans. 3 . The method of claim 1 , further comprising prioritizing a number of security flaws based on the correlations between the security flaw evolution and the code metrics. 4 . The method of claim 1 , further comprising predicting risks associated with the codebase based on the correlations between the security flaw evolution and the code metrics. 5 . The method of claim 1 , further comprising storing the historical scans in a historical scan database. 6 . The method of claim 1 , in which the number of iterations is a plurality iterations. 7 . A system for analyzing target software for security vulnerabilities comprising: a processor; a data storage device coupled to the processor, the data storage device comprising: a static analysis module to scan a codebase of a target software to identify a number of security flaws; a runtime security module to obtain runtime security information from the runtime environment of a version of the target software; and a code metrics module to calculate a number of code metrics of the codebase of the target software; and a historical scan database for storing a number of historical scans over a number of iterations over a period of time, the historical scans comprising results of at least one of the static analysis module, runtime security module, and code metrics module. 8 . The system of claim 7 , further comprising a security correlation module to analyze a number of correlations between security flaw evolution and a number of the code metrics stored within the historical scan database. 9 . The system of claim 7 , further comprising a security flaw prioritization module to prioritize a number of security flaws based a number of correlations between the security flaw evolution and the code metrics. 10 . The system of claim 7 , further comprising a security flaw prediction module to predict risks associated with the codebase based on the correlations between the security flaw evolution and the code metrics. 11 . The system of claim 7 , further comprising a server, in which the functionality of the system is provided as a Software as a Service (SaaS), a Platform as a Service (PaaS), a Infrastructure as a Service (IaaS), an application program interface (API) as a service (APIaaS) or combinations thereof via the server. 12 . A computer program product for analyzing target software for security vulnerabilities, the computer program product comprising: a non-transitory computer readable storage medium comprising computer usable program code embodied therewith, the computer usable program code comprising: computer usable program code to, when executed by at least one processor, analyze a number of correlations between a number of static analysis scans, a number of code metrics, and a number of runtime security scans determined from target software; and computer usable program code to, when executed by the at least one processor, prioritize a number of security flaws based on the correlations. 13 . The computer program product of claim 11 , further comprising computer usable program code to, when executed by the at least one processor, predict security flaws associated with the target software based on the correlations. 14 . The computer program product of claim 11 , further comprising: computer usable program code to, when executed by the at least one processor, scan a codebase of the target software using static analysis to identify a number of security flaws in the static analysis scans; and computer usable program code to, when executed by the at least one processor, calculate a number of code metrics of an codebase of the target software. 15 . The computer program product of claim 11 , further comprising computer usable program code to, when executed by the at least one processor, obtain runtime security information from a runtime environment of the target software.

Assignees

Inventors

Classifications

  • Checking; Contextual analysis · CPC title

  • Software metrics · CPC title

  • Test or assess software · CPC title

  • G06F21/577Primary

    Assessing vulnerabilities and evaluating computer system security · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016110549A1 cover?
A method of analyzing target software for security vulnerabilities comprises, with a processor, scanning a codebase of a target software using a static analysis scan to identify a number of security flaws, and calculating a number of code metrics of the codebase of the target software for a number of iterations over a period of time to obtain a number of historical scans.
Who is the assignee on this patent?
Hewlett Packard Development Co
What technology area does this patent fall under?
Primary CPC classification G06F21/577. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Apr 21 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).