EXTENDING PRIVATE CLOUD SECURITY MODEL TO PUBLIC CLOUD

Abstract

Methods and systems disclosed herein extend an entity's private cloud security model to the entity's public cloud. Public cloud access permissions are defined, in accordance with a security model implemented in the entity's private cloud, for one or more of the entity's public cloud resources. The public cloud permissions are pushed or otherwise provided to an access module within the private cloud. Upon receiving a request to access a public cloud resource, the private cloud access module is invoked to grant or deny the access request in accordance with the public cloud access permissions. Similarly, upon receiving a request to access a private cloud resource, the private cloud access module is invoked to process the access request in accordance with private cloud access permissions, thereby beneficially enabling users to interact with a single access interface regardless of whether the resource reside within the entity's cloud platform.

Claims

1. A method for managing access security in a cloud environment, wherein the method comprises: defining public cloud access permissions for one or more public cloud resources associated with an entity, wherein the public cloud access permissions are in accordance with a security model implemented in a private cloud of the entity; providing the public cloud permissions to a private cloud access module; responsive to an access request to access a public cloud resource, invoking the private cloud access module to process the access request in accordance with the public cloud access permissions; and responsive to an access request to access a private cloud resource, invoking the private cloud access module to process the access request in accordance with private cloud access permissions.

2. The method of claim 1, wherein providing the public cloud permissions comprises pushing the public cloud access permissions from the public cloud to the private cloud access module.

3. The method of claim 1, further comprising: managing the private cloud access permissions and the public cloud access permissions from within the private cloud.

4. The method of claim 3, further comprising: responsive to completing an instance of managing a public cloud access permission from within the private cloud, forwarding the public cloud access permission to the private cloud via a secure channel between the private cloud and public cloud.

5. The method of claim 1, wherein the private cloud security model comprises a role-based access model wherein an access permission is associated with a resource, indicates one or more authorized users to which the permission pertains, and identifies a role, comprising one or more access privileges, accorded to the one or more authorized users with respect to the resource.

6. An information handling system, comprising: a central processing unit (CPU); and a computer readable memory, accessible to the CPU, including process executable program instructions that, when executed by the CPU, cause the CPU to perform operations for managing access security in a cloud environment, wherein the operations include: defining public cloud access permissions for one or more public cloud resources associated with an entity, wherein the public cloud access permissions are in accordance with a security model implemented in a private cloud of the entity; providing the public cloud permissions to a private cloud access module; responsive to an access request to access a public cloud resource, invoking the private cloud access module to process the access request in accordance with the public cloud access permissions; and responsive to an access request to access a private cloud resource, invoking the private cloud access module to process the access request in accordance with private cloud access permissions.

7. The information handling system of claim 6, wherein providing the public cloud permissions comprises pushing the public cloud access permissions from the public cloud to the private cloud access module.

8. The information handling system of claim 6, wherein the operations further include: managing the private cloud access permissions and the public cloud access permissions from within the private cloud.

9. The information handling system of claim 8, wherein the operations further include: responsive to completing an instance of managing a public cloud access permission from within the private cloud, forwarding the public cloud access permission to the private cloud via a secure channel between the private cloud and public cloud.

10. The information handling system of claim 6, wherein the private cloud security model comprises a role-based access model wherein an access permission is associated with a resource, indicates one or more authorized users to which the permission pertains, and identifies a role, comprising one or more access privileges, accorded to the one or more authorized users with respect to the resource.

11. A non-transitory computer readable memory including process executable program instructions that, when executed by a processor of an information handing system, cause the system to perform operations for managing access security in a cloud environment, wherein the operations include: defining public cloud access permissions for one or more public cloud resources associated with an entity, wherein the public cloud access permissions are in accordance with a security model implemented in a private cloud of the entity; providing the public cloud permissions to a private cloud access module; responsive to an access request to access a public cloud resource, invoking the private cloud access module to process the access request in accordance with the public cloud access permissions; and responsive to an access request to access a private cloud resource, invoking the private cloud access module to process the access request in accordance with private cloud access permissions.

