Cookie Filtering

​

Problem

Websites set cookies for sessions, tracking, and advertising. Unrestricted cookies enable silent logins to personal mail and shopping sites, expand tracking surface, and complicate compliance. Administrators need host-scoped allow and deny rules aligned with acceptable-use policy.

​

Benefits

The Cookie Filter lets administrators choose which hosts (websites) may send and receive cookies. Administrators control cookie exchange between remote websites and browsers, support privacy goals, and block login flows to selected destinations while keeping search or read-only access where configured.

​

Advantages

Confirmed: Cookie filter integrates with SafeSquid profiles and the same Real-time content security workflow as Header Re-Write and Access Restriction. Missing: Third-party browser privacy benchmarks versus SafeSquid cookie policy are not cataloged—do not cite without a source register entry.

​

Call to action

Open the Configuration Portal path documented in Cookie Filter Configuration and Reference. Define Global policy and Allow/Deny rules (profiles, domain, path, direction, time). Test with a controlled client and verify expected login block or allow behavior.

​

Verification and validation

After configuring cookie inspection, test both:

• a destination that should still receive or send cookies
• a destination that should fail or lose login persistence because cookie transfer is blocked

Use a controlled client and compare browser behavior before and after the rule change.

​

Troubleshooting

Symptom: Users can still log in to a site that should be cookie-restricted.
Likely cause: The domain, path, direction, or profile match is too broad or wrong.
Isolation: Compare the request against the configured cookie rule scope.
Remediation: Narrow or correct the rule.
Retest: Repeat the same login flow and confirm cookie-dependent behavior changes. Symptom: A business-critical site unexpectedly breaks.
Likely cause: Cookie filtering is denying a required session cookie.
Isolation: Test the site against the allow and deny policy with developer tools or controlled browser behavior.
Remediation: Add a narrowly scoped allow entry for the required host or path.
Retest: Confirm the site works without weakening unrelated cookie restrictions.

​

Cookie filter controls which hosts can send and receive cookies

An HTTP cookie is a small piece of data sent from a website and stored in the browser while the user browses. Example: Block cookies from advertising sites such as tribalfusion.com and doubleclick.net to prevent private information from being transferred. Users can query search engines (Google, Yahoo) but cannot log into personal accounts (Gmail, shopping, trading sites).

​

Cookie filter configuration guides

​

Cookie Filter Configuration and Reference

Cookie allow/deny behavior requires correct Global policy and Allow/Deny rules. The document covers the Configuration Portal path, Global and Policy options, and Allow/Deny rule parameters (profiles, expiry, domain, path, direction, time match). Example rules and solution verification support validation. Use the document to configure and validate cookie filtering.

​

Next steps

Combine with Header Obfuscation and Access Restriction for full request/response and privacy control.