CSPRules
Reference

CSP tools compared

Tools that touch a Content Security Policy fall into three groups: services that collect reports and generate policies, platforms that monitor scripts on payment pages, and tools that write the header. This page records what each states on its own public pages, as checked on 17 November 2026. It is not a hands-on test. Features change; confirm with the vendor before buying.

Capabilities

CapabilityReport URICentralCSPcsideCloudflareWordPress pluginsCSP Ledger
Collects violation reportsSTATEDSTATEDSTATEDNOT FOUNDSTATEDPLANNED
Generates a policy from observed trafficSTATEDSTATEDSTATEDNOT FOUNDNOT FOUNDNOT PLANNED
Script inventory or script change alertsSTATEDSTATEDSTATEDSTATEDNOT FOUNDNOT PLANNED
Records every policy versionSTATEDNOT FOUNDSTATEDNOT FOUNDNOT FOUNDPLANNED
Justification recorded per entryNOT FOUNDSTATEDNOT FOUNDNOT FOUNDNOT FOUNDPLANNED
Named owner per entryNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDPLANNED
Review or expiry date per entryNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDPLANNED
Approval before a change reaches the headerNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDNOT FOUNDPLANNED

"Stated" means the vendor's own page describes the feature. "Not found" means it was not described on the pages checked; the product may still offer it. CSP Ledger is in development, so its column shows plans, not shipped features. It is meant to take reports and script data from tools like these rather than duplicate them.

Reporting and policy management

Report URI

  • Covers the policy lifecycle from creation to enforcement. The CSP Wizard builds a policy from report-only violation reports; the Builder edits it.
  • Watches for new violations and unauthorised changes. Policy Watch records every version of the policy delivered to browsers, on the Business plan or higher.
  • Script Watch alerts on changes to JavaScript dependencies.

Not found on its pages Per-entry owner, justification, review date or approval step.

Source: 1,2,3

CentralCSP

  • Managed reporting endpoint and a builder that generates policies from real reports.
  • On the Scale plan (listed at €349.99 per month): a payment-page script inventory with a justification and an authorisation status recorded per script, new scripts marked pending review, and a dated history of script changes.

Not found on its pages Named owner, review or expiry date, or approval of policy changes before deployment. The justification fields cover scripts, not CSP sources.

Source: 4,5

cside

  • Free CSP management and violation reporting, with policy generation from observed scripts.
  • Lets users approve new domains and shows policy versions. A separate paid product covers PCI DSS 6.4.3 and 11.6.1.

Not found on its pages Owner, justification or review date per domain, or an approver role.

Source: 6,7

Csper

  • Report endpoint that groups similar reports and generates policies from them, with a policy evaluator.

Not found on its pages Governance fields of any kind.

Source: 8

CSP Radar

  • Groups violation logs, sends alerts, and builds rules from live traffic. Listed on Product Hunt in 2026.

Source: 9

Client-side security platforms

Cloudflare Client-Side Security

  • Formerly Page Shield. Script and connection monitoring on pages served through Cloudflare, an inventory for PCI DSS 6.4.3, and rules that block unauthorised scripts.

Not found on its pages Per-entry owner, justification or review date.

Source: 10

Akamai, Imperva, HUMAN, Feroot, Jscrambler

  • Enterprise products aimed at PCI DSS 6.4.3 and 11.6.1: inventories of scripts on payment pages, authorisation, and tamper detection. Scope is the payment page rather than the site-wide policy.

Source: 11,12,13,14,15

Header configuration

WordPress plugins

  • Content Security Policy Manager sets separate policies for wp-admin, logged-in users and visitors. WordPress.org notes it has not been tested with the last three major WordPress releases.
  • Security Headers Audit adds a builder and violation monitoring for CSP and other headers.

Not found on its pages Any record of why a source is allowed or who allowed it.

Source: 16,17

Google CSP Evaluator

  • Free, one-off analysis of a policy for known bypasses.

Source: 18

Where CSP Ledger fits

The tools above answer what a policy contains, what browsers report, and which scripts changed. Few record why each source is allowed, who owns that decision, and when it should be reviewed. The closest is CentralCSP's per-script justification, which covers payment-page scripts on its top plan. PCI DSS 6.4.3 asks for exactly that record on payment pages.19

CSP Ledger is built around that record for every source, across every page and environment, with approval before a change reaches the header. It is planned to work alongside a reporting service rather than replace one: reports supply the evidence of use, and the Ledger supplies the decision.

References

  1. [1]
  2. [2]
    CSP Wizard. Report URI documentation.
  3. [3]
    Policy Watch. Report URI.
  4. [4]
  5. [5]
    CSP Builder. CentralCSP.
  6. [6]
  7. [7]
  8. [8]
    Csper. Csper / Product Hunt listing.
  9. [9]
    CSP Radar. Product Hunt listing.
  10. [10]
    Client-side security. Cloudflare Docs. Formerly Page Shield.
  11. [11]
  12. [12]
  13. [13]
  14. [14]
    Feroot. Feroot Security.
  15. [15]
    Jscrambler. Jscrambler.
  16. [16]
    Content Security Policy Manager. WordPress.org plugin directory.
  17. [17]
    Security Headers Audit. WordPress.org plugin directory.
  18. [18]
    CSP Evaluator. Google.
  19. [19]
    PCI DSS v4.0.1, Requirements 6.4.3 and 11.6.1. PCI Security Standards Council. Payment-page script inventory, authorization and tamper detection. Mandatory from 31 March 2025.