Configuration Page

The Configuration page allows Proton administrators and power users (but not standard users) to control client configuration settings (for heartbeat, data push, and inventory), data retention settings, cloud service definition settings, data collection options, and cloud file data collection (uploads and synced files).

Client Configuration

For the Client Configuration options, administrators can specify the frequency in which Proton clients will interact with the Proton server. Standard Proton user accounts will not be able to view or modify the settings on this page.

The available settings for Client Configuration are as follows. BCMS is designed to scale to a large number of client systems, with higher Client Configuration values adding to the server’s scalability.

---

Value Description Proton Server Default

---

Heartbeat interval The interval at which clients poll the server (for new settings, rules, etc.) 15 minutes

Data push interval The interval at which clients push data to the server. 60 minutes

Inventory interval The interval at which clients perform an inventory of installed ActiveX controls, Java versions, etc. 1440 minutes

Extension Analyzer Configuration

Proton provides the ability to adjust browser extension risk scoring according to parameters specific and important to your organization. The default values for each category are listed next to each section, and can easily be adjusted at the granular permissions level. In addition, an entire category of permissions risk scoring can be disabled by using the toggle switch next to the section header label.

The ‘Permissions Breakdown’ configuration section is extensive and long, so users must click the ‘Show More’ button to fully expand it for review and adjustment.

Data Retention

BCMS and Proton offer the ability to define data retention policies to support organizational or regulatory compliance requirements, as well as serve to ensure organizations have the ability to limit unbounded growth of the Browsium Proton dataset. The default settings for BCMS are to automatically delete data on a rolling 90-day window, each night at midnight. The values can be adjusted by using the drop-down menu. Alternatively, data retention policies can be entirely disabled by switching the button to the left (off) position.

If no data retention policy is defined, the data set will continue to grow, eventually resulting in certain Proton reports taking an extended time to display.

Data Collection Options

Data Collection Options provide the ability to control what data is collected from client systems. This provides the ability to turn on or off the collection of Java inventory (versions installed), Java usage details, ActiveX inventory (controls and versions installed), ActiveX usage details, Browser extension inventory, page load performance metrics, server IP addresses, and script errors. All options are enabled by default.

The first five, Java inventory, Java usage, ActiveX inventory, ActiveX usage, and Browser extension inventory, are globally controlled, either on or off for all clients and web applications. The last four, performance analytics, server IP addresses, script errors and Query strings, have a global control with more granular control per web application. When enabled on the Configuration page, performance analytics and server IP address data collection defaults to enabled for each new web application. However, script errors and user accounts work differently.

Query strings are always off by default. This is done in part to conserve space, as query strings can be large as well as often provide little specific value in dataset aggregates. In addition, the default settings help ensure no inadvertent privacy leakage should a poorly designed web application contain PII in the query string.

When enabled on the Configuration Page, the per-web-application script errors setting will default to disabled and must be manually enabled for each web application. This is done to minimize extraneous and potentially private user data. In the case of script errors, many web applications generate harmless script errors in various browsers, so this feature should be turned on only for web applications where you’re investigating specific error conditions reported by users or testers.

[]{#_Users_Page .anchor}