All spotlights

Product spotlight · January 2026

Build, test and monitor a Content Security Policy for your site

ScriptAttest is a new hosted service that builds, tests and monitors a Content Security Policy for your site, and reports scripts added, changed or removed since a trusted baseline.

New product ScriptAttest For site owners and security teams

What it includes

The January 2026 changelog has the full details.

  • Discovery and policy generation

    Discovery scans load the pages you add in a real browser and list the scripts, stylesheets, fonts, images and connections they use. You approve each source by domain, or approve inline scripts and styles by hash. ScriptAttest then generates a strict policy from your approvals. The source list flags public package CDNs as a supply-chain risk.

  • Validation and violation reports

    A validation scan tests the policy against your live pages before you deploy it. Each generated policy includes a reporting endpoint for your site, so browsers send violation reports to ScriptAttest. Email alerts tell you about new violations. On the Violations tab, you approve a reported resource, which adds it to a new policy version, or dismiss the report.

  • Script attestation and drift detection

    Attestation scans record each script on a page with its source, its content hash and the domains it sends requests to. The first scan becomes your trusted baseline. Later scans report scripts added, changed or removed since the baseline, rated by severity. When a change is expected, such as a vendor update, you accept that scan as the new baseline.

  • Deployment to Quant projects

    You link a ScriptAttest site to a QuantCDN or QuantGov project from the CSP Management tab, and deploy the policy to its custom headers. When approving a violation publishes a new policy version, ScriptAttest deploys that version to the linked project automatically.

  • Schedules and SRI values

    On the Schedules tab, you run attestation and policy validation scans daily, weekly, monthly or on a custom cron expression. The ScriptAttest tab lists Subresource Integrity (SRI) values for external scripts that do not change, ready to copy into integrity attributes.

  • Security headers and teams

    The Security Headers tab grades headers such as HSTS, X-Frame-Options and Referrer-Policy. In Settings, you invite team members as admins or members, and you switch between the organisations you belong to.

Who it is for

  • Security teams

    Get a strict Content Security Policy built from the sources you approve and tested against your live pages first.

  • Sites with vendor scripts

    Attestation scans record each script's content hash and report scripts that change, such as after a vendor update.

  • Quant project owners

    Link a QuantCDN or QuantGov project, and ScriptAttest deploys each policy version that an approval publishes.

What it is

ScriptAttest (scriptattest.com) is a new hosted service that builds, tests and monitors a Content Security Policy (CSP) for your site. A policy that allows a domain does not show when a script from that domain changes. ScriptAttest also runs attestation scans, which record the content hash of each script and report changes.

ScriptAttest has its own sign-up and accounts, separate from the Quant dashboard. To deploy a policy to Quant, you link a ScriptAttest site to a QuantCDN or QuantGov project and sign in with your Quant account.

How it works

A policy update for a site linked to a Quant project has these steps:

  1. Deploy to QuantCDN adds the policy and its Reporting-Endpoints header to the project’s Custom headers page. Your other custom headers stay as they are.
  2. A browser sends a violation report to ScriptAttest for a resource that the policy does not allow.
  3. An email alert tells you about the new violation. You approve the resource on the Violations tab.
  4. ScriptAttest publishes a new policy version and deploys it to the linked project.
  5. Organisation owners and admins get an email about the new version, and another email if the deployment fails.

The CSP Management tab shows the policy version and the time of the last deployment.

From an attestation report, you can mark domains whose scripts change by design, such as an internal CDN or an A/B testing service. Their script changes then show as expected.

Get started

  1. Create an account

    Sign up at scriptattest.com, separate from the Quant dashboard.

  2. Run a discovery scan

    Add your pages, then approve each source by domain or inline code by hash.

  3. Validate the policy

    Run a validation scan to test the policy against your live pages.

  4. Deploy to your project

    Link a QuantCDN or QuantGov project on the CSP Management tab, then deploy.

  5. Set a baseline

    Run an attestation scan, then schedule scans on the Schedules tab.

Related: Explore ScriptAttest · Documentation · January 2026 changelog

Ready to try it on Quant?

Use ScriptAttest on your own project, or talk to our team first.