[OWASP-cheat-sheets] Clickjacking Defense CS: legacy vs CSP
dominique.righetto at owasp.org
Fri Apr 13 04:41:17 UTC 2018
For older browsers (only IE11 is supported about security updates so it's
recommanded to upgrade), one idea is to mimic the behavior of the SRI using
client JS hashing code but honnestly it's acceptable to request a "recent"
browser like IE>= 11 or recent version of FF,Chrome,Safari in order to
benefits from SRI, X-Frame-Optiosn or full CSP moreover in the context of
using feature like OAuth.
Cordialement, Best regards,
dominique.righetto at gmail.com
<dominique.righetto at gmail.com>dominique.righetto at owasp.org
<dominique.righetto at gmail.com>
On Thu, Apr 12, 2018 at 11:13 PM, Alex Efros <powerman at powerman.name> wrote:
> Looks like recommended clickjacking protection for legacy browsers
> require switching off much more powerful protection against XSS:
> Content-Security-Policy: default-src 'unsafe-inline';
> I'm developing OAuth server and really need best clickjacking protection,
> but I'm afraid this trade-off is too disadvantageous.
> Maybe it's possible to somehow move recommended CSS and JS snippets to
> separate files? I'm not really sure, but I suppose they are recommended to
> keep in <head> for a reason, because with external files there is always a
> chance they won't be (timely, at least) loaded for some reason.
> Another option is to keep CSS/JS inline, but use 'nonce-*' or 'sha256-*'
> instead of 'unsafe-inline' - but as these features of CSP2 I'm not sure is
> this combination will works in all cases (legacy browser without CSP,
> usual browser with CSP1, modern browser with CSP2).
> So, how to get best clickjacking protection without relaxing CSP too much?
> : https://www.owasp.org/index.php/Clickjacking_Defense_
> WBR, Alex.
> OWASP-cheat-sheets mailing list
> OWASP-cheat-sheets at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-cheat-sheets