# US 2023/0267232 A1 · System and method for protecting browser data

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

- Number: US 2023/0267232 A1
- Document ID: US20230267232A1
- Status: Published application
- Kind: A1
- Application number: 17/994,978
- Filed: 2022-11-28
- Published: 2023-08-24
- Earliest claimed: 2022-02-22
- Assignees: Uab 360 It
- Applicants: Uab 360 It
- Inventors: Mohamed Adly Amer ELGAAFARY; Aleksandr SEVCENKO
- Web page: https://patentgrep.com/patent/US20230267232A1

## CPC

- G06F 21/629: {to features or functions of an application}
- G06F 16/9538: Presentation of query results
- G06F 21/31: User authentication
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 9/0631: {Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for controlling access to process data includes encrypting process data of a process; receiving a request to access the process data; requesting a security code to access the encrypted process data; receiving the security code; authenticating the received security code; and granting access to the encrypted process data if the received security code is successfully authenticated and denying access to the encrypted process data if the received security code is not successfully authenticated.

## Claims

### Claim 1

A method for controlling access to process data comprising:
encrypting process data of a first process;
receiving a request from a second process different from the first process to access the process data;
requesting authentication information from the second process to access the encrypted process data;
receiving authentication information automatically generated by the second process upon the requesting;
authenticating the received authentication information; and
granting the second process access to the encrypted process data if the received authentication information is successfully authenticated and denying the second process access to the encrypted process data if the received authentication information is not successfully authenticated.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the first process is a browser.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the process data comprises at least one of a browser model, a browser version, or a browser configuration file.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the process data is patched before the process data is encrypted.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising performing a threat assessment for the request to access to the process data before requesting the authentication information.

### Claim 6 (depends on 5)

The method according to claim 5, wherein performing the threat assessment comprises noting a source associated with the request to access the process data, a time associated with the request to access the process data, and how many times access to the process data has been requested by the source.

### Claim 7 (depends on 5)

The method according to claim 5, wherein a threat notification is displayed to a user before the authentication information is requested.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the authentication information is a PIN.

### Claim 9 (depends on 1)

The method according to claim 1, further comprising locking the process data upon receipt of more than one denial of access to the requested process data.

### Claim 10

A non-transitory computer readable medium having instructions stored thereon, which, when executed by the at least one processor, causes the at least one processor to perform a method for controlling access to process data comprising:
encrypting process data of a first process;
receiving a request from a second process different from the first process to access the process data;
requesting authentication information from the second process to access the encrypted process data;
receiving authentication information automatically generated by the second process upon the requesting;
authenticating the received authentication information; and
granting the second process access to the encrypted process data if the received authentication information is successfully authenticated and denying the second process access to the encrypted process data if the received authentication information is not successfully authenticated.

### Claim 11 (depends on 10)

The non-transitory computer readable medium according to claim 10, wherein the first process is a browser.

### Claim 12 (depends on 11)

The non-transitory computer readable medium according to claim 11, wherein the process data comprises at least one of a browser model, a browser version, or a browser configuration file.

### Claim 13 (depends on 10)

The non-transitory computer readable medium according to claim 10, wherein the process data is patched before the process data is encrypted.

### Claim 14 (depends on 10)

The non-transitory computer readable medium according to claim 10, further comprising performing a threat assessment for the request to access to the process data before requesting the authentication information.

### Claim 15 (depends on 14)

The non-transitory computer readable medium according to claim 14, wherein performing the threat assessment comprises noting a source associated with the request to access the process data, a time associated with the request to access the process data, and how many times access to the process data has been requested by the source.

### Claim 16 (depends on 14)

The non-transitory computer readable medium according to claim 14, wherein a threat notification is displayed to a user before the authentication information is requested.

### Claim 17 (depends on 10)

The non-transitory computer readable medium according to claim 10, wherein the authentication information is a PIN.

### Claim 18 (depends on 10)

The non-transitory computer readable medium according to claim 10, further comprising locking the process data upon receipt of more than one denial of access to the requested process data.

### Claim 19

A system for controlling access to process data comprising:
at least one user device or a server configured to:
encrypt process data of a first process;
receive a request from a second process different from the first process to access the process data;
request authentication information from the second process to access the encrypted process data;
receive authentication information automatically generated by the second process upon the requesting;
authenticate the received authentication information; and
grant the second process access to the encrypted process data if the received authentication information is successfully authenticated and denying the second process access to the encrypted process data if the received authentication information is not successfully authenticated.

### Claim 20 (depends on 19)

The system of claim 19, wherein the process data is stored on the user device or the server.
