Skip to content
docs.browsium

[About this Release]

This document lists new features and known issues, and potential incompatibilities as of the release date. If you discover an issue, please review the Known Issues list below to determine if it has already been documented. If the issue is not referenced, please visit the Browsium Support website for troubleshooting tips, product documentation, and the option to submit support tickets.

[What is Proton]{.underline}

Section titled “[What is Proton]{.underline}”

Proton, the newest module in Browsium’s browser management suite, is an easy to use web application inventory and analytics solution for enterprise IT. Along with its comprehensive inventory capabilities, Proton also provides critical correlations between browsers, web applications, and add-ons, giving IT teams the actionable insights they need to make better decisions. As a result, Proton is an invaluable resource in every modern IT department’s management toolset.

[What’s New in this Release]{.underline}

Section titled “[What’s New in this Release]{.underline}”

This section of the release notes is reserved for notable changes and new features since the prior version

[What’s new in Proton 4.9.7]{.underline} This section details changes to Proton since the prior version, Proton 4.9.6

  • Update to browser extension manifest V3

  • Added ‘Extension Analyzer’ feature.

[Minimum System Requirements]{.underline}

Section titled “[Minimum System Requirements]{.underline}”

Browsium Client Management Server & Database

Operating System Windows Server 2008 R2 or later

.NET Framework Version 4.0 or later

Additional Components Microsoft IIS 7 or later
Microsoft SQL Server 2017 Express

Processor 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor

Memory 4 GB system RAM

Section titled “Memory 4 GB system RAM”

Browsium Client

+----------------------+--------------------------------------------------------------------------+ | Operating System | Windows 10 (1607) or later | | | | | | Windows Server 2008 R2 or later (for multi-user terminal servers) | +======================+==========================================================================+ | Browsers | Microsoft Internet Explorer 11 | | | | | | Microsoft Edge (Legacy) 42 or later | | | | | | Microsoft Edge (Chromium) 80 or later | | | | | | Google Chrome 39 or later | | | | | | Mozilla Firefox 52 or later (41 or later with Browsium legacy extension) | +----------------------+--------------------------------------------------------------------------+ | .NET Framework | Version 4.0 or later (full version only) | | | | | | AND | | | | | | .NET Framework 3.5 | | | | | | For use with Edge: | | | | | | .NET Native Runtime 1.4 | | | | | | .NET Native Framework 1.5 | +----------------------+--------------------------------------------------------------------------+ | Processor | 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor | +----------------------+--------------------------------------------------------------------------+ | Memory | 1 GB total system RAM; 2 GB for use on multi-user terminal servers | +----------------------+--------------------------------------------------------------------------+

[Installing and Using This Release]{.underline}

Section titled “[Installing and Using This Release]{.underline}”

  • Run Proton-Setup.exe to install the server components of Proton. Once you have a functioning server, then you may install the Browsium Client using Browsium-ClientSetup.exe, which utilizes the address of your Proton server.

  • To access Proton Manager, choose (or search for) Proton Manager from the Start menu of the system running Proton Server. This will provide a special link to the Manager, with your server URL embedded, to automatically populate the server URL in the login screen.

    • If you’re accessing Proton Manager for the first time, select Create Account to create your Proton Administrator account. The first account is auto-approved. Subsequent accounts will need to be approved via the Manager’s Users page.

  • Browsium Client extensions for Internet Explorer, Edge, Chrome, and Firefox must be enabled before Proton activity data is recorded from each browser. See section 5 of the Proton Administration Guide for details on managing browser extensions in an enterprise deployment.

  • Proton is designed so that older clients can communicate with and send activity data to newer versions of Proton server. However, we recommend that you upgrade clients soon after upgrading the server to provide comprehensive collection of new inventory and activity data elements.

    • Browsium Client 4.9 can be installed as a direct upgrade to Browsium Client 4.x, or Proton Client 1.x, and will automatically inherit the Proton Server URL value from the prior client installation.

    • Proton Server 4.9 can be installed as a direct upgrade to Proton Server 4.x or 1.x. Both the Server and Database must be upgraded, so check both the Server and Database boxes during setup. If these are running on separate server systems, only check the box for the component running on that system.

  • Read the Proton Administration Guide for more information on installing and using Browsium Proton.

