How to List Chrome Extensions Across All Mac, Windows, and Linux Devices

Introduction

Google Chrome provides the ability to extend the core functionality of the browser via the installation of 'extensions'. Extensions may be published by Google by 3rd party authors, and can be distributed either through the Google Chrome Web Store or via manual download and installation.

A small subset of extensions are installed by default by Google (eg. Google Docs, Google Sheets, Google Slides, etc.).

Chrome extensions are installed on a per-profile basis and can be enabled or disabled while remaining installed.

Chrome Extensions can do, among other things:

• Extend the functionality of Google Chrome (such as integrating with installed apps like 1Password)

• Customize the appearance of Google Chrome through the installation of 'Theme' extensions

Kolide collects metadata about Chrome Extensions such as their name, their publisher, when they were installed, and whether they are enabled.

In addition to this host-specific data, Kolide enriches this information with Chrome Webstore analytics (such as rating and download count) and security advisories such as permissions risk scores.

What Chrome Extension Data Can Kolide Collect?

Kolide's endpoint agent bundles in osquery to efficiently collect Chrome Extensions from Mac, Windows, and Linux devices in your fleet. Once collected, Kolide will parse, clean up, and centrally store this data in Inventory for your team to view, query, or export via API.

Kolide meticulously documents every piece of data returned so you can understand the results.

Chrome Extensions Schema

What Can You Do With This Information?

Kolide enables you to write your own queries against the data the agent collects. This allows you to build your own reports and API endpoints. For example, you can:

SELECT
device_name,
name AS extension_name,
version
 FROM device_chrome_extensions WHERE name ILIKE '%Grammarly%'

WITH 
collated_extensions AS (
  SELECT
    device_id,
    browser_type AS browser,
    uid, 
    name, 
    identifier, 
    version, 
    '' AS profile
  FROM device_chrome_extensions
  UNION ALL
  SELECT
    device_id,
    'firefox' AS browser,
    uid, 
    name, 
    identifier, 
    version, 
    '' AS profile
  FROM device_firefox_addons
  UNION ALL
  SELECT
    device_id,
    'safari' AS browser,
    uid, 
    name, 
    team_identifier AS identifier, 
    version, '' AS profile
  FROM mac_safari_extensions
  )
  SELECT 
    COUNT(*) AS install_count, 
    name, 
    browser, 
    identifier, 
    version 
  FROM collated_extensions 
  WHERE name ILIKE '%1password%'
  GROUP BY identifier, name, browser, version
  ORDER BY install_count DESC
  LIMIT 10

Why Should I Collect Chrome Extensions?

Due to the high-value of a user's browser activity, Chrome is a frequent target of malware authors who wish to obtain secure details about an end-user (eg. sites they visit, credit cards they use, etc.) and its extension configuration should be regularly audited to ensure that they are not at risk of attack.

Chrome Extension installations are cataloged and tracked to facilitate a number of potential purposes, for example:

• Reviewing installed extensions to verify the desired configuration of Google Chrome (eg. 1Password extension is installed)

• Discovering potential malicious extensions

• Identifying extensions with overreaching permissions (eg. ability to record all browsing history)

End-User Privacy Consideration

Kolide practices Honest Security. We believe that data should be collected from end-user devices transparently and with privacy in mind.

Extensions which you install could reveal suggestive details about your personal browsing habits if they are named after a specific service you utilize. For example:

• eBay Bid Sniper
• Adult Website Video Downloader
• Netflix Region Unblocker
• Chrome BitCoin Miner

When you use Kolide to list Chrome Extension data from end-user devices, Kolide gives the people using those devices insight into exactly what data is collected, the privacy implications, and who on the IT team can see the data. This all happens in our end-user privacy center which can be accessed directly by employees.