# US 2021/0243183 A1 · Automated on call and ad hoc access to restricted resources

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

- Number: US 2021/0243183 A1
- Document ID: US20210243183A1
- Status: Published application
- Kind: A1
- Application number: 16/779,247
- Filed: 2020-01-31
- Published: 2021-08-05
- Earliest claimed: 2020-01-31
- Assignees: salesforce.com, inc.
- Applicants: salesforce.com, inc.
- Inventors: LaDean CLARK; Ramesh Ramani
- Web page: https://patentgrep.com/patent/US20210243183A1

## CPC

- H04L 63/0846: {using time-dependent-passwords, e.g. periodically changing passwords}
- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04L 51/212: using filtering or selective blocking
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Complex cloud-based system with many different entities, e.g., servers, clients, databases, firewalls, other machines, etc. often require on call engineers to be available to help with maintenance, emergencies, and other tasks. Sometimes ad hoc access is required when on call engineers are unable to resolve a particular issue. Organizations that manually manage access to on call and ad hoc engineer access, may do so relatively easily if they are a smaller organization. But, for larger or more complex environments, manual processes represent a significant burden. An alternative is automatically grant and revoke access. For example, if a vendor tracks your on call engineers, on call statuses may be identified to automatically grant access while on call. For ad hoc access, a requestor may request temporary access, and if valid, access may also be automatically granted for a desired time period. Automation frees valuable limited resources for other tasks.

## Claims

### Claim 1

A method for automatically granting and revoking access to restricted resources based at least in part on selected ones of an indicator stored with an access resource or an ad hoc request from a requestor, the restricted resources include a first restricted resource and a second restricted resource, the method comprising:
periodically retrieving the indicator from the access resource, the indicator at least identifying a first entity having an associated on call status;
automatically determining an access for the first entity to the first restricted resource based at least in part on the indicator;
receiving the ad hoc request to authorize a second entity with access to the second restricted resource for a time period;
determining if the requestor is authorized to make the ad hoc request, and if so, granting the second entity access to the second restricted resource;
sending a message corresponding to the ad hoc request from the requestor;
automatically de-authorizing the first entity based at least in part on the indicator; and
automatically de-authorizing the second entity based at least in part on the time period.

### Claim 2 (depends on 1)

The method of claim 1, further comprising determining the indicator fails to identify the first entity with an on call status.

### Claim 3 (depends on 1)

The method of claim 1, further comprising determining an expiration of the time period.

### Claim 4 (depends on 1)

The method of claim 1, wherein the determining if the requestor is authorized further comprising:
verifying compliance with a request limit associated with the ad hoc request;
wherein the requestor is unauthorized to make the ad hoc request based at least in part on a noncompliance with the request limit.

### Claim 5 (depends on 4)

The method of claim 4, wherein the request limit corresponds to a frequency of receiving ad hoc requests associated with one or more of the requestor and the second entity.

### Claim 6 (depends on 1)

The method of claim 1, in which a group messaging platform may distribute messages having an associated topic, the method further comprising providing the message to the messaging platform with an associated topic corresponding to the ad hoc request.

### Claim 7 (depends on 1)

The method of claim 1, in which a directory service permits access to the first restricted resource based at least in part on membership in a directory service group, the method further comprising:
automatically adding the first entity to the directory service group based at least in part on the indicator; and
granting the first entity the access to the first restricted resource based at least in part on being a member of the directory service group.

### Claim 8 (depends on 7)

The method of claim 7, the method further comprising:
automatically removing the first entity from the directory service group based at least in part on the indicator; and
denying the first entity the access to the first restricted resource after the removing the first entity from the directory service group.

### Claim 9 (depends on 1)

The method of claim 1, in which the restricted resources are hosted in a virtual private cloud (VPC), a directory service is hosted by a cloud service, and a chat system is accessible by both the VPC and the cloud service, the method further comprising:
providing the message to the chat system; and
receiving, responsive to the providing the message, data from the cloud service data indicating at least whether the requestor is authorized to make the ad hoc request.

### Claim 10

A system to automatically granting and revoking access to restricted resources based at least in part on selected ones of an indicator stored with an access resource or an ad hoc request from a requestor, the restricted resources include a first restricted resource and a second restricted resource, comprising: a processor; and memory coupled to the processor and storing instructions that, when executed by the processor, cause the system to perform operations comprising:
periodically retrieve the indicator from the access resource, the indicator at least identifying a first entity having an associated on call status;
automatically determine an access for the first entity to the first restricted resource based at least in part on the indicator;
receive the ad hoc request to authorize a second entity with access to the second restricted resource for a time period;
determine if the requestor is authorized to make the ad hoc request, and if so, grant the second entity access to the second restricted resource;
send a message corresponding to the ad hoc request from the requestor; and
automatically de-authorize the first entity based at least in part on the indicator, and de-authorize the second entity based at least in part on the time period.

