# US 2008/0313739 A1 · System Test and Evaluation Automation Modules

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

- Number: US 2008/0313739 A1
- Document ID: US20080313739A1
- Status: Published application
- Kind: A1
- Application number: 11/761,775
- Filed: 2007-06-12
- Published: 2008-12-18
- Earliest claimed: 2007-06-12
- Assignees: Honeywell International Inc.
- Inventors: Charles Edward Martin
- Web page: https://patentgrep.com/patent/US20080313739A1

## CPC

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

## Abstract

Methods are provided for providing uniform and repeatable information security (INFOSEC) assessments. In the embodiments, a security assessor interacts with a system test evaluation and automation module (S.T.E.A.M.) to perform an INFOSEC assessment on a computer system. S.T.E.A.M. generates reports and checklists to help determine whether the computer system being assessed is compliant with one or more INFOSEC requirements. Additionally, S.T.E.A.M. generates reports and checklists that assist the INFOSEC assessor in determining the most important, and most vulnerable data on the computer system.

## Claims

### Claim 1

A method for performing an information security assessment of a computer system, comprising:
encoding at least one information security requirement in a database, wherein each encoded information security requirement is associated with at least one encoded policy;
receiving a first input, wherein the first input requests at least one encoded information security requirement, wherein performing the information security assessment comprises determining whether the computer system complies with the requested encoded information security requirement;
in response to the first input, generating a first checklist comprising at least one policy associated with the at least one information security requirement;
receiving a second input, wherein the second input indicates whether the computer system satisfied the at least one policy; and
in response to receiving the second input, generating a second report, wherein the second report comprises a description as to whether the computer system satisfied the at least one policy.

### Claim 2 (depends on 1)

The method of claim 1, wherein each encoded information security requirement is further associated with at least one encoded control.

### Claim 3 (depends on 1)

The method of claim 1, wherein the encoded information security requirement corresponds to the Department of Defense Instruction 8500.2.

### Claim 4 (depends on 1)

The method of claim 1, wherein the second report further comprises a listing of each policy that was not satisfied.

### Claim 5 (depends on 2)

The method of claim 2, wherein the second report further comprises listing each policy and each control that were not satisfied.

### Claim 6

A method for performing an information security assessment of a computer system, comprising:
generating a list, wherein the list comprises at least one criticality definition;
receiving a first input, wherein the first input associates a value to each of the at least one criticality definition;
generating a first report, wherein the first report comprises a description of the at least one criticality definition and associated value;
receiving a second input, wherein the second input (i) defines at least one data type and (ii) associates impact attributes with the at least one data type, each impact attribute being assigned with a criticality value;
receiving a third input, wherein the third input associates each of the at least one data type with at least one sub-system;
associating the at least one criticality definition and associated value with at least one encoded information security requirement, wherein the at least one encoded information security requirement is associated with at least one encoded policy;
generating a checklist comprising the at least one encoded policy;
receiving a fourth input, wherein the fourth input comprises an indication of whether the computer system satisfied the at least one encoded policy; and
generating a second report, wherein the second report comprises a description as to whether the computer system satisfied the at least one policy.

### Claim 7 (depends on 6)

The method of claim 6, wherein the fourth input further comprises a finding level.

### Claim 8 (depends on 7)

The method of claim 7, wherein the fourth input further comprises comments regarding the at least one policy.

### Claim 9 (depends on 6)

The method of claim 6, wherein the checklist further comprises at least one control.

### Claim 10 (depends on 6)

The method of claim 6, further comprising:
generating an impact criticality matrix.

### Claim 11

A method for performing an information security evaluation of a computer system, comprising:
providing encoded information security vulnerabilities, wherein each encoded vulnerability is associated with (i) a CVE/CAN number, (ii) a description, (iii) a severity level, and (iv) a list of impact attributes;
receiving a completed information security assessment of a computer system, wherein the completed information security assessment includes a set of data types.
receiving a first input, wherein the first input associates a set of IP addresses to a set of data types;
receiving a second input, wherein the second input associates a set of CVE/CAN numbers to the set of IP addresses;
using the first and second inputs to associate a set of CVE/CAN numbers to a set of data types, and produce a first report of data types associated with the set of CVE/CAN numbers;
receiving a third input, wherein the third input comprises a data type criticality weight for each data type in the first report;
receiving a fourth input, wherein the fourth input comprises a technical finding weight for each CVE/CAN number of the second input; and
using the third and fourth inputs to generate an overall vulnerability criticality matrix.

### Claim 12 (depends on 11)

The method of claim 11 further comprising presenting the set of data types.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
using the second input to produce a second report CVE/CAN numbers.

### Claim 14 (depends on 11)

The method of claim 11, wherein the overall vulnerability criticality matrix comprises an x-axis, wherein each entry along the x-axis corresponds to ordered pairs of data types and impact attributes.

### Claim 15 (depends on 14)

The method of claim 14, wherein entries along the x-axis are listed in descending order of data type criticality weight.

### Claim 16 (depends on 14)

The method of claim 14, wherein the overall vulnerability criticality matrix further comprises a y-axis, wherein each entry along the y-axis corresponds to a CVE/CAN vulnerability listed in the second report.

### Claim 17 (depends on 16)

The method of claim 16, wherein entries along the y-axis are listed in descending order of technical finding weight.

### Claim 18 (depends on 11)

The method of claim 11, further comprising:
receiving a fifth input, wherein the fifth input defines an information security vulnerability that has not been associated with a CVE/CAN number.

### Claim 19 (depends on 15)

The method of claim 15, wherein the fifth input assigns to the information security vulnerability that has not been associated with a CVE/CAN number (i) a description, (ii) a severity level, and (iii) at least one impact attribute affected by the information security vulnerability.

### Claim 20 (depends on 1)

The method of claim 1, wherein the encoded information security requirement corresponds to the Health Insurance Portability and Accountability Act.
