Browser security
Compatibility & evidence
Content execution

CSP sandbox

Applies a configurable sandbox to a protected resource.

Support in current browsers

Checked against the current browser versions recorded in MDN browser data 8.1.5.

BrowserMinimumOutcomeReason
Chrome155WorksEvery required mapped BCD feature is available without a recorded qualification.
Edge154WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari27WorksEvery required mapped BCD feature is available without a recorded qualification.
Chrome for Android155WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox for Android157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari on iOS27WorksEvery required mapped BCD feature is available without a recorded qualification.
Android WebView155WorksEvery required mapped BCD feature is available without a recorded qualification.
Samsung Internet30.0WorksEvery required mapped BCD feature is available without a recorded qualification.
The release trace

How support changed

Each segment groups recorded releases with the same result. Gaps between recorded versions are not filled in. This is support at each release, rather than the planner’s check of every release above a minimum.

Chrome

http.headers.Content-Security-Policy.sandbox
  1. 1 – 2424 recorded releases
    Not supported
  2. 25 – 155130 recorded releases
    Works

Edge

http.headers.Content-Security-Policy.sandbox
  1. 12 – 132 recorded releases
    Not supported
  2. 14 – 15480 recorded releases
    Works

Firefox

http.headers.Content-Security-Policy.sandbox
  1. 1 – 4952 recorded releases
    Not supported
  2. 50 – 157108 recorded releases
    Works

Safari

http.headers.Content-Security-Policy.sandbox
  1. 1 – 611 recorded releases
    Not supported
  2. 7 – 2750 recorded releases
    Works

Chrome for Android

http.headers.Content-Security-Policy.sandbox
  1. 181 recorded release
    Not supported
  2. 25 – 155130 recorded releases
    Works

Firefox for Android

http.headers.Content-Security-Policy.sandbox
  1. 4 – 4943 recorded releases
    Not supported
  2. 50 – 15798 recorded releases
    Works

Safari on iOS

http.headers.Content-Security-Policy.sandbox
  1. 1 – 68 recorded releases
    Not supported
  2. 7 – 2750 recorded releases
    Works

Android WebView

http.headers.Content-Security-Policy.sandbox
  1. 1 – 46 recorded releases
    Not supported
  2. 4.4 – 155120 recorded releases
    Works

Samsung Internet

http.headers.Content-Security-Policy.sandbox
  1. 1.01 recorded release
    Not supported
  2. 1.5 – 30.051 recorded releases
    Works

BCD 8.1.5 · catalogue 2.3.0. Source corrections can change this trace without a new browser release.

What this feature can and cannot do

Helps protect against

  • Over-privileged embedded documents
  • Untrusted active content

Does not guarantee

  • Every browser exploit
  • Unsafe granted sandbox tokens
  • Server authorisation

What you need before using it

  • A tested list of required sandbox capabilities

Fallback to keep in place

Isolate untrusted content on a separate origin and minimise active capabilities.