[]{.underline}

[Known Issues]{.underline}

Section titled “[Known Issues]{.underline}”

  • Due to a bug in Microsoft Edge (Chromium) 80, the browser extension will not be automatically enabled. To force enablement, the extension will have to be installed into Edge’s extension install forcelist. Once this bug is addressed by Microsoft the extension will be automatically enabled without this additional step.

  • Due to the forced user notification change in the way Mozilla Firefox handles sideloading of extensions, starting with Firefox 74 Browsium Client requires the use of the ESR to ensure extensions are auto-enabled during installation. Use of the non ESR will prohibit automatic enablement of the Browsium Client Extension.

  • Some users may experience an installation failure, resulting in a loop, with the Microsoft Visual C++ 2017 redistributable (x86 and x64) installers. This is an issue with the prerequisite installation process and not the Browsium Client installer. To resolve this issue, manually install the Visual C++ runtimes prior to installing the Browsium Client.

  • Proton Manager may throw an exception when attempting to export CSV files with large number of rows. The CSV export feature was designed for smaller reporting uses. For larger data exports, query the Proton database directly using alternate reporting tools.

  • The name of the Proton database cannot have a ”.” in the string (e.g., naming the database “Proton4.4”). Completing set-up with such a string will result in failure to properly set up the Proton database.

  • Java usage detection may detect the incorrect version if the web site requesting the Java applet is only open briefly, either because the tab was closed or because there was a navigation to another web site.

  • Java usage detection may detect the incorrect version if there are navigations to multiple web sites requesting Java applets in a tab and one of the web sites uses a non-default version of Java. For example, if there is a navigation to site A for which Ion is remediating a non-default version of Java followed by a navigation to site B for which the default version of Java is used, then Proton may detect that site B used the non-default version of Java that was used by site A.

  • As part of creating an inventory of ActiveX components installed on a machine, Proton will attempt to load the ActiveX components to test the safety flags. If Proton cannot load the ActiveX component for any reason (e.g., the component has dependencies not loaded by Proton), Proton will not be able to determine the safety flags reported by the component’s module. Proton will still determine the safety flags reported in the registry for the component.

  • Java version detection during browsing activity may not be reported until the browser tab is closed because of the way Java interacts with the Internet Explorer DOM.

  • The version number of the Browsium Client extensions for Edge (Legacy and Chromium) Chrome and Firefox may not be an exact match with the version number of the Browsium Client and Internet Explorer extension. This is by design as the version and publishing mechanisms are different for each component. Consult the Proton Knowledge Base for a current list of the version numbers for each Proton component.

  • Running the Browsium Client on virtual machines that have been cloned may result in a duplicate machine SID causing Proton to only see inventory and activity data from one of the clients. It’s also possible that the client connected to the Proton Server may alternate, resulting in unpredictable inventory and activity data.

  • Proton does not provide an easy way to recover lost administrator passwords. If you forget your Proton administrator account password, contact Browsium Support for assistance. Direct access to the SQL database can be used to reset the accounts so you can re-create the first, auto-approved administrator account.

  • The bar chart on the Activity -> Web Application Usage page shows a bar for each application displayed in the table. When a large page size (e.g. 100 or 1000) is selected, the bar chart may become unreadable.

  • When you make a rule change, you can see the new or updated rule in the Manager, but the changes to web application mappings are not enacted immediately. Rule mapping is done in the background on the Proton database server. The length of time that takes varies depending on the size of the database, the change made, how many URLs the rule matches, the speed and load on the database server, and what other background processing is occurring.

[Contact]{.underline}

Section titled “[Contact]{.underline}”

For technical support, please visit the Browsium Support website.

[]{.underline}

[What’s New in Prior Releases]{.underline}

Section titled “[What’s New in Prior Releases]{.underline}”

[
What’s new in Proton 4.9.6]{.underline} This section details changes to Proton since the prior version, Proton 4.9.5

  • Added ‘Extension installation date’ parameter to Proton extension installation tracking.

