Guidance for Content Security Policies (CSPs)
We recommend setting a strict Content Security Policy (CSP) as a part of a defense-in-depth strategy to mitigate XSS (Cross-Site Scripting), clickjacking, and cross-site leak vulnerabilities. CSPs help secure your site by informing your browser of resources that should be allowed to load for each page.
Content Security Policies impact your site’s functionality, so changes to your CSP should be made with care. Changes to your site may also require updates to your CSP.
Some important directives
script-srcas locked down as possible. If you are using NextJS, use their guide to set up script nonces.
noneunless you expect your website to be embedded.
connect-srcas locked down as possible. This will prevent bad actors from injecting scripts and sending compromised data to third parties.
CSP directives for @privy-io/react-auth
As part of enforcing a CSP, you will need to allow certain trusted resources that your site needs to load as part of normal operation, such as the Privy iframe, Privy dependencies, and any other resources you intentionally consume. Below is a list of resources you must allow for Privy to operate as expected:
- https://auth.privy.io (Privy API)
- wss://relay.walletconnect.com (WalletConnect API)
- wss://relay.walletconnect.org (WalletConnect fallback API)
- wss://www.walletlink.org (Coinbase Wallet API)
- https://*.infura.io (Privy RPC provider)
- https://*.blastapi.io (Privy RPC provider for Base)
- https://challenges.cloudflare.com (Cloudflare Turnstile CAPTCHA scripts)
Testing and deploying your CSP
We highly recommend testing your CSP thoroughly before deploying and enforcing in production.
Test your CSP in a staging environment
Run through your standard user flows in a staging environment with CSP enforcement. This may mean connecting to browser extension wallets / mobile app wallets, transacting, logging out, etc.
It is possible that directives need to be updated after Privy SDK upgrades. Whenever upgrading the Privy SDK, always test your CSP again before deploying the update to production.
Other software you use, such as MetaMask, may document their own guidance on CSP usage.
Using Report-Only mode
Most browsers support a
Content-Security-Policy-Report-Only header, which sends violation reports without actually enforcing policies. This allows the developer to judge whether a modification to their CSP will impact their site’s expected functionality.
If your policy is strict, you will see many reported violations due to extensions trying to inject scripts into the browser. This is completely normal. It's best to filter these out to avoid the noise.
We recommend that you first deploy your CSP in
report-only mode with the header
Content-Security-Policy-Report-Only. Once it has been validated in production, you can migrate to
Content-Security-Policy, which will enforce directive violations.
Going forward, you can deploy with both
Content-Security-Policy headers set simultaneously. This will allow you to test on the report only header and A/B test against your existing policy.
We recommend that you configure the
report-uri to see violation/enforcement reports and set up a monitoring dashboard so you can review reports.