Tenant lockbox

Abstract

Tenant approval for operator access to tenant data is provided. In order to grant service personnel operators access to a tenant's data for performing a requested action, a lockbox determines a security group role to which an operator needs to be elevated to perform a requested action, computes a set of internal administrators and tenant administrators authorized to grant a temporary role elevation, and sends an access control request to the administrators. Upon receiving approval of the access control request from an internal administrator and a tenant administrator, the lockbox elevates the operator to the security group role, granting the operator a set of permissions needed in order to allow the operator to perform the requested action. Accordingly, tenants are enabled to control access to their data and scrutinize access requests per their company procedures and compliance needs.

Description

BACKGROUND

There are various scenarios in which support personnel need access to customer data for benefit of the customer, for example, when making a change in a system as a corrective action, or to perform invasive debugging of customer-specific issues. When accessing customer data, whether on-premise or on the cloud, there is a need for security measures. For example, in a Software as a Service (SaaS) or cloud service system, business-critical customer data is oftentimes stored in the cloud, where customers do not have complete control over access to their data. For example, various administrators, engineers, and other support personnel of the cloud service provider can gain access to customer's data via access control systems that are not controlled by the customer. Accordingly, such access to customer data that is invisible to customers subjects cloud service providers to increased scrutiny by customers, for example, customers may be concerned about why cloud service personnel are accessing customer data, how often cloud service personnel are accessing customer data, what level of background clearance and personnel standards are being required to access customer data, etc.

It is with respect to these and other considerations that examples have been made.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description section. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Aspects of the present disclosure are directed to providing tenant approval for operator access to tenant data. In order to provide a service personnel, herein referred to as an operator, permissions for granting the operator a temporary role elevation and allowing access to a tenant's data for performing a requested action, a lockbox computes the role needed by the operator for performing the requested action, a set of one or more internal administrators who are authorized to grant a temporary role elevation to the operator, and a set of one or more tenant administrators who are authorized to grant permission to allow the operator access to the tenant's data, and sends an access control request to the one or more internal and tenant administrators. Upon receiving an approval of the access control request from an internal administrator and a tenant administrator, the lockbox temporarily elevates the operator to the role, giving the operator a set of permissions to allow the operator to perform the requested action. According to aspects of the present disclosure, increased security is provided by enabling tenants to control access to their data and scrutinize access requests per their company procedures and compliance needs.

Examples may be implemented as a computer process, a computing system, or as an article of manufacture such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The details of one or more aspects are set forth in the accompanying drawings and description below. Other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that the following detailed description is explanatory only and is not restrictive of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various aspects of the present invention. In the drawings:

FIG. 1 is a simplified block diagram of one example of a tenant lockbox system;

FIG. 2 is an illustration of an example user interface including an access control request;

FIG. 3 is a flowchart of an example method for providing tenant approval for operator access to tenant data;

FIG. 4 is a block diagram illustrating example physical components of a computing device with which aspects of the invention may be practiced;

FIGS. 5A and 5B are simplified block diagrams of a mobile computing device with which aspects of the present invention may be practiced; and

FIG. 6 is a simplified block diagram of a distributed computing system in which aspects of the present invention may be practiced.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While aspects of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention, but instead, the proper scope of the invention is defined by the appended claims. Examples may take the form of a hardware implementation, or an entirely software implementation, or an implementation combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.

Aspects of a tenant lockbox system provide tenant-approval within an approval chain for workflow processes that grant service personnel access to the tenant's data. Accordingly, tenants are enabled to control access to their data, and scrutinize access request per their company procedures and compliance needs.

FIG. 1 is a simplified block diagram of one example of a tenant lockbox system 100. According to an aspect, components of the tenant lockbox system 100 operate as a distributed system, where each component is accessed via a suitable network. According to another aspect, various components of the system operate together as an integrated system. As illustrated, the tenant lockbox system 100 includes a server 112 comprising a lockbox engine 120, a plurality of software services 114A-N (collectively 114), and a plurality of tenant data storage components 116A-N (collectively 116). According to an aspect, the server 112 is operable to execute a plurality of other application and/or services that are not illustrated in FIG. 1.

According to an aspect, the software services 114 include one or more on-premise services, for example, where software applications are hosted in an on-premises data center (i.e., server 112). According to another aspect, the software services 114 include one or more cloud or web services. For example, a cloud service generally refers to a hosted service providing scalable processing and storage capabilities. For example, a cloud service oftentimes includes virtualized resources, such as a multi-tenant application server 118. The resources presented by cloud computing are provided as a service, where cloud computing customers rent usage of the resources (e.g., tenant data storage components 116) from a third-party provider that owns the physical infrastructure. As used herein, a client organization that is served by a cloud service and shares resources controlled or managed by the cloud service with other client organizations is referred to as a tenant 136.