[What’s new in Proton 4.9.5]{.underline} This section details changes to Proton since the prior version, Proton 4.9.4

  • Fixed customer portal download link for the Administration guide.

  • Added new filter for web activity by domain.

  • Fixed browser extension reporting bug in Proton manager.

[What’s new in Proton 4.9.4]{.underline} This section details changes to Proton since the prior version, Proton 4.9.3

  • Removed unused web navigation permission from chrome and edge extensions.

  • Explicitly set PKCS7 as the padding mode for cryptographic utility.

  • Updated cert for appx extension. 

  • Enabled whichconfig command results to console instead of dialog box.

  • Updated EULA language displayed during installation.

  • Changed default machine SID retrieval strategy to 2 (Randomized SID) on new client installs only. Machine SID retrieval strategy can now also be specified via command line on CLI install.

  • Added Windows 11 logos to reporting.

[What’s new in Proton 4.9.3]{.underline} This section details changes to Proton since the prior version, Proton 4.9.2

  • Fixed an issue where the browser pie chart on the Browsium Client Manager dashboard may show incorrect counts for Microsoft Edge.

[What’s new in Proton 4.9.2]{.underline} This section details changes to Proton since the prior version, Proton 4.9.1

  • Fixed an issue when activating a module when another module is already active may require a system restart for the newly activated module to work properly.

[What’s new in Proton 4.9.1]{.underline} This section details changes to Proton since the prior version, Proton 4.8.7

  • Added SAML 2.0 Single Sign-On (SSO) support to the Browsium Client Management System.

    • Currently supported identity providers are Azure AD and Okta.

    • Contact Browsium Support for guidance on how to properly configure your BCMS deployment for SSO.

  • Added ability to disable local account creation in BCMS if desired.

  • Fixed an issue where, if about:newsfeed is set as IE’s homepage on a machine where both Browsium Ion and Proton are active, the URL that about:newsfeed resolves to may report as being attached to an Ion profile even though it isn’t.

[What’s new in Proton 4.9]{.underline} This section details changes to Proton since the prior version, Proton 4.8.7

  • Browsium Proton Client now supports Edge IE Mode.

  • Browsium Proton now collects TPM version information on client systems to facilitate Windows 11 readiness planning. TPM detection information has been added to client drilldowns in the Browsium Client Management System.

  • Added additional logging for advanced debugging scenarios.

  • Browsium Client now has a configurable system tray icon that notifies of an unlicensed state. By default, this icon is only visible when the client is unlicensed. This was added to help administrators know when they have accidentally deployed unlicensed clients.

  • Running the “whichconfig” command against the Browsium Controller will now display seat reservation / licensing information.

  • Upgraded bundled version of SQL Server Express in the Browsium Client Management System installer to SQL Server 2017 Express. Reflecting upcoming end of life dates, SQL Server 2017 is now the minimum supported version of SQL Server for the Browsium Client Management System.

  • Added the ability to mark accounts in the Browsium Client Management System as “service” accounts which cannot be deleted.

[What’s new in Proton 4.8.7]{.underline} This section details changes to Proton since the prior version, Proton 4.8.6

  • Added enhanced logging for cryptographic exceptions thrown when certain cryptographic providers are not available on the system.

  • Fixed issue where pre-existing enterprise mode sitelist settings were incorrectly not getting honored when Ion was enabled.

  • Fixed issue where the BCMS database install would not succeed when utilizing service accounts that only had the DBCREATOR role assigned.

[What’s new in Proton 4.8.6]{.underline} This section details changes to Proton since the prior version, Proton 4.8.5

  • Added ability to retrieve machine SID from active directory machine account or by randomly generating a unique SID per machine

Fixed an issue where the browser extensions tab was visible in the client machine drilldown even when Proton was not activated and no browser extension inventory was collected.

[What’s new in Proton 4.8.5]{.underline} This section details changes to Proton since the prior version, Proton 4.8.4

  • Removed need for SQL CLR Types and SQL Server Shared Management Objects as prerequisites for BCMS installation.

  • Moved Visual C++ 2017 redistributable prerequisite installation to the pre-install phase of the client installer.

