Facilitating encrypted persistent storage in browsers
US-2019386971-A1 · Dec 19, 2019 · US
US11531784B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11531784-B1 |
| Application number | US-202217677061-A |
| Country | US |
| Kind code | B1 |
| Filing date | Feb 22, 2022 |
| Priority date | Feb 22, 2022 |
| Publication date | Dec 20, 2022 |
| Grant date | Dec 20, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A method for controlling access to process data comprising: encrypting process data of a first browser; receiving a request from a second browser to access the process data; performing a threat assessment for the request to access to the process data; displaying a threat notification based on the threat assessment; requesting a security code to access the encrypted process data; receiving the security code; authenticating the received security code; and granting the second browser access to the encrypted process data if the received security code is successfully authenticated and denying the second browser access to the encrypted process data if the received security code is not successfully authenticated. 2. The method according to claim 1 , wherein the process data comprises at least one of a browser model, a browser version, or a browser configuration file. 3. The method according to claim 1 , wherein the first browser is patched before the process data is encrypted using Advanced Encryption Standard (AES). 4. The method according to claim 1 , 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 process data, and how many times access to the process data has been requested by the source. 5. The method according to claim 1 , wherein the security code is a PIN. 6. 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. 7. The method according to claim 1 , wherein the process data is encrypted using Rivest-Shamir-Adlemand (RSA) encryption. 8. The method according to claim 1 , wherein the process data is encrypted using Elliptic Curve. 9. The method according to claim 1 , wherein the process data is encrypted using Advanced Encryption Standard (AES). 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 browser; receiving a request from a second browser to access the process data; performing a threat assessment for the request to access to the process data; displaying a threat notification based on the threat assessment; requesting a security code to access the encrypted process data; receiving the security code; authenticating the received security code; and granting the second browser access to the encrypted process data if the received security code is successfully authenticated and denying the second browser access to the encrypted process data if the received security code is not successfully authenticated. 11. The medium according to claim 10 , wherein the process data comprises at least one of a browser model, a browser version or a browser configuration file. 12. The medium according to claim 10 , wherein performing the threat assessment includes identifying at least one of a source associated with the request, a time associated with the request, or how many times access to the process data has been requested by the source. 13. The 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. 14. The medium according to claim 10 , wherein the process data is encrypted using Rivest-Shamir-Adlemand (RSA) encryption. 15. The medium according to claim 10 , wherein the process data is encrypted using Elliptic Curve. 16. The medium according to claim 10 , wherein the process data is encrypted using Advanced Encryption Standard (AES).
Presentation of query results · CPC title
Providing cryptographic facilities or services · CPC title
User authentication · CPC title
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 · CPC title
to features or functions of an application · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.