According to an aspect, a web service is provided by or hosted by a cloud service. For example, a web service is a software system that supports interoperable machine-to-machine interaction over a network 110, and enables software to connect to other software applications. Tenant users 102 have access to application software and databases on the cloud, which manage infrastructures and platforms. Tenant users 102 are enabled to access the cloud service via entering a uniform resource locator (URL) in a browser application on client device 138. According to an aspect, when using a cloud service, a limited amount of data may be stored on the client device 138. Instead, data is stored on the infrastructure, “the cloud,” (e.g., in tenant data storage components 116).

According to an aspect, the client device 138 includes any suitable computing device such as a desktop computer, laptop computer, tablet-style computer, handheld computing device, mobile communication device, gaming device, and the like. According to an aspect, the network 110 can include, but is not limited to, a cellular network (e.g., wireless phone), a point-to-point dial up connection, a satellite network, the Internet, a local area network (LAN), a wide area network (WAN), a WiFi network, an ad hoc network or a combination thereof. The network may include one or more connected networks (e.g., a multi-network environment) including public networks, such as the Internet, and/or private networks such as a secure enterprise private network. Access to the network 110 may be provided via one or more wired or wireless access networks as is understood by those skilled in the art.

According to an aspect, administrative access to systems used to provide software services 114 to tenants 136 are regulated to ensure there is no unauthorized access or exposure to user data. By default, service personnel, including operators 106 such as on-call engineers (OCEs) and one or more administrators 108A-N (collectively 108), who have access to operate the service, debug issues, or respond to escalations and incidents in the system are provided with configuration view-only permissions. At times, elevated access by the operator 106 is needed, for example, when making a change in the system as a corrective action or to perform invasive debugging of customer-specific issues. In order to get authorization for accessing servers 118 or tenant data 116, the operator 106 submits an access control request to the lockbox engine 120 that identifies the operator 106, the action that the operator 106 wants to perform, and the tenant 136 for whom the action is being performed.

As illustrated, the lockbox engine 120 comprises a request creation module 122 operable to create an access control request for elevating the operator 106 to a role that allows the operator to view or access tenant data 116. According to an aspect, the request creation module 122 determines an appropriate role corresponding to a security group that is configured with a set of permissions to run certain actions in a data center. The determination is made according to the action that the operator 106 wants to perform and the tenant 136 for whom the action is being performed. According to an aspect, the lockbox engine 120 comprises a request storage component 124 operable to store access control requests.

As illustrated in FIG. 1, the lockbox engine 120 further comprises a request authentication and authorization module 126 operable to pull an access control request from the request storage component 124, and perform authentication and authorization based on client certificates. Upon successful authentication, the request authentication and authorization module 126 is further operable to determine a correct service or workload, and to perform request validation. According to an aspect, the request authentication and authorization module 126 is operable to check a set of permission policies to determine if the access control request can be automatically approved. If the access control request can be automatically approved, the request authentication and authorization module 126 is operable to approve the request and add the requesting operator 106 into a role-based access control configuration scoped to the tenant 136 or tenant user 102. If the access control request cannot be automatically approved, the request authentication and authorization module 126 is operable to compute a set of one or more internal decision-makers or administrators 108 who have authorization to grant a temporary role elevation to the operator 106. According to an aspect, an internal administrator 108 is an individual in the operator's organization designated with authorization status according to a management hierarchy, role in the organization, or other determining factor. According to an aspect, the request authentication and authorization module 126 makes an API call to a relational database 140 to query the relational database 140 for the set of internal administrators 108 for the operator 106 and the requested role.

As illustrated, the lockbox engine 120 comprises a request notification and response module 128 operable to send the request to the one or more internal administrators 108 computed by the request authentication and authorization module 126. The request notification and response module 128 is operable to send the request via various methods, for example, the request can be sent via email, SMS text message, MMS text message, or other notification method. According to an aspect, the request comprises a link to an application interface via which an internal administrator 108 can approve or reject the request. According to another aspect, the request is provided to the one or more administrators 108 via an application interface. The one or more internal administrators 108 are enabled to log into the server 112 to approve or reject the request. According to an aspect, the request notification and response module 128 is further operable to receive a response from an internal administrator 108, and to communicate the approval or rejection of the request to the request authentication and authorization module 126.

After the request has been internally approved (e.g., by an internal administrator 108), the request authentication and authorization module 126 computes eligibility of the tenant user 102 for a second level of approval. According to an aspect, the request authentication and authorization module 126 parses a mailbox where the tenant data 116 is stored for a Boolean flag that indicates whether the tenant 136 has opted-in to the tenant lockbox feature. If the flag is set to on, the tenant 136 has opted-in to the tenant lockbox feature and permission from the tenant 136 is required for accessing the tenant's data 116. The request authentication and authorization module 126 is further operable to determine a set of decision-makers or tenant administrators 104A-N (collectively, 104) of a security group within the tenant 136 organization who are authorized to grant permission to the operator 106 to access the tenant's data 116 for performing the requested action. According to an aspect, a service administrator can delegate one or more users from the tenant 136 organization as tenant administrators 104. The request authentication and authorization module 126 is operable to query for the set of tenant administrators 104, for example, in an online directory service, and obtain contact information, such as email addresses, of the one or more tenant administrators 104.

