Locate SafeSquid Files and Folders
SafeSquid server paths are part of the enforcement boundary. They hold service control scripts, module binaries, policy XML, and activation material. They also hold SSL data, reporting databases, signature stores, runtime files, and logs. Uncontrolled edits can break proxy availability, weaken inspection, erase rollback evidence, or create audit gaps. Use this section to prove what changed, locate operational evidence, and decide which files need change control. Do this before an upgrade or incident response.Control the file surface
Treat these paths as production controls, not ordinary local files:Protect sensitive evidence
Activation files, SSL folders, policy XML, reporting databases, and SafeSquid logs contain security-sensitive data. Logs can include user identifiers, source IP addresses, destinations, policy outcomes, browser metadata, and investigation context. Before exporting or sharing evidence, redact personal data unless an approved audit or incident investigation requires it. Retain copied files according to your organization’s evidence-handling policy.Use change control
Do not edit SafeSquid-controlled files directly unless a documented procedure requires it. Record the path, owner, reason, backup location, reviewer, and rollback step. Do this before changing service scripts, startup parameters, policy XML, SSL material, modules, templates, or log settings. For policy work, prefer the SafeSquid interface. File-level edits should be reserved for recovery, support-directed remediation, or documented administrative tasks.Locate the right path
Minimum incident set
For an operational incident, preserve:- affected user, source IP, destination, and timestamp
- matching report entry or SIEM event
- relevant
extended.log,native.log,performance.log, orconfig.loglines - recent configuration backup files
- service state and startup parameters
- Monit, BIND, and NTP health status
- SafeSquid process ID from
/var/run/safesquid
Next steps
- Use Logs and Audit Evidence to collect proof for investigation and audit.
- Use Support to prepare escalation evidence.
- Use Policy, Security, and UI Files to locate policy, security, and UI files.