> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safesquid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Cases

> Find the SafeSquid control that closes a specific attack surface, compliance gap, or operational risk.

# Find the Control for Your Risk

A proxy that only forwards traffic is not a security control. Each use case below closes one
specific gap — encrypted-traffic blindness, credential misuse, DNS-layer evasion, sensitive-data
exfiltration — with a policy you configure and can prove is enforced. Start from the risk you
need to close, not from a feature list.

## Foundation

Controls most deployments configure first, because later use cases depend on them.

* **[SSL Inspection](https://docs.safesquid.com/use_cases/ssl_inspection/ssl_inspection.md)** - decrypt and inspect HTTPS traffic; without it, every other control is blind to most of today's web.
* **[Authentication](https://docs.safesquid.com/use_cases/authentication/authentication.md)** - attribute every request to a user or group so policy and logs mean something.
* **[Profiling Engine](https://docs.safesquid.com/use_cases/profiling_engine/profiling_engine.md)** - classify requests and responses so downstream controls act on the right traffic.

## Threat prevention

* **[DNS Security](https://docs.safesquid.com/use_cases/dns_security/dns_security.md)** - block malicious and tunnelling domains before a connection is ever made.
* **[Malware Scanning](https://docs.safesquid.com/use_cases/malware_scanning/malware_scanners.md)** - inspect downloads and payloads in the request path, not after the fact.

## Access control

* **[Access Restriction](https://docs.safesquid.com/use_cases/access_restriction/access_restriction.md)** - allow or block sites, apps, and categories by user, group, or time window.
* **[Content Modifier](https://docs.safesquid.com/use_cases/content_modifier/content_modifier.md)** - rewrite pages in flight to remove risky elements without blocking the whole site.
* **[Cookie Inspection](https://docs.safesquid.com/use_cases/cookie_inspection/cookie_inspection.md)** - strip or filter cookies that leak session or tracking data.
* **[Header Rewrite](https://docs.safesquid.com/use_cases/header_rewrite/header_obfuscation.md)** - rewrite request and response headers to enforce corporate-account-only access to consumer services.
* **[URL Redirection](https://docs.safesquid.com/use_cases/url_redirection/url_redirection.md)** - send a matched request to a different destination instead of blocking it outright.

## Data protection

* **[Data Leakage Prevention](https://docs.safesquid.com/use_cases/data_leakage_prevention/data_leakage_prevention.md)** - stop sensitive content leaving over the web egress path, not just email.

## Visibility

* **[Audit & Forensics](https://docs.safesquid.com/use_cases/audit_and_forensics/audit_forensics.md)** - preserve evidence an auditor or incident responder can actually use.

## Integrations

* **[Integrations](https://docs.safesquid.com/use_cases/integrations/integrations.md)** - connect SafeSquid to ICAP scanners, SIEM, and VPN so existing tooling sees proxy-layer evidence.

## Operations and lifecycle

Day-2 operations for a control already in production — scaling, tuning, customisation, and
upgrades.

* **[Scaling & High Availability](https://docs.safesquid.com/use_cases/scaling_and_high_availability/proxy_clustering.md)** - add clustering and failover once a single node is proven.
* **[Performance Acceleration](https://docs.safesquid.com/use_cases/performance_acceleration/performance_accelerators.md)** - cache and tune so inspection doesn't cost you latency.
* **[Customisation](https://docs.safesquid.com/use_cases/customisation/customisation.md)** - adapt templates, startup parameters, and configuration sync to your environment.
* **[Upgrade](https://docs.safesquid.com/use_cases/upgrade/version_upgrade.md)** - plan version and OS upgrades without an enforcement gap.

## Next steps

* [SSL Inspection](https://docs.safesquid.com/use_cases/ssl_inspection/ssl_inspection.md) - close the encrypted-traffic blind spot first.
* [Authentication](https://docs.safesquid.com/use_cases/authentication/authentication.md) - attribute traffic before you write policy against it.
* [Deployment](https://docs.safesquid.com/deployment/main) - plan sizing, installation, and rollout before configuring use cases.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.