The Chrome Plugin to be developed needs to change the default proxy settings ([url removed, login to view]) and thus the internet connections of the browser. The headers of http and https traffic are added an authentication string and redirected to the a Webfilter by using the routing information stored in the proxy.pac. The authentication string consists of the userID, which is provided from us via an API call during Plugin installation and the currently used surf mode and thus policy in an obfuscated fashion.
With these piggy-backed packets, our webfilter cloud is able to authenticate the user and enable him to surf securely based on the predefined policies. Three types of policies are possible: surfSafe, childProtection and anonymous. For all policy types, lists of allowed and forbidden categories are stored in the cloud and autonomously retrieved back into the browser traffic. The Chrome Plugin shall work with all Windows and MAC versions supported by the Chrome Browser.
A detailed Requirement Specification can be provided from us.