Banking Request Token Validation Against Replay Attacks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current application security systems rely on a single gateway module, which is a single point of failure, and fail to provide adequate security against web-based and mobile banking requests, especially vulnerable to replay attacks due to session tokens remaining valid throughout the user session.

Innovation Solution

Implement a system that issues new session tokens, such as MORF tokens, for each request, requiring validation for every request, and includes multiple layers of token validation across various components to ensure security and prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single gateway module is used for application security, then the system structure is simple, but the system becomes a single point of failure and reliability decreases

Engineering Contradiction:
Improvesystem structureVSAvoidsystem reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the single gateway module into multiple distributed gateway instances that operate independently. Each gateway handles specific requests and can fail without affecting other gateways, transforming the system from a single point of failure to a resilient distributed architecture while maintaining manageable complexity through modular design

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If session tokens remain valid throughout the user session, then the ease of operation is improved, but the security against replay attacks deteriorates

Engineering Contradiction:
Improveuser session continuityVSAvoidreplay attack vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements periodic token validation and regeneration at multiple checkpoints during the user session. Instead of validating once at login, the system performs validation at gateway entry points, API boundaries, and session milestones, continuously refreshing tokens to maintain security while preserving user experience through automated background validation

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system establishes feedback loops where token validation results are fed back into the session management mechanism. Invalidated tokens trigger session termination or token refresh, while valid tokens enable continued access. This feedback-driven approach dynamically adjusts security posture based on real-time validation outcomes, preventing replay attacks without manual user intervention

Inventive Principle:
Principle #23Feedback

3Productivity

If full authorization is performed only at the start of the user session, then the productivity is improved, but the security against replay attacks deteriorates

Engineering Contradiction:
Improveauthorization efficiencyVSAvoidreplay attack vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent applies partial authorization validation at strategic points throughout the session rather than requiring complete re-authentication for every action. Validation occurs at gateway entry points, between microservices, and at session milestones, providing sufficient security coverage without the performance penalty of full re-authorization for every request

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary token validation and session verification at gateway entry points before allowing requests to reach backend services. This preliminary action ensures that only authenticated and authorized requests proceed, establishing security early in the request lifecycle and reducing the burden on subsequent validation points

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260073025A1Systems and methods for application security improvements
Publication Date: 2026.03.12 PNC FINANCIAL SERVICES GROUP INC
  • US20260073025A1 patent drawing
  • US20260073025A1 patent drawing
  • US20260073025A1 patent drawing

AI summary

Systems and methods for application security improvements are provided. The systems and methods may receive a banking request, including a request header, from a web browser or mobile application. Thereafter, a session cookie may be extracted from the request header. The session cookie may include one or more of a CSRF token, a MORF token, and a JWT. Thereafter, an outer API may validate the one or more tokens and create a validated banking request object. Upon such validations, a financial institution's APIs may allow a banking request to proceed with a high degree of confidence that the request is free of interference by bad actors and fraud. The validated banking request object may be transmitted to an inner API to accomplish the banking request. Thus, the system and methods described herein provide an improved system for application security, which decreases rates of fraud below that of known systems.