Upon determining the one or more tenant administrators 104 for the access control request, the request notification and response module 128 is further operable to send the request to the one or more tenant administrators 104 computed by the request authentication and authorization module 126. The request notification and response module 128 is operable to send the request via various methods, for example, via email, SMS text message, MMS message, or other notification method. According to an aspect, the request comprises a link to an application interface via which a tenant administrator 104 can approve or reject the request. According to another aspect, tenant administrators 104 are enabled to log into the server 112 via an application programming interface (API) 134 to approve or reject the request. The request notification and response module 128 is further operable to receive a response from a tenant administrator 104, and to communicate the approval or rejection of the request to the request authentication and authorization module 126. According to an aspect, the request notification and response module 128 notifies the requesting operator 106 of the approval or rejection of the access control request. After the access control request has been approved by a tenant administrator 104, the request authentication and authorization module 126 is operable to add the requesting operator 106 into a role-based access control (RBAC) configuration scoped to the tenant 136 or tenant user 102, giving the operator 106 a set of permissions to access the tenant's data 116 and perform the requested actions.

As illustrated in FIG. 1, the lockbox engine 120 further comprises a record module 130 operable to create a log entry of the access control request. According to an aspect, the log entry comprises information such as, but not limited to: the requesting operator 106; a timestamp of the request; a reason for the request; whether the access control request resulted in an automatic approval; if the access control request did not result in an automatic approval; the one or more internal administrators 108 and the one or more tenant administrators 104; whether an access control request was rejected; the role temporarily assigned to the operator 106, and a record of data accessed by the requesting operator 106 while the elevated permissions were in force.

With reference now to FIG. 2, an example user interface 200 for viewing access control requests and via which an internal administrator 108 or a tenant administrator 104 can act on an access control request is shown. For example, the example user interface 200 can be exposed to an internal administrator 108 or a tenant administrator 104 via the API 134. As illustrated, the user interface 200 comprises a display of data access or access control requests 202 for an internal administrator 108 or a tenant administrator 104. According to an aspect, each access control request 202 includes a request creation timestamp 204 of the request. According to another aspect, each access control request 202 includes a reason 206 for the request. According to another aspect, each access control request 202 includes an action status 208 of the request, for example, whether the access control request 202 is pending approval or rejection or whether the access control request 202 is complete. According to another aspect, if an access control request 202 has been approved or rejected, the access control request 202 includes a request action timestamp 210, for example, a date and time of when the access control request 202 was approved or rejected. According to another aspect, each access control request 202 includes a request completion timestamp 212, for example, a date and time of when the work was completed for which the access control request 202 was created. According to another aspect, if an approval action 214 is pending, the access control request 202 includes a selectable approval action control 216 and a selectable rejection action control 218, which when selected, sends an approval or rejection response to the lockbox engine 120.

With reference now to FIG. 3, a flow chart of an example method 300 for providing tenant approval for operator access to tenant data 116 is illustrated. The method 300 starts at OPERATION 302, and advances to OPERATION 304, where an operator 106 needs authorization for accessing tenant data 116 for performing a certain action or operation, for example, to run a debugging trace on a process associated with software service 114. To protect the privacy of tenant data 116, such access may not be always available to operators 106 associated with server 112. Such operators 106 may be limited to basic access permissions, such as viewing log data or configuration information, and access to tenant data 116 is prohibited. At OPERATION 304, the request creation module 122 receives a request from an operator 106 for elevation to a role that allows the operator 106 to view or access tenant data 116 for performing the action or operation. For example, the operator 106 selects to create an access control request 202 via an administrative console or application interface. According to an aspect, the request includes a tenant identifier and a reason for accessing the tenant data 116. Upon receiving an indication to create a request for a role elevation, the request creation module 122 determines where the tenant 136 is provisioned (e.g., server forest, data center, server, etc.) via referencing a command list, determines a role corresponded to a security group that would give the operator 106 the set of permissions needed to perform the action or operation, creates an access control request 202 to temporarily elevate the operator 106 to the determined role, and stores the request 202 in a storage compartment 124.

The method 300 advances to OPERATION 305, where the request authentication and authorization module 126 authorizes the access control request 202. For example, the authentication and authorization module 126 determines a current role of the requesting operator 106 and the requested role of the operator 106, and determines whether elevation to the requested role from the current role complies with at least one of a plurality of policies associated with the lockbox engine 120.

