SDP Controller Identity Mapping for Zero-Trust Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional zero-trust security approaches introduce latency, complexity, and increased risk of network-based attacks by requiring intermediate brokers and momentarily opened ports, which contradict the zero-trust model and increase organizational friction.
Innovation Solution
A software-defined perimeter (SDP) controller establishes a secure connection between devices by mapping identities using a firewall connection table and initiating a hole punching protocol, allowing direct communication without intermediate brokers or open ports, thus maintaining the integrity of the zero-trust model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an intermediate broker is used to convey traffic between client and server system, then security is improved, but latency increases and bandwidth cost increases
Solution Approach 1:
The patent uses an intermediate broker (gateway system) to mediate traffic between untrusted external networks and trusted internal networks. The broker authenticates devices, establishes secure tunnels, and filters traffic while maintaining the zero-trust security model. This resolves the contradiction by providing security through mediation without requiring permanently open ports, thereby reducing latency compared to traditional firewall approaches while maintaining security.
2Ease of operation
If ports are opened in border-firewall to permit traffic from external broker, then connectivity is improved, but deployment effort increases and security risk increases
Solution Approach 1:
The patent implements dynamic port opening where the border firewall ports are opened temporarily only when needed for specific authenticated connections, rather than remaining permanently open. The gateway system dynamically requests port openings, receives authentication, and the firewall opens ports only for the duration of the connection. This dynamic approach maintains connectivity while reducing deployment effort and security risk compared to static open ports.
3Ease of operation
If ports are momentarily opened on SDP gateway to permit network connection, then connectivity is improved, but latency increases and bandwidth usage increases
Solution Approach 1:
The patent performs preliminary authentication and connection establishment through the gateway before actual data transfer begins. The gateway pre-authenticates devices, pre-establishes secure tunnels, and pre-coordinates firewall port openings. This preliminary action ensures that once connectivity is established, data transfer occurs directly between devices without repeated authentication overhead, thereby reducing latency for the actual data transmission while maintaining security.
4Reliability
If intermediate broker is used to route traffic, then security is improved, but bandwidth cost increases
Solution Approach 1:
The patent segments the network communication into two distinct phases: a control plane phase where the intermediate broker (gateway) handles authentication, tunnel establishment, and security policies; and a data plane phase where traffic flows directly between devices through established secure tunnels. This segmentation allows security management to be handled by the broker while data transmission occurs on direct paths, minimizing bandwidth consumption by the broker to only control messages rather than all data traffic.
Data Source
AI summary
A method and system include a SDP controller in a SDP receiving a request from a first device for communicating with a second device. The second device is in the SDP. A firewall includes a connection table configured to map an identity of the first device and second device, and a filter table is configured to open and close ports. The SDP controller authenticates the first device, and provides the identity of the first device to the second device. The second device transmits a first packet to the first device. The firewall maps in the connection table, the identity of the first device in association with the second device. The first device transmits a second packet to the second device. The firewall determines that the identity of the first device is in the connection table for communicating with the second device and forwards the second packet to the second device.


