Skip to content

Resources

Practical guides for compliance drift monitoring

Learn what to monitor, why drift happens, and how to keep an evidence trail your team can review and share.

Cookie change monitoring

Cookies change when vendors, tag managers, and site updates change. WebAssure detects newly appearing cookie names and captures cookie details per scan so you can review drift quickly.

High risk signalCompliance / RiskContinuous monitoring
Why cookie drift matters
New cookies often indicate new tracking behavior, a new vendor, or a configuration change. If it’s not reviewed, risk accumulates quietly.
What to monitor
The most actionable baseline is “new cookie names since last scan”, supported by per-cookie details for investigation.

WebAssure highlights changes and risk signals. It does not provide legal advice or certify compliance.

What WebAssure captures per scan

WebAssure records cookie information observed during scans so you have context when something changes.

New cookie names
WebAssure flags newly observed cookie names compared to the previous scan.
Cookie details (for investigation)
Each scan captures cookie attributes like domain, path, secure/HTTP-only, sameSite, and expiration fields to support internal review.
Correlated signals
New cookies often appear alongside new third-party domains or new external scripts — giving you a faster path to root cause.
Page change review
If page structure changes without obvious new cookies/domains/scripts, you still get a review signal.

Shareable exports

Generate audit-ready exports you can download and share. Export access is bounded by your plan’s retention window.

Related resources

    Cookies & privacy

    We use essential cookies to run the app. With your permission, we also use analytics to improve WebAssure. You can change your choice anytime.