[What’s new in Proton 4.8.4]{.underline} This section details changes to Proton since the prior version, Proton 4.8.3

  • Fixed an issue where BCM Server nodes may not install correctly if trying to connect to a database via SQL authentication while being domain-joined.

[What’s new in Proton 4.8.3]{.underline} This section details changes to Proton since the prior version, Proton 4.8.2

  • Fixed an issue in the Browsium Client Management System installer that was blocking users from being able to specify database credentials in certain environmental configurations.

  • Fixed an issue where a prerequisite may fail to install when installing the Browsium Client Manager.

[What’s new in Proton 4.8.2]{.underline} This section details changes to Proton since the prior version, Proton 4.8.1

  • Fixed an issue with Ion broker incompatibility issue in Windows 10 build 2004 that was causing use of custom files to crash the managed tab process in some environments.

[What’s new in Proton 4.8.1]{.underline} This section details changes to Proton since the prior version, Proton 4.8.0

  • Fixed an issue where the Edge Classic extension may not be upgraded properly in certain multi-user desktop environments.

  • Fixed an issue where the legend for the zones chart on the dashboard page of the Browsium Client Manager may not display correctly.

  • Fixed an issue where the web applications bar chart on the dashboard page of the Browsium Client Manager may not display correctly.

[What’s new in Proton 4.8]{.underline} This section details changes to Proton since the prior version, Proton 4.7.1

  • Added support for the new Chromium-based Edge browser.

  • Fixed an issue where there may be a delay activating products on first logon due to the way certain multi-user environments are configured.

  • New product licenses set in the Browsium Client Management System no longer automatically update and is now an opt-in process.

  • Added additional logging to the Browsium Client Management System installer to help diagnose issues with certain rare IIS configurations.

Fixed an issue in the Browsium Client Manager where users were not able to drill down into Java version details on Java inventory reports.

[What’s new in Proton 4.7.1]{.underline}

This section details changes to Proton since the prior version, Proton 4.7

  • Updated installer platform to fix interaction with certain endpoint protection suites that caused file operation to be blocked during the cleanup step.

[What’s new in Proton 4.7]{.underline}

This section details changes to Proton since the prior version, Proton 4.6.4

  • Added relevant links to MITRE’s Common Vulnerabilities and Exposures (CVE) report to ActiveX and Browser Extension inventory reporting.

  • Fixed an issue where the Browsium Client Manager UI sometimes crashed if individual filters were cleared while viewing the Java applications by version report.

  • Fixed a display issue with performance report graphs.

  • Fixed a display issue with the web application user report.

  • Fixed an issue that could affect client installation on Windows 7 machines with no versions of the .NET Framework installed.

  • By default, the Browsium Client Management System now supports communicating with the Browsium Client over TLS 1.2 without any additional configuration.

  • Fixed an issue in Firefox 68+ where the client couldn’t reliably detect if the Firefox extension was enabled.

[What’s new in Proton 4.6.4]{.underline}

This section details changes to Proton since the prior version, Proton 4.6.3

  • Fixed issue where Chrome 75+ wasn’t being detected as part of Proton Inventory.

  • Fixed issue where automatic extension enablement was no longer working correctly in Firefox due to a change in the profile.ini format.

  • Added detection of Chrome extensions that have been added via the ExtensionInstallForcelist policy or via other managed methods.

[What’s new in Proton 4.6.3]{.underline}

This section details changes to Proton since the prior version, Proton 4.6.2

Changed Proton to use TLS 1.2 by default.

[What’s new in Proton 4.6.2]{.underline}

This section details changes to Proton since the prior version, Proton 4.6.1

  • No changes to Proton. Fixed an issue where Catalyst projects weren’t being properly sent to Edge in some environments.

[What’s new in Proton 4.6.1]{.underline} This section details changes to Proton since the prior version, Proton 4.6

  • General performance improvements with the Browsium Client Extension for Microsoft Edge.

[What’s new in Proton 4.6.0]{.underline} This section details changes to Proton since the prior version, Proton 4.5

  • The Browsium Proton Server is now integrated into the Browsium Client Management System. The Proton features can be enabled by entering a valid Proton license key.

  • AD site list filters are now sorted alphabetically.