The method 300 advances to DECISION OPERATION 306, where a determination is made as to whether the access control request 202 can be automatically approved. According to an aspect, the request authentication and authorization module 126 determines whether the access control request 202 complies with at least one of a plurality of permission policies associated with a lockbox service. For example, the access control request 202 may be checked for compliance with at least one permission policy of plurality of permission policies. According to an aspect, such policies comprise checks for factors such as a user group criterion, a security flag criterion, an action scope criterion, and a schedule criterion. For example, an operator 106 may belong to an “onsite” user group that allows greater automated elevation of permissions than an operator 106 accessing server 112 from offsite.

If a determination is made that the access control request 202 can be automatically approved at DECISION OPERATION 306, the method 300 advances to OPERATION 308, where the request authentication and authorization module 126 grants the elevated permission to the operator 106. For example, the request authentication and authorization module 126 may elevate the permissions allocated to the operator 106 in order to allow the operator 106 to perform a requested action. According to an aspect, the elevation is for a limited duration that is defined, for example, by the permission policy, by a configuration setting associated with the software service, or by a configuration setting associated with a user group. According to an aspect, such permissions may comprise a set of permissions associated with a task, such as the need to modify overall configuration data for server 112 and restart several core services (e.g., network and/or user management services) in order to install a new software service into production.

After elevating the operator's permissions at OPERATION 308, the method 300 advances to OPERATION 310, where the operator 106 performs the requested action. For example, the operator 106 may perform a debugging trace as allowed by the newly elevated permissions.

The method 300 advances to OPERATION 312, where the record module 130 creates a log entry of the access control request 202. According to an aspect, the log entry comprises information about whether the access control request 202 resulted in automatic approval of elevation of the operator's 106 permissions. According to another aspect, the log entry further comprises a record of the role to which the operator 106 was temporarily elevated and the tenant data 116 accessed by the operator 106 while the elevated permissions were in force.

The method 300 advances to OPERATION 314, where the record module 130 provides an audit report. For example, an administrator or tenant 136 personnel (e.g., tenant user 102, tenant administrator(s) 104, etc.) may be provided with an audit report comprising a list of all operators 106 who have been granted elevated permissions that allow access to tenant data 116.

Referring back to DECISION OPERATION 306, if the access control request 202 is determined not to comply with the permission policies for automatic approval, the method 300 advances to OPERATION 316, where the request authentication and authorization module 126 computes a set of internal administrators 108 in an organizational hierarchy of the operator 106 who are authorized to grant a temporary role elevation to the operator 106. According to an aspect, the request authentication and authorization module 126 determines the set of one or more internal administrators 108 for the access control request 202 according to the requesting operator 106, the role requested by the operator 106, and the schedules and rotations of the operator's administrators 108.

The method 300 advances to OPERATION 318, where the record module 130 sends the access control request 202 to the one or more internal administrators 108. For example, the access control request 202 is sent to the one or more internal administrators 108 via an email, a text message, notification, or via an application interface. The method 300 advances to OPERATION 320, where the request notification and response module 128 receives a response from one of the one or more internal administrators 108. For example, an internal administrator 108 may accept or reject an access control request 202 via a selection of the approval action control 216 or the rejection action control 218 displayed in the user interface 200 as illustrated in FIG. 2.

At DECISION OPERATION 322, a determination is made as to whether the response is an approval or a rejection of the access control request 202. If the response is a rejection, the method 300 advances to OPERATION 312, where a log entry is made of the access control request 202 being sent for administrator approval and of the received rejection. If the response is an approval, the method 300 advances to OPERATION 324, where the request authentication and authorization module 128 computes a set of one or more tenant administrators 104 within the tenant 136 organization who are authorized to grant permission to allow the operator 106 access to the tenant's data 116. For example, a tenant administrator 104 may be delegated by a service administrator, may be a manager of the tenant user 102, etc. According to an aspect, the request authentication and authorization module 128 obtains contact information, such as email addresses, of the one or more tenant administrators 104 from an online directory service.

The method 300 advances to OPERATION 326, where the request notification and response module 128 sends the access control request 202 to the one or more tenant administrators 104. For example, the access control request 202 is sent to the one or more tenant administrators 104 via an email, a text message, notification, or via an application interface. According to an aspect, the access control request 202 includes a reason for accessing the tenant data 116.

The method 300 advances to OPERATION 328, where the request notification and response module 128 receives a response from one of the one or more tenant administrators 104. For example, a tenant administrator 104 may accept or reject an access control request 202 via a selection of the approval action control 216 or the rejection action control 218 displayed in the user interface 200 as illustrated in FIG. 2.

At DECISION OPERATION 330, a determination is made as to whether the response is an approval or a rejection of the access control request 202. If the response is a rejection, the method 300 advances to OPERATION 312, where a log entry is made of the access control request 202 being sent for tenant approval and of the received rejection. If the response is an approval, the method 300 advances to OPERATION 308, where the request authentication and authorization module 126 temporarily elevates the operator 106 to the requested role, granting elevated permissions to the operator 106 for performing the requested action.

