Content Security Policy
Restricts the browser resources and execution paths that a document may use.
Support in current browsers
Checked against the current browser versions recorded in MDN browser data 8.0.7.
| Browser | Minimum | Outcome | Reason |
|---|---|---|---|
| Chrome | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Edge | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Chrome for Android | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox for Android | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari on iOS | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Android WebView | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Samsung Internet | 29.0 | Works | Every required mapped BCD feature is available without a recorded qualification. |
What this feature can and cannot do
Helps protect against
- Content injection
- Cross-site scripting
- Untrusted embedding
Does not guarantee
- Unsafe application logic already permitted by the policy
- Server-side injection
- Complete prevention of browser implementation defects
What you need before using it
- A policy designed and tested for the application
Fallback to keep in place
Keep output encoding, input handling, dependency review, and other application controls in place.