CSP2

内容セキュリティーポリシー (CSP)

[138] CSP (内容セキュリティーポリシー (content security policy) ) は、当該Webページが満たすべきセキュリティー上の制約を記述するものです。 CSP を使うことで、 XSS などの Webアプリケーション脆弱性の影響範囲を限定するなど、 Webサイトの安全性を向上させることができます。

仕様書

用法

[174] Webページで利用する機能 (アクセスする範囲) が元々限られている場合に、 悪意ある第三者の攻撃でそれ以外の機能が利用されようとするとき、 (Webページに脆弱性があって本来それが防げないとしても) CSP で利用する範囲を予め指定しておいたなら、攻撃を防ぐことができます。

[175] UGC 系の Webアプリケーションなどで利用者による任意の入力を Webページに掲載したい場合に、悪意ある利用者が攻撃目的の入力を与えても他の利用者に危害を加えることがないよう、 CSP を使って認められる範囲を指定することができます。

指令

[71] 次の指令があります。


[113] (なぜか) IANA登録簿があります >>112, >>111

[176] しかし古い CSP2 のものしか登録されていません。 W3C勧告になったものしか登録されないのでしょうか。 CSP3 で全体的に大きな変更が加わっていますし、 CSP 本体以外にも色々な仕様書があるのに、 それらが登録されていないのでは登録簿の意味がありません。

CSP リスト

[83] 文書 >>82WorkerGlobalScope >>87 は、CSPリスト (CSP list) を持ちます。

[84] これは適用される CSP のオブジェクトのリストです。初期状態では空です。 >>82

[86] navigate ではDocumentのCSPリストの初期化により値が設定されます。

[88] run a worker では応答CSPリストが引き継がれます。

[85] overridden reloadsrcdoc 属性の読み込みでは、元の文書CSPリストが引き継がれます。

関連

[139] fetchnavigate砂箱化と深く関係しています。

歴史

[1] Security/CSP - MozillaWiki ( 版) https://wiki.mozilla.org/Security/CSP

[2] Security/CSP/Spec - MozillaWiki ( 版) https://wiki.mozilla.org/Security/CSP/Spec

[3] Security/CSP/Specification - MozillaWiki ( 版) https://wiki.mozilla.org/Security/CSP/Specification

[4] XSS mitigation in browsers ( (Adam Barth 著, 版)) http://lists.w3.org/Archives/Public/public-web-security/2011Jan/0002.html

[5] Content Security Policy ( ( 版)) http://www.w3.org/TR/2011/WD-CSP-20111129/

[6] IRC logs: freenode / #whatwg / 20111206 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20111206

[7] [whatwg] CSP sandbox directive integration with HTML ( 版) http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-December/034071.html

[8] Content Security Policy ( ( 版)) http://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html

[9] draft-gondrom-websec-csp-header-00 - HTTP Header Content Security Policy ( ( 版)) http://tools.ietf.org/html/draft-gondrom-websec-csp-header-00

[10] Content Security Policy (CSP) - Google Chrome Extensions - Google Code ( ( 版)) http://code.google.com/chrome/extensions/contentSecurityPolicy.html

[11] Content Security Policy 1.0 ( ( 版)) http://www.w3.org/TR/2012/WD-CSP-20120710/

[12] Content Security Policy 1.0 ( ( 版)) http://www.w3.org/TR/2012/CR-CSP-20121115/

[13] User Interface Safety Directives for Content Security Policy ( ( 版)) http://www.w3.org/TR/2012/WD-UISafety-20121120/

[14] Content Security Policy 1.1 ( ( 版)) http://www.w3.org/TR/2012/WD-CSP11-20121213/

[15] Chromium Blog: Chrome 25 Beta: Content Security Policy and Shadow DOM ( ( 版)) http://blog.chromium.org/2013/01/content-security-policy-and-shadow-dom.html

[16] Runtime and Security Model for Web Applications ( ( 版)) http://www.w3.org/TR/2013/WD-runtime-20130321/#csp-policy

[17] User Interface Security Directives for Content Security Policy ( ( 版)) http://www.w3.org/TR/2013/WD-UISecurity-20130523/

[18] Chromium Blog: Chrome 28 Beta: A more immersive web, everywhere ( ( 版)) http://blog.chromium.org/2013/05/chrome-28-beta-more-immersive-web.html

[19] Content Security Policy 1.1 ( ( 版)) http://www.w3.org/TR/2013/WD-CSP11-20130604/

[20] Content Security Policy (CSP) - Google Chrome ( ( 版)) http://developer.chrome.com/extensions/contentSecurityPolicy.html

[21] Default CSP restrictions - Security | MDN ( ( 版)) https://developer.mozilla.org/en/docs/Security/CSP/Default_CSP_restrictions

[22] Introducing Content Security Policy - Security | MDN ( ( 版)) https://developer.mozilla.org/en-US/docs/Security/CSP/Introducing_Content_Security_Policy

