API Gateway Whitelisting for Microservice Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing systems face significant security risks due to the ubiquity of APIs, which are often exploited by hackers for unauthorized access, as existing security measures are inadequate in controlling access to distributed microservices architectures.

Innovation Solution

Implementing distributed API whitelisting through an API gateway that validates client API requests against a whitelist of permitted endpoints, ensuring only authorized requests are routed to target microservices, thereby reducing attack vectors and enhancing access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If API gateway implements whitelisting validation by comparing API endpoints against a whitelist of permitted endpoints, then security against unauthorized access is improved, but system complexity and processing time increase

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent pre-generates a whitelist of permitted API endpoints and stores it in a data structure (e.g., hash set, trie) before runtime validation. This preliminary action allows the system to perform fast O(1) or O(log n) lookups during request validation, rather than scanning through all possible endpoints each time, thus reducing processing complexity while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an API gateway as an intermediary component between clients and microservices. The gateway intercepts API requests, performs whitelist validation, and routes permitted requests to appropriate microservices. This intermediary layer centralizes security enforcement and isolates the validation logic from individual microservices, improving overall system security without requiring changes to each service.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If API gateway validates every client API request against a whitelist, then unauthorized access is reduced, but request processing time increases

Engineering Contradiction:
Improveunauthorized accessVSAvoidrequest processing time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The patent pre-processes and stores permitted API endpoints in optimized data structures (such as hash sets or tries) before runtime. This allows the validation process to perform rapid lookups with constant or logarithmic time complexity, rather than linear scanning, significantly reducing the time penalty for security validation while maintaining comprehensive whitelist checking.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of endpoint matching from exact string comparison to more efficient data structure-based lookup. By transforming the endpoint validation into a key-based search operation in a pre-built index structure, the system achieves faster validation speeds while maintaining the security requirement of checking against the complete whitelist.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If distributed microservices architecture is implemented to provide cloud computing services, then system versatility and scalability are improved, but security vulnerabilities and attack vectors increase

Engineering Contradiction:
Improvesystem versatilityVSAvoidattack vectors
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an API gateway as a centralized intermediary that all microservices communicate through. This gateway enforces uniform security policies, including whitelist validation, authentication, and authorization, across all microservices. By concentrating security enforcement at the gateway layer, the system maintains the versatility and scalability benefits of distributed microservices while reducing security vulnerabilities through centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct components: the API gateway handling security and routing, and microservices handling business logic. This segmentation allows each component to be optimized independently - the gateway focuses on security validation while microservices focus on functionality - and reduces the attack surface by isolating security-critical operations in the gateway layer.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11388164B2Distributed application programming interface whitelisting
Publication Date: 2022.07.12 MODERNSOLID INDUSTRIAL CO LTD
  • US11388164B2 patent drawing
  • US11388164B2 patent drawing
  • US11388164B2 patent drawing

AI summary

Techniques are provided to implement distributed application programming interface (API) whitelisting for access control of a computing system. For example, an API gateway receives a client API request to access an application comprising a distributed microservices architecture. The API gateway initiates a whitelisting validation operation determine if the client API request is permitted. The whitelisting validation operation includes comparing an API endpoint of the client API request to a whitelist of permitted API endpoints of registered microservices of the application to determine whether the API endpoint of the client API request comprises a permitted API endpoint in the whitelist. The API gateway routes the client API request to a target microservice of the application, in response to the whitelisting validation operation determining that the client API request is permitted.