System Test and Evaluation Automation Modules
AssigneeHoneywell International Inc.
InventorCharles Edward Martin
Life of this patent
Estimating the term…
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.
Claims20
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.
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.
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.
Dependencies are inferred from the claim text.