12. The non-transitory computer readable medium of claim 11, wherein providing the public cloud permissions comprises pushing the public cloud access permissions from the public cloud to the private cloud access module.

13. The non-transitory computer readable medium of claim 11, wherein the operations further include: managing the private cloud access permissions and the public cloud access permissions from within the private cloud.

14. The non-transitory computer readable medium of claim 13, wherein the operations further include: responsive to completing an instance of managing a public cloud access permission from within the private cloud, forwarding the public cloud access permission to the private cloud via a secure channel between the private cloud and public cloud.

15. The non-transitory computer readable medium of claim 11, wherein the private cloud security model comprises a role-based access model wherein an access permission is associated with a resource, indicates one or more authorized users to which the permission pertains, and identifies a role, comprising one or more access privileges, accorded to the one or more authorized users with respect to the resource.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

[0012] FIG. 1 illustrates a cloud platform, including a private cloud and a public cloud, in accordance with disclosed teachings of a uniform access feature;

[0013] FIG. 2 illustrates a flow diagram of a disclosed method for extending a private cloud security model to public cloud assets; and

[0014] FIG. 3 illustrates an information handling system suitable for use in conjunction with method and systems disclosed in FIG. 1 and FIG. 2.

DETAILED DESCRIPTION

[0015] Exemplary embodiments and their advantages are best understood by reference to FIGS. 1-3, wherein like numbers are used to indicate like and corresponding parts unless expressly indicated otherwise.

[0016] For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (“CPU”), microcontroller, or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input/output (“I/O”) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

[0017] Additionally, an information handling system may include firmware for controlling and/or communicating with, for example, hard drives, network circuitry, memory devices, I/O devices, and other peripheral devices. For example, the hypervisor and/or other components may comprise firmware. As used in this disclosure, firmware includes software embedded in an information handling system component used to perform predefined tasks. Firmware is commonly stored in non-volatile memory, or memory that does not lose stored data upon the loss of power. In certain embodiments, firmware associated with an information handling system component is stored in non-volatile memory that is accessible to one or more information handling system components. In the same or alternative embodiments, firmware associated with an information handling system component is stored in non-volatile memory that is dedicated to and comprises part of that component.

[0018] For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

[0019] For the purposes of this disclosure, information handling resources may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems (BIOSs), buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, and/or any other components and/or elements of an information handling system.

[0020] In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments.

[0021] Throughout this disclosure, a hyphenated form of a reference numeral refers to a specific instance of an element and the un-hyphenated form of the reference numeral refers to the element generically. Thus, for example, “device 12-1” refers to an instance of a device class, which may be referred to collectively as “devices 12” and any one of which may be referred to generically as “a device 12”.

[0022] As used herein, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication, mechanical communication, including thermal and fluidic communication, thermal, communication or mechanical communication, as applicable, whether connected indirectly or directly, with or without intervening elements.

[0023] Referring now to the drawings, FIG. 1 an exemplary hybrid cloud 100 in accordance with disclosed teachings for security model and access control management is illustrated.

[0024] A customer's existing private network or on-premises security model is leveraged and adopted in the customer's public cloud application. In some embodiments, a plugin for the on-premises network management resource augments the on-premises security model to support additional access permissions for use by the public cloud application. This adaptation beneficially enables the customer to perform all platform management for public as well as private cloud resources with a private network management resource portal serving as the user's single cloud management source and window. A collection agent may be configured to collect on-premises security permissions and synchronize the permissions up to the public could application using a secure channel. With such features, the customer simply needs to set required security permissions in the private network management resource, thereby rendering the customer's platform somewhat less hybrid in an area where uniformity is generally desirable and more efficient.

