# US 2017/0255782 A1 · Method and system for identifying test cases for penetration testing of an application

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0255782 A1
- Document ID: US20170255782A1
- Status: Published application
- Kind: A1
- Application number: 15/070,490
- Filed: 2016-03-15
- Published: 2017-09-07
- Earliest claimed: 2016-03-01
- Assignees: Wipro Limited
- Applicants: Wipro Limited
- Inventors: Venkata Subramanian JAYARAMAN; Sumithra SUNDARESAN
- Web page: https://patentgrep.com/patent/US20170255782A1

## CPC

- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure relates to a method and a system for identifying one or more test cases for penetration testing of an application associated with an entity. An application testing system receives data related to application from one or more data sources and uses the data to determine threat score, vulnerability score, human error score, business impact score and popularity score. Further, application testing system identifies threat quantifier value based on threat score, vulnerability score and human error score. The application testing system also determines impact quantifier value based on business score and popularity score. The application testing system then determines threat severity level and impact severity level based on threat quantifier value and impact quantifier value. Based on the determined threat severity level and the impact severity level, the application testing system identifies the one or more test cases for performing penetration testing of the application.

## Claims

### Claim 1

A method of identifying one or more test cases for penetration testing of an application associated with an entity, the method comprising:
receiving, by an application testing system, data related to the application from one or more data sources;
determining, based on the received data, by the application testing system, a threat score indicating one or more threats to the application, a vulnerability score indicating one or more vulnerabilities of the application to the one or more threats, a human error score indicating probability of the one or more threats due to one or more human errors, a business impact score indicating impact of the application on the entity, and a popularity score indicating popularity of the application;
determining, by the application testing system, a threat quantifier value based on the threat score, the vulnerability score and the human error score;
determining, by the application testing system, an impact quantifier value based on the business impact score and the popularity score;
determining, by the application testing system, a threat severity level and an impact severity level based on the corresponding threat quantifier value and the impact quantifier value; and
identifying, by the application testing system, the one or more test cases based on the threat severity level and the impact severity level for performing penetration testing of the application.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein the data comprises application type, human error data, vulnerability data, business impact data, and popularity data.

### Claim 3 (depends on 1)

The method as claimed in claim 1, wherein determining the threat score comprises:
classifying, by the application testing system, one or more predefined threat parameters related to an application type into one of a low category, a medium category, and a high category;
assigning, by the application testing system, a predefined weightage value to the low category, the medium category and the high category; and
determining, by the application testing system, the threat score based on the assigned predefined weightage value using a first predefined technique.

### Claim 4 (depends on 1)

The method as claimed in claim 1, wherein determining the vulnerability score comprises:
classifying, by the application testing system, one or more predefined vulnerability parameters related to a vulnerability data into one of a low category, a medium category, and a high category;
assigning, by the application testing system, a predefined weightage value to the low category, the medium category and the high category; and
determining, by the application testing system, the vulnerability score based on the assigned predefined weightage value using a second predefined technique.

### Claim 5 (depends on 1)

The method as claimed in claim 1, wherein determining the human error score comprises:
classifying, by the application testing system, one or more predefined human error parameters related to a human error data into one of a low category, a medium category, and a high category;
assigning, by the application testing system, a predefined weightage value to the low category, the medium category and the high category; and
determining, by the application testing system, the human error score based on the assigned predefined weightage value using a third predefined technique.

### Claim 6 (depends on 1)

The method as claimed in claim 1, wherein determining the business impact score comprises:
classifying, by the application testing system, one or more predefined business impact parameters related to a business impact data into one of a low category, a medium category, and a high category;
assigning, by the application testing system, a predefined weightage value to the low category, the medium category and the high category; and
determining, by the application testing system, the business impact score based on the assigned predefined weightage value using a fourth predefined technique.

### Claim 7 (depends on 1)

The method as claimed in claim 1, wherein determining the popularity score comprises:
classifying, by the application testing system, one or more predefined popularity parameters related to a popularity data into one of a low category, a medium category, and a high category;
assigning, by the application testing system, a predefined weightage value to the low category, the medium category and the high category; and
determining, by the application testing system, the popularity score based on the assigned predefined weightage value using a fifth predefined technique.

### Claim 8 (depends on 1)

The method as claimed in claim 1, wherein determining the threat severity level comprises:
comparing, by the application testing system, the threat quantifier value with one or more predefined threat range of values, wherein each of the one or more predefined threat range of values is associated with one of a low category, a medium category and a high category; and
obtaining, by the application testing system, one of the low category, the medium category and the high category corresponding to the matched predefined threat range of value.