The method 300 advances to OPERATION where the operator 106 performs the requested action. For example, the operator 106 may perform a debugging trace as allowed by the newly elevated permissions.

The method 300 advances to OPERATION 312, where the record module 130 creates a log entry of the access control request 202. According to an aspect, the log entry comprises information about whether the access control request 202 resulted in approval of elevation of the operator's 106 permissions via the internal administrator 108 and the tenant administrator 104. According to an aspect, the log entry further comprises a record of the role to which the operator 106 was temporarily elevated and tenant data 116 accessed by the operator 106 while the elevated permissions were in force.

The method 300 advances to OPERATION 314, where the record module 130 provides an audit report. For example, an administrator or tenant 136 personnel (e.g., tenant user 102, tenant administrator(s) 104, etc.) may be provided with an audit report comprising a list of all operators 106 who have been granted elevated permissions that allow access to tenant data 116. The method 300 ends at OPERATION 398.

Aspects of the present disclosure provide a computer-implemented method, system, and computer-readable medium for providing tenant approval for operator access to a tenant's data. Aspects of the tenant lockbox system receive an indication to create an access control request for temporarily elevating a role of an operator to a security group giving the operator a set of permissions for allowing the operator to perform an action on behalf of the tenant and to enable operator access to the tenant's data; create the access control request for temporarily elevating the role of the operator; compute a set of one or more internal administrators authorized to grant a first set of permissions to temporarily elevate the role of the operator; send the access control request to the one or more internal administrators; receive an access control response from one of the one or more internal administrators; determine whether the access control response from the internal administrator is an approval or a rejection of the access control request; upon determining that the access control response from the internal administrator is an approval of the access control request, grant the first set of permissions to temporarily elevate the role of the operator; compute a set of one or more tenant administrators authorized to grant a second set of permissions to temporarily elevate the role of the operator; send the access control request to the one or more tenant administrators; receive an access control response from one of the one or more tenant administrators; determine whether the access control response from the tenant administrator is an approval or a rejection of the access control request; upon determining that the access control response from the tenant administrator is an approval of the access control request, grant the second set of permissions to temporarily elevate the role of the operator; and temporarily elevate the role of the operator to the security group giving the operator the set of permissions for allowing the operator to perform the action on behalf of the tenant and to enable operator access to the tenant's data.

While the invention has been described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computer, those skilled in the art will recognize that the invention may also be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.

The aspects and functionalities described herein may operate via a multitude of computing systems including, without limitation, desktop computer systems, wired and wireless computing systems, mobile computing systems (e.g., mobile telephones, netbooks, tablet or slate type computers, notebook computers, and laptop computers), hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, and mainframe computers.

In addition, according to an aspect, the aspects and functionalities described herein operate over distributed systems (e.g., cloud-based computing systems), where application functionality, memory, data storage and retrieval and various processing functions are operated remotely from each other over a distributed computing network, such as the Internet or an intranet. According to an aspect, user interfaces and information of various types are displayed via on-board computing device displays or via remote display units associated with one or more computing devices. For example, user interfaces and information of various types are displayed and interacted with on a wall surface onto which user interfaces and information of various types are projected. Interaction with the multitude of computing systems with which aspects of the invention are practiced include, keystroke entry, touch screen entry, voice or other audio entry, gesture entry where an associated computing device is equipped with detection (e.g., camera) functionality for capturing and interpreting user gestures for controlling the functionality of the computing device, and the like.

FIG. 4-6 and the associated descriptions provide a discussion of a variety of operating environments in which examples of the invention are practiced. However, the devices and systems illustrated and discussed with respect to FIGS. 4-6 are for purposes of example and illustration and are not limiting of a vast number of computing device configurations that are utilized for practicing aspects of the invention, described herein.

FIG. 4 is a block diagram illustrating physical components (i.e., hardware) of a computing device 400 with which examples of the present disclosure are be practiced. In a basic configuration, the computing device 400 includes at least one processing unit 402 and a system memory 404. According to an aspect, depending on the configuration and type of computing device, the system memory 404 comprises, but is not limited to, volatile storage (e.g., random access memory), non-volatile storage (e.g., read-only memory), flash memory, or any combination of such memories. According to an aspect, the system memory 404 includes an operating system 405 and one or more programming modules 406 suitable for running software applications 450. According to an aspect, the system memory 404 includes the lockbox engine 120. The operating system 405, for example, is suitable for controlling the operation of the computing device 400. Furthermore, aspects of the invention are practiced in conjunction with a graphics library, other operating systems, or any other application program, and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 4 by those components within a dashed line 408. According to an aspect, the computing device 400 has additional features or functionality. For example, according to an aspect, the computing device 400 includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 4 by a removable storage device 409 and a non-removable storage device 410.

