Browser extension security system

US11468172B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11468172-B2
Application numberUS-201916529987-A
CountryUS
Kind codeB2
Filing dateAug 2, 2019
Priority dateFeb 6, 2019
Publication dateOct 11, 2022
Grant dateOct 11, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Presented herein are techniques for automatically generating information about risks associated with browser extensions used by browsers in an enterprise network for purposes of determining whether to whitelist a browser extension in response to a request from a user. A request to install a browser extension is obtained from a user device of a plurality of user devices associated with an organization, wherein the request comprises an extension identifier for the browser extension. A risk score is generated for the browser extension based on risk values for each of one or more permissions requested by the browser extension. The risk score is compared to a threshold value to determine whether the browser extension satisfies risk standards of the organization, and if so, the browser extension is automatically added to a whitelist of permitted extensions for future installation on the plurality of user devices.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method comprising: obtaining, from a user device of a plurality of user devices associated with an organization, a first request to install a browser extension for a browser of the user device, wherein the first request comprises an extension identifier and a business justification for the browser extension; in response to obtaining the first request to install the browser extension, generating, for the browser extension, a risk score that is based on risk values for each of one or more permissions requested in a second request by the browser extension, wherein each permission provides access to particular data of the browser; determining whether the browser extension satisfies risk standards of the organization by comparing the risk score to a threshold value for the organization; and in response to determining that the browser extension satisfies the risk standards, automatically adding the browser extension to a whitelist of permitted extensions for approved installation on the plurality of user devices. 2. The computer-implemented method of claim 1 , further comprising generating a risk assessment report by: accessing, via an application programming interface, information pertaining to the browser extension from a browser extension store; and analyzing the information to generate the risk assessment report. 3. The computer-implemented method of claim 2 , wherein the information comprises one or more of: manifest information, permission information, content security policy, and extension metadata. 4. The computer-implemented method of claim 2 , wherein analyzing the information comprises determining whether the browser extension includes one or more of: a vulnerability in a third-party library, a dangerous function, and a dangerous entry point. 5. The computer-implemented method of claim 1 , further comprising: in response to automatically whitelisting the browser extension, transmitting an instruction to the user device to install the browser extension. 6. The computer-implemented method of claim 1 , wherein the browser includes a gatherer extension, and wherein the gatherer extension obtains the extension identifier from the browser. 7. The computer-implemented method of claim 1 , further comprising: determining that an updated version of the browser extension is available; generating, for the updated version of the browser extension, an updated risk score that is based on risk values for each of one or more permissions requested by the updated version of the browser extension; determining whether the updated version of the browser extension satisfies risk standards of the organization by comparing the updated risk score to a threshold value for the organization; and in response to determining that the browser extension does not satisfy the risk standards, removing the browser extension from the whitelist. 8. The computer-implemented method of claim 1 , wherein a user of the user device is prompted to provide the business justification for installation of the browser extension. 9. An apparatus comprising: a communication interface configured to enable network communications; one or more computer processors; one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media for execution by at least one of the one or more computer processors, that when executed by the one or more computer processors, cause the one or more computer processors to: obtain, from a user device of a plurality of user devices associated with an organization, a first request to install a browser extension for a browser of the user device, wherein the first request comprises an extension identifier and a business justification for the browser extension; in response to obtaining the first request to install the browser extension, generate, for the browser extension, a risk score that is based on risk values for each of one or more permissions requested in a second request by the browser extension, wherein each permission provides access to particular data of the browser; determine whether the browser extension satisfies risk standards of the organization by comparing the risk score to a threshold value for the organization; and in response to determining that the browser extension satisfies the risk standards, automatically add the browser extension to a whitelist of permitted extensions for approved installation on the plurality of user devices. 10. The apparatus of claim 9 , wherein the program instructions to generate a risk assessment report further cause the one or more processors to: access, via an application programming interface, information pertaining to the browser extension from a browser extension store; and analyze the information to generate the risk assessment report. 11. The apparatus of claim 10 , wherein the information comprises one or more of: manifest information, permission information, content security policy, and extension metadata. 12. The apparatus of claim 10 , wherein the program instructions to analyze the information comprise instructions to determine whether the browser extension includes one or more of: a vulnerability in a third-party library, a dangerous function, and a dangerous entry point. 13. The apparatus of claim 9 , wherein the program instructions further comprise instructions to cause the one or more processors to: in response to automatically whitelisting the browser extension, transmit an instruction to the user device to install the browser extension. 14. The apparatus of claim 9 , wherein the browser includes a gatherer extension, and wherein the gatherer extension obtains the extension identifier from the browser. 15. The apparatus of claim 9 , wherein the program instructions further comprise instructions to cause the one or more processors to: determine that an updated version of the browser extension is available; generate, for the updated version of the browser extension, an updated risk score that is based on risk values for each of one or more permissions requested by the updated version of the browser extension; determine whether the updated version of the browser extension satisfies risk standards of the organization by comparing the updated risk score to a threshold value for the organization; and in response to determining that the browser extension does not satisfy the risk standards, remove the browser extension from the whitelist. 16. One or more non-transitory computer readable storage media encoded with program instructions that, when executed by one or more processors, cause the one or more processors to: obtain, from a user device of a plurality of user devices associated with an organization, a first request to install a browser extension for a browser of the user device, wherein the first request comprises an extension identifier and a business justification for the browser extension; in response to obtaining the first request to install the browser extension, generate, for the browser extension, a risk score that is based on risk values for each of one or more permissions requested in a second request by the browser extension, wherein t each permission provides access to particular data of the browser; determine whether the browser extension satisfies risk standards of the organization by comparing the risk score to a threshold value for the organization; and in response to determining that the browser extension satisfies the risk standards, automatically add the browser extension to a whitelist of permitted

Assignees

Inventors

Classifications

  • Test or assess software · CPC title

  • Risk analysis of enterprise or organisation activities · CPC title

  • Access rights, e.g. capability lists, access control lists, access tables, access matrices · CPC title

  • Installation · CPC title

  • Plug-ins; Add-ons · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11468172B2 cover?
Presented herein are techniques for automatically generating information about risks associated with browser extensions used by browsers in an enterprise network for purposes of determining whether to whitelist a browser extension in response to a request from a user. A request to install a browser extension is obtained from a user device of a plurality of user devices associated with an organi…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06Q10/0635. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Oct 11 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 6 related publications on this page (citations in our corpus or others sharing the same primary CPC).