# US 2013/0160115 A1 · Sandboxing for multi-tenancy

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0160115 A1
- Document ID: US20130160115A1
- Status: Published application
- Kind: A1
- Application number: 13/330,682
- Filed: 2011-12-20
- Published: 2013-06-20
- Earliest claimed: 2011-12-20
- Assignees: Microsoft Corporation
- Inventors: Girish Mittur Venkataramanappa; Mandyam Kishore; Andreas Ulbrich; Aarthi Rajmohan Saravanakumar; Chandra Prasad; Yann Christensen; Dharma Shukla; Amol Kulkarni
- Web page: https://patentgrep.com/patent/US20130160115A1

## CPC

- G06F 9/5011: {the resources being hardware resources other than CPUs, Servers and Terminals}
- G06F 11/3409: {for performance assessment}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 2201/815: Virtual
- G06F 2201/86: Event-based monitoring
- G06F 2201/88: Monitoring involving counting
- G06F 2209/504: Resource capping
- G06F 2221/2149: Restricted operating environment
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Systems and methods according to various embodiments disclose a worker process manager adapted to spawn one or more worker processes on a server and to load an application on each of the worker processes. The worker process manager is adapted to isolate the one or more worker processes from each other and to control resource usage by the worker processes. A resource manager is adapted to detect applications that overuse system resources. The worker process manager is adapted to isolate worker processes and to control resource usage using one or more of the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security. Heuristic algorithms are used to detect applications that frequently overuse system resources that are unchargeable and that cause system unresponsiveness.

## Claims

### Claim 1

A server, comprising:
a worker process manager adapted to spawn one or more worker processes on the server and to load an application on each of the worker processes;
the worker process manager further adapted to isolate the one or more worker processes from each other and to control resource usage by the worker processes; and
a resource manager adapted to detect applications that overuse system resources.

### Claim 2 (depends on 1)

The server of claim 1, wherein the worker process manager is adapted to isolate worker processes and to control resource usage using one or more of the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security.

### Claim 3 (depends on 1)

The server of claim 1, wherein the resource manager is adapted to detect applications that overuse system resources using a heuristic algorithm that comprises identifying suspect applications that were running when a host server becomes unresponsive, assigning a point to each of the suspect applications, distributing the suspect applications to other host servers, and monitoring points accumulated by the suspect applications to identify a suspect application having a greatest number of points.

### Claim 4 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a least-privilege execution technique that comprises spawning a worker process using a process token that has minimal system privileges and security group memberships.

### Claim 5 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a messaging isolation technique that comprises isolating each worker process in its own Window station and desktop object.

### Claim 6 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a credentials isolation technique that comprises using access control lists to secure certificates and private keys for use only by authorized applications.

### Claim 7 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a data isolation technique that comprises using access control lists to limit each application to using only its own data folder.

### Claim 8 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a network isolation technique that comprises reserving http and https endpoints for each application and using access control lists to limit each application to using only its own reserved endpoints.

### Claim 9 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a fair share resource usage technique that comprises sending warning notifications to applications that exceeds a first resource usage level and terminates applications that exceed a second resource usage level.

### Claim 10 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a fair share resource usage technique that comprises throttling CPU usage by adjusting each application's priority level depending upon the application's historical CPU usage.

### Claim 11 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a fair share resource usage technique that comprises throttling network usage using a quality of service (QoS) policy to control each application's access to destination port ranges assigned to the application.

### Claim 12 (depends on 2)

The server of claim 2, wherein the worker process manager uses at least a managed runtime security technique that comprises restricting application access to predetermined allowed API calls and runtime libraries.

### Claim 13

A method, comprising:
spawning one or more worker processes via a worker process manager;
assigning an application to each of the one or more worker processes by the worker process manager;
isolating each of the one or more worker processes from each other by the worker process manager; and
detecting applications that overuse system resources using a resource manager.

### Claim 14 (depends on 13)

The method of claim 13, wherein the worker process manager isolates the one or more worker processes and controls resource usage using one or more of the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security.

### Claim 15 (depends on 13)

The method of claim 13, wherein the worker process manager isolates the one or more worker processes and controls resource usage using the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security.

### Claim 16 (depends on 13)

The method of claim 13, wherein detecting applications that overuse system resources further comprises:
determining when a server becomes unresponsive;
identifying all suspect applications running on the server when the server becomes unresponsive;
assigning a point to each suspect application;
redistributing the suspect applications to different servers; and
identifying a suspect application with the highest point total.

### Claim 17

A computer program product for implementing a method for sandboxing applications on a multi-tenant server, the computer program product comprising one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of a computing system (600), cause the computing system to perform the method comprising:
spawning one or more worker processes via a worker process manager;
assigning an application to each of the one or more worker processes by the worker process manager;
isolating each of the one or more worker processes from each other by the worker process manager; and
detecting applications that overuse system resources using a resource manager.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein the worker process manager isolates the one or more worker processes and controls resource usage using one or more of the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security.

### Claim 19 (depends on 17)

The computer program product of claim 17, wherein the worker process manager isolates the one or more worker processes and controls resource usage using the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security.

### Claim 20 (depends on 17)

The computer program product of claim 17, wherein detecting applications that overuse system resources further comprises:
determining when a server becomes unresponsive;
identifying all suspect applications running on the server when the server becomes unresponsive;
assigning a point to each suspect application;
redistributing the suspect applications to different servers; and
identifying a suspect application with the highest point total.