As stated above, according to an aspect, a number of program modules and data files are stored in the system memory 404. While executing on the processing unit 402, the program modules 406 (e.g., lockbox engine 120) performs processes including, but not limited to, one or more of the stages of the method 300 illustrated in FIG. 3. According to an aspect, other program modules are used in accordance with examples of the present invention and include applications such as electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.

According to an aspect, aspects of the invention are practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For example, aspects of the invention are practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in FIG. 4 are integrated onto a single integrated circuit. According to an aspect, such an SOC device includes one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which are integrated (or “burned”) onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality, described herein, is operated via application-specific logic integrated with other components of the computing device 400 on the single integrated circuit (chip). According to an aspect, aspects of the present disclosure are practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, aspects of the invention are practiced within a general purpose computer or in any other circuits or systems.

According to an aspect, the computing device 400 has one or more input device(s) 412 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. The output device(s) 414 such as a display, speakers, a printer, etc. are also included according to an aspect. The aforementioned devices are examples and others may be used. According to an aspect, the computing device 400 includes one or more communication connections 416 allowing communications with other computing devices 418. Examples of suitable communication connections 416 include, but are not limited to, RF transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, and/or serial ports.

The term computer readable media as used herein include computer storage media. Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, or program modules. The system memory 404, the removable storage device 409, and the non-removable storage device 410 are all computer storage media examples (i.e., memory storage.) According to an aspect, computer storage media includes RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other article of manufacture which can be used to store information and which can be accessed by the computing device 400. According to an aspect, any such computer storage media is part of the computing device 400. Computer storage media does not include a carrier wave or other propagated data signal.

According to an aspect, communication media is embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. According to an aspect, the term “modulated data signal” describes a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.

FIGS. 5A and 5B illustrate a mobile computing device 500, for example, a mobile telephone, a smart phone, a tablet personal computer, a laptop computer, and the like, with which aspects of the invention may be practiced. With reference to FIG. 5A, an example of a mobile computing device 500 for implementing the aspects is illustrated. In a basic configuration, the mobile computing device 500 is a handheld computer having both input elements and output elements. The mobile computing device 500 typically includes a display 505 and one or more input buttons 510 that allow the user to enter information into the mobile computing device 500. According to an aspect, the display 505 of the mobile computing device 500 functions as an input device (e.g., a touch screen display). If included, an optional side input element 515 allows further user input. According to an aspect, the side input element 515 is a rotary switch, a button, or any other type of manual input element. In alternative examples, mobile computing device 500 incorporates more or less input elements. For example, the display 505 may not be a touch screen in some examples. In alternative examples, the mobile computing device 500 is a portable phone system, such as a cellular phone. According to an aspect, the mobile computing device 500 includes an optional keypad 535. According to an aspect, the optional keypad 535 is a physical keypad. According to another aspect, the optional keypad 535 is a “soft” keypad generated on the touch screen display. In various aspects, the output elements include the display 505 for showing a graphical user interface (GUI), a visual indicator 520 (e.g., a light emitting diode), and/or an audio transducer 525 (e.g., a speaker). In some examples, the mobile computing device 500 incorporates a vibration transducer for providing the user with tactile feedback. In yet another example, the mobile computing device 500 incorporates input and/or output ports, such as an audio input (e.g., a microphone jack), an audio output (e.g., a headphone jack), and a video output (e.g., a HDMI port) for sending signals to or receiving signals from an external device. In yet another example, the mobile computing device 500 incorporates peripheral device port 540, such as an audio input (e.g., a microphone jack), an audio output (e.g., a headphone jack), and a video output (e.g., a HDMI port) for sending signals to or receiving signals from an external device.

FIG. 5B is a block diagram illustrating the architecture of one example of a mobile computing device. That is, the mobile computing device 500 incorporates a system (i.e., an architecture) 502 to implement some examples. In one example, the system 502 is implemented as a “smart phone” capable of running one or more applications (e.g., browser, e-mail, calendaring, contact managers, messaging clients, games, and media clients/players). In some examples, the system 502 is integrated as a computing device, such as an integrated personal digital assistant (PDA) and wireless phone.

According to an aspect, one or more application programs 550 are loaded into the memory 562 and run on or in association with the operating system 564. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. According to an aspect, the lockbox engine 120 is loaded into memory 562. The system 502 also includes a non-volatile storage area 568 within the memory 562. The non-volatile storage area 568 is used to store persistent information that should not be lost if the system 502 is powered down. The application programs 550 may use and store information in the non-volatile storage area 568, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system 502 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area 568 synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory 562 and run on the mobile computing device 500.

According to an aspect, the system 502 has a power supply 570, which is implemented as one or more batteries. According to an aspect, the power supply 570 further includes an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.