[0025] FIG. 1 illustrates hybrid cloud platform 100 including on-premises resources 102, alternatively referred to herein as private network resources, and public cloud resources 104, alternatively referred to herein as off-premises resources. The on-premises resources 102 illustrated in FIG. 1 include one or more hyper-converged infrastructure (HCI) clusters 110, including a first HCI cluster 110-1 and a second HCI cluster 110-2 illustrated in FIG. 1. Each HCI cluster 110 illustrated in FIG. 1 is a multi-node cluster that includes two or more nodes 114, each of which supports tightly integrated and easily managed virtualized and/or containerized compute, storage, and networking resources. A commercially distributed example of an HCI device suitable to support the clusters 110 of FIG. 1 is any of the VxRail family of HCI appliances from Dell Technologies.

[0026] Each HCI cluster 110 illustrated in FIG. 1 includes a corresponding collection agent 112. The illustrated collection agent 112 may be configured to collect security permission information 120 from a private network management resource, such as a VMware vCenter Server from Dell Technologies, and synchronize the security data, including access permissions, to the customer's public cloud Application database 140 via a secure channel 130.

[0027] FIG. 1 further illustrates a role based access control (RBAC) service 150 configured to extend the private network security model to public cloud 104. FIG. 1 depicts a user 103 within private network 102 accessing a cloud-based resource 114, e.g., a web page. The RBAC service 150 is configured to detect the access request from user 103, retrieve access permissions from public cloud application database 140, and grant or deny the access request in accordance with the on-premises access control model.

[0028] In at least one embodiment, the public cloud resources 104 may extend new security permissions including permissions for public cloud resources and usage. The customer manages the security permission centrally in the private network management resource (not explicitly depicted in FIG. 1. After permissions are set in the private network management resource the cloud platform receives permission changes that apply to both public cloud 104 and private on-premises resources 102.

[0029] Referring now to FIG. 2, a method for extending private cloud security models and/or access permissions to public cloud resources is illustrated in flow diagram format. The method 200 illustrated in FIG. 2 defines (block 202) public cloud access permissions for one or more public cloud resources associated with a customer, wherein the public cloud access permissions are formatted and are otherwise structured in compliance with a security model implemented in the customer's private cloud. The public cloud access permissions are provided (block 204) to an access module associated with a private cloud management resource such as the customer's vCenter Server software. Whenever a request to access a public cloud resource is received via a portal of the private cloud management resource, the access module is invoked (block 206) to process the access request in accordance with the public cloud access permissions. Similarly, whenever a request to access a private cloud resource is received via a portal of the private cloud management resource, the access module is invoked (block 210) to process the access request in accordance with the public cloud access permissions. Responsive to the private cloud management resource receiving a request to access a private cloud resource, invoking (block 210). In this manner, the illustrated method 200 extends the customer's well developed private cloud security model and access permissions to at least some of the customer's public cloud resources, thereby facilitating a more uniform perception of the customer's hybrid cloud platform.

[0030] Referring now to FIG. 3, any one or more of the elements illustrated in FIG. 1 through FIG. 2 may be implemented as or within an information handling system exemplified by the information handling system 300 illustrated in FIG. 3. The illustrated information handling system includes one or more general purpose processors or central processing units (CPUs) 301 communicatively coupled to a memory resource 310 and to an input/output hub 320 to which various I/O resources and/or components are communicatively coupled. The I/O resources explicitly depicted in FIG. 3 include a network interface 340, commonly referred to as a NIC (network interface card), storage resources 330, and additional I/O devices, components, or resources 350 including as non-limiting examples, keyboards, mice, displays, printers, speakers, microphones, etc. The illustrated information handling system 300 includes a baseboard management controller (BMC) 360 providing, among other features and services, an out-of-band management resource which may be coupled to a management server (not depicted). In at least some embodiments, BMC 360 may manage information handling system 300 even when information handling system 300 is powered off or powered to a standby state. BMC 360 may include a processor, memory, an out-of-band network interface separate from and physically isolated from an in-band network interface of information handling system 300, and/or other embedded information handling resources. In certain embodiments, BMC 360 may include or may be an integral part of a remote access controller (e.g., a Dell Remote Access Controller or Integrated Dell Remote Access Controller) or a chassis management controller.

[0031] This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.

[0032] All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the disclosure and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.