Granular web access control for policy and compliance

Uncontrolled web access increases malware, data loss, and compliance gaps (e.g. unacceptable use, access to restricted categories). SafeSquid access restriction enforces allow/deny/redirect by user, group, time, URL, category, and application with profiles for SSL inspection, headers, and DLP. Access and security logs record policy hits; the Reporting Module and Security Logs provide reports and exports for SOC 2, acceptable-use, and audit.

Granular web access control enforces policy and compliance

Enterprises need to allow or block web access by user, group, time, destination, and content type. Broad allow/deny rules create gaps; overly strict rules block legitimate use. SafeSquid access restriction combines identity, time profiles, URL and category matching, and request/response profiles so administrators enforce least-privilege access and meet compliance requirements.

Access policies and profiles define what is allowed

Access restriction in SafeSquid uses policies and profiles. Policies define conditions (user, group, time, URL, category, application). Profiles attach to policies and carry actions (allow, deny, redirect, or apply SSL inspection, header filter, cookie filter, and similar controls). The Configuration Portal — web interface for policy and system settings — provides the interface to create and order these policies. Identity comes from Authentication (user and group identity sources); HTTPS visibility comes from SSL Inspection (decrypt and inspect HTTPS traffic). Configure access restriction in the Configuration Portal under the relevant restriction and real-time content security sections.

Next steps

Enable SSL Inspection and Authentication so policies can apply to HTTPS traffic and by user; then configure Profiling Engine and Malware Scanners for content and threat control.