According to an aspect, the system 502 includes a radio 572 that performs the function of transmitting and receiving radio frequency communications. The radio 572 facilitates wireless connectivity between the system 502 and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio 572 are conducted under control of the operating system 564. In other words, communications received by the radio 572 may be disseminated to the application programs 550 via the operating system 564, and vice versa.

According to an aspect, the visual indicator 520 is used to provide visual notifications and/or an audio interface 574 is used for producing audible notifications via the audio transducer 525. In the illustrated example, the visual indicator 520 is a light emitting diode (LED) and the audio transducer 525 is a speaker. These devices may be directly coupled to the power supply 570 so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor 560 and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface 574 is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer 525, the audio interface 574 may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. According to an aspect, the system 502 further includes a video interface 576 that enables an operation of an on-board camera 530 to record still images, video stream, and the like.

According to an aspect, a mobile computing device 500 implementing the system 502 has additional features or functionality. For example, the mobile computing device 500 includes additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 5B by the non-volatile storage area 568.

According to an aspect, data/information generated or captured by the mobile computing device 500 and stored via the system 502 is stored locally on the mobile computing device 500, as described above. According to another aspect, the data is stored on any number of storage media that is accessible by the device via the radio 572 or via a wired connection between the mobile computing device 500 and a separate computing device associated with the mobile computing device 500, for example, a server computer in a distributed computing network, such as the Internet. As should be appreciated such data/information is accessible via the mobile computing device 500 via the radio 572 or via a distributed computing network. Similarly, according to an aspect, such data/information is readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.

FIG. 6 illustrates one example of the architecture of a system for providing tenant approval for operator access to tenant data 116 as described above. Content developed, interacted with, or edited in association with the lockbox engine 120 is enabled to be stored in different communication channels or other storage types. For example, various documents may be stored using a directory service 622, a web portal 624, a mailbox service 626, an instant messaging store 628, or a social networking site 630. The lockbox engine 120 is operable to use any of these types of systems or the like for providing tenant approval for operator access to tenant data, as described herein. According to an aspect, a server 615 provides the lockbox engine 120 to clients 605A,B,C. As one example, the server 615 is a web server providing the lockbox engine 120 over the web. The server 615 provides the lockbox engine 120 over the web to clients 605 through a network 110. By way of example, the client computing device is implemented and embodied in a personal computer 605A, a tablet computing device 605B or a mobile computing device 605C (e.g., a smart phone), or other computing device. Any of these examples of the client computing device are operable to obtain content from the store 616.

Aspects of the present invention, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to aspects of the invention. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

The description and illustration of one or more examples provided in this application are not intended to limit or restrict the scope of the invention as claimed in any way. The aspects, examples, and details provided in this application are considered sufficient to convey possession and enable others to make and use the best mode of claimed invention. The claimed invention should not be construed as being limited to any aspect, example, or detail provided in this application. Regardless of whether shown and described in combination or separately, the various features (both structural and methodological) are intended to be selectively included or omitted to produce an example with a particular set of features. Having been provided with the description and illustration of the present application, one skilled in the art may envision variations, modifications, and alternate examples falling within the spirit of the broader aspects of the general inventive concept embodied in this application that do not depart from the broader scope of the claimed invention.

Claims

1. A computer-implemented method for providing tenant approval for operator access to data of a tenant, comprising: receiving, by a third-party cloud service provider, an indication to create an access control request for temporarily elevating a role of an operator to provide a set of permissions for allowing the operator to perform an action that allows access to data of the tenant, wherein the operator is employed by a third-party cloud service provider, and wherein the tenant is a customer of the cloud service provider;creating, by the third-party cloud service provider, the access control request for temporarily elevating the role of the operator to perform the action, wherein the action comprises servicing a resource at the third-party cloud service provider, and wherein the resource hosts at least some data of the tenant;identifying, by the third-party cloud service provider, one or more tenant administrators authorized to grant the set of permissions to temporarily elevate the role of the operator, wherein the one or more tenant administrators are associated with an organization of the tenant;sending, by the third-party cloud service provider, the access control request to the one or more tenant administrators;receiving, by the third-party cloud service provider, an access control response from at least one of the one or more tenant administrators;upon determining that the access control response from the at least one tenant administrator is an approval of the access control request, granting, by the third-party cloud service provider, the set of permissions to temporarily elevate the role of the operator; andtemporarily elevating, by the third-party cloud service provider, the role of the operator to allow the operator to perform the action that allows access to the at least some data of the tenant.

2. The computer-implemented method of claim 1, wherein receiving the indication to create the access control request for temporarily elevating the role of the operator comprises receiving an identification of one or more of: the tenant, the operator, and the action.

3. The computer-implemented method of claim 2, determining the set of permissions needed to allow the operator to perform the action based at least in part on one of: the tenant, the operator, and the action.

