Authorization proxy
By generating and maintaining credentials in the computing system and performing actions on behalf of the client device, the credential security problem in cloud service providers is solved, and the prevention of unauthorized actions and the management of credential security is realized.
Patent Information
- Application Number
- CN202280087815.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-01-07
- Filing Date
- 2022-11-16
- Publication Date
- 2024-11-01
AI Technical Summary
In the prior art, the credentials provided by cloud service providers to clients are easily exploited by bad actors, resulting in unauthorized actions, and it is difficult to ensure security when the credentials exist on the client device.
By receiving the request from the client device in the computing system, determining its corresponding subscriber and generating credentials, maintaining the credentials separate from the client device, and using the credentials on behalf of the client device to perform actions and ensure that the credentials are stored in a trusted environment and use.
Effectively reduces the chances of unauthorized participants to obtain and utilize credentials, improves the access rights management of security entities, and prevents unauthorized actions from being executed.
Smart Images

Figure CN118891850A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Non-Provisional Application No. 17 / 571,338, filed on January 7, 2022, entitled “Authorization Brokering,” the disclosure of which is incorporated herein by reference in its entirety for all purposes. Technical Field
[0003] The present disclosure relates to a framework for managing credentials for secure entities used to access infrastructure services. Background Art
[0004] Cloud Service Providers (CSPs) use different systems and infrastructure services to provide various services to users or clients on demand. CSPs provide infrastructure services that can be used by clients to build their own networks and deploy customer resources. In order for a client to be provided access to a CSP, the client may need to provide credentials to the CSP that grants the client access.
[0005] The traditional method of credentials for accessing a CSP involves the CSP providing credentials to the client, which in turn will provide the credentials to the CSP when requesting services to gain access to the CSP. The credentials provided to the client may be used by bad actors to perform unauthorized actions against the CSP. Therefore, the credentials shared with the client may be a weakness within the CSP. Summary of the invention
[0006] The present disclosure generally relates to a framework for managing credentials for accessing computing systems, such as cloud infrastructure services. Various embodiments are described herein, including methods, systems, non-transitory computer-readable storage media storing programs, codes, or instructions executable by one or more processors, and the like. These illustrative embodiments are mentioned not to limit or define the present disclosure, but to provide examples to aid in understanding the present disclosure. Additional embodiments are discussed in the detailed description section, and further description is provided therein.
[0007] Aspects of the present disclosure relate to one or more non-transitory computer-readable storage media having instructions stored thereon, wherein when the instructions are executed by a computing system, the computing system may receive a request to perform an action from a client device, the request including an identifier of the client device and an action to be performed by a security entity. The instructions may also cause the computing system to determine a subscriber corresponding to the client device based at least in part on the identifier of the client device, and to determine that the subscriber has provided authorization to the client device to perform the action. In addition, the instructions may cause the computing system to generate a credential for accessing a security entity on behalf of the client device based at least in part on determining that the client device has authorization to perform the action, maintain the credential separately from the client device, and use the credential to perform the action on behalf of the client device.
[0008] Aspects of the present disclosure relate to a computing system including a memory for storing one or more credentials and one or more processors coupled to the memory, the one or more processors being able to receive a request for an action to be performed by a security entity, the request being received from a client device. The one or more processors are also configured to determine a subscriber corresponding to the client device based at least in part on an identifier of the client device, and to determine that the subscriber has provided authorization to perform the action to the client device. The one or more processors are also configured to generate a credential for accessing the security entity based at least in part on determining that the subscriber has provided authorization to perform the action to the client device, store the credential in a memory (the credential being stored separately from the client device), and use the credential to perform the action on behalf of the client device.
[0009] Aspects of the present disclosure relate to a method for performing an action using a security entity, including receiving, by a broker, a request from a client device to perform an action by the security entity, and determining, by the broker, that the client device is authorized to perform the action. The method may also include generating, by the broker, a credential for accessing the security entity based at least in part on determining that the client device is authorized to perform the action, and using, by the broker on behalf of the client device, the credential to cause the security entity to perform the action.
[0010] The foregoing and other features and embodiments will become more fully apparent by reference to the following description, claims and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The features, embodiments, and advantages of the present disclosure may be better understood when the following detailed description is read with reference to the accompanying drawings.
[0012] Figure 1 An example infrastructure services arrangement is illustrated in accordance with some embodiments.
[0013] Figure 2 An example access arrangement is illustrated in accordance with some embodiments.
[0014] Figure 3 An example process flow for client device registration according to some embodiments is illustrated.
[0015] Figure 4 An example process flow of action performance according to some embodiments is illustrated.
[0016] Figure 5 An example process flow for key refresh according to some embodiments is illustrated.
[0017] Figure 6 An example process of performance of actions according to some embodiments is illustrated.
[0018] Figure 7 Another example process of performance of actions according to some embodiments is illustrated.
[0019] Figure 8 Another example process of performance of actions according to some embodiments is illustrated.
[0020] Fig. 9 is a block diagram illustrating one mode for implementing a cloud infrastructure as a service system according to at least one embodiment.
[0021] Fig.10 is a block diagram illustrating another mode for implementing a cloud infrastructure as a service system according to at least one embodiment.
[0022] Fig.11 is a block diagram illustrating another mode for implementing a cloud infrastructure as a service system according to at least one embodiment.
[0023] Fig.12 is a block diagram illustrating another mode for implementing a cloud infrastructure as a service system according to at least one embodiment.
[0024] Fig.13 is a block diagram illustrating an example computer system in accordance with at least one embodiment. DETAILED DESCRIPTION
[0025] In the following description, for the purpose of explanation, specific details are set forth in order to provide a thorough understanding of certain embodiments. However, it will be clear that various embodiments can be practiced without these specific details. The drawings and descriptions are not intended to be limiting. The word "exemplary" as used herein means "serving as an example, instance, or illustration." Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
[0026] The present disclosure describes a method for managing a method for accessing infrastructure services provided by a cloud service provider (CSP), such as a cloud infrastructure service, e.g. Fig. 9 Cloud infrastructure, Fig.10 Cloud infrastructure, Fig.11 Cloud infrastructure and / or Fig.12 The invention relates to a technology for obtaining credentials for a security entity within an infrastructure service (a cloud infrastructure) and / or utilizing an infrastructure service to perform an action. More specifically, in order to be granted access to a security entity within an infrastructure service, the security entity may check the credentials to determine whether the participant is authorized to utilize the security entity to perform an action. The infrastructure service, or a portion thereof, may coordinate with the security entity and the client device to generate credentials for the client device. The infrastructure service, or a portion thereof, may maintain the credentials instead of providing the credentials to the client device. The infrastructure service, or a portion thereof, may utilize the credentials on behalf of the client device to perform an action requested by the client device, while the client device does not have access to the credentials. Therefore, the credentials may be maintained in a trusted environment and not provided to an untrusted environment (such as a client device). By maintaining the credentials in a trusted environment, the chances of unauthorized participants obtaining and / or utilizing the credentials to access the security entity are reduced.
[0027] CSPs can provide various services to clients on demand using different systems and infrastructure services (referred to herein as cloud infrastructure services). In some embodiments, CSPs can provide services under an Infrastructure as a Service (IaaS) model, in which CSPs provide infrastructure services that can be used by clients to build their own networks and deploy customer resources. The infrastructure provided by CSPs may include interconnected high-performance computer resources that form a physical network called a base network or underlying network, including various host machines (also referred to as hosts), storage resources, and network resources. The infrastructure provided by CSPs may be distributed across one or more data centers, which may be geographically distributed across one or more regions.
[0028] The physical network of the CSP (which may include various hosts, storage resources, and / or network resources) can provide the basis for creating one or more virtual or overlay networks on top of the physical network. These virtual or overlay networks (also referred to as software-based or software-defined networks) can be implemented using software virtualization technology to create a network abstraction layer that can run on top of the physical network. Overlay networks can take many forms. Overlay networks can use layer 3 IP addressing, where endpoints are specified by their virtual IP addresses. This approach to overlay networking is often referred to as virtual layer 3 networking.
[0029] When a client subscribes to or registers for an IaaS service provided by a CSP, a tenancy may be created for the client, where a tenancy is a secure and isolated partition within the CSP infrastructure service in which the client can create, organize, and manage the client's cloud resources. For example, the client may use the resources provided by the CSP to build one or more customizable and private virtual networks (one or more) (referred to as virtual cloud networks (VCNs)) within the client's tenancy. One or more client resources, such as compute instances (e.g., virtual machines, bare metal instances, etc.), may be deployed on these client VCNs.
[0030] When a client attempts to access an infrastructure service to establish a lease or perform other actions, the client may send a request to the infrastructure service to establish the lease or perform the other action. The infrastructure service may receive the request and determine that the client is requesting the infrastructure service to utilize a security entity within the infrastructure service to perform an action. Based on the action, the infrastructure service may generate a credential associated with the client that provides access to the security entity. The infrastructure service may utilize the credential on behalf of the client to perform the requested action without providing the credential to the client. Thus, the credential may be maintained in the infrastructure service, thereby providing protection for the credential.
[0031] Figure 1 An example infrastructure service arrangement 100 is illustrated according to some embodiments. Specifically, the infrastructure service arrangement 100 illustrates a portion of an infrastructure service that can implement one or more methods for maintaining credentials described throughout this disclosure. In some embodiments, the infrastructure service may include Fig. 9 Cloud infrastructure, Fig.10 Cloud infrastructure, Fig.11 Cloud infrastructure and / or Fig.12 The infrastructure service may include one or more features of a cloud infrastructure. The infrastructure service may include a computing system. In some embodiments, the infrastructure service may include a cloud computing system. The infrastructure service may include hardware and / or software of an infrastructure that can provide services to a client.
[0032] The infrastructure service may include one or more devices 102 that are communicatively coupled to provide a portion of the infrastructure service. For example, in the illustrated embodiment, the infrastructure service arrangement 100 includes a first device 102a, a second device 102b, and a third device 102c. The devices 102 may include computing devices, such as computer terminals, servers, other computer devices, or some combination thereof. The devices 102 may communicate with each other to form a portion of an infrastructure service, wherein the infrastructure service may provide an infrastructure service such as a cloud infrastructure service.
[0033] Devices 102 may be grouped into different enclaves. For example, a first device 102a, a second device 102b, and a third device 102c may form part of an enclave 104 of infrastructure services. Each of the enclaves of infrastructure services may form its own security entity, or may be part of a security entity that includes multiple enclaves. Enclave 104 may perform specific operations. For example, enclave 104 may include a management enclave that provides management operations, a service enclave that provides service operations, or a client enclave that provides client operations to clients. Enclave 104 may implement a software defined perimeter (SDP) security model to create a protected IaaS instance. Enclave 104 may have a defined SDP that includes one or more devices (such as first device 102a, second device 102b, and third device 102c) and / or certain software, wherein the edge of enclave 104 is defined by the separation of these devices and / or software from elements outside of enclave 104. Enclave 104 may have a unique communication profile that may be different from other communication profiles of different enclaves in infrastructure services. The access rights to and from the enclave 104 may be controlled, monitored, and / or policy-driven. For example, the access rights to the enclave 104 may be based on authorization, where the access rights to the enclave 104 may be limited to authorized clients. The enclave 104 may determine the authorization of the access rights to the enclave 104 based on one or more credentials provided to the enclave 104.
[0034] The infrastructure services may include one or more security agents, such as agent 106. Agent 106 may include a device, software, or some combination thereof. Agent 106 may be located at the edge of enclave 104. For example, agent 106 may be located at the edge of enclave 104 to allow communication with agent 106 without accessing secure portions of enclave 104.
[0035] The proxy 106 may receive a registration request from a client. The registration request may include an identifier of the client, which the proxy 106 may use to determine that future requests received are from the client. In some embodiments, the identifier may include a key (such as a public key) corresponding to the client. The proxy 106 may store the identifier received from the client for future identification of the client.
[0036] In some cases, the registration request may also include an indication of the following subscriber for which the client is requesting an association. For example, a subscriber to the infrastructure service may have previously established a lease within the infrastructure service. The client may indicate that they want to be associated with the subscriber and to operate with the lease generated by the subscriber. The proxy 106 may perform an authentication and / or authorization process to verify that the client is authorized to associate with the subscriber and to operate with the lease generated by the subscriber. If the proxy 106 determines that the client is authorized to associate with the subscriber, the proxy 106 may allow the client to operate with the lease associated with the subscriber. In some other cases, the proxy 106 may operate with another part of the infrastructure service to generate a lease for the client based on the registration request. In the case where the proxy 106 generates a lease for the client based on the registration request, the client may act as a subscriber of the infrastructure service.
[0037] After the registration of the client, or in addition to the registration of the client, the client can send a request to perform an action on the infrastructure service. The proxy 106 can receive the request and determine that the client is requesting an action based on the identifier of the client included in the request. The proxy 106 can determine whether the client is authorized to perform the action by the infrastructure service. For example, the proxy 106 or another part of the infrastructure service can maintain a set of one or more actions or action types that the subscriber is authorized to perform using the infrastructure service or a set of one or more actions or action types that the subscriber has authorized the client to perform using the infrastructure service. The proxy 106 can compare the requested action with the authorized action or action type of the client to determine whether the requested action corresponds to the authorized action or action type. If the proxy 106 determines that the requested action does not correspond to the authorized action or action type, the proxy 106 can prevent the execution of the action for the client. If the proxy 106 determines that the requested action does correspond to the authorized action or action type, the proxy 106 can continue towards the execution of the operation.
[0038] Based on the action, the agent 106 may determine which service of the infrastructure services to utilize to perform the requested action for the client. For example, the agent 106 may determine that the action will be performed by a service within the enclave 104. The agent 106 may coordinate with the enclave 104 to generate a credential for accessing the enclave 104. In some embodiments, the credential may be a token, a key, or some combination thereof. In addition, in some embodiments, the credential may be signed by the enclave 104. The credential may be presented to the enclave 104 for the enclave 104 to determine whether to provide access rights to the requester. In some embodiments, the agent 106 may send a request to generate a credential to the enclave 104. In some embodiments, the request to generate a credential may include an identifier of the client. The enclave 104 may respond to the request with a key (which may be referred to herein as a "proof key"), which will be used by the agent 106 for the generation of the credential. The agent 106 may utilize the proof key to generate a credential for accessing the enclave 104. For example, in some embodiments, the agent 106 may generate a credential based on the proof key and the identifier of the client. In some cases, agent 106 may have previously received an attestation key from enclave 104, and agent 106 may utilize the previously received attestation key to generate the credential rather than requesting the attestation key upon request.
[0039] Once generated, the proxy 106 may store the credentials. For example, the proxy 106 may store the credentials in association with the client, such as by the proxy 106 storing the credentials in association with the client identifier. Compared to conventional approaches, the proxy 106 may maintain the credentials separately from the client. Specifically, the proxy 106 may not provide the credentials to the client. Therefore, the credentials may remain stored by the proxy 106 rather than being provided to the client for storage. The proxy 106 and the enclave 104 may be part of a trusted environment in which the operator of the infrastructure service may manage the security of the trusted environment and have a higher trust in the security of the data managed in the trusted environment. The client may be separate from the trusted environment, wherein the client may be managed by a party separate from the operator of the infrastructure service, and the operator of the infrastructure service may not manage the security of the client. Because the client is separate from the trusted environment, it is more likely that bad actors (which may include the client) may use the credentials provided to the client and / or derive a proof token from the credentials provided to the client to perform unauthorized actions using the infrastructure service than if the credentials were maintained within the trusted environment.
[0040] In some embodiments, the proxy 106 may store the credentials in association with actions or action types for which the client has authorization. For example, the proxy 106 may identify actions or action types for which the client has authorization, such as actions or action types for which the corresponding subscriber has provided authorization to the client. The proxy 106 may store the credentials together with an indication of the actions or action types for which the client has authorization. The proxy 106 may then restrict the use of the credentials to actions or action types for which the client has authorization. Restricting the use of the credentials to actions or action types for which the client has authorization may contrast with conventional methods of providing credentials to clients. Specifically, the credentials provided to the client in conventional methods may provide the client with access rights to the enclave 104 without restricting the actions that the client may perform using the enclave 104. By restricting the use of the credentials by the proxy 106 to actions or action types, the proxy 106 may prevent the client from using the credentials to perform unauthorized actions using the enclave 104, whereas conventional methods of providing credentials to the client would not prevent the client from using the credentials to perform unauthorized actions using the enclave 104.
[0041] The proxy 106 may then utilize the credentials to perform the action requested by the client. Specifically, the proxy 106 may utilize the enclave 104 to perform the action on behalf of the client, rather than the client utilizing the enclave 104 to perform the action. For example, the proxy 106 provides the enclave 104 with a request for the action requested by the client, along with the credentials providing access rights to the enclave 104. The service within the enclave 104 may perform the action and respond to the proxy 106 with the result of the action. The proxy 106 may forward the result of the action to the client after the action has been performed. Having the proxy 106 perform the action on behalf of the client, rather than having the client perform the action using the enclave 104, may prevent the client from performing unauthorized actions. For example, when the client is able to use the enclave 104 to perform the action, the client may receive authorization for the performance of one action and then request the enclave 104 to perform a different action. The proxy 106 may maintain the same requested action for both the authorization of the action and the performance of the action, thereby preventing the action from being changed between authorization and performance.
[0042] In some embodiments, after the action has been completed and / or the client has ended the session with the proxy 106, the proxy 106 can delete the credentials from the storage. For example, the proxy 106 can determine that the action has been completed and / or the client has ended the session. The session between the proxy 106 and the client can end based on the client signing out with the proxy 106, the termination of the connection between the proxy 106 and the client, or some combination thereof. Based on determining that the action has been completed and / or the client has ended the session, the proxy 106 can delete the credentials. Therefore, in some embodiments, the credentials can be short-lived. If a bad actor does manage to gain access to the proxy after the action has been completed and / or the client has ended the session, the proxy 106 will no longer have the credentials and the bad actor will not be able to steal the credentials that provide access to the enclave 104.
[0043] Although infrastructure service arrangement 100 illustrates an embodiment of a portion of an infrastructure service, it should be understood that other embodiments of infrastructure services having features of infrastructure service arrangement 100 are also covered by the present disclosure. For example, an enclave (such as enclave 104) can be formed by one or more devices, and / or one or more devices can be included in multiple enclaves. In addition, an infrastructure service can include multiple enclaves instead of the single enclave shown. Each enclave can also include multiple security elements, where each of the security elements can be accessed by any client, each of the security elements can be dedicated to a corresponding client so that the corresponding client can access the corresponding security element, or some combination thereof.
[0044] Furthermore, while in the illustrated embodiment the enclaves of the infrastructure services arrangement 100 are described as security entities, it should be understood that in other embodiments the security entities may be different parts of the infrastructure services arrangement 100. For example, the security entity of the infrastructure services arrangement 100 may be any part of the infrastructure services arrangement 100 that requires credentials for access permissions. Additionally, while in the illustrated embodiment the proxy 106 is shown as a separate element, it should be understood that in other embodiments the proxy 106 may be included in or combined with one or more elements, such as with a security element.
[0045] Figure 2 An example access arrangement 200 according to some embodiments is illustrated. For example, the access arrangement 200 shows an example layout of a device for illustrating a method of an authorization agent according to some embodiments. It should be understood that the access arrangement 200 is a single embodiment for illustrating the method, and the implementation of the method is not limited to the example layout shown.
[0046] Access device 200 may include enclave 202. Enclave 202 may include enclave 104 ( Figure 1) One or more features of the enclave 202. The enclave 202 may include infrastructure services or portions thereof, such as Figure 1 Related Description Infrastructure Services. In some embodiments, the infrastructure services may include computing systems, such as cloud computing systems.
[0047] The access arrangement 200 may also include an agent 204. The agent 204 may include the agent 106 ( Figure 1 ) One or more features of the enclave 202. The agent 204 may correspond to the enclave 202 and may access the enclave 202 and the execution of actions of the enclave 202. The agent 204 may be located at the edge of the enclave 202 to allow communication with the agent 204 without providing access to secure portions of the enclave 202.
[0048] The enclave 202 and the proxy 204 may operate within a trusted environment 206. The trusted environment 206 may be defined as an environment over which the operator of the infrastructure service has control. For example, the operator of the infrastructure service may have exclusive control over the trusted environment 206. The operator may control the security of the trusted environment 206, where the security may only allow the operator and / or selected users to access the trusted environment 206. The operator having control over the trusted environment 206 may provide greater trust in the data stored within the trusted environment 206 than if users not specifically indicated by the operator were able to access the trusted environment 206. The trusted environment 206 may include specific hardware, specific software, or some combination thereof. Restricted access may be provided to the trusted environment 206.
[0049] The access arrangement 200 may also include a client device 208. The client device 208 may include a single device, another infrastructure service, or a cloud computing system. The client device 208 may be maintained by a different operator than the trusted environment 206. The client device 208 may communicate with elements within the trusted environment 206 (such as the proxy 204) via a network (such as the Internet). The client device 208 may be able to request services provided by the enclave 202. A user may access the client device 208 to request services from the enclave 202. For example, the user may be an individual who may log in to the client device 208, where the user's login to the client device 208 may verify the user's identity.
[0050] The client device 208 may request to register with the infrastructure service and / or the enclave 202. For example, the client device 208 may send a registration request including an identifier of the client device 208 and / or the user. In some cases, the registration request may also include an indication of a subscriber for which the client device 208 requests association. The proxy 204 may receive the registration request from the client device 208. The proxy 204 may store the identifier of the client device 208 and / or the user in association with the client device 208 and / or the user. In the event that the registration request includes an indication of the subscriber, the proxy 204 may also determine whether the client device 208 and / or the user has authorization for the subscriber. For example, the enclave 202 may have subscriber information 210 associated with one or more subscribers stored in the enclave 202. In other embodiments, the subscriber information 210 may be stored in the proxy 204 or another part of the infrastructure service. The proxy 204 may obtain the subscriber information associated with the subscriber indicated in the registration request from the subscriber information 210 and determine whether the subscriber has provided authorization for the client device 208 and / or the user. If the proxy 204 determines that the subscriber has provided authorization for the client device 208 and / or the user, the proxy 204 may store the identifier of the client device 208 and / or the user in association with the subscriber.
[0051] In other cases, the client device 208 may act as a subscriber, where the registration request may not include an indication of the subscriber, and subscriber information for the client device 208 and / or user may be stored in the subscriber information 210. The subscriber information for the client device 208 and / or user may include indications of other client devices and / or users that can be associated with the subscriber and actions or types of actions that can be performed in association with the subscriber.
[0052] The client device 208 may also request the infrastructure service to perform one or more actions. For example, the client device 208 may transmit a request to the infrastructure service to perform an action, wherein the request may include an identifier of the client device 208 and / or the user. The proxy 204 may receive the request from the client device 208. The proxy 204 may identify the identifier of the client device 208 and / or the user and the action requested by the client device 208 from the request. Based on the identifier and the action, the proxy 204 may determine whether the client device 208 is authorized for the execution of the action. For example, the proxy 204 may identify a subscriber associated with the client device 208 based on the identifier. The proxy 204 may then determine which actions or types of actions the subscriber has authorized for the client device 208. The proxy 204 may determine whether the action requested by the client device 208 corresponds to an action and / or action type for which the client device 208 has authorization. If proxy 204 determines that actions requested by client device 208 do not correspond to actions and / or action types for which client device 208 has authorization, proxy 204 can prevent those actions from being performed without sharing information about infrastructure services with client device 208 .
[0053] If the agent 204 determines that the action requested by the client device 208 corresponds to an action and / or action type for which the client device 208 has authorization, the agent 204 may proceed toward the execution of the action. For example, the agent 204 may coordinate with the enclave 202 to generate a credential for accessing the enclave 202. The agent 204 may transmit a request to generate the credential to the enclave 202. In some embodiments, the request to generate the credential may include an identifier of the client device 208 and / or the user. The enclave 202 may respond to the request with a key to be used by the agent 204 to generate the credential. The agent 204 may generate the credential using the key. In some embodiments, the agent 204 may generate the credential based on the key and the identifier of the client device 208 and / or the user. In some cases, the agent 204 may have previously received the key from the enclave 202, and the agent 204 may generate the credential using the previously received key.
[0054] The proxy 204 may store the credential in association with the client device 208 and / or the user. For example, the proxy 204 may store the credential in association with an identifier of the client device 208 and / or the user, wherein the proxy 204 may determine to use the credential for an authorized action request that includes the identifier of the client device 208 and / or the user. The proxy 204 may maintain the credential separately from the client device 208, wherein the proxy does not provide the credential to the client device 208. Thus, the proxy 204 may maintain the credential within the trusted environment 206, which may provide greater security against bad actors accessing the credential and / or deriving keys corresponding to the enclave 202 from the credential.
[0055] In some embodiments, the proxy 204 may store the credentials in association with actions or action types for which the client device 208 has authorization. For example, the proxy 204 may identify actions or action types for which the client device 208 and / or user has authorization, such as actions or action types for which the corresponding subscriber has provided authorization to the client. The proxy 204 may restrict the use of the credentials to actions or action types for which the client has authorization.
[0056] The proxy 204 may utilize the credentials to perform the action requested by the client device 208. For example, the proxy 204 may utilize the enclave 202 to perform the action on behalf of the client device 208, rather than the client device 208 utilizing the enclave 202 to perform the action. The proxy 204 may provide the enclave 202 with a request for the action requested by the client device 208, along with the credentials that provide access rights to the enclave 202. Services within the enclave 202 may perform the action based on the request for the action. The enclave 202 may provide the proxy 204 with the result of the action (such as a confirmation that the action was completed, an indication that the action failed for some reason, and / or one or more values generated by the action). The proxy 204 may then provide the result of the action to the client device 208.
[0057] In some embodiments, the proxy 204 can delete the credentials from storage after the action has been completed and / or the client device 208 ends the session with the proxy 204. For example, the proxy 204 can determine that the action has been completed and / or the client ends the session. The session between the proxy 204 and the client device 208 can end based on the client device 208 providing a request to end the session, the connection between the proxy 204 and the client device 208 being terminated, or some combination thereof. The proxy 204 can delete the credentials based on determining that the action has been completed and / or the session has ended.
[0058] Figure 3An example process flow 300 for client device registration according to some embodiments is illustrated. For example, process flow 300 illustrates example operations that may be performed using client device 302 and agent 304 during registration of client device 302 according to some embodiments. Client device 302 may include client device 208 ( Figure 2 ) features. Agent 304 may include agent 106 ( Figure 1 ) and / or Proxy 204 ( Figure 2 It should be understood that the operations shown are examples of embodiments, and in other embodiments, the operations may be performed in a different order, one or more of the operations may be performed simultaneously, additional operations may be included in the process flow 300, and / or one or more of the operations may be omitted from the process flow 300.
[0059] To initiate process flow 300, a user of client device 302 may request that client device 302 provide a proxy to an infrastructure service (such as a proxy server) including proxy 304. Figure 1 and / or Figure 2 304). The client device 302 may transmit a registration request 306 to the proxy 304 to register with the infrastructure service. The registration request 306 may include an identifier of the client device 302 and / or a user of the client device 302. The registration request 306 may indicate to the proxy 304 that the client device 302 and / or the user of the client device 302 wishes to register with the infrastructure service. In some cases, the registration request 306 may also include an indication of a subscriber with which the client device 302 and / or the user of the client device 302 wishes to be associated.
[0060] The proxy 304 may receive a registration request 306 from the client device 302. The proxy 304 may perform an authentication and / or authorization process 308 for the client device 302 based on the registration request 306. For example, where the registration request 306 includes an indication of a subscriber with which the client device 302 and / or the user of the client device 302 wishes to be associated, the proxy 304 may identify information associated with the subscriber, which may include an indication of the following client devices and / or users to which the subscriber provides authorization for association. The proxy 304 may determine whether the client device 302 and / or the user of the client device 302 is included in the client devices and / or users to which the subscriber provides authorization based on the identifier received in the registration request. In some cases, the subscriber may include one or more authentication procedures (such as a password check, token authentication, multi-factor authentication, or some combination thereof) for the client device 302 to complete in order for the client device 302 and / or the user of the client device 302 to prove their identity.
[0061] In some cases, the client device 302 may operate as a subscriber with the registration request 306. For example, the registration request 306 transmitted by the client device 302 may be part of a process for the client device 302 to subscribe to an infrastructure service and / or generate a lease with the infrastructure service. In these cases, the indication of the associated subscriber may be omitted from the registration request 306. Additionally, the authentication and / or authorization process 308 may be omitted in these cases. In these cases, the registration request 306 or another message may include information related to the subscriber, such as information about other client devices and / or users for whom the client device 302 is to grant authorization related to the subscription.
[0062] Based on the proxy 304 authenticating the client device 302 and / or determining its authorization, the proxy 304 can store the identifier 310. For example, the proxy 304 can store the identifier provided in the registration request 306 associated with the client device 302 and / or the user of the client device 302. The proxy 304 can then use the identifier to identify the transmission from the client device 302 based on the identifier. In the case where the proxy 304 determines that the client device 302 and / or the user of the client device 302 can be associated with the subscriber or the proxy 304 acts as a subscriber, the proxy 304 can also associate the stored identifier with the subscriber. The proxy 304 can then use the identifier to determine that the client device 302 and / or the user of the client device 302 can be associated with the subscriber to perform an action.
[0063] The agent 304 may transmit a confirmation message 312 to the client device 302 upon completion of the client device registration. The confirmation message 312 may indicate whether the client device 302 and / or the user of the client device 302 has been successfully registered. For example, the confirmation message 312 may indicate that the client device 302 and / or the user of the client device 302 has been successfully registered based on an identifier being stored in association with the client device 302 and / or the user of the client device 302. The confirmation message 312 may also indicate whether the client device 302 and / or the user of the client device 302 has been successfully associated with a subscriber. Based on receipt of the confirmation message 312, the client device 302 may indicate whether the client device registration has been successfully completed.
[0064] Figure 4 400 illustrates an example process flow 400 for the execution of an action according to some embodiments. For example, process flow 400 illustrates example operations that may be performed using client device 402, proxy 404, and security entity 406 during the execution of an action for client device 402. Client device 402 may include client device 208 ( Figure 2 ) features. Agent 404 may include agent 106 ( Figure 1 ) and / or Proxy 204 ( Figure 2 ) features. Security entity 406 may include enclave 104 ( Figure 1 )、Enclave 202( Figure 2 ) and / or one or more of the features of other security entities described throughout this disclosure. It should be understood that the operations shown are examples of embodiments, and in other embodiments, the operations may be performed in a different order, one or more of the operations may be performed simultaneously, additional operations may be included in process flow 400, and / or one or more of the operations may be omitted from process flow 400.
[0065] To initiate process flow 400, client device 402 may transmit an action request 408 to an infrastructure service. Action request 408 may indicate an action that client device 402 is requesting the infrastructure service to perform. Additionally, action request 408 may also include an identifier of client device 402 and / or a user of client device 402. Proxy 404 may receive action request 408 at the infrastructure service. Proxy 404 may determine the action requested by client device 402 and / or an identifier of client device 402 and / or a user of client device 402 based on action request 408.
[0066] The proxy 404 may perform action authorization 410 based on the action and identifier determined from the action request 408. For example, the proxy 404 may determine the client device 402 and / or the user of the client device 402 based on the identifier. In some cases, the proxy 404 may also determine the subscriber associated with the client device 402 and / or the user of the client device 402 based on the identifier. For example, the proxy 404 may have one or more identifiers stored, wherein the stored identifiers may indicate the client device, user, and / or subscriber associated with each of the identifiers. The proxy 404 may determine which actions or action types the client device 402 and / or the user of the client device 402 has authorization to perform. In some cases, the actions or action types that the client device 402 and / or the user of the client device 402 are authorized for may be defined by the subscriber that the proxy 404 has determined to be associated with the client device 402 and / or the user of the client device 402. The proxy 404 may compare the action requested by the client device 402 in the action request 408 with the actions or action types for which the client device 402 and / or the user of the client device 402 has authorization to determine whether the client device 402 and / or the user of the client device 402 has authorization for the action. If the proxy 404 determines that the client device 402 and / or the user of the client device 402 does not have authorization for the action, the proxy 404 may prevent the execution of the action. If the proxy 404 determines that the client device 402 and / or the user of the client device 402 has authorization for the action, the proxy 404 may continue the execution of the action.
[0067] Based on the determination by the agent 404 that the client device 402 and / or the user of the client device 402 has authorization for performance of the action, the agent 404 may transmit a key request 412 to the security entity 406. The key request 412 may request a key from the security entity 406 for generation of a credential for accessing the security entity 406. In some embodiments, the key request 412 may include an indication of the client device 402 and / or the user of the client device 402, an indication of a subscriber associated with the client device 402 and / or the user of the client device 402 (such as an indication of a lease associated with the subscriber), or some combination thereof.
[0068] The security entity 406 may receive a key request 412 from the proxy 404. In some embodiments, the security entity 406 may verify that the client device 402 and / or the user of the client device 402, the subscriber, or some combination thereof is valid. For example, the security entity 406 may verify that the subscriber, the client device 402, and / or the user of the client device 402 is authorized to access the security entity 406. The security entity 406 may return a key 414 to the proxy 404 in response to the key request 412. In some embodiments, the security entity 406 may also return the key 414 based on the security entity 406 verifying that the subscriber, the client device 402, and / or the user is authorized to access the security entity 406. In some embodiments, the security entity 406 may indicate an effective time during which the key may be valid for accessing the security entity 406. The key may be used to access the security entity 406. In some cases, the security entity 406 may have previously provided the key to the proxy 404, in which case the key request 412 and the return of the key 414 may be omitted from the process flow 400.
[0069] The agent 404 may receive a key from the security entity 406. The agent 404 may store the key for generation of a credential that provides access to the security entity 406. The agent 404 may generate a credential 416 for the client device 402 to access the security entity. In some embodiments, the agent may generate the credential based on an identifier of the client device 402 and / or a user of the client device 402, a subscriber (such as a lease), or some combination thereof. The agent 404 may store the credential for use in accessing the security entity 406 for performing actions associated with the client device 402.
[0070] The agent 404 may transmit an action request with the credentials 418 to the security entity 406. The agent 404 may request the security entity 406 to perform the action requested by the client device 402 in the action request 408. The security entity 406 may receive the action request from the agent 404. The security entity 406 may determine the access rights to be granted to the security entity 406 based on the credentials. The security entity 406 may perform the action based on the action request and based on the credentials. Because the agent 404 requests the action and the security entity 406 performs the action in response to the request from the agent 404, the agent 404 may have caused the action to be performed on behalf of the client device 402. Because the agent 404 (rather than the client device 402) accesses the security entity 406, the agent 404 can store the credentials without having to provide the credentials to the client device 402 for the execution of the action. Storing the credentials separately from the client device 402 can maintain the credentials in a trusted environment including the agent 404 and the security entity 406, which can provide protection to prevent bad actors from obtaining the credentials and / or deriving keys from the credentials.
[0071] Security entity 406 may provide confirmation message 420 to agent 404. In the event that security entity 406 completes an action requested by agent 404, confirmation message 420 may indicate that the action has been performed. In some cases, confirmation message 420 may also include a result of the action, such as a value produced by the action. Agent 404 may receive confirmation message 420 from security entity 406 and may store the information included in confirmation message 420.
[0072] The proxy 404 may provide a confirmation message 422 to the client device 402. In the event that the security entity 406 completes the action and provides the confirmation message 420, the confirmation message 422 transmitted by the proxy 404 to the client device 402 may include information from the confirmation message 420 or may be the confirmation message 420 forwarded to the client device 402. In the event that the proxy 404 determines that the client device 402 is not authorized for the action, the confirmation message 422 may indicate to the client device 402 that the action was not performed.
[0073] Figure 5 An example process flow 500 for key refresh according to some embodiments is illustrated. For example, process flow 500 illustrates example operations that may be performed using agent 502 and security entity 504 to refresh a key used to generate a credential for accessing security entity 504 according to some embodiments. The key being refreshed may have been previously provided to agent 502 by security entity 504, such as in process flow 400 ( Figure 4 ) provided in the proxy 502. The proxy 502 may include the proxy 108 ( Figure 1 ) and / or Proxy 204 ( Figure 2 ) features. Security entity 504 may include enclave 104 ( Figure 1 )、Enclave 202( Figure 2 ) and / or one or more of the features of other security entities described throughout this disclosure. It should be understood that the operations shown are examples of embodiments, and in other embodiments, the operations may be performed in a different order, one or more of the operations may be performed simultaneously, additional operations may be included in process flow 500, and / or one or more of the operations may be omitted from process flow 500.
[0074] Process flow 500 may be initiated with agent 502 determining that a validity time for a key has expired 506. For example, when security entity 504 previously provided a key to agent 502, security entity 504 may have indicated a validity time at which the provided key will expire and / or a validity time at which the key will remain valid. Agent 502 may determine that the validity time for the key indicated by security entity 504 has expired.
[0075] Based on the agent 502 determining that the validity time of the key has expired, the agent 502 can transmit a key refresh request 508 to the security entity 504. The key refresh request 508 can request a new key for accessing the security entity 504. In some embodiments, the key refresh request 508 can also indicate that the previously provided key has expired and / or the value of the previously provided key. The key refresh request 508 can indicate that the requested key will replace the previously provided key.
[0076] The security entity 504 may receive a key refresh request 508 from the agent 502. The security entity 504 may generate a new key for accessing the security entity based on the key refresh request 508. The key may be generated by the security entity 504 and may be used to generate one or more credentials for accessing the security entity 504. The security entity 504 may return the key 510 to the agent 502. In some embodiments, the security entity 504 may also indicate the validity period of the new key along with the returned key. The agent 502 may store the key provided by the security entity 504 and / or the validity period of the key. The agent 502 may generate one or more credentials for accessing the security entity 504 using the key.
[0077] Figure 6 An example process 600 for the performance of an action according to some embodiments is illustrated. This process (e.g., process 600) is shown as a logical flow diagram, where each operation can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, these operations can represent computer-executable instructions stored on one or more computer-readable storage media, which, when executed by one or more processors, perform the operations. Typically, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and / or in parallel to implement the process.
[0078] Process 600 may be performed by an agent, such as agent 106 ( Figure 1 ) and / or Proxy 204 ( Figure 2 ) or another part of the infrastructure service (such as Figure 1 Describes the infrastructure services, Fig.10 Cloud infrastructure, Fig.11 Cloud infrastructure, Fig.12 Cloud infrastructure and / or Fig.13 The process 600 may be performed by a client device (such as client device 208 ( Figure 2 ))Execution of the requested action.
[0079] For simplicity, process 600 is described herein as being performed by a computing system, but it should be understood that process 600 may be performed by an infrastructure service, an agent, or some combination thereof. In some embodiments, the computing system may include a cloud infrastructure service.
[0080] At 602, the computing system may implement a proxy. For example, the computing system may implement a proxy at the edge of a secure entity. In some embodiments, the secure entity may be an enclave of the computing system (such as enclave 104 ( Figure 1 ) and / or Enclave 202 ( Figure 2 )). In some embodiments, the computing system may implement a proxy at the edge of the enclave. In some embodiments, 602 may be omitted.
[0081] At 604, the computing system may receive a request to perform an action. For example, the computing system may receive a request to perform an action from a client device. The request may include an identifier of the client device and / or a user of the client device and an action to be performed by the security entity. In some embodiments, the action may be a request to write a billing record for a subscriber, which may indicate an amount of resources that have been consumed.
[0082] At 606, the computing system may determine the subscriber. For example, the computing system may determine the subscriber corresponding to the client device based at least in part on an identifier of the client device. The computing system may store one or more identifiers and associations of the identifiers with subscribers. The computing system may compare the identifier received from the client device with the stored identifiers and determine the subscriber associated with the client device based on the comparison.
[0083] In 608, the computing system may determine that the subscriber has provided authorization for performance of the action. For example, the computing system may determine that the subscriber has provided authorization for performance of the action to the client device. In some embodiments, determining that the subscriber has provided authorization for performance of the action to the client device may include determining one or more actions for which the subscriber has provided authorization for the client device. The computing system may determine that the action indicated by the request is included in the one or more actions.
[0084] In 610, the computing system may generate a credential. For example, the computing system may generate a credential for accessing the security entity on behalf of the client device based at least in part on determining that the client device has authorization to perform the action. In some embodiments, generating the credential may include generating the credential using a key corresponding to the security entity. The computing system may have received the key from the security entity. In some embodiments, the credential may be generated by an agent implemented in 602.
[0085] At 612, the computing system may maintain the credentials. For example, the credentials may be maintained separately from the client device. In some embodiments, the computing system and the security entity may be located in a trusted environment (such as trusted environment 206 ( Figure 2 Maintaining the credentials separately from the client device may include maintaining the credentials within a trusted environment. In some embodiments, the agent implemented in 602 may maintain the credentials separately from the client device.
[0086] In 614, the computing system may use the credentials for the performance of the action. For example, the computing system may use the credentials for the performance of the action on behalf of the client device. In some embodiments, the computing system may provide the credentials to the security entity to obtain access rights to the security entity. In addition, the computing system may request the security entity to perform the action. The security entity may perform the action based on a request from the computing system. In some embodiments, the agent implemented in 602 may utilize the credentials on behalf of the client device to perform the action.
[0087] In 616, the computing system may determine that the validity time of the key has expired. For example, the computing system may determine that the validity time of the key received from the security entity has expired. The security entity may indicate the validity time when the key is provided that the key can be used to generate credentials. In some embodiments, 616 may be omitted.
[0088] In 618, the computing system may refresh the key. For example, the computing system may utilize the security entity to refresh the key based at least in part on determining that the validity time of the key has expired. The computing system may provide a request for a new key from the security entity to refresh the key. In some embodiments, 618 may be omitted.
[0089] At 620, the computing system may maintain the refreshed key. For example, the computing system may maintain the refreshed key separately from the client device. The computing system may receive the new key from the security entity and store the new key as the refreshed key. The computing system may maintain the credential separately from the client device by maintaining the credential within a trusted environment.
[0090] Figure 7Another example process 700 for the performance of an action according to some embodiments is illustrated. This process (e.g., process 700) is shown as a logical flow diagram, where each operation can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, an operation can represent a computer-executable instruction stored on one or more computer-readable storage media, which, when executed by one or more processors, performs the operation. Typically, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and / or in parallel to implement the process.
[0091] Process 700 may be performed by an agent, such as agent 106 ( Figure 1 ) and / or Proxy 204 ( Figure 2 ) or infrastructure services (such as Figure 1 Related description of infrastructure services, Fig.10 Cloud infrastructure, Fig.11 Cloud infrastructure, Fig.12 Cloud infrastructure and / or Fig.13 The process 700 may be performed by another portion of a cloud infrastructure (which may include a computing system and / or a cloud computing system) of the client device (such as the client device 208 ( Figure 2 ))Execution of the requested action.
[0092] For simplicity, process 700 is described herein as being performed by a computing system, but it should be understood that process 700 may be performed by an infrastructure service, an agent, or some combination thereof. In some embodiments, the computing system may include a cloud infrastructure service.
[0093] In 702, the computing system may implement a proxy. For example, the computing system may include a cloud infrastructure service. The cloud infrastructure service may include a security entity. In some embodiments, the security entity may be an enclave within the cloud infrastructure service. The computing system may implement a proxy at the edge of the security entity. In some embodiments, 702 may be omitted.
[0094] At 704, the computing system may receive a request to perform an action. For example, the computing system may receive a request to perform an action by a security entity, which may be received from a client device. The request may include an identifier of the client device and / or a user of the client device and the action to be performed by the security entity. In some embodiments, the action may be a request to write a billing record for a subscriber, which may indicate an amount of resources that have been consumed.
[0095] At 706, the computing system may determine the subscriber. For example, the computing system may determine the subscriber corresponding to the client device based at least in part on an identifier of the client device. The computing system may store one or more identifiers and associations of the identifiers with subscribers. The computing system may compare the identifier received from the client device with the stored identifiers and determine the subscriber associated with the client device based on the comparison.
[0096] In 708, the computing system may determine that the subscriber has provided authorization for the performance of the action. For example, the computing system may determine that the subscriber has provided authorization for the performance of the action to the client device. In some embodiments, determining that the subscriber has provided authorization for the performance of the action to the client device may include determining one or more actions for which the subscriber has provided authorization for the client device. The computing system may determine that the action indicated by the request is included in the one or more actions.
[0097] In 710, the computing system may retrieve the key. For example, the computing system may retrieve the key from the security entity. The computing system may determine, at least in part, to request the key from the security entity based on the subscriber having provided authorization to the client device for the performance of the action. In some embodiments, 710 may be omitted.
[0098] In 712, the computing system may generate a credential. For example, the computing system may generate a credential for accessing a secure entity based at least in part on determining that the subscriber has provided authorization to the client device for performance of the action. In some embodiments, generating the credential may include generating the credential based at least in part on a key. In some embodiments, the agent implemented in 702 may generate a credential for accessing a secure entity.
[0099] At 714, the computing system may store the credentials. For example, the computing system may store the credentials in memory. The credentials may be stored separately from the client device. In some embodiments, the computing system and the security entity may be located in a trusted environment (such as trusted environment 206 ( Figure 2 Storing the credentials separately from the client device may include maintaining the credentials within a trusted environment.
[0100] At 716, the computing system may use the credentials for performance of the action. For example, the computing system may use the credentials for performance of the action on behalf of the client device. The computing system may provide the credentials to the security entity to obtain access rights to the security entity and may cause the security entity to perform the action. In the case where the action is to enter a billing record, the computing system may cause the security entity to enter the billing record. In some embodiments, the agent implemented at 702 may utilize the credentials for performance of the action.
[0101] In 718, the computing system may determine that the validity time of the key has expired. For example, the computing system may determine that the validity time of the key received from the security entity has expired. The security entity may indicate the validity time when the key is provided that the key can be used to generate credentials. In some embodiments, 718 may be omitted.
[0102] At 720, the computing system may refresh the key. For example, the computing system may determine, at least in part, to refresh the key with the security entity based on the validity time of the key having expired. The computing system may provide a request for a new key from the security entity to refresh the key. In some embodiments, 720 may be omitted.
[0103] Figure 8 Another example process 800 for the performance of an action according to some embodiments is illustrated. This process (e.g., process 800) is shown as a logical flow diagram, where each operation can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, an operation can represent a computer-executable instruction stored on one or more computer-readable storage media, which, when executed by one or more processors, performs the enumerated operation. Typically, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. The order in which the operations are described should not be intended to be construed as a limitation, and any number of the described operations can be combined in any order and / or in parallel to implement the process.
[0104] Process 800 may be performed by an agent, such as agent 106 ( Figure 1 ) and / or Proxy 204 ( Figure 2 ) or infrastructure services (such as Figure 1 Related description of infrastructure services, Fig.10 Cloud infrastructure, Fig.11 Cloud infrastructure, Fig.12 Cloud infrastructure and / or Fig.13 The process 800 may be performed by another portion of a cloud infrastructure (which may include a computing system and / or a cloud computing system) of the client device (such as the client device 208 ( Figure 2 ))Execution of the requested action.
[0105] For simplicity, process 800 is described herein as being performed by an agent, but it should be understood that process 800 may be performed by an infrastructure service, an agent, or some combination thereof. In some embodiments, the computing system may include a cloud infrastructure service.
[0106] In 802, the proxy may receive a request to perform an action. For example, the proxy may receive a request from a client device to perform an action by a security entity. The request may include an identifier of the client device and an action to be performed by the security entity. In some embodiments, the action may be a request to write a billing record for a subscriber, which may indicate an amount of resources that have been consumed. In some embodiments, the security entity may be an enclave. The proxy may receive the request to perform the action at an edge of the enclave.
[0107] In 804, the agent may determine that the client device is authorized to perform the action. In some embodiments, determining that the client device is authorized to perform the action may include determining one or more actions for which the subscriber has provided authorization for the client device. The computing system may determine that the action indicated by the request is included in the one or more actions.
[0108] In 806, the agent may retrieve the key. For example, the agent may retrieve the key from the security entity. The computing system may request the key from the security entity based at least in part on determining that the subscriber has provided authorization to the client device for the performance of the action. In some embodiments, 806 may be omitted.
[0109] In 808, the agent may generate a credential. For example, the agent may generate a credential for accessing the security entity based at least in part on determining that the client device is authorized to perform the action. In some embodiments, generating the credential may include generating the credential based at least in part on a key.
[0110] In 810, the agent can maintain the credentials within the trusted environment. For example, the security entity and the agent can be located within the trusted environment. The client device can be located outside the trusted environment. The agent can maintain the credentials within the trusted environment including the security entity and the agent.
[0111] At 812, the computing system may utilize the credentials to cause the security entity to perform an action. For example, the agent may utilize the credentials on behalf of the client device to cause the security entity to perform an action. The agent may provide the credentials to the security entity to obtain access rights to the security entity and may cause the security entity to perform the action. In the case where the action is to enter a billing record, the agent may cause the security entity to enter the billing record.
[0112] In 814, the agent may determine that the validity time of the key has expired. For example, the agent may determine that the validity time of the key received from the security entity has expired. The security entity may indicate the validity time when the key is provided that the key can be used to generate credentials. In some embodiments, 814 may be omitted.
[0113] At 816, the agent may refresh the key. For example, the agent may refresh the key with the security entity based at least in part on determining that the validity time of the key has expired. The agent may provide a request for a new key from the security entity to refresh the key, and may receive the new key based on the request for the new key. In some embodiments, 816 may be omitted.
[0114] As noted above, Infrastructure as a Service (IaaS) is a specific type of cloud computing. IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In the IaaS model, a cloud computing provider can host infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., hypervisor layer), etc.). In some cases, IaaS providers can also provide various services to accompany these infrastructure components (e.g., billing, monitoring, logging, load balancing and clustering, etc.). Therefore, since these services may be policy-driven, IaaS users may be able to implement policies to drive load balancing to maintain application availability and performance.
[0115] In some cases, IaaS customers can access resources and services over a wide area network (WAN) such as the Internet, and can use the cloud provider's services to install the remaining elements of the application stack. For example, a user can log in to the IaaS platform to create a virtual machine (VM), install an operating system (OS) on each VM, deploy middleware such as a database, create storage buckets for workloads and backups, and even install enterprise software into that VM. Customers can then use the provider's services to perform a variety of functions, including balancing network traffic, troubleshooting application problems, monitoring performance, managing disaster recovery, and more.
[0116] In most cases, the cloud computing model will require the involvement of a cloud provider. A cloud provider may, but need not, specialize in providing (e.g., provisioning, renting, selling) third-party IaaS services. An entity may also choose to deploy a private cloud, thereby becoming its own infrastructure service provider.
[0117] In some examples, IaaS deployment is the process of placing a new application or a new version of an application onto a prepared application server, etc. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is typically managed by the cloud provider, below the hypervisor layer (e.g., servers, storage, network hardware, and virtualization). Thus, the customer may be responsible for handling (OS), middleware, and / or application deployment (e.g., on a self-service virtual machine (e.g., that can be started on demand), etc.).
[0118] In some examples, IaaS provisioning can refer to acquiring computers or virtual hosts for use, and even installing required libraries or services on them. Most of the time, deployment does not include provisioning, and provisioning may need to be performed first.
[0119] In some cases, there are two distinct challenges with IaaS provisioning. First, there is the initial challenge of provisioning the initial set of infrastructure before anything is running. Second, once everything has been provisioned, there is the challenge of evolving the existing infrastructure (e.g., adding new services, changing services, removing services, etc.). In some cases, both of these challenges can be addressed by enabling configuration that defines the infrastructure in a declarative manner. In other words, the infrastructure (e.g., which components are required and how they interact) can be defined by one or more configuration files. Thus, the overall topology of the infrastructure (e.g., which resources depend on which resources, and how they work together) can be described in a declarative manner. In some cases, once the topology is defined, workflows can be generated that create and / or manage the different components described in the configuration files.
[0120] In some examples, the infrastructure can have many interconnected elements. For example, there may be one or more virtual private clouds (VPCs) (e.g., a potential on-demand pool of configurable and / or shared computing resources), also referred to as a core network. In some examples, one or more inbound / outbound traffic group rules may also be provisioned to define how inbound and / or outbound traffic for the network and one or more virtual machines (VMs) is set up. Other infrastructure elements may also be provisioned, such as load balancers, databases, etc. The infrastructure may evolve gradually as more and more infrastructure elements are desired and / or added.
[0121] In some cases, continuous deployment techniques can be employed to enable infrastructure code to be deployed across various virtual computing environments. In addition, the described techniques can enable infrastructure management within these environments. In some examples, a service team can write code that is expected to be deployed to one or more but typically many different production environments (e.g., across various different geographic locations, sometimes across the entire world). However, in some examples, the infrastructure on which the code will be deployed must first be set up. In some cases, provisioning can be done manually, resources can be provisioned using a provisioning tool, and / or code can be deployed using a deployment tool once the infrastructure is provisioned.
[0122] Fig. 9900 is a block diagram illustrating an example mode of an IaaS architecture according to at least one embodiment. A service operator 902 may be communicatively coupled to a secure host lease 904 that may include a virtual cloud network (VCN) 906 and a secure host subnet 908. In some examples, the service operator 902 may use one or more client computing devices, which may be portable handheld devices (e.g., iPhone®, cellular phones, iPad®, computing tablets, personal digital assistants (PDAs)) or wearable devices (e.g., Google Glass® head-mounted displays), running software (such as Microsoft Windows Mobile®) and / or various mobile operating systems (such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, etc.), and supporting Internet, email, short message service (SMS), Blackberry® or other communication protocols. Alternatively, the client computing device may be a general-purpose personal computer, including, for example, a personal computer and / or laptop computer running various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux operating systems. The client computing device may be a workstation computer running any of a variety of commercially available UNIX® or UNIX-like operating systems, including but not limited to a variety of GNU / Linux operating systems (such as, for example, Google Chrome OS). Alternatively or additionally, the client computing device may be any other electronic device, such as a thin client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and / or a personal messaging device capable of communicating over a network that has access to VCN 906 and / or the Internet.
[0123] The VCN 906 may include a local peer gateway (LPG) 910, which may be communicatively coupled to a secure shell (SSH) VCN 912 via the LPG 910 contained in an SSH VCN 912. The SSH VCN 912 may include an SSH subnet 914, and the SSH VCN 912 may be communicatively coupled to a control plane VCN 916 via the LPG 910 contained in a control plane VCN 916. In addition, the SSH VCN 912 may be communicatively coupled to a data plane VCN 918 via the LPG 910. The control plane VCN 916 and the data plane VCN 918 may be contained in a service lease 919, which may be owned and / or operated by an IaaS provider.
[0124] The control plane VCN 916 may include a control plane demilitarized zone (DMZ) layer 920 that acts as a perimeter network (e.g., a portion of a corporate network between a corporate intranet and an external network). DMZ-based servers may have limited liability and help control vulnerabilities. In addition, the DMZ layer 920 may include one or more load balancer (LB) subnets 922, a control plane application layer 924 that may include (one or more) application subnets 926, and a control plane data layer 928 that may include (one or more) database (DB) subnets 930 (e.g., (one or more) front-end DB subnets and / or (one or more) back-end DB subnets). The LB subnet(s) 922 included in the control plane DMZ layer 920 may be communicatively coupled to the application subnet(s) 926 included in the control plane application layer 924 and the Internet gateway 934 that may be included in the control plane VCN 916, and the application subnet(s) 926 may be communicatively coupled to the DB subnet(s) 930 included in the control plane data layer 928 as well as the service gateway 936 and the network address translation (NAT) gateway 938. The control plane VCN 916 may include the service gateway 936 and the NAT gateway 938.
[0125] The control plane VCN 916 may include a data plane mirror application layer 940, which may include application subnet(s) 926. The application subnet(s) 926 included in the data plane mirror application layer 940 may include a virtual network interface controller (VNIC) 942 that may execute a compute instance 944. The compute instance 944 may communicatively couple the application subnet(s) 926 of the data plane mirror application layer 940 to the application subnet(s) 926 that may be included in the data plane application layer 946.
[0126] The data plane VCN 918 may include a data plane application layer 946, a data plane DMZ layer 948, and a data plane data layer 950. The data plane DMZ layer 948 may include (one or more) LB subnets 922, which may be communicatively coupled to the (one or more) application subnets 926 of the data plane application layer 946 and the Internet gateway 934 of the data plane VCN 918. The (one or more) application subnets 926 may be communicatively coupled to the service gateway 936 of the data plane VCN 918 and the NAT gateway 938 of the data plane VCN 918. The data plane data layer 950 may also include (one or more) DB subnets 930, which may be communicatively coupled to the (one or more) application subnets 926 of the data plane application layer 946.
[0127] The internet gateway 934 of the control plane VCN 916 and the data plane VCN 918 may be communicatively coupled to a metadata management service 952, which may be communicatively coupled to a public Internet 954. The public Internet 954 may be communicatively coupled to a NAT gateway 938 of the control plane VCN 916 and the data plane VCN 918. The service gateway 936 of the control plane VCN 916 and the data plane VCN 918 may be communicatively coupled to a cloud service 956.
[0128] In some examples, a service gateway 936 of a control plane VCN 916 or a data plane VCN 918 can make application programming interface (API) calls to cloud services 956 without going through public internet 954. API calls from service gateway 936 to cloud services 956 can be one-way: service gateway 936 can make API calls to cloud services 956, and cloud services 956 can send requested data to service gateway 936. However, cloud services 956 may not initiate API calls to service gateway 936.
[0129] In some examples, secure host lease 904 can be directly connected to service lease 919, which can otherwise be isolated. Secure host subnet 908 can communicate with SSH subnet 914 through LPG 910, which can enable two-way communication on otherwise isolated systems. Connecting secure host subnet 908 to SSH subnet 914 can enable secure host subnet 908 to access other entities within service lease 919.
[0130] The control plane VCN 916 may allow a user of the service lease 919 to set up or otherwise provision desired resources. The desired resources provisioned in the control plane VCN 916 may be deployed or otherwise used in the data plane VCN 918. In some examples, the control plane VCN 916 may be isolated from the data plane VCN 918, and the data plane mirror application layer 940 of the control plane VCN 916 may communicate with the data plane application layer 946 of the data plane VCN 918 via the VNIC 942, which may be included in the data plane mirror application layer 940 and the data plane application layer 946.
[0131] In some examples, a user or customer of the system may make a request, such as a create, read, update, or delete (CRUD) operation, through the public Internet 954, which may transmit the request to the metadata management service 952. The metadata management service 952 may transmit the request to the control plane VCN 916 through the Internet gateway 934. The request may be received by the LB subnet(s) 922 contained in the control plane DMZ layer 920. The LB subnet(s) 922 may determine that the request is valid, and in response to the determination, the LB subnet(s) 922 may transmit the request to the application subnet(s) 926 contained in the control plane application layer 924. If the request is validated and a call to the public Internet 954 is required, the call to the public Internet 954 may be transmitted to the NAT gateway 938, which may make the call to the public Internet 954. The storage that the request may desire to be stored may be stored in the DB subnet(s) 930.
[0132] In some examples, data plane mirror application layer 940 may facilitate direct communication between control plane VCN 916 and data plane VCN 918. For example, it may be desirable to apply changes, updates, or other appropriate modifications to the configuration to the resources contained in data plane VCN 918. Control plane VCN 916 may communicate directly with the resources contained in data plane VCN 918 via VNIC 942 and may thereby perform changes, updates, or other appropriate modifications to the configuration.
[0133] In some embodiments, the control plane VCN 916 and the data plane VCN 918 may be included in the service lease 919. In this case, the user or customer of the system may not own or operate the control plane VCN 916 or the data plane VCN 918. Alternatively, the IaaS provider may own or operate the control plane VCN 916 and the data plane VCN 918, both of which may be included in the service lease 919. This embodiment may enable the isolation of networks that may prevent a user or customer from interacting with the resources of other users or other customers. In addition, this embodiment may allow users or customers of the system to store databases privately without relying on the public Internet 954, which may not have the desired level of threat protection, for storage.
[0134] In other embodiments, the LB subnet(s) 922 contained in the control plane VCN 916 may be configured to receive signals from the service gateway 936. In this embodiment, the control plane VCN 916 and the data plane VCN 918 may be configured to be called by customers of the IaaS provider without calling the public Internet 954. Customers of the IaaS provider may desire this embodiment because the database(s) used by the customer may be controlled by the IaaS provider and may be stored on the service lease 919, which may be isolated from the public Internet 954.
[0135] Fig.10 1 is a block diagram 1000 illustrating another example model of an IaaS architecture according to at least one embodiment. A service operator 1002 (e.g., Fig. 9 The service operator 902) may be communicatively coupled to the secure host lease 1004 (e.g., Fig. 9 The secure host lease 904 may include a virtual cloud network (VCN) 1006 (eg, Fig. 9 VCN 906) and secure host subnet 1008 (e.g., Fig. 9 The VCN 1006 may include a local peer gateway (LPG) 1010 (e.g., Fig. 9 910 ), which may be communicatively coupled to a secure shell (SSH) VCN 1012 (e.g., Fig. 9 SSH VCN 1012 may include SSH subnet 1014 (e.g., Fig. 9 SSH subnet 914), and SSH VCN 1012 can be communicatively coupled to control plane VCN 1016 via LPG 1010 included in control plane VCN 1016 (e.g., Fig. 9 The control plane VCN 916). The control plane VCN 1016 may be included in a service lease 1019 (e.g., Fig. 9 service lease 919), and the data plane VCN 1018 (e.g., Fig. 9 The data plane VCN 918) may be contained in a customer lease 1021 which may be owned or operated by a user or customer of the system.
[0136] The control plane VCN 1016 may include a control plane DMZ layer 1020 (e.g., Fig. 9 The control plane DMZ layer 920 may include (one or more) LB subnets 1022 (e.g., Fig. 9(one or more) LB subnets 922), may include (one or more) application subnets 1026 (e.g., Fig. 9 The control plane application layer 1024 (e.g., Fig. 9 The control plane application layer 924 of FIG. 100 may include (one or more) database (DB) subnets 1030 (e.g., similar to Fig. 9 The control plane data layer 1028 (e.g., Fig. 9 1028). The LB subnet(s) 1022 contained in the control plane DMZ layer 1020 may be communicatively coupled to the application subnet(s) 1026 contained in the control plane application layer 1024 and the internet gateway 1034 (e.g., Fig. 9 934), and the application subnet(s) 1026 may be communicatively coupled to the DB subnet(s) 1030 and the service gateway 1036 (e.g., Fig. 9 ) and a network address translation (NAT) gateway 1038 (e.g., Fig. 9 The control plane VCN 1016 may include a service gateway 1036 and a NAT gateway 1038.
[0137] The control plane VCN 1016 may include a data plane mirror application layer 1040 (eg, Fig. 9 The data plane image application layer 940). The application subnet(s) 1026 included in the data plane image application layer 1040 may include a computing instance 1044 (e.g., similar to Fig. 9 A virtual network interface controller (VNIC) 1042 (e.g., Fig. 9 The compute instance 1044 can facilitate the application subnet(s) 1026 of the data plane mirroring application layer 1040 and can include the application subnet(s) 1026 of the data plane application layer 1046 (e.g., Fig. 9 Communication between (one or more) application subnets 1026 in the data plane application layer 946) via the VNIC 1042 contained in the data plane mirror application layer 1040 and the VNIC 1042 contained in the data plane application layer 1046.
[0138] The Internet gateway 1034 included in the control plane VCN 1016 can be communicatively coupled to the metadata management service 1052 (e.g., Fig. 9952), which can be communicatively coupled to the public Internet 1054 (e.g., Fig. 9 The public Internet 1054 can be communicatively coupled to a NAT gateway 1038 included in the control plane VCN 1016. The service gateway 1036 included in the control plane VCN 1016 can be communicatively coupled to a cloud service 1056 (e.g., Fig. 9 Cloud services 956).
[0139] In some examples, the data plane VCN 1018 may be contained in a customer lease 1021. In this case, the IaaS provider may provide a control plane VCN 1016 for each customer, and the IaaS provider may provision each customer with a unique compute instance 1044 contained in a service lease 1019. Each compute instance 1044 may allow communication between the control plane VCN 1016 contained in the service lease 1019 and the data plane VCN 1018 contained in the customer lease 1021. The compute instance 1044 may allow resources provisioned in the control plane VCN 1016 contained in the service lease 1019 to be deployed or otherwise used in the data plane VCN 1018 contained in the customer lease 1021.
[0140] In other examples, a customer of the IaaS provider may have a database that exists in the customer tenancy 1021. In this example, the control plane VCN 1016 may include a data plane mirror application layer 1040, which may include (one or more) application subnets 1026. The data plane mirror application layer 1040 may reside in the data plane VCN 1018, but the data plane mirror application layer 1040 may not be in the data plane VCN 1018. That is, the data plane mirror application layer 1040 may access the customer tenancy 1021, but the data plane mirror application layer 1040 may not exist in the data plane VCN 1018 or be owned or operated by the customer of the IaaS provider. The data plane mirror application layer 1040 may be configured to make calls to the data plane VCN 1018, but may not be configured to make calls to any entity contained in the control plane VCN 1016. A customer may desire to deploy or otherwise use resources provisioned in control plane VCN 1016 in data plane VCN 1018, and data plane mirror application layer 1040 may facilitate the customer's desired deployment or other use of resources.
[0141] In some embodiments, a customer of an IaaS provider may apply filters to the data plane VCN 1018. In this embodiment, the customer may determine what the data plane VCN 1018 may access, and the customer may restrict access to the public Internet 1054 from the data plane VCN 1018. The IaaS provider may not apply filters or otherwise control access to any external network or database by the data plane VCN 1018. The customer applying filters and controls to the data plane VCN 1018 contained in the customer lease 1021 may help isolate the data plane VCN 1018 from other customers and the public Internet 1054.
[0142] In some embodiments, cloud services 1056 may be called by service gateway 1036 to access services that may not exist on public Internet 1054, control plane VCN 1016, or data plane VCN 1018. The connection between cloud services 1056 and control plane VCN 1016 or data plane VCN 1018 may not be real-time or continuous. Cloud services 1056 may exist on different networks owned or operated by IaaS providers. Cloud services 1056 may be configured to receive calls from service gateway 1036 and may be configured not to receive calls from public Internet 1054. Some cloud services 1056 may be isolated from other cloud services 1056, and control plane VCN 1016 may be isolated from cloud services 1056 that may not be in the same region as control plane VCN 1016. For example, control plane VCN 1016 may be located in "region 1", and cloud service "deployment 9" may be located in region 1 and "region 2". If a service gateway 1036 contained in a control plane VCN 1016 located in region 1 makes a call to deployment 9, the call may be transmitted to deployment 9 in region 1. In this example, control plane VCN 1016 or deployment 9 in region 1 may not be communicatively coupled or otherwise in communication with deployment 9 in region 2.
[0143] Fig.11 1 is a block diagram 1100 illustrating another example model of an IaaS architecture according to at least one embodiment. A service operator 1102 (e.g., Fig. 9 The service operator 902) may be communicatively coupled to the secure host lease 1104 (e.g., Fig. 9 The secure host lease 1104 may include a virtual cloud network (VCN) 1106 (e.g., Fig. 9 VCN 906) and secure host subnet 1108 (e.g., Fig. 9 VCN 1106 may include LPG 1110 (e.g., Fig. 9910), which may be communicatively coupled to the SSH VCN 1112 via the LPG 1110 contained in the SSH VCN 1112 (e.g., Fig. 9 SSH VCN 1112 may include SSH subnet 1114 (e.g., Fig. 9 SSH subnet 914), and SSH VCN 1112 may be communicatively coupled to control plane VCN 1116 via LPG 1110 included in control plane VCN 1116 (e.g., Fig. 9 The control plane VCN 916 of the present invention is coupled to the data plane VCN 1118 (eg, control plane VCN 916 of the present invention) and is coupled to the data plane VCN 1118 via the LPG 1110 contained in the data plane VCN 1118 (eg, Fig. 9 The control plane VCN 1116 and the data plane VCN 1118 may be included in a service lease 1119 (e.g., Fig. 9 Service lease 919).
[0144] The control plane VCN 1116 may include a subnet 1122 that may include (one or more) load balancers (LBs) (e.g., Fig. 9 The control plane DMZ layer 1120 (e.g., Fig. 9 The control plane DMZ layer 920 may include (one or more) application subnets 1126 (e.g., similar to Fig. 9 (one or more) application subnets 926) of the control plane application layer 1124 (e.g., Fig. 9 The control plane application layer 924 of the embodiment of the present invention may include a control plane data layer 1128 (eg, Fig. 9 The LB subnet(s) 1122 contained in the control plane DMZ layer 1120 may be communicatively coupled to the application subnet(s) 1126 contained in the control plane application layer 1124 and the Internet gateway 1134 (e.g., Fig. 9 934), and the application subnet(s) 1126 may be communicatively coupled to the DB subnet(s) 1130 and the service gateway 1136 (e.g., Fig. 9 Serving gateway 936) and network address translation (NAT) gateway 1138 (e.g., Fig. 9 The control plane VCN 1116 may include a service gateway 1136 and a NAT gateway 1138.
[0145] Data plane VCN 1118 may include a data plane application layer 1146 (e.g., Fig. 9 Data plane application layer 946), data plane DMZ layer 1148 (for example, Fig. 9 Data plane DMZ layer 948), and data plane data layer 1150 (e.g., Fig. 9 The data plane DMZ layer 1148 may include (one or more) trusted application subnets 1160 and (one or more) untrusted application subnets 1162 that may be communicatively coupled to the data plane application layer 1146 and (one or more) LB subnets 1122 of the Internet gateway 1134 included in the data plane VCN 1118. The (one or more) trusted application subnets 1160 may be communicatively coupled to the service gateway 1136 included in the data plane VCN 1118, the NAT gateway 1138 included in the data plane VCN 1118, and (one or more) DB subnets 1130 included in the data plane data layer 1150. The (one or more) untrusted application subnets 1162 may be communicatively coupled to the service gateway 1136 included in the data plane VCN 1118 and (one or more) DB subnets 1130 included in the data plane data layer 1150. Data plane data layer 1150 may include DB subnet(s) 1130 that may be communicatively coupled to service gateway 1136 included in data plane VCN 1118 .
[0146] The non-trusted application subnet(s) 1162 may include one or more primary VNICs 1164(1)-(N) that may be communicatively coupled to tenant virtual machines (VMs) 1166(1)-(N). Each tenant VM 1166(1)-(N) may be communicatively coupled to a respective application subnet 1167(1)-(N) that may be contained in a respective container egress VCN 1168(1)-(N), which may be contained in a respective customer tenancy 1170(1)-(N). Respective secondary VNICs 1172(1)-(N) may facilitate communications between the non-trusted application subnet(s) 1162 contained in the data plane VCN 1118 and the application subnets contained in the container egress VCNs 1168(1)-(N). Each container egress VCN 1168(1)-(N) may include a NAT gateway 1138 that may be communicatively coupled to the public Internet 1154 (e.g., Fig. 9 of the public Internet 954).
[0147] Internet gateway 1134 included in control plane VCN 1116 and included in data plane VCN 1118 may be communicatively coupled to metadata management service 1152 (e.g., Fig. 9 1154), which can be communicatively coupled to the public Internet 1154. The public Internet 1154 can be communicatively coupled to the NAT gateway 1138 included in the control plane VCN 1116 and included in the data plane VCN 1118. The service gateway 1136 included in the control plane VCN 1116 and included in the data plane VCN 1118 can be communicatively coupled to the cloud service 1156.
[0148] In some embodiments, the data plane VCN 1118 can be integrated with the customer lease 1170. In some cases, such integration may be useful or desirable for customers of the IaaS provider, such as where support may be desired when executing code. A customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects. In response to this, the IaaS provider may determine whether to run the code given to the IaaS provider by the customer.
[0149] In some examples, a customer of an IaaS provider may grant temporary network access to the IaaS provider and request functionality attached to the data plane application layer 1146. Code running the functionality may be executed in a VM 1166(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN 1118. Each VM 1166(1)-(N) may be connected to one customer tenancy 1170. The corresponding container 1171(1)-(N) contained in the VM 1166(1)-(N) may be configured to run code. In this case, there may be double isolation (e.g., the container 1171(1)-(N) runs code, where the container 1171(1)-(N) may be contained at least in the VM 1166(1)-(N) contained in the (one or more) untrusted application subnets 1162), which may help prevent incorrect or otherwise undesirable code from damaging the IaaS provider's network or damaging the network of a different customer. Containers 1171(1)-(N) may be communicatively coupled to customer lease 1170 and may be configured to transmit or receive data from customer lease 1170. Containers 1171(1)-(N) may not be configured to transmit or receive data from any other entity in data plane VCN 1118. After running the code, the IaaS provider may terminate or otherwise dispose of containers 1171(1)-(N).
[0150] In some embodiments, the trusted application subnet(s) 1160 may run code that may be owned or operated by the IaaS provider. In this embodiment, the trusted application subnet(s) 1160 may be communicatively coupled to the DB subnet(s) 1130 and configured to perform CRUD operations in the DB subnet(s) 1130. The untrusted application subnet(s) 1162 may be communicatively coupled to the DB subnet(s) 1130, but in this embodiment, the untrusted application subnet(s) may be configured to perform read operations in the DB subnet(s) 1130. The containers 1171(s)-(N) that may be included in each customer's VM 1166(s)-(N) and that may run code from the customer may not be communicatively coupled to the DB subnet(s) 1130.
[0151] In other embodiments, the control plane VCN 1116 and the data plane VCN 1118 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 1116 and the data plane VCN 1118. However, communication may occur indirectly through at least one method. The LPG 1110 may be established by an IaaS provider, which may facilitate communication between the control plane VCN 1116 and the data plane VCN 1118. In another example, the control plane VCN 1116 or the data plane VCN 1118 may call the cloud service 1156 via the service gateway 1136. For example, the call from the control plane VCN 1116 to the cloud service 1156 may include a request for a service that may communicate with the data plane VCN 1118.
[0152] Fig.12 12 is a block diagram 1200 illustrating another example model of an IaaS architecture according to at least one embodiment. A service operator 1202 (e.g., Fig. 9 The service operator 902) may be communicatively coupled to the secure host lease 1204 (e.g., Fig. 9 The secure host lease 1204 may include a virtual cloud network (VCN) 1206 (e.g., Fig. 9 VCN 906) and secure host subnet 1208 (e.g., Fig. 9 VCN 1206 may include LPG 1210 (e.g., Fig. 9 LPG 910), the LPG 1210 can be connected to the SSH VCN 1212 (e.g., Fig. 9The LPG 1210 in the SSH VCN 912 is communicatively coupled to the SSH VCN 1212. The SSH VCN 1212 may include an SSH subnet 1214 (e.g., Fig. 9 SSH subnet 914), and SSH VCN 1212 may be communicatively coupled to control plane VCN 1216 via LPG 1210 included in control plane VCN 1216 (e.g., Fig. 9 916) and is coupled to the data plane VCN 1218 via the LPG 1210 contained in the data plane VCN 1218 (e.g., Fig. 9 The control plane VCN 1216 and the data plane VCN 1218 may be included in a service lease 1219 (e.g., Fig. 9 Service lease 919).
[0153] The control plane VCN 1216 may include a LB subnet 1222 (e.g., Fig. 9 The control plane DMZ layer 1220 (e.g., Fig. 9 The control plane DMZ layer 920 may include (one or more) application subnets 1226 (e.g., Fig. 9 (one or more) application subnets 926) of the control plane application layer 1224 (e.g., Fig. 9 The control plane application layer 924 of FIG. 120 may include (one or more) DB subnets 1230 (eg, Fig.11 The control plane data layer 1228 (e.g., Fig. 9 The LB subnet(s) 1222 contained in the control plane DMZ layer 1220 may be communicatively coupled to the application subnet(s) 1226 contained in the control plane application layer 1224 and the Internet gateway 1234 (e.g., Fig. 9 934), and the application subnet(s) 1226 may be communicatively coupled to the DB subnet(s) 1230 and the service gateway 1236 (e.g., Fig. 9 ) and a network address translation (NAT) gateway 1238 (e.g., Fig. 9 The control plane VCN 1216 may include a service gateway 1236 and a NAT gateway 1238.
[0154] The data plane VCN 1218 may include a data plane application layer 1246 (e.g., Fig. 9 Data plane application layer 946), data plane DMZ layer 1248 (for example, Fig. 9 Data plane DMZ layer 948)), and data plane data layer 1250 (e.g., Fig. 9 The data plane DMZ layer 1248 may include (one or more) trusted application subnets 1260 (e.g., Fig.11 (one or more) trusted application subnets 1160) and (one or more) untrusted application subnets 1262 (e.g., Fig.11 The trusted application subnet(s) 1260 may be communicatively coupled to the service gateway 1236 included in the data plane VCN 1218, the NAT gateway 1238 included in the data plane VCN 1218, and the DB subnet(s) 1230 included in the data plane data layer 1250. The untrusted application subnet(s) 1262 may be communicatively coupled to the service gateway 1236 included in the data plane VCN 1218 and the DB subnet(s) 1230 included in the data plane data layer 1250. The data plane data layer 1250 may include the DB subnet(s) 1230 that may be communicatively coupled to the service gateway 1236 included in the data plane VCN 1218.
[0155] The non-trusted application subnet(s) 1262 may include primary VNICs 1264(1)-(N) that may be communicatively coupled to tenant virtual machines (VMs) 1266(1)-(N) residing within the non-trusted application subnet(s) 1262. Each tenant VM 1266(1)-(N) may run code in a corresponding container 1267(1)-(N) and may be communicatively coupled to an application subnet 1226 contained in a data plane application layer 1246 contained in a container egress VCN 1268. Corresponding secondary VNICs 1272(1)-(N) may facilitate communications between the non-trusted application subnet(s) 1262 contained in the data plane VCN 1218 and the application subnets contained in the container egress VCN 1268. The container egress VCN may include a primary VNIC 1264(1)-(N) that may be communicatively coupled to a public Internet 1254 (e.g., Fig. 9 NAT gateway 1238 for the public Internet 954).
[0156] The Internet gateway 1234 included in the control plane VCN 1216 and included in the data plane VCN 1218 can be communicatively coupled to the metadata management service 1252 (e.g., Fig. 9 1254), which metadata management service can be communicatively coupled to the public Internet 1254. The public Internet 1254 can be communicatively coupled to a NAT gateway 1238 included in the control plane VCN 1216 and included in the data plane VCN 1218. The service gateway 1236 included in the control plane VCN 1216 and included in the data plane VCN 1218 can be communicatively coupled to the cloud service 1256.
[0157] In some examples, Fig.12 The architecture model shown in block diagram 1200 can be considered as Fig.11 1100 , and may be desirable to customers of the IaaS provider if the IaaS provider cannot communicate directly with the customer (e.g., in a disconnected region). The customer may access the corresponding container 1267(1)-(N) contained in each customer's VM 1266(1)-(N) in real time. The container 1267(1)-(N) may be configured to make calls to the corresponding secondary VNIC 1272(1)-(N) contained in the application subnet(s) 1226 of the data plane application layer 1246, which may be contained in the container egress VCN 1268. The secondary VNIC 1272(1)-(N) may transmit the call to the NAT gateway 1238, which may transmit the call to the public Internet 1254. In this example, containers 1267(1)-(N), which may be accessed by customers in real time, may be isolated from control plane VCN 1216 and may be isolated from other entities contained in data plane VCN 1218. Containers 1267(1)-(N) may also be isolated from resources from other customers.
[0158] In other examples, a customer may use containers 1267(1)-(N) to call cloud service 1256. In this example, a customer may run code in containers 1267(1)-(N) to request a service from cloud service 1256. Containers 1267(1)-(N) may transmit the request to secondary VNICs 1272(1)-(N), which may transmit the request to a NAT gateway, which may transmit the request to public Internet 1254. Public Internet 1254 may transmit the request to LB subnet(s) 1222 contained in control plane VCN 1216 via Internet gateway 1234. In response to determining that the request is valid, LB subnet(s) may transmit the request to application subnet(s) 1226, which may transmit the request to cloud service 1256 via service gateway 1236.
[0159] It should be appreciated that the IaaS architectures 900, 1000, 1100, 1200 depicted in the various figures may have other components in addition to those depicted. In addition, the embodiments shown in the various figures are merely some examples of cloud infrastructure systems that may be combined with embodiments of the present disclosure. In some other embodiments, the IaaS system may have more or fewer components than shown in the various figures, may combine two or more components, or may have a different configuration or component arrangement.
[0160] In certain embodiments, the IaaS system described herein may include application suites, middleware, and database service offerings delivered to customers in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. An example of such an IaaS system is Oracle Cloud Infrastructure (OCI) provided by the present assignee.
[0161] Fig.13 An example computer system 1300 is illustrated in which various embodiments may be implemented. System 1300 may be used to implement any of the computer systems described above. As shown, computer system 1300 includes a processing unit 1304 that communicates with multiple peripheral subsystems via a bus subsystem 1302. These peripheral subsystems may include a processing acceleration unit 1306, an I / O subsystem 1308, a storage subsystem 1318, and a communication subsystem 1324. Storage subsystem 1318 includes a tangible computer-readable storage medium 1322 and a system memory 1310.
[0162] The bus subsystem 1302 provides a mechanism for the various components and subsystems of the computer system 1300 to communicate with each other as intended. Although the bus subsystem 1302 is schematically shown as a single bus, alternative embodiments of the bus subsystem can utilize multiple buses. The bus subsystem 1302 can be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of various bus architectures. For example, such an architecture can include an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an enhanced ISA (EISA) bus, a video electronics standard association (VESA) local bus, and a peripheral component interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured by the IEEE P1386.1 standard.
[0163] The processing unit 1304, which may be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of the computer system 1300. One or more processors may be included in the processing unit 1304. These processors may include single-core or multi-core processors. In some embodiments, the processing unit 1304 may be implemented as one or more independent processing units 1332 and / or 1334, wherein a single-core or multi-core processor is included in each processing unit. In other embodiments, the processing unit 1304 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.
[0164] In various embodiments, the processing unit 1304 can execute various programs in response to the program code and can maintain multiple concurrently executed programs or processes. At any given time, some or all of the program code to be executed may reside in (one or more) processors 1304 and / or in the storage subsystem 1318. Through appropriate programming, (one or more) processors 1304 can provide the various functions described above. The computer system 1300 can additionally include a processing acceleration unit 1306, which can include a digital signal processor (DSP), a special processor, and the like.
[0165] I / O subsystem 1308 may include user interface input devices and user interface output devices. User interface input devices may include keyboards, pointing devices such as mice or trackballs, touch pads or touch screens incorporated into displays, scroll wheels, click wheels, dials, buttons, switches, keyboards, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and / or gesture recognition devices, such as Microsoft Kinect® motion sensors, which enable users to control input devices such as Microsoft Xbox® 360 game controllers and interact with them through natural user interfaces using gestures and voice commands. User interface input devices may also include eye gesture recognition devices, such as Google Glass® blink detectors that detect eye activity from users (e.g., "blinking" when taking photos and / or making menu selections) and convert eye gestures into inputs in input devices (e.g., Google Glass®). In addition, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigators) through voice commands.
[0166] User interface input devices may also include, but are not limited to, three-dimensional (3D) mice, joysticks or pointing sticks, game panels and drawing tablets, and audio / video devices such as speakers, digital cameras, digital video cameras, portable media players, webcams, image scanners, fingerprint scanners, barcode readers 3D scanners, 3D printers, laser rangefinders, and eye tracking devices. In addition, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, positron emission tomography, medical ultrasound equipment. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments, etc.
[0167] The user interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat panel device such as using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, etc. In general, the use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from the computer system 1300 to a user or other computers. For example, the user interface output devices may include, but are not limited to, various display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, car navigation systems, plotters, voice output devices, and modems.
[0168] Computer system 1300 may include a storage subsystem 1318 containing software elements, shown currently located in system memory 1310. System memory 1310 may store program instructions that may be loaded and executed on processing unit 1304, as well as data generated during execution of these programs.
[0169] Depending on the configuration and type of computer system 1300, system memory 1310 may be volatile (such as random access memory (RAM)) and / or non-volatile (such as read-only memory (ROM), flash memory, etc.). RAM typically contains data and / or program modules that are immediately accessible to and / or currently being operated and executed by processing unit 1304. In some implementations, system memory 1310 may include a variety of different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM). In some implementations, a basic input / output system (BIOS), such as one containing basic routines that help transfer information between elements of computer system 1300 during startup, may typically be stored in ROM. By way of example, but not limitation, system memory 1310 also illustrates application programs 1312 that may include client applications, web browsers, middle-tier applications, relational database management systems (RDBMS), etc., program data 1314, and operating system 1316. As examples, operating system 1316 may include various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux operating systems, various commercially available UNIX® or UNIX-like operating systems (including but not limited to various GNU / Linux operating systems, Google Chrome® operating system, etc.), and / or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® OS, and Palm® OS operating systems.
[0170] Storage subsystem 1318 may also provide a tangible computer-readable storage medium for storing basic programming and data structures that provide the functionality of some embodiments. Software (programs, code modules, instructions) that provide the above-described functionality when executed by the processor may be stored in storage subsystem 1318. These software modules or instructions may be executed by processing unit 1304. Storage subsystem 1318 may also provide a repository for storing data used in accordance with the present disclosure.
[0171] The storage subsystem 1318 may also include a computer-readable storage media reader 1320, which may be further connected to a computer-readable storage media 1322. Together with the system memory 1310 and, optionally, in conjunction therewith, the computer-readable storage media 1322 may comprehensively represent remote, local, fixed, and / or removable storage devices plus storage media for temporarily and / or more permanently containing, storing, transmitting, and retrieving computer-readable information.
[0172] The computer-readable storage medium 1322 containing the code or portions of the code may also include any suitable media known or used in the art, including storage media and communication media, such as, but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and / or transmission of information. This may include tangible computer-readable storage media, such as RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer-readable media. This may also include non-tangible computer-readable media, such as data signals, data transmissions, or any other media that can be used to send the desired information and can be accessed by the computing system 1300.
[0173] As an example, the computer-readable storage medium 1322 may include a hard disk drive that reads or writes from a non-removable non-volatile magnetic medium, a magnetic disk drive that reads or writes from a removable non-volatile magnetic disk, and an optical disk drive that reads or writes from a removable non-volatile optical disk (such as a CD ROM, a DVD, and a Blu-Ray® disk or other optical media). The computer-readable storage medium 1322 may include, but is not limited to, a Zip® drive, a flash memory card, a universal serial bus (USB) flash drive, a secure digital (SD) card, a DVD disk, a digital audio tape, and the like. The computer-readable storage medium 1322 may also include a solid-state drive (SSD) based on non-volatile memory (such as an SSD based on flash memory, an enterprise flash drive, a solid-state ROM, etc.), an SSD based on volatile memory (such as a solid-state RAM, a dynamic RAM, a static RAM), a DRAM-based SSD, a magnetoresistive RAM (MRAM) SSD, and a hybrid SSD using a combination of SSDs based on DRAM and flash memory. The disk drives and their associated computer-readable media may provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer system 1300 .
[0174] The communication subsystem 1324 provides an interface to other computer systems and networks. The communication subsystem 1324 is used as an interface for receiving data from other systems and sending data from the computer system 1300 to other systems. For example, the communication subsystem 1324 can enable the computer system 1300 to connect to one or more devices via the Internet. In some embodiments, the communication subsystem 1324 may include a radio frequency (RF) transceiver component for accessing a wireless voice and / or data network (e.g., using cellular phone technology, advanced data network technology such as 3G, 4G or EDGE (Enhanced Data Rates for Global Evolution), WiFi (IEEE 802.11 family of standards), or other mobile communication technologies, or any combination thereof), a global positioning system (GPS) receiver component, and / or other components. In some embodiments, as an addition or alternative to a wireless interface, the communication subsystem 1324 may provide a wired network connection (e.g., Ethernet).
[0175] In some embodiments, communication subsystem 1324 may also receive incoming communications in the form of structured and / or unstructured data feeds 1326 , event streams 1328 , event updates 1330 , and the like on behalf of one or more users who may use computer system 1300 .
[0176] As an example, the communication subsystem 1324 can be configured to receive data feeds 1326 in real time from users of a social network and / or other communication service, such as Twitter® feeds, Facebook® updates, web feeds such as Rich Site Summary (RSS) feeds, and / or real-time updates from one or more third-party information sources.
[0177] Additionally, the communication subsystem 1324 may also be configured to receive data in the form of a continuous data stream, which may include event streams 1328 and / or event updates 1330, which may be continuous or unbounded in nature, real-time events without explicit termination. Examples of applications that generate continuous data may include, for example, sensor data applications, financial quote machines, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automotive traffic monitoring, and the like.
[0178] The communication subsystem 1324 may also be configured to output structured and / or unstructured data feeds 1326 , event streams 1328 , event updates 1330 , etc. to one or more databases that may be in computer communication with one or more streaming data source computers coupled to the computer system 1300 .
[0179] Computer system 1300 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google® Glass head-mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.
[0180] Due to the ever-changing nature of computers and networks, the description of the computer system 1300 drawn in the figure is only intended to be a specific example. It is possible to have many other configurations with more or less parts than the system drawn in the figure. For example, customized hardware may also be used and / or specific elements may be realized with hardware, firmware, software (comprising Applets) or a combination thereof. In addition, the connection to other computing devices such as network input / output devices may also be adopted. Based on the disclosure and teachings provided herein, those of ordinary skill in the art will recognize other ways and / or methods for realizing various embodiments.
[0181] Although specific embodiments have been described, various modifications, variations, alternative constructions, and equivalents are also included within the scope of this disclosure. Embodiments are not limited to operating within certain specific data processing environments, but can be freely operated within multiple data processing environments. In addition, although embodiments have been described using a specific series of transactions and steps, it should be clear to those skilled in the art that the scope of this disclosure is not limited to the described series of transactions and steps. The various features and aspects of the above-described embodiments may be used alone or in combination.
[0182] In addition, although the embodiments have been described using a specific combination of hardware and software, it should be appreciated that other combinations of hardware and software are also within the scope of the present disclosure. The embodiments may be implemented using only hardware, or only software, or using a combination thereof. The embodiments may be implemented using a computer program product, which includes a computer program / instruction that causes the processor to perform any method described in the present disclosure when executed by a processor. The various processes described herein may be implemented in any combination on the same processor or on different processors. Accordingly, in the case where a component or module is described as being configured to perform certain operations, such configuration may be accomplished by, for example, designing an electronic circuit to perform the operation, by programming a programmable electronic circuit (such as a microprocessor) to perform the operation, or any combination thereof. Processing may communicate using a variety of techniques, including but not limited to conventional techniques for inter-processing communication, and different processing pairs may use different techniques, or the same pair of processing may use different techniques at different times.
[0183] Accordingly, the description and drawings are to be regarded as illustrative rather than restrictive. However, additions, subtractions, deletions and other modifications and changes may be made thereto without departing from the broader spirit and scope set forth in the claims. Therefore, although specific disclosed embodiments have been described, these are not intended to be limiting. Various modifications and equivalent forms are within the scope of the following claims.
[0184] The use of the terms "a" and "an" and "the" and similar references in the context of describing the disclosed embodiments (especially in the context of the following claims) is to be interpreted as covering the singular and the plural, unless otherwise indicated herein or clearly contradicted by the context. Unless otherwise stated, the terms "include", "have", "include (including)" and "include (containing)" are to be interpreted as open terms (i.e., meaning "including but not limited to"). The term "connected" should be interpreted as partially or completely contained in, attached to or connected together, even if there are something in the middle. Unless otherwise indicated herein, the enumeration of value ranges herein is intended only to be used as a shorthand method of individually referencing each individual value falling within the range, and each individual value is incorporated into the specification as if it were individually listed herein. Unless otherwise indicated herein or clearly contradicted by the context, all methods described herein can be performed in any suitable order. The use of any and all examples or exemplary language (e.g., "such as") provided herein is intended only to better illustrate the embodiments and does not limit the scope of the present disclosure unless otherwise stated. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.
[0185] Disjunctive language, such as the phrase "at least one of X, Y, or Z," is intended to be understood in the context generally used to indicate that an item, term, or the like, can be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z), unless expressly stated otherwise. Thus, such disjunctive language is generally not intended to, and should not, imply that certain embodiments require that at least one of X, at least one of Y, or at least one of Z each be present.
[0186] Preferred embodiments of the present disclosure are described herein, including the best mode known for implementing the present disclosure. Variations of those preferred embodiments will become apparent to those of ordinary skill in the art after reading the above description. Those of ordinary skill should be able to appropriately adopt such variations and may practice the present disclosure in a manner different from that specifically described herein. Accordingly, the present disclosure includes all modifications and equivalent forms of the subject matter recorded in the appended claims where permitted by applicable law. In addition, unless otherwise indicated herein, the present disclosure includes any combination of the above-mentioned elements in all possible variations thereof.
[0187] All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.
[0188] In the foregoing description, various aspects of the present disclosure are described with reference to their specific embodiments, but those skilled in the art will appreciate that the present disclosure is not limited thereto. Each feature and aspect disclosed above can be used alone or in combination. In addition, without departing from the broader spirit and scope of this specification, the embodiment can be used in any number of environments and applications other than those described herein. Accordingly, this specification and the accompanying drawings should be considered illustrative rather than restrictive.
Claims
1. One or more non-transitory computer-readable media having instructions stored thereon that, when executed by a computing system, cause the computing system to: receiving a request to perform an action from a client device, the request comprising an identifier of the client device and an action to be performed by the security entity; determining a subscriber corresponding to the client device based at least in part on the identifier of the client device; determining that the subscriber has provided authorization to the client device for performance of the action; generating a credential for accessing the secure entity on behalf of the client device based at least in part on a determination that the client device has authorization for performance of the action; maintaining the credential separately from the client device; as well as The credential is utilized on behalf of the client device to perform the action.
2. The one or more non-transitory computer-readable media of claim 1, wherein the computing system and the security entity are located within a trusted environment, and wherein maintaining the credential separately from the client device comprises maintaining the credential within the trusted environment.
3. One or more non-transitory computer-readable media according to claim 1 or claim 2, wherein determining that the subscriber has provided authorization for the performance of the action include: determining that the subscriber has provided one or more actions of authorization to the client device; as well as The act of determining the request indication is included in the one or more actions.
4. One or more non-transitory computer-readable media according to any preceding claim, wherein generating the credential comprises generating the credential using a key corresponding to the security entity.
5. One or more non-transitory computer readable media according to claim 4, in, The instructions, when executed by the computing system, further cause the computing system to: Determining that the validity period of the key has expired; refreshing, with the security entity, the key based at least in part on determining that the validity time of the key has expired; as well as The refreshed key is maintained separately from the client device.
6. One or more non-transitory computer readable media as claimed in any preceding claim, in, The instructions, when executed by the computing system, also cause the computing system to implement an agent at the edge of the security entity, wherein the agent of the computing system is used to generate the credentials, maintain the credentials separately from the client device, and utilize the credentials on behalf of the client device to perform the action.
7. The one or more non-transitory computer-readable media of claim 6, wherein the security entity is an enclave of the computing system.
8. One or more non-transitory computer-readable media as claimed in any preceding claim, wherein the credential is utilized to perform the action include: providing the credentials to the security entity to obtain access rights to the security entity; as well as The security entity is requested to perform the action.
9. A computing system, include: A memory for storing one or more credentials; as well as One or more processors, coupled to the memory, the one or more processors: receiving a request for an action to be performed by a security entity, the request being received from a client device; determining a subscriber corresponding to the client device based at least in part on an identifier of the client device; determining that the subscriber has provided authorization to the client device for performance of the action; generating credentials for accessing the secure entity based at least in part on determining that the subscriber has provided authorization to the client device for performance of the action; storing the credentials in the memory, the credentials being stored separately from the client device; as well as The credential is utilized on behalf of the client device to perform the action.
10. The computing system of claim 9, wherein the one or more processors further retrieve a key from the security entity, wherein generating the credential comprises generating the credential based at least in part on the key.
11. The computing system of claim 10, wherein the one or more processors further: determining that the validity period of the key has expired; and Based at least in part on determining that the validity time of the key has expired, refreshing the key with the security entity.
12. The computing system of any one of claims 9 to 11, wherein determining that the subscriber has provided authorization to the client device for the performance of the action include: determining that the subscriber has provided one or more actions of authorization to the client device; as well as Determining that the action is included in the one or more actions.
13. The computing system of claim 12, wherein the credential is associated with the one or more actions.
14. A computing system according to any one of claims 9 to 13, wherein the action comprises entering a billing record, and wherein the credential is used to perform the action include: providing the credentials to the security entity to obtain access rights to the security entity; as well as The security entity is caused to input the billing record.
15. The computing system of any one of claims 9 to 14, wherein the computing system comprises a cloud infrastructure service, wherein the secure entity comprises an enclave within the cloud infrastructure service, wherein the one or more processors further implement an agent at an edge of the enclave, and wherein the agent of the computing system generates the credential for accessing the secure entity and utilizes the credential for performing the action.
16. A method for performing an action using a security entity, include: receiving, by the agent, from a client device, a request for an action to be performed by the security entity; determining, by the agent, that the client device is authorized to perform the action; generating, by the agent, credentials for accessing the secure entity based at least in part on determining that the client device is authorized to perform the action; and The credential is utilized by the agent on behalf of the client device to cause the security entity to perform the action.
17. The method of claim 16, wherein the security entity and the proxy are located within a trusted environment, wherein the client device is located outside the trusted environment, and wherein the method further comprises maintaining, by the proxy, the credentials within the trusted environment.
18. The method of claim 16 or claim 17, wherein the secure entity comprises an enclave of a computing system, and wherein receiving the request to perform the action comprises receiving, by the agent, the request to perform the action at an edge of the enclave.
19. The method of any one of claims 16 to 18, further comprising retrieving, by the agent, a key from the security entity, wherein the credential is generated based at least in part on the key.
20. The method according to claim 19, further comprising: include: Determining, by the agent, that the validity period of the key has expired; as well as Based at least in part on determining that the validity time of the key has expired, refreshing the key by the agent with the security entity.
