IP Library Granted Patent US 8,407,324
Granted Patent B2
US 8,407,324 · App. 12/828,785 · Granted Mar 26, 2013

Dynamic modification of the address of a proxy

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,407,324
App. No.
12/828,785
Granted
Mar 26, 2013
Kind
B2
Abstract

In certain embodiments, a method includes receiving, at a first address of a proxy, a first request for access to a network from an application on an endpoint and forwarding, by the proxy, the request to the network on behalf of the application from the first address of the proxy. The method also includes determining, by the proxy, to change the address of the proxy from the first address to a second address and determining, by the proxy, the second address. Even further, the method includes changing, by the proxy, the address of the proxy to the second address. Moreover, the method includes receiving, at the second address of the proxy, a second request for access to the network from the application. The method also includes forwarding, by the proxy, the second request to the network on behalf of the application from the second address of the proxy.

Claims (45)

1. A method, comprising:

receiving, at a first address of a proxy, a first request for access to a network from an application on an endpoint;

forwarding, by the proxy, the request to the network on behalf of the application from the first address of the proxy;

determining, by the proxy, to change the address of the proxy from the first address to a second address;

determining, by the proxy, the second address;

changing, by the proxy, the address of the proxy to the second address;

receiving, at the second address of the proxy, a second request for access to the network from the application; and

forwarding, by the proxy, the second request to the network on behalf of the application from the second address of the proxy.

2. The method of claim 1 , wherein the proxy determines the second address by selecting, by the proxy, the second address from a list of available addresses.

3. The method of claim 1 , wherein the first address and the second address are Internet Protocol (IP) addresses.

4. The method of claim 1 , wherein the first address and the second address are Domain Name System (DNS) addresses.

5. The method of claim 1 , further comprising sending the second address to the application prior to receiving the second request.

6. The method of claim 1 , wherein the proxy determines the second address by using a key to generate the second address, the key being known by the application.

7. The method of claim 6 , wherein the method further comprises generating, by the application, the second address using the key.

8. The method of claim 1 , wherein the proxy determines the second address by registering and deregistering an IP address associated with the proxy with a plurality of DNS addresses.

9. A system, comprising:

at least one memory;

at least one processor operable to:

receive, at a first address of a proxy, a first request for access to a network from an application on an endpoint;

forward, by the proxy, the request to the network on behalf of the application from the first address of the proxy;

determine, by the proxy, to change the address of the proxy from the first address to a second address;

determine, by the proxy, the second address;

change, by the proxy, the address of the proxy to the second address;

receive, at the second address of the proxy, a second request for access to the network from the application; and

forward, by the proxy, the second request to the network on behalf of the application from the second address of the proxy.

10. The system of claim 9 , wherein the at least one processor is operable to determine, by the proxy, the second address by selecting, by the proxy, the second address from a list of available addresses.

11. The system of claim 9 , wherein the first address and the second address are Internet Protocol (IP) addresses.

12. The system of claim 9 , wherein the first address and the second address are Domain Name System (DNS) addresses.

13. The system of claim 9 , wherein the at least one processor is operable to send the second address to the application prior to receiving the second request.

14. The system of claim 9 , wherein the at least one processor is operable to determine, by the proxy, the second address by using a key to generate the second address, the key being known by the application.

15. The system of claim 14 , further comprising the application, the application operable to generate the second address using the key.

16. The system of claim 9 , wherein the at least one processor is operable to determine, by the proxy, a second address by registering and deregistering an IP address associated with the proxy with a plurality of DNS addresses.

17. At least one non-transitory computer-readable medium comprising code, that, when executed by at least one processor, is operable to:

receive, at a first address of a proxy, a first request for access to a network from an application on an endpoint; forward, by the proxy, the request to the network on behalf of the application from the first address of the proxy;

determine, by the proxy, to change the address of the proxy from the first address to a second address;

determine, by the proxy, the second address; change, by the proxy, the address of the proxy to the second address;

receive, at the second address of the proxy, a second request for access to the network from the application; and