[What’s new in Proton 4.5.0]{.underline} This section details changes to Proton since the prior version, Proton 4.4.2

  • The Browsium Proton Server is now integrated into the Browsium Client Management System. The Proton features can be enabled by entering a valid Proton license key.

  • Improved Java reporting.

  • Added reporting for Java versions 9 and 10.

  • AD site list filters are now sorted alphabetically.

[What’s new in Proton 4.4.2]{.underline} This section details changes to Proton since the prior version, Proton 4.4.1

  • Added multi select filters in Proton Manager.

  • Added ability to filter on OS in Proton Manager.

  • Added ability to start Proton in an inactive mode.

  • URL query strings are now ignored by default. Setting is configurable for organizations that wish to collect the full strings.

  • Added new “Attempts by URL” report under Java and ActiveX activity reporting tab.

  • All activity data in Proton database is now deleted upon enabling Anonymization. This is done to ensure no PII or unintended data remains available for view or potential disclosure.

  • Fixed an exception in Proton background activity processing.

  • Removed noisy error type event logs in Browsium Client that are generated because of temporary connectivity issues.

  • Improved performance of the Browsium Client while analyzing component (Java and ActiveX) usage.

  • Disabled auto-enabling Browsium Chrome Extension when “Load unpacked extensions” setting is disabled by system administrator.

  • Browsium Client queries AD fewer times by caching the responses for 7 days.

  • Browsium Client improves its resiliency on systems with WMI subsystem problems.

[What’s new in Proton 4.4.1]{.underline} This section details changes to Proton since the prior version, Proton 4.4

  • Fixes a setup dependency issue when Proton Manager is not installed on the same machine as Proton Server.

  • Fixes an exception while processing incoming activities from Proton Clients.

  • Fixes arithmetic overflow issue displaying performance reports.

  • Added check to reject all non-anonymized data when anonymization is enabled for all users and machines.

[What’s new in Proton 4.4]{.underline} This section details changes to Proton since the prior version, Proton 4.3.1

  • Adds support for Microsoft Edge.

    • Edge support requires systems be domain joined and side loading extensions enabled.

  • Adds support for 64-bit Firefox.

  • Adds Script Error Reporting for Chrome and Firefox for broader web application error detection.

  • Added Client Authentication Tokens and IP filtering for enhanced security.

  • Fixes an issue where changing settings in Configuration may revert Privacy settings to OFF.

[What’s new in Proton 4.3.1]{.underline} This section details changes to Proton since the prior version, Proton 4.3.

  • Improves file upload detection to properly detect the upload and properly capture the “uploaded to” field on more websites.

  • Improves detection of user accounts on Google properties.

  • Synced files detection no longer detects hidden metadata files from Dropbox.

  • Improves performance of synced files detection for collections with a very large number of individual files.

  • Fixes a bug in Proton Manager when navigating between pages where the page title changes but no navigation occurs.

  • Fixes a bug in user account detection so that it now functions properly even if a page has multiple forms that meet login criteria.

  • Fixes a bug in Proton Server that caused an arithmetic overflow error converting IDENTITY to data type tinyint.

  • Fixes a bug in Browsium Client Internet Explorer Extension so that it now properly registers itself as compatible with Internet Explorer Enhanced Protected Mode on Windows 8 and later.

  • Improves Browsium Client performance when it detects Proton Server is offline or unreachable.