### Claim 9 (depends on 1)

The method as claimed in claim 1, wherein determining the impact severity level comprises:
comparing, by the application testing system, the impact quantifier value with one or more predefined impact range of values, wherein each of the one or more predefined impact range of values is associated with one of a low category, a medium category and a high category; and
obtaining, by the application testing system, one of the low category, the medium category and the high category corresponding to the matched predefined impact range of value.

### Claim 10

An application testing system to identify one or more test cases for penetration testing of an application associated with an entity, the application testing system comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores the processor-executable instructions, which, on execution, causes the processor to:
receive data related to the application from one or more data sources;
determine based on the received data, a threat score indicating one or more threats to the application, a vulnerability score indicating one or more vulnerabilities of the application to the one or more threats, a human error score indicating probability of the one or more threats due to one or more human errors, a business impact score indicating impact of the application on the entity, and a popularity score indicating popularity of the application;
determine a threat quantifier value based on the threat score, the vulnerability score and the human error score;
determine an impact quantifier value based on the business impact score and the popularity score;
determine a threat severity level and an impact severity level based on the corresponding threat quantifier value and the impact quantifier value; and
identify the one or more test cases based on the threat severity level and the impact severity level for performing penetration testing of the application.

### Claim 11 (depends on 10)

The application testing system as claimed in claim 10, wherein the data comprises application type, human error data, vulnerability data, business impact data, and popularity data.

### Claim 12 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the threat score by:
classifying one or more predefined threat parameters related to an application type into one of a low category, a medium category, and a high category;
assigning a predefined weightage value to the low category, the medium category and the high category; and
determining the threat score based on the assigned predefined weightage value using a first predefined technique.

### Claim 13 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the vulnerability score by:
classifying one or more predefined vulnerability parameters related to a vulnerability data into one of the low category, the medium category, and the high category;
assigning a predefined weightage value to a low category, a medium category and a high category; and
determining the vulnerability score based on the assigned predefined weightage value using a second predefined technique.

### Claim 14 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the human error score by:
classifying one or more predefined human error parameters related to a human error data into one of a low category, a medium category, and a high category;
assigning a predefined weightage value to the low category, the medium category and the high category; and
determining the human error score based on the assigned predefined weightage value using a third predefined technique.

### Claim 15 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the business impact score by:
classifying one or more predefined business impact parameters related to a business impact data into one of a low category, a medium category, and a high category;
assigning a predefined weightage value to the low category, the medium category and the high category; and
determining the business impact score based on the assigned predefined weightage value using a fourth predefined technique.

### Claim 16 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the popularity score by:
classifying one or more predefined popularity parameters related to a popularity data into one of a low category, a medium category, and a high category;
assigning a predefined weightage value to the low category, the medium category and the high category; and
determining the popularity score based on the assigned predefined weightage value using a fifth predefined technique.

### Claim 17 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the threat severity level by:
comparing the threat quantifier value with one or more predefined threat range of values, wherein each of the one or more predefined threat range of values is associated with one of a low category, a medium category and a high category; and
obtaining one of the low category, the medium category and the high category corresponding to the matched predefined threat range of value.

### Claim 18 (depends on 10)

The application testing system as claimed in claim 10, wherein the processor determines the impact severity level by:
comparing the impact quantifier value with one or more predefined impact range of values, wherein each of the one or more predefined impact range of values is associated with one of a low category, a medium category and a high category; and
obtaining one of the low category, the medium category and the high category corresponding to the matched predefined impact range of value.

### Claim 19

A non-transitory computer readable medium including instructions stored thereon that when processed by at least one processor causes an application testing system to perform operations comprising:
receiving data related to the application from one or more data sources;
determining based on the received data, a threat score indicating one or more threats to the application, a vulnerability score indicating one or more vulnerabilities of the application to the one or more threats, a human error score indicating probability of the one or more threats due to one or more human errors, a business impact score indicating impact of the application on the entity, and a popularity score indicating popularity of the application;
determining a threat quantifier value based on the threat score, the vulnerability score and the human error score;
determining an impact quantifier value based on the business impact score and the popularity score;
determining a threat severity level and an impact severity level based on the corresponding threat quantifier value and the impact quantifier value; and
identifying the one or more test cases based on the threat severity level and the impact severity level for performing penetration testing of the application.
