# US 2024/0205287 A1 · Systems and methods to protect against information disclosure

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0205287 A1
- Document ID: US20240205287A1
- Status: Published application
- Kind: A1
- Application number: 18/067,875
- Filed: 2022-12-19
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: Salesforce, Inc.
- Applicants: Salesforce, Inc.
- Inventors: Jose Lejin P. J.
- Web page: https://patentgrep.com/patent/US20240205287A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- H04L 63/168: {above the transport layer}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 65/401: wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for protecting against sensitive data disclosure includes receiving a user request to launch a web application in a web browser; loading code for the web application in the web browser; requesting session initialization from a web server; and receiving a dynamically and randomly generated URL map specific to a session from the web server, wherein the URL map identifies a plurality of randomly generated URL positions and for each URL position a randomly generated number of characters to skip. The method further includes modifying sensitive information associated with a URL in accordance with the URL map; transmitting the URL with the modified sensitive information to the web server; and receiving a requested data object from the web server, wherein the web server decoded the URL with the modified sensitive information to recover the sensitive information and used the decoded URL to access the data object.

## Claims

### Claim 1

A computing system comprising:
a server-side component comprising non-transitory computer readable media encoded with programming instructions configurable to cause a processor in a server-side computing system to:
generate a dynamically and randomly generated map specific to a session, the map identifying a plurality of randomly generated URL positions and for each URL position a randomly generated number of characters to skip;
transmit the dynamically and randomly generated map to a client-side computing system for use with a specific session; and
responsive to a GET call request received from the client-side computing system for the specific session, decode a URL associated with the GET call request using the dynamically and randomly generated map; and
a client-side component comprising non-transitory computer readable media encoded with programming instructions configurable to cause a processor in the client-side computing system to:
modify a URL associated with the GET call request in accordance with the dynamically and randomly generated map received from the server-side computing system for the specific session; and
transmit the GET call request with the modified URL to the server-side computing system.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein to generate a dynamically and randomly generated map specific to a session, the programming instructions cause the processor in the server-side computing system to:
retrieve app owner input on endpoints to be protected and maximum GET URL length; and
generate a dynamically and randomly generated map specific to a session based on the app owner input on endpoints to be protected and maximum GET URL length.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein to decode a URL associated with the GET call request using the dynamically and randomly generated map, the programming instructions cause the processor in the server-side computing system to:
extract a URL after an endpoint of a main domain name;
remove a number of characters specified in the URL map to be skipped at a first URL position specified in the URL map; and
repeatedly remove the number of characters specified in the map to be skipped at a next URL position specified in the map until no more URL positions are left.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein to modify a URL associated with the GET call request in accordance with the randomly generated map, the programming instructions cause the processor in the client-side computing system to:
generate for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position;
build a dynamic and random URL by adding at each URL position specified in the map the quantity of randomly generated characters generated for the URL position; and
prepend a main domain name to the dynamic and random URL.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein to modify a URL associated with the GET call request in accordance with the randomly generated map, the programming instructions cause the processor in the client-side computing system to:
store the URL map in a local variable in session context;
monitor for a GET call;
detect a GET call;
responsive to detecting a GET call, generate for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position; and
build a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the server-side component is configured to cause the processor in the server-side computing system to implement a URL map server controller and a dynamic random URL server controller, and wherein:
the URL map server controller is configured to build random URL map for a specific session and transmit the map to the client-side computing system; and
the dynamic random URL server controller is configured to, responsive to being informed of a GET call URL with dynamic random characters added, get map information from the URL map server controller and restore original URL information.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the client-side component is configured to cause the processor in the client-side computing system to implement a GET call detector, a URL map client controller, and a dynamic random URL client controller, and wherein:
the GET call detector is configured to monitor calls for a GET call, detect a GET call, and inform the URL map client controller of the detected GET call;
the URL map client controller is configured to store the URL map in a local variable in session context, generate for each URL position specified in the map a quantity of randomly generated characters equal to a number of characters to skip specified in the map for the URL position, and inform the dynamic random URL client controller of the generated quantity of randomly generated characters; and
the dynamic random URL client controller is configured to build a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position and transmit the GET call with the modified URL to server-side computing system.

### Claim 8

A method of executing a GET call request, the method comprising:
generating, in a server-side component, a dynamically and randomly generated URL map specific to a session, the map identifying a plurality of randomly generated URL positions and for each URL position a randomly generated number of characters to skip;
transmitting, by the server-side component over a network, the URL map to a client-side component for use with a specific session;
modifying, by the client-side component, original URL information associated with a GET call request in accordance with the URL map received from the server-side component for the session;
transmitting, by the client-side component over the network, the GET call request with the modified URL information to the server-side component;
decoding, by the server-side component, the modified URL associated with the GET call request using the URL map responsive to receiving the GET call request from the client-side component for the session; and
recovering, by the server-side component, the original URL information based on the decoding.

