One dimension the browser looses control even with a CSP is via third-party plugins, which may have little / no enforcement.
The good people at Google via the W3C project have a CSP for white-listing allowed plugins, so a website can use plugins, that might break CSP, but restrict them, so the possible attack space is known (for example we know we don't allow swf files, we are not vulnerable to flash exploits...)
Right now it's only reported as working by chrome 40.0+ and android chrome 40.0+ source MDN
Awesome idea to make a library for this! :+1:
One dimension the browser looses control even with a CSP is via third-party plugins, which may have little / no enforcement.
The good people at Google via the W3C project have a CSP for white-listing allowed plugins, so a website can use plugins, that might break CSP, but restrict them, so the possible attack space is known (for example we know we don't allow swf files, we are not vulnerable to flash exploits...)
Right now it's only reported as working by chrome 40.0+ and android chrome 40.0+ source MDN
w3c spec with examples. http://www.w3.org/TR/CSP2/#directive-plugin-types