IP Library › Granted Patent US 11,792,133
Granted Patent B2
US 11,792,133 · App. 17/834,286 · Granted Oct 17, 2023

Systems and methods for performing header protection in distributed systems

Inventors: Rama Rao Katta (Fremont, CA); Kasirao Velugu (Bengaluru, IN)
H04L47/783H04L47/72H04L47/762H04L67/146H04L69/22
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 11,792,133
App. No.
17/834,286
Filed
Jun 7, 2022
Granted
Oct 17, 2023
Kind
B2
Art Unit
2419
USPC
709/225
Abstract

Described embodiments provide systems and methods performing header protection. A device can receive from a client, a request relating to a first resource, for a second resource. The device can determine, using an identifier for the session, whether an address of the first resource has been previously accessed by the client during the session. The device can verify, using an address of the second resource, whether the address of the second resource is mapped to the address of the first resource for the session between the client and the device. The device can determine whether to provide access to the second resource responsive to the address of the first resource being previously accessed by the client during the session and the address of the second resource being mapped to the address of the first resource for the session.

Claims (33)

1. A method comprising:

receiving, by a first device from a second device that accessed a first resource at a first address during a session via the first device, a request to access a second resource at a second address different than the first address of the first resource, the request identifying an identifier of the session;

identifying, by the first device using a list maintained by the first device based on the identifier of the session, that the second device had accessed the first address of the first resource during the session;

determining, by the first device using the list, that the second address of the second resource is mapped to the first address of the first resource for the session; and

providing, by the first device responsive to the request, the second device access to the second resource responsive to determining that the second address of the second resource is mapped to the first address of the first resource for the session.

2. The method of claim 1 , further comprising establishing, by the first device, the list for the session responsive to establishing the session between the first device and the second device.

3. The method of claim 1 , further comprising generating, by the first device, a first identifier for the first address of the first resource.

4. The method of claim 3 , further comprising mapping, by the first device, in the list the first address of the first resource to the first identifier.

5. The method of claim 1 , further comprising receiving, by the first device, from the second device the first resource, the first resource including the first address and determining, by the first device, the first address from the first resource.

6. The method of claim 1 , further comprising identifying, by the first device, the list for the session using the identifier of the session.

7. A method comprising:

receiving, by a first device from a second device that accessed a first resource at a first address during a session via the first device, a request to access a second resource at a second address different than the first address of the first resource, the request identifying an identifier of the session;

identifying, by the first device using a list maintained by the first device based on the identifier of the session, that the second device had accessed the first address of the first resource during the session;

determining, by the first device using the list, that the second address of the second resource is not mapped to the first address of the first resource for the session; and

denying, by the first device responsive to the request, the second device access to the second resource responsive to determining that the second address of the second resource is not mapped to the first address of the first resource for the session.

8. The method of claim 7 , further comprising establishing, by the first device, the list for the session responsive to establishing the session between the first device and the second device.

9. The method of claim 7 , further comprising generating, by the first device, a first identifier for the first address of the first resource.

10. The method of claim 9 , further comprising mapping, by the first device, in the list the first address of the first resource to the first identifier.

11. The method of claim 7 , further comprising receiving, by the first device, from the second device the first resource, the first resource including the first address and determining, by the first device, the first address from the first resource.

12. The method of claim 7 , further comprising identifying, by the first device, the list for the session using the identifier of the session.

13. A system comprising:

a first device, comprising one or more processors and memory, configured to:

receive from a second device that accessed a first resource at a first address during a session via the first device, a request to access a second resource at a second address different than the first address of the first resource, the request identifying an identifier of the session;

identify, using a list maintained by the first device for the identifier of the session, that the second device had accessed the first address of the first resource during the session;

determine, using the list, whether the second address of the second resource is mapped to the first address of the first resource for the session; and

determine, responsive to the request, whether to provide or deny access by the second device access to the second resource responsive to determining whether the second address of the second resource is mapped to the first address of the first resource for the session.

14. The system of claim 13 , wherein the first device is further configured to determine that the second address of the second resource is mapped to the first address of the first resource for the session and provide access to the second resource.

15. The system of claim 13 , wherein the first device is further configured to determine that the second address of the second resource is not mapped to the first address of the first resource for the session and deny access to the second resource.

16. The system of claim 13 , wherein the first device is further configured to establish the list for the session responsive to establishing the session between the first device and the second device.

17. The system of claim 13 , wherein the first device is further configured to generate a first identifier for the first address of the first resource.

18. The system of claim 17 , wherein the first device is further configured to map in the list the first address of the first resource to the first identifier.

19. The system of claim 13 , wherein the first device is further configured to receive from the second device the first resource, the first resource including the first address and determining the first address from the first resource.

20. The system of claim 13 , wherein the first device is further configured to identify the list for the session using the identifier of the session.