SECURITY TEST TOOL

• US 20170264625A1
• Filed: 03/11/2016
• Published: 09/14/2017
• Est. Priority Date: 03/11/2016
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Jaganmohan, Karthik, Biswas, lndrajit
• Granted Patent: US 10,164,990 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection
• CPC Class Codes: H04L 63/1433 Vulnerability analysis

Abstract

A test tool includes a connection engine, a transformation engine, a validation engine, and a messaging engine. The connection engine connects to a first non-relational database, a second non-relational database, and a server. The transformation engine receives first and second messages from the first and second non-relational databases and transforms the second message into a JavaScript Object Notation message. The validation engine compares the first message with a server log stored on the server to determine whether information in the first message matches information in the server log and compares the JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log. The messaging engine communicates a message indicating that information in the first message and the second message match information in the server log.

Claims

1. A test tool comprising:

a connection engine configured to connect to a first non-relational database, a second non-relational database, and a server;

a transformation engine configured to;

receive a first message from the first non-relational database;

receive a second message from the second non-relational database; and

transform the second message into a JavaScript Object Notation message;

a validation engine configured to;

compare the first message with a server log stored on the server to determine whether information in the first message matches information in the server log;

compare the JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log; and

a messaging engine configured to communicate a message indicating that information in the first message and the second message match information in the server log.

2. The test tool of claim 1, wherein the first non-relational database is a Cassandra database and the second non-relational database is a Hadoop database.

3. The test tool of claim 1, wherein:

the first message comprises a name of a first column of a table in the first non-relational database, a type of the first column, and a plurality of values stored in the first column; and

the second message comprises a name of a second column of a table in the second non-relational database, a type of the second column, and a plurality of values stored in the second column.

4. The test tool of claim 1, wherein:

the validation engine is further configured to compare the first message with the server log to determine whether the first message contains an error; and

the messaging engine is further configured to communicate a message indicating that the first message contains an error.

5. The test tool of claim 1, wherein the validation engine is further configured to request the second message by sending a Hive query to the second non-relational database.

6. The test tool of claim 1, wherein the messaging engine is further configured communicate a message indicating that information in the first message does not match information in the server log.

7. The test tool of claim 1, wherein the first non-relational database is flushed periodically.

8. A method comprising:

connecting to a first non-relational database, a second non-relational database, and a server;

receiving a first message from the first non-relational database;

receiving a second message from the second non-relational database;

transforming the second message into a JavaScript Object Notation message;

comparing the first message with a server log stored on the server to determine whether information in the first message matches information in the server log;

comparing the JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log; and

communicating a message indicating that information in the first message and the second message match information in the server log.

9. The method of claim 8, wherein the first non-relational database is a Cassandra database and the second non-relational database is a Hadoop database.

10. The method of claim 8, wherein:

the first message comprises a name of a first column of a table in the first non-relational database, a type of the first column, and a plurality of values stored in the first column; and

the second message comprises a name of a second column of a table in the second non-relational database, a type of the second column, and a plurality of values stored in the second column.

11. The method of claim 8, further comprising:

comparing the first message with the server log to determine whether the first message contains an error; and

communicating a message indicating that the first message contains an error.

12. The method of claim 8, further comprising requesting the second message by sending a Hive query to the second non-relational database.

13. The method of claim 8, further comprising communicating a message indicating that information in the first message does not match information in the server log.

14. The method of claim 8, wherein the first non-relational database is flushed periodically.

15. A system comprising:

a transformation engine configured to;

receive a first message from a first non-relational database;

receive a second message from a second non-relational database; and

transform the second message into a JavaScript Object Notation message;

a validation engine configured to;

compare the first message with a server log to determine whether information in the first message matches information in the server log;

compare the second JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log; and

a messaging engine configured to communicate a message indicating that information in the first message and the second message match information in the server log.

16. The system of claim 15, wherein the first non-relational database is a Cassandra database and the second non-relational database is a Hadoop database.

17. The system of claim 15, wherein:

the first message comprises a name of a first column of a table in the first non-relational database, a type of the first column, and a plurality of values stored in the first column; and

the second message comprises a name of a second column of a table in the second non-relational database, a type of the second column, and a plurality of values stored in the second column.

18. The system of claim 15, wherein:

the validation engine is further configured to compare the first message with the server log to determine whether the first message contains an error; and

the messaging engine is further configured to communicate a message indicating that the first message contains an error.

19. The system of claim 15, wherein the validation engine is further configured to request the second message by sending a Hive query to the second non-relational database.

20. The system of claim 15, wherein the messaging engine is further configured communicate a message indicating that information in the first message does not match information in the server log.

21. The system of claim 15, wherein the first non-relational database is flushed periodically.