# US 2013/0254835 A1 · Access authorization having embedded policies

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

- Number: US 2013/0254835 A1
- Document ID: US20130254835A1
- Status: Published application
- Kind: A1
- Application number: 13/890,965
- Filed: 2013-05-09
- Published: 2013-09-26
- Earliest claimed: 2004-10-01
- Assignees: Microsoft Corporation
- Applicants: Microsoft Corporation
- Inventors: Gilad Golan; Mark Vayman
- Web page: https://patentgrep.com/patent/US20130254835A1

## CPC

- G06F 21/30: Authentication, i.e. establishing the identity or authorisation of security principals
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/554: {involving event detection and direct action}
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A facility for receiving an embedded policy is provided. The facility checks an application program image for the presence of an embedded policy. If an embedded policy is detected, the facility extracts the policy from within the application program image. The facility may then apply the extracted policy to the application program image before the application program image is loaded and/or executed. Moreover, the facility may check the application program image's integrity prior to extracting the embedded policy.

## Claims

### Claim at position 1

1-30. (canceled)

### Claim 31

A computer-implemented method of setting a revocable policy on a target process, the method comprising:
receiving, via an access control application programming interface (“API”), a first request from a controlling process to set a revocable policy on a target process;
determining whether the controlling process possesses adequate privilege to set the revocable policy on the target process;
upon determining that the controlling process possesses adequate privilege to set the revocable policy on the target process, setting an indication to apply the revocable policy on the target process;
sending to the controlling process an identifier indicating whether the indication to apply the revocable policy on the target process was set;
receiving, via the API, a second request to revoke the revocable policy on the target process, wherein the second request includes the identifier;
based upon the identifier, authenticating the second request as having authorization to revoke the revocable policy on the target process; and
revoking the revocable policy on the target process.

### Claim 32 (depends on 30)

The computer-implemented method of claim 30 wherein the identifier authenticates the controlling process.

### Claim 33 (depends on 30)

The computer-implemented method of claim 30 wherein the identifier is a cookie.

### Claim 34 (depends on 30)

The computer-implemented method of claim 30 wherein the identifier identifies the policy that is to be revoked.

### Claim 35 (depends on 30)

The computer-implemented method of claim 30 wherein the second request is received, via the API, from the target process.

### Claim 36 (depends on 30)

The computer-implemented method of claim 30 wherein the second request is received, via the API, from the controlling process.

### Claim 37 (depends on 30)

The computer-implemented method of claim 30 further comprising:
applying a prior policy to the target process, wherein the prior policy was applied to the target process prior to the setting of the indication to apply the revocable policy on the target process.

### Claim 38 (depends on 37)

The computer-implemented method of claim 37 wherein the identifier identifies the prior policy.

### Claim 39 (depends on 30)

The computer-implemented method of claim 30 further comprising:
preserving state information of the target process prior to the setting of the indication to apply the revocable policy on the target process.

### Claim 40

A computer storage media encoding computer-executable instructions that when executed by a processor perform a method of setting a revocable policy on a target process, the method comprising:
receiving, via an access control application programming interface (“API”), a first request from a controlling process to set a revocable policy on a target process;
determining whether the controlling process possesses adequate privilege to set the revocable policy on the target process;
upon determining that the controlling process possesses adequate privilege to set the revocable policy on the target process, setting an indication to apply the revocable policy on the target process;
sending to the controlling process an identifier indicating whether the indication to apply the revocable policy on the target process was set;
receiving, via the API, a second request to revoke the revocable policy on the target process, wherein the second request includes the identifier;
based upon the identifier, authenticating the second request as having authorization to revoke the revocable policy on the target process; and
revoking the revocable policy on the target process.

### Claim 41 (depends on 40)

The computer storage media of claim 40 wherein the identifier authenticates the controlling process.

### Claim 42 (depends on 40)

The computer storage media of claim 40 wherein the identifier is a cookie.

### Claim 43 (depends on 40)

The computer storage media of claim 40 wherein the identifier identifies the policy that is to be revoked.

### Claim 44 (depends on 40)

The computer storage media of claim 40 wherein the second request is received, via the API, from the target process.

### Claim 45 (depends on 40)

The computer storage media of claim 40 wherein the second request is received, via the API, from the controlling process.

### Claim 46 (depends on 40)

The computer storage media of claim 40 wherein the method further comprises:
applying a prior policy to the target process, wherein the prior policy was applied to the target process prior to the setting of the indication to apply the revocable policy on the target process.

### Claim 47 (depends on 46)

The computer storage media of claim 46 wherein the identifier identifies the prior policy.

### Claim 48 (depends on 40)

The computer storage media of claim 40 wherein the method further comprises:
preserving state information of the target process prior to the setting of the indication to apply the revocable policy on the target process.

### Claim 49

A system for setting a revocable policy, the system comprising:
a processor;
a memory communicatively coupled to the processor, the memory comprising:
computer-executable instructions encoding a controlling process;
computer-executable instructions encoding a target process;
computer-executable instructions encoding an access control application programming interface (“API”) communicatively coupled to an operating system, the controlling process, and the target process; and
computer-executable instructions encoding the operating system, the operating system comprised of:
an authorization module configured to:
determine whether the controlling process possesses adequate privilege to set a revocable policy on the target process; and
authenticate a request to revoke the revocable policy on the target process;
a policy store configured to store the revocable policy; and
wherein the operating system is configured to:
receive a first request, via the API, from the controlling process to set the revocable policy on the target process;
set within the policy store an indication to apply the revocable policy on the target process;
send to the controlling process, via the API, an identifier indicating whether the indication to apply the revocable policy on the target process was set within the policy store;
receive a second request to revoke the revocable policy on the target process, wherein the second request includes the identifier; and
revoke the revocable policy stored in the policy store.

### Claim 50 (depends on 49)

The system of claim 49 wherein the identifier authenticates the controlling process.

### Claim 51 (depends on 49)

The system of claim 49 wherein the identifier is a cookie.

### Claim 52 (depends on 49)

The system of claim 49 wherein the identifier identifies the policy that is to be revoked.

### Claim 53 (depends on 49)

The system of claim 49 wherein the operating system is further configured to receive the second request, via the API, from the target process.

### Claim 54 (depends on 49)

The system of claim 49 wherein the operating system is further configured to receive the second request, via the API, from the controlling process.

### Claim 55 (depends on 49)

The system of claim 49 wherein a prior policy of the target process is stored in the policy store.

### Claim 56 (depends on 55)

The system of claim 55 wherein the identifier identifies the prior policy.

### Claim 57 (depends on 49)

The system of claim 49 wherein state information of the target process is stored in the policy store.
