* Fix for memory leaks in trusted ca load functionality.
* Integrated latest webfiltering engine.
"Appropriateness is a relatively subjective term and its definition entirely depends on its relevance."
A variety of content is served by various Internet web-sites. Similarly, a variety of users have to access it. For each user, therefore the definition of the term - "appropriate", is so unique.
Consider this hypothetical scenario -
Sheila is the sales manager of a company. The company would prefer her and other managers to access content from a larger number of web-sites. Now, Sheila and three of her colleagues from the sales department, also have to visit the supply-chain-management applications, hosted on quite a few of their customers' web-sites. Two of her colleagues have been specifically assigned the task of accessing some auction web-sites as the company sells some of their products through these web-sites. Sheila leads a sizable direct sales-force, most of these personnel randomly visit the company office but only for a few hours. These personnel do not have a specific computer allotted to each of them, but have been given a common use of about ten computers. The company is in the business of coffee-makers, and the sales-personnel would like to use the Internet to know more about the customers, they intend to meet.
In this scenario, without any Internet access, Sheila's team would hardly be able to function. Yet Sheila is quite justifiably concerned that if her colleagues were given unrestricted use of Internet, she would never get anything done in time!
Ensuring appropriate access and delivering appropriate content is mostly frustrated in defining. SafeSquid uses the concept of Profiles to overcome this problem. Every rule that you frame to set the action of any feature, can be specified for specific profiles or globally. Profiles, thus allow you to achieve granularity, of any desired level, as you frame rules to set the appropriateness of access and content.
SafeSquid allows you to give every individual user an Access Profile. Common Profiles can be created for users based on their functions, hierarchy or business units. Profiles could be logically named as per the enterprise perceptions. Each of such Access Profiles could be unique depending upon the combination of username & network address. You can may have Profiles like Accounts, Sales, Managers, Secretaries, Visitors, etc. A user may be included in more than one Profile.
Application Profiles can be created for content that would be fetched from the web-sites. Profiles can be logically named as per the utility of the content as perceived by the enterprise. Each of such Application Profiles could be a unique combination of the - name of the web-site serving the content, URL of the content, file name, time of access, nature of the content like image or music or text, etc. Even the variety of client used like Internet Explorer or FireFox can be used to distinguish an Application Profile. You may have Profiles like Pictures, Music, Research, Vendor Web-Sites, Security Patches, Business Applications, job search, etc.
If you have a multi-location environment, that is served by various slave-installations of SafeSquid, you can even bind a Profile to one or more specific instance of SafeSquid. The apparent complexities in the earlier described hypothetical scenario can be quite simplified, by using the Profiles.
SafeSquid allows you to create granular policies that can take care of intricate demands like these -