Turn Enforcement Into Evidence
SafeSquid blocks and allows traffic in real time. That decision only survives an audit or an incident review once it is logged and retained long enough to matter. It must also be reachable through the right report. A control you cannot evidence is a control nobody will credit. Plan retention before deployment and prove the audit trail works once SafeSquid is live. Then find the right report or log for a specific question.Quickstart path
- Log-Retention Planning - set the retention target and size the log volume before installation. Retention is a sizing input, not an afterthought.
- Logging and Reporting - confirm access logs are written, retained, and forwarded before calling the deployment audit-ready.
- Tools and Reports - locate Reports and Support utilities in the Web UI once the proxy is live.
- Logging and troubleshooting - pick the right log family for a specific symptom, instead of searching blind.
Next steps
- Deployment - size and sequence the rest of the deployment around this evidence path.
- Audit & Forensics - go deeper on forensic workflows and security-log analysis.
- Troubleshooting - diagnose a specific symptom instead of planning or validating reporting.