### Claim 9 (depends on 8)

The method of claim 8, wherein generating a dynamically and randomly generated map specific to a session comprises:
retrieving app owner input on endpoints to be protected and maximum GET URL length; and
generating a dynamically and randomly generated map specific to a session based on the app owner input on endpoints to be protected and maximum GET URL length.

### Claim 10 (depends on 8)

The method of claim 8, wherein decoding the modified URL associated with the GET call request using the URL map comprises:
extracting a URL after an endpoint of a main domain name;
removing a number of characters specified in the URL map to be skipped at a first URL position specified in the map; and
repeatedly removing a number of characters specified in the map to be skipped at a next URL position specified in the URL map until no more URL positions are left.

### Claim 11 (depends on 8)

The method of claim 8, wherein modifying original URL information comprises:
generating for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position;
building a dynamic and random URL by adding at each URL position specified in the map the quantity of randomly generated characters generated for the URL position; and
prepending a main domain name to the dynamic and random URL.

### Claim 12 (depends on 8)

The method of claim 8, wherein modifying original URL information associated with a GET call request in accordance with the URL map received from the server-side component for the session comprises:
storing the URL map in a local variable in session context;
monitoring for a GET call;
detecting a GET call;
responsive to detecting a GET call, generating for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position; and
building a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position.

### Claim 13 (depends on 8)

The method of claim 8, further comprising:
implementing, by the server-side component, a URL map server controller and a dynamic random URL server controller;
building the random URL map for a specific session and transmitting the map to the client-side component, by the URL map server controller; and
obtaining map information from the URL map server controller and restoring the original URL information, by the dynamic random URL server controller.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
implementing, by the client-side component, a GET call detector, a URL map client controller, and a dynamic random URL client controller;
monitoring calls for a GET call, detecting a GET call, and informing the URL map client controller of the detected GET call, by the GET call detector;
storing the URL map in a local variable in session context, generating for each URL position specified in the URL map a quantity of randomly generated characters equal to a number of characters to skip specified in the URL map for the URL position, and informing the dynamic random URL client controller of the generated quantity of randomly generated characters, by the URL map client controller; and
building a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position, and transmit the GET call with the modified URL to server-side component, by the dynamic random URL client controller.

### Claim 15

A non-transitory computer readable medium encoded with programming instructions configurable to cause a processor in a client-side computing system to perform a method, the method comprising:
receiving a user request to launch a web application in a web browser;
loading code for the web application in the web browser;
requesting session initialization from a web server;
receiving a dynamically and randomly generated URL map specific to a session from the web server, wherein the URL map identifies a plurality of randomly generated URL positions and for each URL position a randomly generated number of characters to skip;
modifying sensitive information associated with a URL at which a data object may be retrieved in accordance with the URL map received from the web server;
transmitting the URL with the modified sensitive information to the web server;
receiving the requested data object from the web server, wherein the web server decoded the URL with the modified sensitive information to recover the sensitive information and used the decoded URL to access the data object; and
causing the data object to be displayed to a user via the web browser.

### Claim 16 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the dynamically and randomly generated URL map specific to a session was generated by:
retrieving app owner input on endpoints to be protected and maximum GET URL length; and
generating a dynamically and randomly generated map specific to a session based on the app owner input on endpoints to be protected and maximum GET URL length.

### Claim 17 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the web server decoded the URL with the modified sensitive information by:
extracting a URL after an endpoint of a main domain name;
removing a number of characters specified in the URL map to be skipped at a first URL position specified in the map; and
repeatedly removing a number of characters specified in the map to be skipped at a next URL position specified in the URL map until no more URL positions are left.

### Claim 18 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein modifying sensitive information associated with a URL comprises:
generating for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position;
building a dynamic and random URL by adding at each URL position specified in the map the quantity of randomly generated characters generated for the URL position; and
prepending a main domain name to the dynamic and random URL.

### Claim 19 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein modifying sensitive information associated with a URL comprises:
storing the URL map in a local variable in session context;
monitoring for a GET call;
detecting a GET call;
responsive to detecting a GET call, generating for each URL position specified in the URL map a quantity of randomly generated characters equal to the number of characters to skip specified in the URL map for the URL position; and
building a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position.

### Claim 20 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the method further comprises:
implementing a GET call detector, a URL map client controller, and a dynamic random URL client controller;
monitoring calls for a GET call, detecting a GET call, and informing the URL map client controller of the detected GET call, by the GET call detector;
storing the URL map in a local variable in session context, generating for each URL position specified in the URL map a quantity of randomly generated characters equal to a number of characters to skip specified in the URL map for the URL position, and informing the dynamic random URL client controller of the generated quantity of randomly generated characters, by the URL map client controller; and
building a dynamic and random URL by adding at each URL position specified in the URL map the quantity of randomly generated characters generated for the URL position, and transmit the GET call with the modified URL to server-side component, by the dynamic random URL client controller.
