Security infrastructure for cloud services

• US 9,319,269 B2
• Filed: 02/10/2015
• Issued: 04/19/2016
• Est. Priority Date: 09/07/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Arun, Gopalan, Chatterjee, Ramkrishna, Vasudevan, Ramesh
• Primary Examiner(s): Zee, Edward
• Application Number:
  US14/618,791
• Publication Number:
  US 20150156218A1
• Time in Patent Office: 434 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5064 Customer relationship management
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 47/70 : Admission control; Resource allocation
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A framework for handling a secure interaction between components in a cloud infrastructure system that wish to transfer information between each other during processing of a customer'"'"'s subscription order is described. The framework orders the security zones of components based on security levels and protects the transfer of information between components in security zones with different security levels. The assignment of a component to a security zone is based upon the sensitivity of the data handled by the components, the sensitivity of functions performed by the component, and the like.

Claims

1. A method comprising:

storing, by a system comprising one or more computing devices, security rules information comprising one or more rules that govern a transfer of information between a first component and a second component in the system;

responsive to a request to transfer information from the first component to the second component;

determining, by the system, based upon the security rules information, a first security zone and a first security level associated with the first component and a second security zone and a second security level associated with the second component; and

determining, by the system, based upon the first security zone and the first security level determined for the first component and the second security zone and the second security level determined for the second component, a particular transfer technique from a plurality of transfer techniques that is permitted for transferring the information from the first component to the second component;

determining, based on the particular transfer technique, that the transfer of the information from the first component to the second component is to be performed by pushing the information from the first component to the second component if the second security level associated with the second component is same as or lower than the first security level associated with the first component; and

enabling, by the system, the transfer of the information from the first component to the second component using the particular transfer technique.

2. The method of claim 1, wherein pushing the information from the first component to the second component comprises invoking a synchronous write Application Programming Interface (API) associated with the second component.

3. The method of claim 1, wherein pushing information from the first component to the second component comprises publishing the information to a queue associated with the second component.

4. The method of claim 1, wherein determining the first security zone and the first security level associated with the first component and the second security zone and the second security level associated with the second component further comprises:

mapping the first component to the first security zone and mapping the first security zone to the first security level; and

mapping the second component to the second security zone and mapping the second security zone to the second security level.

5. The method of claim 1, wherein the first security level and the second security level are determined based on the information associated with the first component and the second component.

6. The method of claim 1 further comprising determining that the transfer of information from the first component to the second component is to be performed by pulling the information by the second component from the first component if the second security level associated with the second component is greater than the first security level of the first component.

7. The method of claim 6, wherein pulling the information comprises the first component writing the information to an output queue associated with the second component and the second component pulling the information from the output queue.

8. The method of claim 1 further comprising:

providing, by the system, a service that is subscribed to by a plurality of users of the system; and

generating the request to transfer the information from the first component to the second component based on the providing, wherein the service is provided in accordance with a Software as a Service (SaaS) model.

9. A system comprising:

one or more computing devices configured to provide one or more services;

a memory configurable to store security rules information comprising one or more rules that govern a transfer of information between a first component and a second component in the system, the first component and the second component executed by the one or more computing devices; and

wherein a computing device from the one or more computing devices is configurable to;

receive a request to transfer information from the first component to the second component;

determine a first security zone and a first security level associated with the first component and a second security zone and a second security level associated with the second component based on the security rules information;

determine, based upon the first security zone and the first security level determined for the first component and the second security zone and the second security level determined for the second component, a particular transfer technique from a plurality of transfer techniques that is permitted for transferring information from the first component to the second component;

determine, based on the particular transfer technique, that the transfer of information from the first component to the second component is to be performed by pulling the information b the second component from the first component if the second security level associated with the second component is greater than the first security level of the first component; and

enable the transfer of the information from the first component to the second component using the particular transfer technique.

10. The system of claim 9, wherein the computing device is further configured to determine that the transfer of the information from the first component to the second component is to be performed by pushing the information from the first component to the second component if the second security level associated with the second component is same as or lower than the first security level associated with the first component.

11. The system of claim 10, wherein the computing device is configured to push information from the first component to the second component by publishing information to a queue associated with the second component.

12. The system of claim 9, wherein pulling the information comprises the first component writing the information to an output queue associated with the second component and the second component pulling the information from the output queue.

13. The system of claim 9, wherein the computing device is further configured to:

map the first component to the first security zone and map the first security zone to the first security level; and

map the second component to the second security zone and map the second security zone to the second security level.

14. A non-transitory computer-readable memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising:

instructions that cause at least one processor from the one or more processors to store security rules information comprising one or more rules that govern a transfer of information between a first component and a second component in a system, the system comprising one or more computing devices;

responsive to a request to transfer information from the first component to the second component;

instructions that cause at least one processor from the one or more processors to determine, based on the security rules information, a first security zone and a first security level associated with the first component and a second security zone and a second security level associated with the second component; and

instructions that cause at least one processor from the one or more processors to determine, based upon the first security zone and the first security level determined for the first component and the second security zone and the second security level determined for the second component, a particular transfer technique from a plurality of transfer techniques that is permitted for transferring information from the first component to the second component;

instructions that cause at least one processor from the one or more processors to determine, based on the particular transfer technique, that the transfer of the information from the first component to the second component is to be performed by pushing the information from the first component to the second component if the second security level associated with the second component is same as or lower than the first security level associated with the first component; and

instructions that cause at least one processor from the one or more processors to enable the transfer of the information from the first component to the second component using the particular transfer technique.

15. The computer-readable memory of claim 14, wherein the plurality of instructions further comprises instructions that cause at least one processor from the one or more processors to push the information by invoking a synchronous write API associated with the second component.

16. The computer-readable memory of claim 14, wherein the plurality of instructions further comprises instructions that cause at least one processor from the one or more processors to determine that the transfer of the information from the first component to the second component is to be performed by pulling the information by the second component from the first component if the second security level associated with the second component is greater than the first security level of the first component.

17. The computer-readable memory of claim 14, wherein the plurality of instructions further comprises instructions that cause at least one processor from the one or more processors to determine the first security level and the second security level based on the information associated with the first component and the second component.