4. The computer-implemented method of claim 3, wherein determining the set of permissions needed to allow the operator to perform the action comprises: referencing a command list to derive, based on the tenant, which resources upon which the tenant is provisioned; anddetermining, based on the derived resources and based on the operator and the action, a corresponding role that would give the operator the set of permissions needed to allow the operator to perform the action.

5. The computer-implemented method of claim 4, further comprising: authenticating the access control request prior to identifying the one or more tenant administrators authorized to grant the set of permissions to temporarily elevate the role of the operator, wherein authenticating the access control request comprises: determining a current role of the operator; anddetermining whether elevation to the corresponding role from the current role complies with at least one of a plurality of policies.

6. The computer-implemented method of claim 1, wherein identifying the one or more tenant administrators comprises querying an online directory service for the one or more tenant administrators and obtaining contact information for the one or more tenant administrators.

7. The computer-implemented method of claim 1, wherein at least one of the one or more tenant administrators is a user in the tenant organization delegated by an administrator of a software service as a tenant administrator.

8. The computer-implemented method of claim 1, wherein prior to computing the one or more tenant administrators authorized to grant the set of permissions to temporarily elevate the role of the operator, the method comprises: making an analytics call to determine whether the tenant has opted in to requiring tenant approval for operator access to the data of the tenant; andreceiving a response including a Boolean flag indicating that the tenant requires tenant approval for operator access to the data of the tenant.

9. The computer-implemented method of claim 1, wherein sending the access control request to the one or more tenant administrators comprises sending a link to an application interface via which the one or more tenant administrators are able to approve or reject the access control request, wherein the link is sent in at least one of: an email;an SMS;an MMS message anda notification.

10. The computer-implemented method of claim 1, wherein receiving the access control response from the at least one tenant administrator comprises receiving an indication of a selection of an approval control or a rejection control provided in an application user interface.

11. The computer-implemented method of claim 1, further comprising notifying the operator that the access control response from the at least one tenant administrator is an approval of the access control request.

12. The computer-implemented method of claim 1, further comprising creating a log entry comprising the operator, the action, a corresponding role to which the operator has been temporarily elevated, and the data accessed by the operator.

13. The computer-implemented method of claim 12, further comprising providing an audit report comprising a plurality of log entries.

14. A computing system, comprising: at least one processing unit; andat least one memory storing computer-executable instructions that when executed by the at least one processing unit cause the computing system to: receive a request for temporarily elevating a role of an operator to perform an action that allows access to data of a tenant, wherein temporarily elevating the role of the operator comprises granting a set of permissions for performing the action, wherein the operator is associated with a third-party cloud service provider, wherein the tenant is a customer of the cloud service provider, wherein the action comprises servicing a resource at the third-party cloud service provider, and wherein the resource hosts at least some data of the tenant;identify one or more individuals authorized to grant the set of permissions, wherein the one or more individuals are associated with an organization of the tenant, and wherein identifying the one or more individuals authorized to grant the set of permissions comprises querying an online directory service to obtain contact information for the one or more individuals;send the request to the one or more individuals;upon determining that a response from at least one individual is an approval of the request, grant the set of permissions; andtemporarily elevate the role of the operator to allow the operator to perform the action that allows access to at least some data of the tenant.

15. The computing system of claim 14, wherein the action comprises accessing data associated with the at least one individual, wherein the at least one individual has a high role within a management hierarchy of the organization.

16. The computing system of claim 14, wherein the at least one individual is authorized to grant the set of permissions based on a management hierarchy of the organization.

17. The computing system of claim 14, wherein the temporarily elevated role of the operator comprises an administrative role.

18. The computing system of claim 17, wherein the action requires access to data of the organization.

19. The computing system of claim 14, the computer-executable instructions further causing the computing system to: authenticate the request prior to identifying the one or more individuals authorized to grant the set of permissions to temporarily elevate the role of the operator, wherein authenticating the request comprises: determining a current role of the operator; anddetermining whether elevating the role of the operator from the current role complies with at least one of a plurality of policies.

20. A computer storage device storing computer-executable instructions that when executed by a processing unit cause the processing unit to: receive a request for temporarily elevating a role of an operator to perform an action that allows access to data of a tenant, wherein temporarily elevating the role of the operator comprises granting a set of permissions for performing the action, wherein the operator is associated with a third-party cloud service provider, wherein the tenant is a customer of the cloud service provider, wherein the action comprises servicing a resource at the third-party cloud service provider, and wherein the resource hosts at least some data of the tenant;determine whether the tenant requires tenant approval for operator access to the data of the tenant;in response to determining that the tenant requires tenant approval, identify one or more individuals authorized to grant the set of permissions, wherein the one or more individuals are associated with an organization of the tenant;send the request to the one or more individuals;upon determining that a response from at least one individual is an approval of the request, grant the set of permissions; andtemporarily elevate the role of the operator to allow the operator to perform the action that allows access to at least some data of the tenant.