forward, by the proxy, the second request to the network on behalf of the application from the second address of the proxy.

18. The at least one medium of claim 17 , wherein the code is operable to determine, by the proxy, the second address by selecting, by the proxy, the second address from a list of available addresses.

19. The at least one medium of claim 17 , wherein the first address and the second address are Internet Protocol (IP) addresses.

20. The at least one medium of claim 17 , wherein the first address and the second address are Domain Name System (DNS) addresses.

21. The at least one medium of claim 17 , wherein the code is operable to send the second address to the application prior to receiving the second request.

22. The at least one medium of claim 17 , wherein the code is operable to determine, by the proxy, the second address by using a key to generate the second address, the key being known by the application.

23. The at least one medium of claim 22 , wherein the code is operable to generate, by the application, the second address using the key.

24. The at least one medium of claim 17 , wherein the code is operable to determine, by the proxy, a second address by registering and deregistering an IP address associated with the proxy with a plurality of DNS addresses.

Assignments (14)
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2025
From: UBS AG, STAMFORD BRANCH
To: FORCEPOINT, LLC; BITGLASS, LLC
Reel/Frame 070706/0263 →
CHANGE OF NAME Recorded Mar 21, 2025
From: FORCEPOINT FEDERAL HOLDINGS LLC
To: EVERFOX HOLDINGS LLC
Reel/Frame 070585/0625 →
SECURITY INTEREST Recorded Sep 29, 2023
From: FORCEPOINT FEDERAL HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC, AS COLLATERAL AGENT
Reel/Frame 065086/0822 →
CHANGE OF NAME Recorded May 12, 2021
From: FORCEPOINT LLC
To: FORCEPOINT FEDERAL HOLDINGS LLC
Reel/Frame 056216/0309 →
PATENT SECURITY AGREEMENT Recorded Jan 20, 2021
From: REDOWL ANALYTICS, INC.; FORCEPOINT LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 055052/0302 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jan 8, 2021
From: RAYTHEON COMPANY
To: FORCEPOINT LLC
Reel/Frame 055452/0207 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jan 8, 2021
From: RAYTHEON COMPANY
To: WEBSENSE, INC.; PORTAUTHORITY TECHNOLOGIES, LLC (FKA PORTAUTHORITY TECHNOLOGIES, INC.); RAYTHEON OAKLEY SYSTEMS, LLC; FORCEPOINT FEDERAL LLC (FKA RAYTHEON CYBER PRODUCTS, LLC, FKA RAYTHEON CYBER PRODUCTS, INC.)
Reel/Frame 055492/0146 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Feb 27, 2020
From: FORCEPOINT LLC
To: RAYTHEON COMPANY
Reel/Frame 052045/0482 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2017
From: FORCEPOINT FEDERAL LLC
To: FORCEPOINT LLC
Reel/Frame 043397/0460 →
CHANGE OF NAME Recorded Feb 16, 2016
From: RAYTHEON CYBER PRODUCTS, LLC
To: FORCEPOINT FEDERAL LLC
Reel/Frame 037821/0818 →
PATENT SECURITY AGREEMENT Recorded Jun 9, 2015
From: WEBSENSE, INC.; RAYTHEON OAKLEY SYSTEMS, LLC; RAYTHEON CYBER PRODUCTS, LLC (FORMERLY KNOWN AS RAYTHEON CYBER PRODUCTS, INC.); PORT AUTHORITY TECHNOLOGIES, INC.
To: RAYTHEON COMPANY
Reel/Frame 035859/0282 →
CHANGE OF NAME Recorded Jun 2, 2015
From: RAYTHEON CYBER PRODUCTS, INC.
To: RAYTHEON CYBER PRODUCTS, LLC
Reel/Frame 035806/0367 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 28, 2015
From: RAYTHEON COMPANY
To: RAYTHEON CYBER PRODUCTS, INC.
Reel/Frame 035774/0322 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2010
From: MCDOUGAL, MONTY D.
To: RAYTHEON COMPANY
Reel/Frame 024625/0350 →