# US 2018/0026943 A1 · Modifying Authentication for an Application Programming Interface

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

- Number: US 2018/0026943 A1
- Document ID: US20180026943A1
- Status: Published application
- Kind: A1
- Application number: 15/671,017
- Filed: 2017-08-07
- Published: 2018-01-25
- Earliest claimed: 2014-08-22
- Assignees: Shape Security, Inc.
- Applicants: Shape Security, Inc.
- Inventors: Justin D. Call; Timothy D. Peacock
- Web page: https://patentgrep.com/patent/US20180026943A1

## CPC

- H04L 63/02: {for separating internal from external traffic, e.g. firewalls}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 21/629: {to features or functions of an application}
- H04L 43/045: for graphical visualisation of monitoring data
- H04L 43/062: related to network traffic
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/101: {Access control lists [ACL]}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Application programming interfaces (APIs) can be unintentionally exposed and allow for potentially undesirable use of corporate resources. An API call filtering system configured to monitor API call requests received via an endpoint and API call responses received via a supporting service of an API or web service. The API call filtering system enables enterprises to improve their security posture by identifying, studying, reporting, and securing their APIs within their enterprise network.

## Claims

### Claim 1

An application programming interface (API) call filtering system to filter API call requests received, via a network, from a device that is network-connected and configured to run endpoint application hardware and/or software, to secure an API service that accepts API call requests and provides API call responses thereto, the system comprising:
at least one computing device configured to implement one or more services, wherein the one or more services are configured to:
a) monitor, at an API filter, API call requests received from an endpoint application directed to a server configured to provide, at least in part, the API service;
b) compile performance indicators of the API call requests;
c) analyze the compiled performance indicators; and
d) create at least one report based at least in part, on the analyzed performance indicators.

### Claim 2 (depends on 1)

The API call filtering system of claim 1, wherein the device is a user device or a machine-to-machine device.

### Claim 3 (depends on 1)

The API call filtering system of claim 1, wherein the API filter initially includes no information of the API to which the API call requests are transmitted.

### Claim 4 (depends on 1)

The API call filtering system of claim 1, wherein the performance indicators include a frequency, a velocity, a time of day, a geo-location, or an authentication indicator related to the API call requests.

### Claim 5 (depends on 1)

The API call filtering system of claim 1, wherein the at least one report includes analysis of the performance indicators and at least one recommendation of an action or non-action to take in response to each of at least some of the API call requests.

### Claim 6 (depends on 1)

The API call filtering system of claim 1, wherein the one or more services are further configured to:
obtain the performance indicators;
determine identification criteria based, at least in part, on the performance indicators; and
identify, using the identification criteria, the API to which the API call requests are transmitted.

### Claim 7 (depends on 1)

The API call filtering system of claim 1, wherein the one or more services are further configured to:
create an access control list (ACL) for the API; and
change access permissions in the ACL for the API, wherein the access permission changes include modifying access to the API, limiting access to the API, or blocking access to the API.

### Claim 8 (depends on 7)

The API call filtering system of claim 7, wherein limiting access to the API comprises at least throttling or reducing throughput.

### Claim 9 (depends on 7)

The API call filtering system of claim 7, wherein the one or more services are further configured to change the access permissions for the API from unauthenticated access permissions to authenticated access permissions.

### Claim 10 (depends on 1)

The API call filtering system of claim 1, wherein the API call request received from the endpoint application includes requests to authenticate the endpoint application with respect to a secure account maintained at, or for, the API service.

### Claim 11 (depends on 1)

The API call filtering system of claim 1, wherein the API filter uses a non-deterministic algorithm to analyze the performance indicators.

### Claim 12

A non-transitory computer-readable storage medium having stored thereon executable instructions that, when executed by one or more processors of a computer system, wherein the computer system is an application programming interface (API) wall, cause the computer system to at least:
identify, at an API wall, API call requests for a web service, the API call requests transmitted from an endpoint to a server, wherein the server is a component of an enterprise network;
identify, at the API wall, API call responses transmitted from the server;
collect business intelligence related to the API call requests and the API call responses, the business intelligence including statistics and properties of the endpoint;
compile a report, the report including statistics, analysis, and/or recommendations related to the API call request;
create, via the API wall, a dashboard including information related to API use across the enterprise network; and
provide, via the API wall, control mechanisms for modifying access to an API, limiting access to the API, creating access control lists (ACLs), and enforcing ACLs.

### Claim 13 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to create, via the API wall, a list of APIs that are called across an enterprise network.

### Claim 14 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to record traffic over the network from an endpoint to a web server, the web server configured to provide web services in response to an API call request from the endpoint.

### Claim 15 (depends on 14)

The non-transitory computer-readable storage medium of claim 14, wherein the instructions that cause the computer system to record traffic over the network further include instructions that cause the computer system to:
systematically browse web assets to identify traffic that originates from browser-driven website interaction; and
remove identified browser-driven website interaction traffic from the traffic recorded over the network in order to improve identification of API calls.

### Claim 16 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to collect properties determined at the API wall, the properties including measured frequency, measured velocity, time of day, geo-location, or response times.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the instructions that cause the computer system to collect properties further include instructions that cause the computer system to determine if APIs are chained together with an API call request to one leading to API call requests to another.

### Claim 18 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to require access via the API wall, by an endpoint, over Transport Layer Security (TLS).

### Claim 19 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to:
identify libraries and/or middleware that include an API; and
record commonly abused APIs in the identified libraries and/or middleware based, at least in part, on information collected at the API wall.

### Claim 20 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to:
identify libraries and/or middleware that include an API; and
record human-compiled data relating to commonly abused APIs.

### Claim 21

A computer-implemented method for filtering application programming interface (API) calls in a secured network environment, the computer-implemented method, comprising:
under control of one or more computer systems configured with executable instructions,
a) receiving, at a server in an enterprise network via an API call filter, an API call request from an endpoint, wherein the API call request is either an original API call request or a modified API call request;
b) providing a secured API supporting service for the endpoint, wherein the secured API supporting service provides at least one API to access a business unit of the enterprise network; and
c) transmitting, over the secured network environment, an API call response to the endpoint.

### Claim 22 (depends on 21)

The computer-implemented method of claim 21, wherein the endpoint is a user device or an instance of an application.

### Claim 23 (depends on 21)

The computer-implemented method of claim 21, further comprising receiving a modified API call request via a transparent request proxy located adjacent to the server, wherein the modified API call request is modified at the API call filter.

### Claim 24 (depends on 23)

The computer-implemented method of claim 23, wherein the modified API call request is modified in real-time.
