Proton Deployment in the Enterprise
Like any enterprise software deployment, Proton deployment in the enterprise requires careful planning. This begins with the Browsium Client, which is designed to be centrally deployed and managed by IT and be completely invisible to end users.
Proton configuration information required by the Browsium Client, such as how often to send inventory and browsing activity data to the Proton server and which sites to ignore (not send to the server), is centrally managed on the Browsium Client Management Server (BCMS). So once the Browsium Client is installed on all PCs in the enterprise, and configured with the URL of the organization’s BCMS, no additional direct management is necessary.
However, readying client systems for central management requires a bit of planning. To communicate with your organization’s Browsium Client Server, the Browsium Client must be deployed to end user PCs with the BCMS URL. This can be set during installation or via a post-installation registry edit using desktop management tools or Group Policy. In addition, the Browsium Client extensions for Microsoft Internet Explorer, Microsoft Edge, Google Chrome, and Mozilla Firefox must be enabled and (optionally) locked down so end users don’t disable or remove them.
In this section, we’ll examine the best practices for enterprise deployment of the Browsium Client and provide guidance for enabling and locking down browser extensions.