Overview
SiteWall client-side security overview
Learn how SiteWall discovers browser resources, supports third-party script governance, applies reviewed controls, and preserves scoped evidence.
Last reviewed September 12, 2026
SiteWall by CellWall is a client-side security and third-party script governance platform for monitoring and controlling code that executes in website visitors’ browsers. It connects observed providers, resources, behavior, data flows, findings, and policies so teams can discover what runs, apply reviewed controls, and preserve evidence without treating browser telemetry as a complete security or compliance conclusion.
When someone opens your website, their browser may load code from analytics tools, payment services, chat widgets, consent platforms, advertising systems, and other third parties. That code can change over time, contact external destinations, use browser APIs, and affect performance or functionality. SiteWall gives your teams a shared view of that activity.
Questions SiteWall helps answer
Use the following table to understand how each area supports the task.
| Question | Where to look |
|---|---|
| Which third-party services are present? | Providers |
| Which individual scripts or assets ran? | Inventory |
| What introduced a resource and where did it connect? | Exposure Map and provider Load Flow |
| What happened during one browser journey? | Sessions |
| What changed or requires review? | Issues and Anomalies |
| What behavior should be allowed or restricted? | Policies |
| What technical records support a compliance review? | Legal & Compliance and Audits |
How SiteWall works
- 1.
Install SiteWall for a project
Each project represents a monitored website boundary. Its initialization code connects captured browser activity to the correct project.
- 2.
Generate representative traffic
Your team visits important pages and exercises real journeys such as login, checkout, consent choices, forms, chat, or media. SiteWall can only describe behavior present in the traffic it receives.
- 3.
Review the connected record
SiteWall groups observations into provider profiles, resource inventory, sessions, metrics, relationships, issues, and anomalies so teams can investigate them in context.
- 4.
Make reviewed control decisions
After purpose, ownership, dependencies, and observed use are understood, policies can be applied globally or more narrowly to a provider or resource.
- 5.
Prepare scoped evidence
Compliance workflows organize relevant technical records by framework and requirement while preserving the project, entity, and time context needed for review.
Five terms to know first
Use the following table to understand how each area supports the task.
| Term | Plain-language meaning |
|---|---|
| Project | The SiteWall workspace and data boundary for a monitored website. |
| Provider | A service or organization associated with one or more observed resources. |
| Resource | An individual client-side file or asset observed in a monitored browser journey. |
| Session | A browser visit or journey that groups related runtime activity. |
| Policy | A reviewed decision that allows, restricts, inherits, or blocks supported behavior. |