Access Token Firewall Whitelisting for Dynamic Client IP Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Identifying and whitelisting the correct IP address and port for client applications accessing cloud services is challenging due to dynamic IP addresses, network translations, and the rise of remote work, complicating the process and endangering cloud service availability.

Innovation Solution

Implementing intelligent firewall rule handling using an access token to dynamically update an access control list with the client's external IP address and port identifier, reducing manual interactions and enhancing resilience to IP address changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual firewall rule updates are used to whitelist IP addresses, then security control is maintained, but service availability deteriorates due to time-consuming coordination with infrastructure teams

Engineering Contradiction:
Improveservice availabilityVSAvoidtime for firewall rule updates
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the client application to automatically request and obtain firewall rule updates without manual intervention. The access control system autonomously processes the whitelist update request based on the provided access token, eliminating the need for coordination with infrastructure teams and reducing update time while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by obtaining the external IP address and preparing the firewall rule update request in advance, before the client application needs to access the server. This proactive approach ensures that the whitelist is updated promptly, preventing service disruptions and reducing the time loss associated with manual updates.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If static IP address whitelisting is used, then security is maintained, but adaptability deteriorates due to dynamic IP addresses from ISPs and remote work scenarios

Engineering Contradiction:
ImproveIP address flexibilityVSAvoidsecurity control
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements dynamics by transitioning from static IP address whitelisting to a dynamic mechanism where the access control list is automatically updated with the client's current external IP address. This allows the system to adapt to changing IP addresses from ISPs, remote work locations, and NAT translations while maintaining security through automated verification and update processes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback by continuously monitoring the client application's access requests and automatically updating the firewall rules based on the current external IP address. The access control system receives feedback from the client network about IP address changes and responds by updating the whitelist, ensuring both adaptability and security are maintained simultaneously.

Inventive Principle:
Principle #23Feedback

3Reliability

If complex coordination processes are used for IP address tracking, then security is maintained, but device complexity increases due to multiple infrastructure teams involved

Engineering Contradiction:
Improvesecurity controlVSAvoidcoordination process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges multiple functions into a single integrated access control mechanism. The access control system combines IP address translation handling, firewall rule management, and security verification into one unified process. This consolidation eliminates the need for complex coordination between multiple infrastructure teams, reducing device complexity while maintaining security control through the centralized access token verification process.

Inventive Principle:
Principle #5Merging (Combining)

4Adaptability or versatility

If frequent firewall rule updates are performed, then adaptability to IP changes is improved, but loss of time increases due to repeated manual interactions

Engineering Contradiction:
Improveresponse to IP changesVSAvoidtime for repeated updates
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables self-service by automating the entire firewall rule update process. When the client application's external IP address changes, the access control system automatically detects the change, verifies the access token, and updates the whitelist without requiring manual intervention. This eliminates repeated manual interactions and time loss while maintaining high adaptability to IP address changes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system ensures continuity of useful action by maintaining a persistent access control mechanism that continuously monitors and updates firewall rules as needed. Rather than performing discrete manual updates, the system maintains continuous awareness of the client's IP address status and automatically adjusts the whitelist, reducing time loss while improving adaptability to changes.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS20250358288A1Intelligent firewall rule handling
Publication Date: 2025.11.20 SAP SE
  • US20250358288A1 patent drawing
  • US20250358288A1 patent drawing
  • US20250358288A1 patent drawing

AI summary

A computer-implemented method may comprise receiving, from a client application running within a client network, a request for a server application running within a server network to perform an action, and then generating, by the client network, a modified version of the request for the server application to perform the action, where the modified version of the request for the server application to perform the action comprises an access token configured to be used by the server network to allow an update of an access control list for the server application. The client network may then send, to the server network, the modified version of the request for the server application to perform the action.