[23] [webappsec] Proposal: Closing the feature set of CSP 1.1 ( (Brad Hill 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2013Sep/0019.html

[24] Content Security Policy 1.1 ( ( 版)) http://w3c.github.io/webappsec/specs/content-security-policy/csp-specification.dev.html

[25] Bug 2494 – Add hooks for CSP ( ( 版)) https://bugs.ecmascript.org/show_bug.cgi?id=2494

[26] Content Security Policy 1.1 ( ( 版)) http://www.w3.org/TR/2014/WD-CSP11-20140211/

[27] User Interface Security Directives for Content Security Policy ( ( 版)) http://www.w3.org/TR/2014/WD-UISecurity-20140318/

[28] User Interface Security Directives for Content Security Policy ( ( 版)) https://dvcs.w3.org/hg/user-interface-safety/raw-file/tip/user-interface-safety.html

[29] Clarify MIX and CSP hooks a bit · 682f68d · whatwg/fetch ( ( 版)) https://github.com/whatwg/fetch/commit/682f68d5f0cce7f9637a8f6d9450b514ed276f9b

[30] Put MIX/CSP hooks in switch. Put second MIX check before tainting. · 567fe8a · whatwg/fetch ( ( 版)) https://github.com/whatwg/fetch/commit/567fe8ad5f1804efdefa7aa273f2a366b223c70e

[31] Content Security Policy Level 2 ( ( 版)) http://www.w3.org/TR/2014/WD-CSP2-20140703/

[32] "Why is CSP failing? Trends and Challenges in CSP Adoption" ( (Oda, Terri 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2014Jul/0100.html

[33] ( ( 版)) http://mweissbacher.com/publications/csp_raid.pdf

[34] [webappsec] Call for Consensus: CSP Level 2 to Candidate Recommendation ( (Brad Hill 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2014Oct/0063.html

[35] [webappsec] Call for Consensus: Stop work on Content Security Policy 1.0, transition to WG Note ( (Brad Hill 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2014Oct/0064.html

[36] CSP3: Starting on DOM API strawman. · 92b8dd4 · w3c/webappsec ( ( 版)) https://github.com/w3c/webappsec/commit/92b8dd4778ad1a237e5b5be015f9482bd3ad2ff4

[37] CSP3: DOM API Strawman ( (Mike West 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2014Nov/0005.html

[38] [webappsec] Rechartering: CSP Level 3 ( (Brad Hill 著, 版)) http://lists.w3.org/Archives/Public/public-webappsec/2014Nov/0126.html

[39] Official Gmail Blog: Reject the unexpected - Content Security Policy in Gmail ( ( 版)) http://gmailblog.blogspot.jp/2014/12/reject-unexpected-content-security.html

[40] Fix the order of CSP, HSTS, Mixed Content, and Referrer https://www.w3.o... · b8c2c49 · whatwg/fetch ( 版) https://github.com/whatwg/fetch/commit/b8c2c4964c233cd3616042c04e2c14e0ff25485d

[41] Re: CfC: Transition CSP2 to CR. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Feb/0124.html

[42] Content Security Policy 1.0 ( ( 版)) http://www.w3.org/TR/2015/NOTE-CSP1-20150219/

[43] Content Security Policy Level 2 ( ( 版)) http://www.w3.org/TR/2015/CR-CSP2-20150219/

[44] Content Security Policy Pinning ( ( 版)) http://www.w3.org/TR/2015/WD-csp-pinning-20150226/

[45] Content Security Policy Pinning ( ( 版)) https://w3c.github.io/webappsec/specs/csp-pinning/

[46] Content Security Policy ( 版) http://people.mozilla.org/~bsterne/content-security-policy/index.html

[47] Security/CSP/Spec - MozillaWiki ( 版) https://wiki.mozilla.org/Security/CSP/Spec

[49] Store a url list for requests and responses so CSP can do the right t… · whatwg/fetch@1d8173a ( 版) https://github.com/whatwg/fetch/commit/1d8173afffcffad2587f2922381878939c9cebea

[50] Add the response CSP check as open issue. Fixes #77. · whatwg/fetch@baeb561 ( 版) https://github.com/whatwg/fetch/commit/baeb561384ee353b13a2ca0b2a31fd79b769caa2

[51] CSP: Blob URLs in new windows. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Jul/0126.html

[52] Re: CfC: Mixed Content to PR; deadline July 6th. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Jul/0144.html

Hammering out scope for CSP3 is on my list for this quarter. Rewriting

enforcement and monitoring in terms of Fetch is totally going to happen.

Sorry it's taken so long.

[53] Content Security Policy Level 2 ( ( 版)) http://www.w3.org/TR/2015/CR-CSP2-20150721/

[54] Runtime and Security Model for Web Applications ( 版) http://www.w3.org/TR/2015/NOTE-runtime-20150806/#csp-policy

[55] RE: CfC: CSP2 to PR; deadline Aug 18th. (Crispin Cowan 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Aug/0069.html

[56] JSON CSP ( 版) https://gist.github.com/jonathanKingston/5699b440f608960dc089

[57] JSON representation of CSP policies (Jonathan Kingston 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Aug/0073.html

[58] Re: JSON representation of CSP policies (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Aug/0079.html

[60] Fix #88: add the 'Content-Security-Policy' pragma directive · whatwg/html@5064a62 ( 版) https://github.com/whatwg/html/commit/5064a629f22bef29839ab4dc6f1ceef17f010bc5

[61] CSP-COOKIES: If nothing else, this will be a good argument aabout doc… · w3c/webappsec@8e1be6f ( 版) https://github.com/w3c/webappsec/commit/8e1be6ff6407b71443b2efe5b21d9455aa607ef8

[62] CSP-COOKIES: Cleaning up for wider review. · w3c/webappsec@ee2d941 ( 版) https://github.com/w3c/webappsec/commit/ee2d9412e651eba82f5c2fc3d628b6d0e55c21be

[63] CSP3 as a polylithic set of modules? (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Sep/0210.html

[64] Content Security Policy Pinning ( 版) https://w3c.github.io/webappsec-csp/pinning/

[65] w3c/webappsec-csp ( 版) https://github.com/w3c/webappsec-csp

[66] CSP: Defining the CH-CSP Client Hint. · 049a3c9 · w3c/webappsec ( ( 版)) https://github.com/w3c/webappsec/commit/049a3c94817770487e21d6151b135bca4b19ba46

[67] CSP: Drop the 'CH-' prefix on the request header. · 548a228 · w3c/webappsec ( ( 版)) https://github.com/w3c/webappsec/commit/548a228a5349b0eef8a14e048500e8eb3dbf3674

[68] CSP2: Note the issue the 'CSP' header was meant to solve. · w3c/webappsec@5233fe8 ( 版) https://github.com/w3c/webappsec/commit/5233fe8e75fd5b155135c6eca35fb48e685c14e5

[69] draft-west-webappsec-csp-reg-00 - Content Security Policy Directive Registry ( 版) https://tools.ietf.org/html/draft-west-webappsec-csp-reg-00

[70] Hey, look at that. A strawman IANA registry. · w3c/webappsec-csp@224f8e6 ( 版) https://github.com/w3c/webappsec-csp/commit/224f8e6ac414119260af0fc8a0f8326b94bac655

[72] 763879 – (CSP) implement blocking of inline stylesheets ( 版) https://bugzilla.mozilla.org/show_bug.cgi?id=763879

[73] Clear response's CSP list before setting. · w3c/webappsec-csp@0545ae0 ( 版) https://github.com/w3c/webappsec-csp/commit/0545ae08d6c74788f006e07b2b991bbf925c9691

[74] Extensions should bypass CSP. · w3c/webappsec-csp@1b7b2c4 ( 版) https://github.com/w3c/webappsec-csp/commit/1b7b2c401ed1dc2b435cb3e68313ced19c88d597

[75] Update Fetch with shiny, new CSP hooks · whatwg/fetch@8ce550b ( 版) https://github.com/whatwg/fetch/commit/8ce550b53c53e2b6e8376373b94d66b2eeada8f8

[76] Drop Fetch issues after https://github.com/whatwg/fetch/commit/8ce550… · w3c/webappsec-csp@c2b6452 ( 版) https://github.com/w3c/webappsec-csp/commit/c2b64522fb6f4cb4f683344ee3cd890dfdcc515d

[77] Update CSP links · whatwg/html@7e8a536 ( 版) https://github.com/whatwg/html/commit/7e8a5367d1e0d9c1b7e84d2c86e7821af0ff167a

[78] Upgrade Insecure Requests ( 版) https://w3c.github.io/webappsec-upgrade-insecure-requests/#reporting-upgrades

Upgrading insecure requests MUST not interfere with an authors' ability to track down requests that would be insecure in a user agent that does not support upgrades. To that end, upgrades MUST be performed after evaluating request against all monitored security policies, but before evaluating request against all enforced policies.

[79] Upgrade Insecure Requests ( 版) https://w3c.github.io/webappsec-upgrade-insecure-requests/#violation-report-target

When sending a violation report for an upgraded resource, user agents MUST target the Document or Worker that triggered the request, rather than the Document or Worker on which the upgrade-insecure-requests directive was set. Due to §3.3 Policy Inheritance, the latter might be a cross-origin ancestor of the former, and sending violation reports to that set of reporting endpoints could leak data in unexpected ways.

Likewise, the SecurityPolicyViolationEvent MUST NOT target any Document other than the one which triggered the request, for the same reasons.

[80] Allow upgrades from explicitly insecure expressions · w3c/webappsec-csp@0e81d81 ( 版) https://github.com/w3c/webappsec-csp/commit/0e81d81b64c42ca3c81c048161162b9697ff7b60

[81] Use the URL from the response, if it has one · whatwg/fetch@ed37f5e ( 版) https://github.com/whatwg/fetch/commit/ed37f5e4cf0ec6615f93b8a575d7349b977ffc3a

[89] Split reporting and enforcement for Fetch. · w3c/webappsec-csp@6647d2d ( 版) https://github.com/w3c/webappsec-csp/commit/6647d2de191283e94cec1059411f536e6d6b95b5

[90] Separate 'report-only' and 'enforce' CSP execution · whatwg/fetch@a58871a ( 版) https://github.com/whatwg/fetch/commit/a58871a92cbf9304ea4e661f31efb9f2b78bf44b

[91] Call out to CSP's inline element hooks · whatwg/html@ee3486e ( 版) https://github.com/whatwg/html/commit/ee3486eb129bc350b5ca684d0c91dff23453ac1a

[92] Move to CSP2. · w3c/webappsec-csp@2a08d9b ( 版) https://github.com/w3c/webappsec-csp/commit/2a08d9b2ee2a5cea8f0bd2bae1f7faedd9a700e7

[93] Updating EMBEDDED for a potential FPWD. · w3c/webappsec-csp@7260140 ( 版) https://github.com/w3c/webappsec-csp/commit/726014018c622455f72cd434a8622e784322318d

[94] CfC: CSP Embedded Enforcement to FPWD; deadline Dec. 7th. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Nov/0070.html

[95] Working on the split. · w3c/webappsec-csp@72c7f3e ( 版) https://github.com/w3c/webappsec-csp/commit/72c7f3ecc3eae190bd5df656cb5e8dbc4abb5a9a

[96] new CSP draft. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Dec/0025.html

[97] Close #384: add CSP hooks to handle inline events and style · whatwg/html@920c918 ( 版) https://github.com/whatwg/html/commit/920c9183a7990968ecac1aeedae22391f3438791

[98] Content Security Policy: Cookie Controls ( ( 版)) http://www.w3.org/TR/2015/WD-csp-cookies-20151215/

[99] Content Security Policy: Embedded Enforcement ( ( 版)) http://www.w3.org/TR/2015/WD-csp-embedded-enforcement-20151215/

[100] Call for Exclusions: Content Security Policy: Cookie Controls and Content Security Policy: Embedded Enforcement (Xueyuan Jia 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2015Dec/0034.html

[101] CfC: CSP3 to FPWD; deadline January 15th. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2016Jan/0034.html

[102] s/serialized policy/serialized CSP/g · w3c/webappsec-csp@17c18c0 ( 版) https://github.com/w3c/webappsec-csp/commit/17c18c04cbe94a0796e353aa99d972cb9021b3cf

[103] Update xrefs for CSP sandbox & frame-ancestors · whatwg/html@088f4f2 ( 版) https://github.com/whatwg/html/commit/088f4f210541f8c131fb92c4f331c40f4b6b3768

[104] Content Security Policy Level 3 ( ( 版)) https://www.w3.org/TR/2016/WD-CSP3-20160126/

[105] IANA: AUTH48 version of the RFC. · w3c/webappsec-csp@1bfbb97 ( 版) https://github.com/w3c/webappsec-csp/commit/1bfbb97a12e6338c563e19bcfd2582291ab33e80

[106] Fix links to CSP list initialization algorithms · whatwg/html@59d9ae1 ( 版) https://github.com/whatwg/html/commit/59d9ae1ed8df16dbea7eb6906e333d12d8ceeecf

[107] CSP: Fix workers' CSP list initialization. · whatwg/html@05f9f32 ( 版) https://github.com/whatwg/html/commit/05f9f3266d6050b8b299ec365fdc63d5eab5b2b3

[108] No CSP report-uri|frame-ancestors|sandbox in meta · whatwg/html@3947072 ( 版) https://github.com/whatwg/html/commit/39470724136a366bab4e893efd889a513d61cc3e

[109] No CSP report-uri|frame-ancestors|sandbox in meta · whatwg/html@3947072 ( 版) https://github.com/whatwg/html/commit/39470724136a366bab4e893efd889a513d61cc3e

[110] RFC 7762 - Initial Assignment for the Content Security Policy Directives Registry ( 版) https://tools.ietf.org/html/rfc7762

[114] FYI: RFC7762 established a registry of CSP directives (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2016Feb/0047.html

[115] IANA bits. · w3c/webappsec-upgrade-insecure-requests@1d4db1a ( 版) https://github.com/w3c/webappsec-upgrade-insecure-requests/commit/1d4db1a5be26ea83caa45e9bbebbb00a100c4102

[116] Making it easier to deploy CSP. (Mike West 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2016Feb/0048.html

[119] Call for Exclusions (Update): Content Security Policy: Cookie Controls; Content Security Policy: Embedded Enforcement (Xueyuan Jia 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2016Mar/0033.html

[120] We're not going to enable 'sandbox' in '<meta>'. · w3c/webappsec-csp@8ca78f0 ( 版) https://github.com/w3c/webappsec-csp/commit/8ca78f0ed12bbbde0a11c4d58fb936ce0a25f9d7

[121] CSP Request Header and CORS preflight fetch. · Issue #52 · whatwg/fetch ( 版) https://github.com/whatwg/fetch/issues/52

[122] CloudFlare - The web performance & security company ( 版) https://www.cloudflare.com/

content-security-policy:default-src 'self' https://*; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://* data:; img-src 'self' https://* data:; style-src 'self' 'unsafe-inline' https://*; font-src 'self' https://* data:; frame-src https://*; connect-src 'self' data: https://*

[123] GitHub ( 版) https://github.com/

Content-Security-Policy:default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src render.githubusercontent.com; connect-src 'self' uploads.github.com status.github.com api.github.com www.google-analytics.com github-cloud.s3.amazonaws.com api.braintreegateway.com client-analytics.braintreegateway.com wss://live.github.com; font-src assets-cdn.github.com; form-action 'self' github.com gist.github.com; frame-ancestors 'none'; frame-src render.githubusercontent.com; img-src 'self' data: assets-cdn.github.com identicons.github.com www.google-analytics.com collector.githubapp.com *.gravatar.com *.wp.com checkout.paypal.com *.githubusercontent.com; media-src 'none'; object-src assets-cdn.github.com; plugin-types application/x-shockwave-flash; script-src assets-cdn.github.com; style-src 'unsafe-inline' assets-cdn.github.com

[124] Twitter ( 版) https://twitter.com/

content-security-policy:script-src https://connect.facebook.net https://cm.g.doubleclick.net https://ssl.google-analytics.com https://graph.facebook.com https://twitter.com 'unsafe-eval' https://*.twimg.com https://api.twitter.com https://analytics.twitter.com https://publish.twitter.com https://ton.twitter.com https://syndication.twitter.com https://www.google.com https://t.tellapart.com https://platform.twitter.com 'nonce-ukbsoXB8DeM97dTLyRPKOw==' https://www.google-analytics.com 'self'; frame-ancestors 'self'; font-src https://twitter.com https://*.twimg.com data: https://ton.twitter.com https://fonts.gstatic.com https://maxcdn.bootstrapcdn.com https://netdna.bootstrapcdn.com 'self'; media-src https://twitter.com https://*.twimg.com https://ton.twitter.com blob: 'self'; connect-src https://graph.facebook.com https://*.giphy.com https://pay.twitter.com https://analytics.twitter.com https://media.riffsy.com https://upload.twitter.com https://api.mapbox.com 'self'; style-src https://fonts.googleapis.com https://twitter.com https://*.twimg.com https://translate.googleapis.com https://ton.twitter.com 'unsafe-inline' https://platform.twitter.com https://maxcdn.bootstrapcdn.com https://netdna.bootstrapcdn.com 'self'; object-src https://twitter.com https://pbs.twimg.com; default-src 'self'; frame-src https://staticxx.facebook.com https://twitter.com https://*.twimg.com https://player.vimeo.com https://pay.twitter.com https://www.facebook.com https://ton.twitter.com https://syndication.twitter.com https://vine.co twitter: https://www.youtube.com https://platform.twitter.com https://upload.twitter.com https://s-static.ak.facebook.com 'self' https://donate.twitter.com; img-src https://graph.facebook.com https://*.giphy.com https://twitter.com https://*.twimg.com data: https://fbcdn-profile-a.akamaihd.net https://www.facebook.com https://ton.twitter.com https://*.fbcdn.net https://syndication.twitter.com https://media.riffsy.com https://www.google.com https://stats.g.doubleclick.net https://*.tiles.mapbox.com https://www.google-analytics.com blob: 'self'; report-uri https://twitter.com/i/csp_report?a=NVQXGYLXFVYXO2LGOQ%3D%3D%3D%3D%3D%3D&ro=false;

[125] Change to expression matching algorithm (#71) · w3c/webappsec-csp@e6d9233 ( 版) https://github.com/w3c/webappsec-csp/commit/e6d92335d0b9797fa72517c16dda01dd8e761449

[126] Define 'Content Security Policy'. · w3c/webappsec-csp@b98e59b ( 版) https://github.com/w3c/webappsec-csp/commit/b98e59bd478435577f78699e65ee135954e2ce42

[127] Content Security Policy Level 3 ( 版) https://www.w3.org/TR/2016/WD-CSP3-20160425/

[128] Allow hashes to match external scripts · w3c/webappsec-csp@a299d38 ( 版) https://github.com/w3c/webappsec-csp/commit/a299d38d1b54e3d9612d11fb69cc8174b5e44051

[129] Fix up the logic in source list matching (#74) ( (shekyan著, )) https://github.com/w3c/webappsec-csp/commit/8c1b6a88777374c3b47976fb5d4201d449a679f1

[130] Fold CSPDOCUMENT into CSP. ( (mikewest著, )) https://github.com/w3c/webappsec-csp/commit/0cd4bf42b5e78168cd85efe798a9a5e719677b8e

[131] Updating references from CSPDOCUMENT to CSP ( (mikewest著, )) https://github.com/whatwg/html/commit/c90e53cfa0d4ae43110589ea7c2718b65be3fda7

[132] CloudFlare - The web performance & security company ( ()) https://www.cloudflare.com/

Content-Security-Policy: default-src 'self' https://*; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://* data:; img-src 'self' https://* data:; style-src 'self' 'unsafe-inline' https://*; font-src 'self' https://* data:; frame-src https://*; connect-src 'self' https://* wss://*.zopim.com data:;

[133] Chrome incompatibilities - Mozilla | MDN ( ()) https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities

content_security_policy

Firefox does not support:

"http://127.0.0.1" or "http://localhost" as script sources: they must be served over HTTPS.

[134] Content Security Policy - Mozilla | MDN ( ()) https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_Security_Policy

[135] Content Security Policy Level 3 ( ()) https://www.w3.org/TR/2016/WD-CSP3-20160621/

[136] Add IANA considerations section referencing `require-sri-for` (shekyan著, ) https://github.com/w3c/webappsec-subresource-integrity/commit/853ab1bd8815e23001a24c57b68f424cdd09f0b5

[137] amphtml/amp-html-format.md at master · ampproject/amphtml () https://github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md

AMP HTML documents must not trigger errors when served with a Content Security Policy that does not include the keywords unsafe-inline and unsafe-eval.

[140] Call for Consensus: Stop work and transition 3 Working Drafts to Working Group Notes (Brad Hill著, ) https://lists.w3.org/Archives/Public/public-webappsec/2016Jul/0013.html

CSP Cookie Controls

https://www.w3.org/TR/csp-cookies/

Last updated ~6 months ago.

Reason to transition to Note: The Feature Policy proposal (

https://wicg.github.io/feature-policy/) could be a better home for the

intended functionality as part of a broader and more coherent approach,

rather than putting this into CSP.

[141] Call for Consensus: Stop work and transition 3 Working Drafts to Working Group Notes (Brad Hill著, ) https://lists.w3.org/Archives/Public/public-webappsec/2016Jul/0013.html

CSP Pinning

https://www.w3.org/TR/csp-pinning/

Last updated ~6 months ago.

Reason to transition to Note: While this kind of feature is still

considered useful, like Cookie Controls and Feature Policy, the editor

feels it would be better managed as part of a more generalized strategy for

header pinning, and as part of that, with a strategy perhaps along the

lines of a manifest, well-known resource or service worker that doesn't

incur the cost of sending the pinning header with every request.

[142] Transition Cookie Controls and Pinning to NOTE status (#103) (hillbrad著, ) https://github.com/w3c/webappsec-csp/commit/d3705f5c4fda042345bfb1457388ba9c27c69420

[143] Pass |origin| into matching algorithms. (@shekyan著, ) https://github.com/w3c/webappsec-csp/commit/3739f6f1b1406c3c88757803859aeb6836028d38

[144] Content Security Policy Level 3 () https://www.w3.org/TR/2016/WD-CSP3-20160818/

[145] Allow "*" to match scheme of protected resource (#105) (shekyan著, ) https://github.com/w3c/webappsec-csp/commit/22c3ab8ff872668b2454227e87427e8677f4db7c

[146] Content Security Policy Level 3 () https://www.w3.org/TR/2016/WD-CSP3-20160901/

[147] path -> path-abempty. Closes w3c/webappsec-csp#89. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/039136ff232995b7573059dbe34c9df3f67a2335

[148] A Refined Content Security Policy | WebKit () https://webkit.org/blog/6830/a-refined-content-security-policy/

[149] generate note versions of obsolete specs (hillbrad著, ) https://github.com/w3c/webappsec-csp/commit/b33ff0aed91c085ebcf1776cc9271f0fc412e678

[150] Updating to get things in line with the current CSP and HTML specs. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/380667c81cea337a78ccc5d1a7ded4976680fa8e

[151] Content Security Policy: Embedded Enforcement () https://www.w3.org/TR/2016/WD-csp-embedded-enforcement-20160909/

[152] CSP: Embedded Enforcement (Mike West著, ) https://lists.w3.org/Archives/Public/public-webappsec/2016Sep/0033.html

[153] Content Security Policy: Cookie Controls () https://www.w3.org/TR/2016/NOTE-csp-cookies-20160913/

[154] Content Security Policy Pinning () https://www.w3.org/TR/2016/NOTE-csp-pinning-20160913/

[155] Content Security Policy Level 3 () https://www.w3.org/TR/2016/WD-CSP3-20160913/

[156] Update IDL to introduce SecurityPolicyVioationEventDisposition type (#… (shekyan著, ) https://github.com/w3c/webappsec-csp/commit/54cdc310b087a61ddff4a79fb8706c55e5b6dc2d

[157] Report destination. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/9c5d9f662bee1948e23ab908c2b9ac65b0a8e291

[158] Use request's "current url" rather than "url". (#135) (@estark37著, ) https://github.com/w3c/webappsec-csp/commit/8a88c0cf306b34da6a8fee7cfa574ff9fa34740c

[159] Content Security Policy Level 2 () https://www.w3.org/TR/2016/PR-CSP2-20161108/

[160] Clarify fetch settings for reporting. (#139) (jdalton著, ) https://github.com/w3c/webappsec-csp/commit/558282b4ea040191066cae4a028dab83a886166a

[161] Adding CSPSource subsumption (#138) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/928d62261496965f16dcf5fddc5d943670d7f963

[162] Handle navigation to `javascript:` URLs as inline script. (#142) (@bzbarsky著, ) https://github.com/w3c/webappsec-csp/commit/479bf6c6e891db0bb1cd7f71be764f3aff6a1a33

[163] Change the model for workers. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/1af72ed19bf952402c514b7e7a966fb234d63217

[164] Finding effective directive for a given name (#153) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/4c10ab80cf996a35106b2c2f4e5a78fbb6fa819f

[165] Intersection of serialized source lists (#157) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/59b2839f98e491d0170d1389c6fd857d44b92247

[166] Adding intersection of two policies (#163) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/317b919cd5819cca0d490b1034f8b9b88abeda16

[167] Intersection of a set of policies (#164) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/d66e1e348bb4c91b91123c2e3b9b4d326f6b9f8b

[168] EE: Effective source list (#165) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/23fb3a53e0701a7c4ac971d6b9fc14aab6e77a41

[169] EE: Response's CSP list subsumption (#168) (Sun77789著, ) https://github.com/w3c/webappsec-csp/commit/716e7196f1e2b5e4de94bf5bfcddb8660f04ac81

[170] Adding issues to take care of the cascade. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/671fcb45caf6e524179bcbfd71fe68e37660f8b6

[171] EE: Cleaning up HTML integration. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/730b36f3ab9492fcf6f2339d23a15319ca6a779d

[172] Restructuring intersection. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/0e9ae5fc8237359a37000fe6b38c6f508c84bf2b

[173] `<iframe srcdoc="<script>">` should not execute when inserted via `innerHTML`. · Issue #2300 · whatwg/html () https://github.com/whatwg/html/issues/2300

[177] Re: Add ability to specify the version of used CSP (Mike West著, ) https://lists.w3.org/Archives/Public/public-webappsec/2017Mar/0025.html

[178] Copy/paste 'paths and redirects' from CSP2. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/402ebd330cd652417d5434d33acba60091a48709

[179] Track the source of a given policy. (#214) (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/1082da46cf89a7e5c4ea298a072aab4580aa1e60

[180] Polishing {scheme,host,port,path}-matching algorithms. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/75fca786bd55e665e39774aa9b52e3fc3e38db66

[181] The 'csp' IDL attribute reflects the content attribute. (@foolip著, ) https://github.com/w3c/webappsec-csp/commit/3ac127abb700a5d36ff69b4e4afe7b68c91afd9d

[182] [Execute Script] Note about CSP policies being ignored. (shs96c著, ) https://github.com/w3c/webdriver/commit/c0cc934c652ef0393ca0317ce3b7b290c0bf47df

[183] Ask for web-platform-tests in CONTRIBUTING.md (#230) (foolip著, ) https://github.com/w3c/webappsec-csp/commit/6b0476da5dfc661d6aed84f2cb2fa1f5aa0826e9

[184] Ask for web-platform-tests in CONTRIBUTING.md by foolip · Pull Request #230 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/230

[185] Cleanup `global object` usage to make sense with `Documents` (#254) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/80bf6a439a744ebc7cb1b6d7373d0f0236d3584b

[186] Cleanup `global object` usage to make sense with `Documents` by andypaicu · Pull Request #254 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/254

[187] Replaced 'alias' with 'copy' for less ambiguity (#273) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/2c0f4aa08621556a34c245345fcfb41ef899af6b

[188] Replaced 'alias' with 'copy' for less ambiguity by andypaicu · Pull Request #273 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/273

[189] What does it mean to alias a policy from a CSP list? · Issue #207 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/207

[190] 23357 – Subverting CSP policies for browser add-ons (extensions). () https://www.w3.org/Bugs/Public/show_bug.cgi?id=23357

[191] CSP 1.1: Remove note about extensions. (mikewest著, ) https://github.com/w3c/webappsec/commit/cbfaa8edfadebf21a9c7428242c12e45934d8c55

[192] CSP vulnerability enabling cross-origin session data exfiltration · Issue #289 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/289

[193] Hide nonce content attribute values (mikewest著, ) https://github.com/whatwg/html/commit/19f5cce801550d278b9459f8c4797f9f86aae864

[194] Consider hiding `nonce` content attributes. · Issue #2369 · whatwg/html () https://github.com/whatwg/html/issues/2369

[195] Twitter名前検索 () https://twitter.com/search-home

content-security-policy:script-src https://connect.facebook.net https://cm.g.doubleclick.net https://ssl.google-analytics.com https://graph.facebook.com 'nonce-OYd+Tgp6EYGXSARn0PRbbg==' https://twitter.com 'unsafe-eval' https://*.twimg.com https://api.twitter.com https://analytics.twitter.com https://publish.twitter.com https://ton.twitter.com https://syndication.twitter.com https://www.google.com https://t.tellapart.com https://platform.twitter.com https://www.google-analytics.com blob: 'self'; frame-ancestors 'self'; font-src https://twitter.com https://*.twimg.com data: https://ton.twitter.com https://fonts.gstatic.com https://maxcdn.bootstrapcdn.com https://netdna.bootstrapcdn.com 'self'; media-src https://rmpdhdsnappytv-vh.akamaihd.net https://prod-video-eu-central-1.pscp.tv https://v.cdn.vine.co https://dwo3ckksxlb0v.cloudfront.net https://twitter.com https://amp.twimg.com https://smmdhdsnappytv-vh.akamaihd.net https://*.twimg.com https://prod-video-eu-west-1.pscp.tv https://rmmdhdsnappytv-vh.akamaihd.net https://clips-media-assets.twitch.tv https://prod-video-us-west-2.pscp.tv https://prod-video-us-west-1.pscp.tv https://prod-video-ap-northeast-1.pscp.tv https://smdhdsnappytv-vh.akamaihd.net https://ton.twitter.com https://rmdhdsnappytv-vh.akamaihd.net https://mmdhdsnappytv-vh.akamaihd.net https://smpdhdsnappytv-vh.akamaihd.net https://prod-video-sa-east-1.pscp.tv https://mdhdsnappytv-vh.akamaihd.net https://prod-video-ap-southeast-2.pscp.tv https://mtc.cdn.vine.co https://dev-video-us-west-2.pscp.tv https://prod-video-us-east-1.pscp.tv blob: 'self' https://prod-video-ap-southeast-1.pscp.tv https://mpdhdsnappytv-vh.akamaihd.net https://dev-video-eu-west-1.pscp.tv; connect-src https://rmpdhdsnappytv-vh.akamaihd.net https://prod-video-eu-central-1.pscp.tv https://graph.facebook.com https://*.giphy.com https://dwo3ckksxlb0v.cloudfront.net https://vmaprel.snappytv.com https://smmdhdsnappytv-vh.akamaihd.net https://*.twimg.com https://embed.pscp.tv https://api.twitter.com https://prod-video-eu-west-1.pscp.tv https://rmmdhdsnappytv-vh.akamaihd.net https://clips-media-assets.twitch.tv https://prod-video-us-west-2.pscp.tv https://pay.twitter.com https://prod-video-us-west-1.pscp.tv https://analytics.twitter.com https://vmap.snappytv.com https://*.twprobe.net https://prod-video-ap-northeast-1.pscp.tv https://smdhdsnappytv-vh.akamaihd.net https://syndication.twitter.com https://sentry.io https://rmdhdsnappytv-vh.akamaihd.net https://media.riffsy.com https://mmdhdsnappytv-vh.akamaihd.net https://embed.periscope.tv https://smpdhdsnappytv-vh.akamaihd.net https://prod-video-sa-east-1.pscp.tv https://vmapstage.snappytv.com https://upload.twitter.com https://proxsee.pscp.tv https://mdhdsnappytv-vh.akamaihd.net https://prod-video-ap-southeast-2.pscp.tv https://dev-video-us-west-2.pscp.tv https://prod-video-us-east-1.pscp.tv 'self' https://vmap.grabyo.com https://prod-video-ap-southeast-1.pscp.tv https://mpdhdsnappytv-vh.akamaihd.net https://dev-video-eu-west-1.pscp.tv; style-src https://fonts.googleapis.com https://twitter.com https://*.twimg.com https://translate.googleapis.com https://ton.twitter.com 'unsafe-inline' https://platform.twitter.com https://maxcdn.bootstrapcdn.com https://netdna.bootstrapcdn.com 'self'; object-src https://twitter.com https://pbs.twimg.com; default-src 'self' blob:; frame-src https://staticxx.facebook.com https://twitter.com https://*.twimg.com https://5415703.fls.doubleclick.net https://player.vimeo.com https://pay.twitter.com https://www.facebook.com https://ton.twitter.com https://syndication.twitter.com https://vine.co twitter: https://www.youtube.com https://platform.twitter.com https://upload.twitter.com https://s-static.ak.facebook.com https://4337974.fls.doubleclick.net https://8122179.fls.doubleclick.net 'self' https://donate.twitter.com; img-src https://graph.facebook.com https://*.giphy.com https://*.pscp.tv https://twitter.com https://*.twimg.com https://ad.doubleclick.net data: https://clips-media-assets.twitch.tv https://lumiere-a.akamaihd.net https://fbcdn-profile-a.akamaihd.net https://www.facebook.com https://ton.twitter.com https://*.fbcdn.net https://syndication.twitter.com https://media.riffsy.com https://www.google.com https://stats.g.doubleclick.net https://platform.twitter.com https://api.mapbox.com https://www.google-analytics.com blob: https://*.periscope.tv 'self'; report-uri https://twitter.com/i/csp_report?a=NVQWGYSXFVZXO24GOQ%3D%3D%3D%3D%3D%3D&ro=false;

[196] Facebook - ログインまたは登録 () https://www.facebook.com/

content-security-policy:default-src * data: blob:;script-src *.facebook.com *.fbcdn.net *.facebook.net *.google-analytics.com *.virtualearth.net *.google.com 127.0.0.1:* *.spotilocal.com:* 'unsafe-inline' 'unsafe-eval' fbstatic-a.akamaihd.net fbcdn-static-b-a.akamaihd.net *.atlassolutions.com blob: data: 'self';style-src data: blob: 'unsafe-inline' *;connect-src *.facebook.com facebook.com *.fbcdn.net *.facebook.net *.spotilocal.com:* *.akamaihd.net wss://*.facebook.com:* https://fb.scanandcleanlocal.com:* *.atlassolutions.com attachment.fbsbx.com ws://localhost:* blob: *.cdninstagram.com 'self' chrome-extension://boadgeojelhgndaghljhdicfkmllpafd chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm;

[197] GitHub () https://github.com/

Content-Security-Policy: default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src render.githubusercontent.com; connect-src 'self' uploads.github.com status.github.com collector.githubapp.com api.github.com www.google-analytics.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com wss://live.github.com; font-src assets-cdn.github.com; form-action 'self' github.com gist.github.com; frame-ancestors 'none'; img-src 'self' data: assets-cdn.github.com identicons.github.com collector.githubapp.com github-cloud.s3.amazonaws.com *.githubusercontent.com; manifest-src 'self'; media-src 'none'; script-src assets-cdn.github.com; style-src 'unsafe-inline' assets-cdn.github.com; worker-src 'self'

[198] Editorial: set response's CSP list once (annevk著, ) https://github.com/whatwg/fetch/commit/860922f2c393c1b5408af7a80771c665b69a5bf7

[199] Should "set response's CSP list" be in Main fetch? · Issue #364 · whatwg/fetch () https://github.com/whatwg/fetch/issues/364

[200] Set response's CSP list once by annevk · Pull Request #701 · whatwg/fetch () https://github.com/whatwg/fetch/pull/701

[201] Editorial: lowercase content-security-policy <meta http-equiv> value (annevk著, ) https://github.com/whatwg/html/commit/e6a29247387e8f362654b280f72f746328667352

[202] Editorial: lowercase content-security-policy <meta http-equiv> value by annevk · Pull Request #3654 · whatwg/html () https://github.com/whatwg/html/pull/3654

[203] 23357 – Subverting CSP policies for browser add-ons (extensions). () https://www.w3.org/Bugs/Public/show_bug.cgi?id=23357

[204] Refactored fetch directives for readability and logic. (#318) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/937f02478703c5eccfa56036712b514b08b3b700

[205] Refactored fetch directives for readability and logic. by andypaicu · Pull Request #318 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/318

[206] Using the correct directive name when reporting violations (#337) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/10294d4e51598dc67106ab51aee144fcf89e5c44

[207] Using the correct directive name when reporting violations by andypaicu · Pull Request #337 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/337

[208] The effective directive for violations is incorrect · Issue #324 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/324

[209] Fixing whitespace issues and 2 comments in the area (#340) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/7c675fc237e300c574f41101f502f51c6398c71a

[210] Fixing whitespace issues and 2 comments in the area by andypaicu · Pull Request #340 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/340

[211] Update comment of directive value parsing · Issue #307 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/307

[212] Grammar: Clarity regarding constraints applied to path-part (path-absolute) production · Issue #303 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/303

[213] CSP: clarify whitespace characters · Issue #5 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/5

[214] Directive names should be lowercased (basically case-insensitive) (#346) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/5c4813650bc2c4f39262ceedf50a92440eb182c7

[215] Directive names should be lowercased (basically case-insensitive) (#346) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/5c4813650bc2c4f39262ceedf50a92440eb182c7

[216] Directive names should be lowercased (basically case-insensitive) by andypaicu · Pull Request #346 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/346

[217] Directive names should be lowercased (basically case-insensitive) by andypaicu · Pull Request #346 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/346

[218] Case-sensitivity resulting in divergent browser behavior · Issue #236 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/236

[219] Case-sensitivity resulting in divergent browser behavior · Issue #236 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/236

[220] Updated published WD. (mikewest著, ) https://github.com/w3c/webappsec-csp/commit/0e11091019856f6a4e2deba233787e7822c289d7

[221] Clone <iframe srcdoc>'s node document's CSP list (annevk著, ) https://github.com/whatwg/html/commit/ebf6d404858bd3d75ec29b4899866935a74c6dc6

[222] What does it mean to alias a policy from a CSP list? · Issue #207 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/issues/207

[223] Is srcdoc aliasing its parent's CSP or copying it? · Issue #2594 · whatwg/html () https://github.com/whatwg/html/issues/2594

[224] Clone <iframe srcdoc>'s node document's CSP list by annevk · Pull Request #4083 · whatwg/html () https://github.com/whatwg/html/pull/4083

[225] Added a note about fetch redirects being covered (#359) (andypaicu著, ) https://github.com/w3c/webappsec-csp/commit/df35fe41260ecd426e7f33dfa6bc1e0b432e1424

[226] Added a note about fetch redirects being covered by andypaicu · Pull Request #359 · w3c/webappsec-csp () https://github.com/w3c/webappsec-csp/pull/359