[What’s new in Proton 4.3]{.underline} This section details changes to Proton since the prior version, Proton 4.2.3.

  • Fixes an issue where websites that relied on an overridden window.onLoad function were failing to render correctly in Firefox and Chrome when the Browsium Client extension was enabled.
    (This fix only available in build 4.3.0.286, slipstreamed into Proton release channel on 5 June 2017.)

  • Detection and reporting of user logins to select web applications provides key insights into SaaS account usage to rationalize and optimize SaaS licenses.

  • Detection and reporting of files shared via cloud services such as Dropbox and OneDrive exposes shadow IT usage and enables IT to preempt inadvertent information disclosure violations.

    • Provides comprehensive listing of all files shared via native cloud service client software installed on Windows PCs throughout the organization.

    • Companion file upload detection reports on files uploaded by end users to select websites via a browser.

  • Detection of native Windows cloud client applications such as Dropbox, Slack, Box, GoToMeeting, etc. provides detailed account usage reporting to track compliance and discover license optimization opportunities.

  • User account and file upload detection utilizes specialized client-side data extraction code for top cloud services. This code is kept current via Proton cloud service definitions which are automatically updated on Proton servers.

  • Redesigned performance analytics summarizes the performance of all web applications and surfaces how current load times compare with the historical average to aid in troubleshooting and performance optimization.

  • Detection of script errors from client browsers provides key troubleshooting insights so problems can be addressed before helpdesk calls come in.

  • Collection of server IP addresses aids in performance optimization and cloud migration reporting.

  • Server processing resilience improves performance of Proton servers under load.

  • Updated Firefox extension uses new WebExtensions model for better performance and reliability.

[What’s new in Proton 4.2.3]{.underline} This section details changes to Proton since the prior version, Proton 4.2.2.

  • Fixes a compatibility issue in the Browsium Internet Explorer Extension that could cause certain older ActiveX controls to crash when closing an Internet Explorer window.

[What’s new in Proton 4.2.2]{.underline} This section details changes to Proton since the prior version, Proton 4.2.

  • Fixes a timeout issue in Proton upgrade scripts while upgrading really large databases.

[What’s new in Proton 4.2]{.underline} This section details changes to Proton since the prior version, Proton 4.1.1.

  • Adds a powerful new set of web application performance analytics to enable enterprise-wide endpoint detection and diagnosis of web application performance issues.

  • Adds detection of 64-bit Java in both client inventory and activity.

  • Improves the performance and functionality of charts and graphs.

  • Improves client startup performance when some modules are inactive.

  • Improves detection of changes in user data (e.g. org unit).

  • Improves client data reporting robustness in server-not-available situations.

  • Improves performance and reliability of full export of datasets from Proton Manager.

  • Extends support for comprehensive user account password restrictions, including password expiration and custom regular expression password strength policies. See section 3.6.1 of the Proton admin guide for details.

  • Adds support for multi-process Firefox which is planned to become the default operating mode in Firefox 51 and later.

  • Fixes an issue that caused Java versions to sort incorrectly in certain reports.

[What’s new in Proton 4.1.1]{.underline} This section details changes to Proton since the prior version, Proton 4.1.

  • Fixes a problem in which initial client reporting of inventory information could take a long time to complete on the server. This resulted in initial scaling issues for large deployments. With this fix, initial inventory processing is many orders of magnitude faster.

  • Improves performance of ActiveX inventory reporting in Proton Manager.

  • Fixes an issue where Java application activity may sometimes not get reported.

  • Fixes an issue that caused changes to the Active Directory Organizational Unit for some users to not be reported to the Proton server.

[What’s new in Proton 4.1]{.underline} This section details changes to Proton since the prior version, Proton 4.0.

  • Comprehensive Java detection and reporting:

    • New suite of dedicated Java usage reports, with full export capabilities, simplifies access to Java usage information and provide the insights needed to proactively manage Java versions and security organization-wide.

    • New detection and reporting for Java applications running outside of web browsers provides a complete view of Java usage throughout the organization.

  • Comprehensive ActiveX control detection and reporting:

    • New suite of dedicated ActiveX usage reports simplifies access to ActiveX dependency and security information, by version and by web application.

    • New reporting on unused ActiveX controls identifies unnecessary attack surfaces to aid in defense-in-depth security mitigation.

  • New web browser and web application performance analytics:

    • Proton now collects and reports on page fetch and load times for every web application, the first of many planned features to provide comprehensive client-side performance analytics for enterprise web applications.

  • Other enhancements to existing Proton server and Browsium Client features:

    • Enhances Privacy Mode to optionally anonymize machine names in addition to previously supported user names and IP addresses.

    • Fixes an issue that caused IP address to be incompletely anonymized in specific network configuration cases.

    • Enhances bulk upload of rules to add support for Map rules (in addition to previously supported Ignore rules), along with new options to append new rules to the existing set or replace all rules with the new set.

    • Improves browser version detection and reporting to better handle multiple versions of the same browser on a single PC.

    • Adds the ability to pull organizational unit information from multiple properties in Active Directory.

    • General improvements to Browsium Client in the areas of stabilization, robustness, and performance.

    • Combines the splash screens for all modules into a single splash screen displaying configuration information for each module.

    • Cleans up client error logging, reducing the spurious error messages in Event Viewer.

    • Fixes a bug that occasionally caused document mode detection to fail.

    • Fixes a bug that caused Browsium Controller to crash on some systems while displaying the splash screen.

