INSIDER ATTACK RESISTANT SYSTEM AND METHOD FOR CLOUD SERVICES INTEGRITY CHECKING

• US 20190007431A1
• Filed: 08/13/2018
• Published: 01/03/2019
• Est. Priority Date: 08/13/2015
• Status: Active Grant

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Jayawardena, Thusitha, Bickford, Jeffrey E., Istomin, Mikhail, Liefert, John, Singaraju, Gokul, Van Wart, Christopher
• Granted Patent: US 10,454,956 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms

Abstract

An insider attack resistant system for providing cloud services integrity checking is disclosed. In particular, the system utilizes an automated integrity checking script and virtual machines to check the integrity of a service. The system may utilize the integrity checking script and virtual machines to execute a set of operations associated with the service so as to check the integrity of the service. When executing the set of operations, the system may only have access to the minimum level of access to peripherals that is required for each operation in the set of operations to be executed. After each operation is executed, the system may log each result for each operation, and analyze each result to determine if a failure exists for any of the operations. If a failure exists, the system may determine that a change in an expected system behavior associated with the service has occurred.

Claims

1. A system, comprising:

a memory that stores instructions; and

a processor that executes the instructions to perform operations, the operations comprising;

executing, during a first mode, a set of operations associated with a service to check an integrity of the service, wherein the set of operations are executed based on a minimum level of access to a peripheral that is required for at least one operation in the set of operations to be executed, wherein the minimum level of access is established by suspending access to a network port;

executing, when the system is in a second mode, the set of operations associated with the service based on a full level of access to the peripheral; and

determining whether a failure of the at least one operation in the set of operations has occurred.

2. The system of claim 1, wherein the operations further comprise determining, if the failure of the at least one operation in the set of operations has occurred, that a change in a system behavior associated with the service has occurred.

3. The system of claim 2, wherein the operations further comprise generating an alert after determining that the change in the system behavior associated with the service has occurred.

4. The system of claim 1, wherein the operations further comprise performing an action to correct the failure.

5. The system of claim 1, wherein the operations further comprise modifying the service after determining that the failure has occurred.

6. The system of claim 1, wherein the operations further comprise executing an anti-virus program to remove malware associated with the failure.

7. The system of claim 1, wherein the operations further comprise identifying an attacker associated with malware associated with the failure.

8. The system of claim 1, wherein the operations further comprise identifying a cause of the failure.

9. The system of claim 1, wherein the operations further comprise identifying a cause of a change in a system behavior associated with the service.

10. The system of claim 1, wherein the operations further comprise logging a result generated based on the executing of the set of operations.

11. The system of claim 10, wherein the determining of whether the failure of the at least one operation in the set of operations has occurred is based on analyzing the result.

12. The system of claim 1, wherein the operations further comprise imposing the minimum level of access by utilizing a hypervisor layer firewall.

13. The system of claim 1, wherein the operations further comprise imposing the minimum level of access by utilizing a software-defined networking script.

14. A method, comprising:

executing, during a first mode, a set of operations associated with a service to check an integrity of the service, wherein the set of operations are executed based on a minimum level of access to a peripheral that is required for at least one operation in the set of operations to be executed, wherein the minimum level of access is established by suspending access to a network port;

executing, when the system is in a second mode, the set of operations associated with the service based on a full level of access to the peripheral; and

determining, based on the executing of the set of operations, that a change in a system behavior associated with the service has occurred, wherein the determining is performed by utilizing instructions from a memory that are executed by a processor.

15. The method of claim 14, further comprising launching an integrity checking script to execute the set of operations associated with the service.

16. The method of claim 14, further comprising activating a virtual machine to check the integrity of the service.

17. The method of claim 14, further comprising determining if an operation in the set of operations has failed.

18. The method of claim 14, further comprising generating an alert in response to determining that the change in the system behavior associated with the service has occurred.

19. The method of claim 14, further comprising identifying a cause of the change in the system behavior associated with the service.

20. A computer-readable device comprising instructions, which when executed by a processor, cause the processor to perform operations comprising:

executing, during a first mode, a set of operations associated with a service to check an integrity of the service, wherein the set of operations are executed based on a minimum level of access to a peripheral that is required for at least one operation in the set of operations to be executed, wherein the minimum level of access is established by suspending access to a network port;

executing, when the system is in a second mode, the set of operations associated with the service based on a full level of access to the peripheral; and

logging each result for each operation in the set of operations.