### Claim 11 (depends on 10)

The system of claim 10, the instructions including further instructions to cause the system to perform: determine the indicator fails to identify the first entity with an on call status.

### Claim 12 (depends on 11)

The system of claim 11, the instructions including further instructions to cause the system to perform: determine an expiration of the time period.

### Claim 13 (depends on 10)

The system of claim 10, wherein the instructions to determine if the requestor is authorized further including instructions to cause the system to perform:
verify compliance with a request limit associated with the ad hoc request; and
determine the requestor is unauthorized to make the ad hoc request based at least in part on a noncompliance with the request limit;
wherein the request limit corresponds to a frequency of receiving ad hoc requests associated with one or more of the requestor and the second entity.

### Claim 14 (depends on 10)

The system of claim 10, in which a group messaging platform may distribute messages having an associated topic, the instructions including further instructions to cause the system to perform:
provide the message to the messaging platform with an associated topic corresponding to the ad hoc request.

### Claim 15 (depends on 10)

The system of claim 10, in which a directory service may permit or deny access to the first restricted resource based at least in part on membership in a directory service group, the instructions including further instructions to cause the system to perform:
automatically add the first entity to the directory service group based at least in part on the indicator, and grant the first entity the access to the first restricted resource based at least in part on being a member of the directory service group; and
automatically remove the first entity from the directory service group based at least in part on the indicator, and deny the first entity the access to the first restricted resource after the removing the first entity from the directory service group.

### Claim 16 (depends on 10)

The system of claim 10, in which one or more network interconnects a virtual private cloud (VPC) hosting the restricted resources, a cloud service hosting a directory service, and a chat system, the instructions including further instructions to cause the system to perform:
provide the message to the chat system; and
receive, responsive to the provide the message, data from the cloud service data indicating at least whether the requestor is authorized to make the ad hoc request.

### Claim 17

A computer readable memory having instructions stored thereon for revoking access to restricted resources based at least in part on selected ones of an indicator stored with an access resource or an ad hoc request from a requestor, the restricted resources include a first restricted resource and a second restricted resource, the instructions that, in response to execution by a processor, are operable to perform operations including:
periodically retrieve the indicator from the access resource, the indicator at least identifying a first entity having an associated on call status;
automatically determine an access for the first entity to the first restricted resource based at least in part on the indicator;
receive the ad hoc request to authorize a second entity with access to the second restricted resource for a time period;
determine if the requestor is authorized to make the ad hoc request, and if so, grant the second entity access to the second restricted resource;
send a message corresponding to the ad hoc request from the requestor; and
automatically de-authorize the first entity based at least in part on the indicator, and de-authorize the second entity based at least in part on the time period.

### Claim 18 (depends on 17)

The memory of claim 17, the instructions including further instructions that, in response to execution by a processor, are operable to perform:
determine the indicator fails to identify the first entity with an on call status.
determine an expiration of the time period;
determine a frequency of receiving ad hoc requests associated with one or more of the requestor and the second entity;
compare the frequency of receiving ad hoc requests with a request limit,
verify compliance with the request limit; and
determine the requestor is unauthorized to make the ad hoc request based at least in part on a noncompliance with the request limit.

### Claim 19 (depends on 17)

The memory of claim 17, in which a group messaging platform may distribute messages having an associated topic, the instructions including further instructions that, in response to execution by a processor, are operable to perform:
provide the message to the messaging platform with an associated topic corresponding to the ad hoc request.

### Claim 20 (depends on 17)

The memory of claim 17, in which one or more datapath connects a virtual private cloud (VPC), a cloud service, a chat system, and a cloud system, the instructions including further instructions to cause the system to perform:
receive from the VPC data corresponding to the restricted resources;
receive from the cloud service data corresponding to a directory service controlling access to the restricted resources based at least in part on membership in a directory service group;
automatically add the first entity to the directory service group based at least in part on the indicator, and grant the first entity the access to the first restricted resource based at least in part on being a member of the directory service group;
automatically remove the first entity from the directory service group based at least in part on the indicator, and deny the first entity the access to the first restricted resource after the removing the first entity from the directory service group;
provide the message to the chat system; and
receive, responsive to the provide the message, data from the cloud service data indicating at least whether the requestor is authorized to make the ad hoc request.
