SafeSquid SWG Architecture and Components
SafeSquid Secure Web Gateway (SWG) is a purpose-built HTTP proxy for application-layer security. It intercepts HTTP/HTTPS traffic, inspects Layer 7 content, and enforces access control, URL filtering, SSL inspection, and data leakage prevention.
This section covers the SWG architecture, components, and supporting services.
Core Components
Configuration Portal
The web-based administrative interface for defining and managing proxy policies. Configure access restriction, SSL inspection, authentication, DLP, and operational settings through a centralized console.
Access: http://safesquid.cfg/ (embedded Rest UI interface built into SafeSquid; accessible only when your client uses the proxy, but NOT resolved by SafeSquid's DNS resolver) or https://SERVER-IP:8443/ (direct access)
Application Ecosystem
Overview of how SafeSquid components work together: proxy cluster, policy console, self-service portal, reporting, DNS security, and supporting services. Understanding the ecosystem helps with deployment planning and integration.
Use for: Architecture planning, understanding component relationships
SafeSquid Proxy Cluster
The central enforcement layer for HTTP/HTTPS traffic. Multiple proxy nodes can be deployed for high availability and load balancing with centralized policy management.
Details: Proxy Clustering
Self-Service Portal
Cloud-based portal for activation keys, license management, and SSL certificate generation. Reduces dependency on support for routine licensing and certificate tasks.
Access: https://key.safesquid.com
Reporting Service
Centralized log aggregation, dashboards, and forensic logging. Provides visibility into traffic patterns, policy enforcement, and compliance evidence.
Use for: Audit trails, usage analytics, incident investigation
Integrated DNS Security
Policy-aware DNS resolution with DNSBL integration. Blocks malicious domains and mitigates DNS tunneling attacks.
Details: DNS Security
Supporting Services
Operational services that ensure reliability and performance:
- Monit — Process monitoring and auto-restart
- BIND — Local DNS resolver for performance
- NTP — Time synchronization for SSO and TLS
Critical for production: Monit prevents service downtime; BIND improves DNS performance; NTP ensures authentication works correctly.
Next Steps
- Getting Started — Install and activate SafeSquid if you haven't already
- SSL Inspection — Enable HTTPS decryption for policy enforcement
- Authentication — Integrate with Active Directory or LDAP
- Access Restriction — Configure URL filtering and content policies