[What’s new in Proton 4.0]{.underline} This section details changes to Proton since the prior version, Proton 1.2.1.

  • The new, unified Browsium Client includes the agent functionality for Proton, Ion, and Catalyst, resulting in a single client deployment that works with all modules in the Browsium browser management suite.

    • Browsium Client includes browser extensions for Internet Explorer, Chrome, and Firefox.

    • Browsium Client installs a new Browsium Service (BrowsiumService.exe) to handle client operations that require administrative privileges at runtime.

    • Browsium Controller (BrowsiumController.exe) and Browsium Monitor (BrowsiumMonitor.exe) replace Browsium Proton Controller (BrowsiumProtonController.exe) and Browsium Proton Monitor (BrowsiumProtonMonitor.exe) from prior versions. These new processes provide functionality for Ion, Catalyst, and Proton if configured, reducing the overall memory footprint and number of processes required to run the Browsium suite.

  • Privacy Mode anonymizes user names and IP addresses to comply with international privacy regulations.

  • Enhances ActiveX detection and reporting provides deeper insights on legacy, insecure ActiveX controls that may be causing an unnecessary attack surface and attack vectors for hackers.

  • Improves report export behavior, increasing speed, providing a full report export option (not just the visible rows), and simplifying the report export experience.

  • Improves integration with Browsium Ion and Browsium Catalyst, with clearer identification of Ion profiles and more granular client inventory details to show the status of Ion and Catalyst configurations.

Client inventory details will only show Ion and Catalyst in the “Browsium” section of the report when Ion and Catalyst have a configuration deployed on the client system.

[What’s new in Proton 1.2.1]{.underline} This section details changes to Proton since the prior version, Proton 1.2.

  • Enhanced ActiveX detection runs faster, is more secure, and finds ActiveX controls by MIME type and within embed tags.

  • Cleaner uninstall and upgrade behaviors.

  • Client stability improvements, including a fix for a mismatched lookup table.

[What’s new in Proton 1.2]{.underline} This section details changes to Proton since the prior version, Proton 1.1.

  • Adds data collection and reporting of Document Mode values (in Internet Explorer only) to help identify which pages are rendered in legacy modes and insights into how that mode was selected.

  • Reports now include information on ActiveX Control security values, specifically safe for scripting and safe for initialization, helping organizations identify and resolve insecure settings needed for line of business applications.

  • Report columns can now be sorted in ascending or descending order to aid in content analysis.

  • Now includes Data View exports, enabling easier sharing and integration of Proton report data into other media and analytics tools.

  • New Diagnostics page in Proton Manager provides additional insights on system health and operations.

  • Enables bulk upload of Ignore Rules to ease the creation of large sets of rules.

  • New Power User account type in Proton Manager enables greater access without opening all settings.

  • Performance enhancements in the Report & Filtering processes enable quicker response and ability to handle significantly larger data sets.

  • Backend database performance optimizations enable larger client deployments and faster integration of data.

  • Filters now support views by AD Site and IP range values.

  • New Data Retention Policy helps compliance with corporate data requirements and manage database growth.

  • Addresses a bug where rule mapping may not complete when too many records are active.

  • Fixes bug where blocked ActiveX controls may be unreported in Proton inventory.

  • Fixes bug where Proton client is not available for download in self-hosted Proton Manager.

  • Fixes issue with F5 (refresh) not updating screen report views.

[What’s new in Proton 1.1]{.underline}

Proton 1.1 was the first commercial release of Proton, so every is new. All future releases will contain a change log detailing the new features and bug fixes in each release.