Network Path Verification via Proof-of-Transit Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authentication services in enterprise networking rely solely on end-to-end encryption, which is not sufficient to prevent information leakage, and do not effectively segregate traffic, making them insecure against timing analysis and packet size correlation attacks.
Innovation Solution
Implementing a system that uses proof-of-transit data within packet flows to verify if the actual path taken by packets matches a mandated route, encoded in Security Assertion Markup Language (SAML) statements, and enabling network routers and way-points to sign TLS sessions transparently, thereby enforcing enterprise security policies and reducing the attack surface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If end-to-end encryption is used to protect traffic, then confidentiality is improved, but security against timing analysis and packet size correlation attacks deteriorates
Solution Approach 1:
The patent segments encrypted traffic into multiple streams by introducing synthetic traffic and interleaving it with actual traffic. This segmentation obscures the characteristics of individual encrypted packets, making timing analysis and packet size correlation attacks ineffective while maintaining end-to-end encryption confidentiality.
Solution Approach 2:
The patent introduces an intermediary component that acts as a traffic mixer between the application and the network. This intermediary adds synthetic traffic, performs traffic interleaving, and embeds covert channels to mask the characteristics of encrypted traffic, thereby enhancing security against analysis attacks while preserving encryption benefits.
2Ease of operation
If individual encrypted flows are carried, then authentication is simplified, but security deteriorates due to information leakage from timing and packet size
Solution Approach 1:
The patent merges multiple traffic streams (actual encrypted traffic and synthetic traffic) into a single aggregated flow. This merging obscures the boundaries between individual encrypted flows, preventing information leakage through timing and packet size analysis while maintaining simplified authentication mechanisms.
Solution Approach 2:
The patent changes the parameters of traffic flows by introducing variable synthetic traffic with different sizes and timing characteristics. This parameter variation masks the original traffic patterns, preventing correlation attacks while allowing authentication to proceed through standard encrypted channels.
3Device complexity
If traffic aggregation is not implemented, then individual flow management is easier, but security deteriorates due to timing and packet size analysis
Solution Approach 1:
The patent segments the traffic management function into multiple independent components: actual traffic handling, synthetic traffic generation, traffic interleaving, and covert channel embedding. This segmentation allows each component to operate independently with simple logic, yet collectively provides robust security against timing and packet size analysis attacks.
Solution Approach 2:
The system generates its own synthetic traffic autonomously to mask actual traffic characteristics. This self-service approach allows the security mechanism to operate without complex external coordination, maintaining simplicity in flow management while achieving high security through automated traffic aggregation and masking.
Data Source
AI summary
Disclosed are concepts for provided for managing application traffic. A method includes receiving a request to access a service from an application, confirming an entity of a user of the application and, based on the confirmation, generating, via an authentication service, a routing policy for data flows between the application and the service. The routing policy defines a mandated path between the application and the service. The method also can include storing proof-of-transit data in the traffic flow for tracking an actual path from the application to the service and determining whether the data path complies with the mandated path defined in the policy. When the determination indicates that the actual path followed the mandated path defined in the routing policy, the method includes granting access to the user for the service. When the actual path differs from the mandated path, the method includes denying access to the user.