diff --git a/draft-foudil-securitytxt.html b/draft-foudil-securitytxt.html index 5792539..3e5cb57 100644 --- a/draft-foudil-securitytxt.html +++ b/draft-foudil-securitytxt.html @@ -339,7 +339,7 @@ - + @@ -363,12 +363,12 @@ Y. Shafranovich -Expires: December 6, 2019 +Expires: December 18, 2019 Nightwatch Cybersecurity -June 04, 2019 +June 16, 2019 @@ -384,7 +384,7 @@

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

-

This Internet-Draft will expire on December 6, 2019.

+

This Internet-Draft will expire on December 18, 2019.

Copyright Notice

Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

@@ -561,7 +561,7 @@

3.3. Separate Fields

-

A separate line is REQUIRED for every new value and field. You MUST NOT chain everything into a single field unless defined by that field. Every line MUST end either with a carriage return and line feed characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).

+

A separate line is REQUIRED for every field. You MUST NOT chain everything into a single field unless defined by that field. Every line MUST end either with a carriage return and line feed characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).

3.4. Digital signature

@@ -799,12 +799,12 @@

6.3. Intentionally Malformed Files, Resources and Reports

-

It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD make sure that any such code be robust against large and malformed files. ABNF grammar (as defined in Section 5) SHOULD be used as a way to verify these files.

+

It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD make sure that any such code is robust against large and malformed files. ABNF grammar (as defined in Section 5) SHOULD be used as a way to verify these files.

Same concerns apply to any other resources referenced within security.txt files, as well as any security reports received as a result of publishing this file. Such resources and reports may be hostile, malformed or malicious.

6.4. No Implied Permission for Testing

-

The presence of a security.txt file can be interpreted by researchers as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not to publish a security.txt file, can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that organization.

+

The presence of a security.txt file can be interpreted by researchers as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not to publish a security.txt file can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that organization.

Therefore, implementors MUST NOT assume that presence or absence of a “security.txt” file grants or denies permission for security testing. Any such permission MAY be defined in a security or disclosure policy (as per Section 3.5.6) or a new directive (as per Section 4.4).

6.5. Multi-user Environments @@ -813,7 +813,7 @@

6.6. Protecting Data in Transit

-

To protect a “security.txt” file from being tampered in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per [RFC6125]).

+

To protect a “security.txt” file from being tampered with in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per [RFC6125]).

As an additional layer of protection, it is also RECOMMENDED that organizations digitally sign their “security.txt” file with OpenPGP (as per Section 3.4). Also, to protect security reports from being tampered with or observed while in transit, organizations SHOULD specify encryption keys (as per Section 3.5.4) unless HTTPS is being used.

However, the determination of validity of keys being used is out of scope for this specification. Implementors MUST establish other secure means to verify these keys.

diff --git a/draft-foudil-securitytxt.md b/draft-foudil-securitytxt.md index 881de9d..47ea8b9 100644 --- a/draft-foudil-securitytxt.md +++ b/draft-foudil-securitytxt.md @@ -149,7 +149,7 @@ respective field. ## Separate Fields -A separate line is REQUIRED for every new value and field. You MUST +A separate line is REQUIRED for every field. You MUST NOT chain everything into a single field unless defined by that field. Every line MUST end either with a carriage return and line feed characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A). @@ -508,7 +508,7 @@ and are kept secure. It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD make sure that any such code -be robust against large and malformed files. ABNF grammar (as defined in +is robust against large and malformed files. ABNF grammar (as defined in {{abnf}}) SHOULD be used as a way to verify these files. Same concerns apply to any other resources referenced within security.txt @@ -520,7 +520,7 @@ this file. Such resources and reports may be hostile, malformed or malicious. The presence of a security.txt file can be interpreted by researchers as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not -to publish a security.txt file, can be interpreted by the +to publish a security.txt file can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that organization. @@ -539,7 +539,7 @@ the "security.txt" AND "/.well-known/security.txt" names. ## Protecting Data in Transit -To protect a "security.txt" file from being tampered in transit, implementors MUST use +To protect a "security.txt" file from being tampered with in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per {{!RFC6125}}). diff --git a/draft-foudil-securitytxt.txt b/draft-foudil-securitytxt.txt index 3b3ae4c..c47731b 100644 --- a/draft-foudil-securitytxt.txt +++ b/draft-foudil-securitytxt.txt @@ -5,8 +5,8 @@ Network Working Group E. Foudil Internet-Draft Intended status: Informational Y. Shafranovich -Expires: December 6, 2019 Nightwatch Cybersecurity - June 04, 2019 +Expires: December 18, 2019 Nightwatch Cybersecurity + June 16, 2019 A Method for Web Security Policies @@ -36,7 +36,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 6, 2019. + This Internet-Draft will expire on December 18, 2019. Copyright Notice @@ -53,7 +53,7 @@ Copyright Notice -Foudil & Shafranovich Expires December 6, 2019 [Page 1] +Foudil & Shafranovich Expires December 18, 2019 [Page 1] Internet-Draft A Method for Web Security Policies June 2019 @@ -109,7 +109,7 @@ Table of Contents -Foudil & Shafranovich Expires December 6, 2019 [Page 2] +Foudil & Shafranovich Expires December 18, 2019 [Page 2] Internet-Draft A Method for Web Security Policies June 2019 @@ -165,7 +165,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 3] +Foudil & Shafranovich Expires December 18, 2019 [Page 3] Internet-Draft A Method for Web Security Policies June 2019 @@ -221,7 +221,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 4] +Foudil & Shafranovich Expires December 18, 2019 [Page 4] Internet-Draft A Method for Web Security Policies June 2019 @@ -277,18 +277,17 @@ https://[2001:db8:8:4::2]/.well-known/security.txt -Foudil & Shafranovich Expires December 6, 2019 [Page 5] +Foudil & Shafranovich Expires December 18, 2019 [Page 5] Internet-Draft A Method for Web Security Policies June 2019 3.3. Separate Fields - A separate line is REQUIRED for every new value and field. You MUST - NOT chain everything into a single field unless defined by that - field. Every line MUST end either with a carriage return and line - feed characters (CRLF / %x0D %x0A) or just a line feed character (LF - / %x0A). + A separate line is REQUIRED for every field. You MUST NOT chain + everything into a single field unless defined by that field. Every + line MUST end either with a carriage return and line feed characters + (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A). 3.4. Digital signature @@ -333,7 +332,8 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 6] + +Foudil & Shafranovich Expires December 18, 2019 [Page 6] Internet-Draft A Method for Web Security Policies June 2019 @@ -389,7 +389,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 7] +Foudil & Shafranovich Expires December 18, 2019 [Page 7] Internet-Draft A Method for Web Security Policies June 2019 @@ -445,7 +445,7 @@ Encryption: dns:5d2d37ab76d47d36._openpgpkey.example.com?type=OPENPGPKEY -Foudil & Shafranovich Expires December 6, 2019 [Page 8] +Foudil & Shafranovich Expires December 18, 2019 [Page 8] Internet-Draft A Method for Web Security Policies June 2019 @@ -501,7 +501,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 9] +Foudil & Shafranovich Expires December 18, 2019 [Page 9] Internet-Draft A Method for Web Security Policies June 2019 @@ -557,7 +557,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 10] +Foudil & Shafranovich Expires December 18, 2019 [Page 10] Internet-Draft A Method for Web Security Policies June 2019 @@ -613,7 +613,7 @@ uri = -Foudil & Shafranovich Expires December 6, 2019 [Page 11] +Foudil & Shafranovich Expires December 18, 2019 [Page 11] Internet-Draft A Method for Web Security Policies June 2019 @@ -669,7 +669,7 @@ unstructured = -Foudil & Shafranovich Expires December 6, 2019 [Page 12] +Foudil & Shafranovich Expires December 18, 2019 [Page 12] Internet-Draft A Method for Web Security Policies June 2019 @@ -691,7 +691,7 @@ Internet-Draft A Method for Web Security Policies June 2019 It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD - make sure that any such code be robust against large and malformed + make sure that any such code is robust against large and malformed files. ABNF grammar (as defined in Section 5) SHOULD be used as a way to verify these files. @@ -706,7 +706,7 @@ Internet-Draft A Method for Web Security Policies June 2019 as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not to publish a - security.txt file, can be interpreted by the organization operating + security.txt file can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that @@ -725,7 +725,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 13] +Foudil & Shafranovich Expires December 18, 2019 [Page 13] Internet-Draft A Method for Web Security Policies June 2019 @@ -735,7 +735,7 @@ Internet-Draft A Method for Web Security Policies June 2019 6.6. Protecting Data in Transit - To protect a "security.txt" file from being tampered in transit, + To protect a "security.txt" file from being tampered with in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per @@ -781,7 +781,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 14] +Foudil & Shafranovich Expires December 18, 2019 [Page 14] Internet-Draft A Method for Web Security Policies June 2019 @@ -837,7 +837,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 15] +Foudil & Shafranovich Expires December 18, 2019 [Page 15] Internet-Draft A Method for Web Security Policies June 2019 @@ -893,7 +893,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 16] +Foudil & Shafranovich Expires December 18, 2019 [Page 16] Internet-Draft A Method for Web Security Policies June 2019 @@ -949,7 +949,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 17] +Foudil & Shafranovich Expires December 18, 2019 [Page 17] Internet-Draft A Method for Web Security Policies June 2019 @@ -1005,7 +1005,7 @@ Internet-Draft A Method for Web Security Policies June 2019 -Foudil & Shafranovich Expires December 6, 2019 [Page 18] +Foudil & Shafranovich Expires December 18, 2019 [Page 18] Internet-Draft A Method for Web Security Policies June 2019 @@ -1061,7 +1061,7 @@ Appendix A. Note to Readers -Foudil & Shafranovich Expires December 6, 2019 [Page 19] +Foudil & Shafranovich Expires December 18, 2019 [Page 19] Internet-Draft A Method for Web Security Policies June 2019 @@ -1117,7 +1117,7 @@ B.2. Since draft-foudil-securitytxt-01 -Foudil & Shafranovich Expires December 6, 2019 [Page 20] +Foudil & Shafranovich Expires December 18, 2019 [Page 20] Internet-Draft A Method for Web Security Policies June 2019 @@ -1173,7 +1173,7 @@ B.5. Since draft-foudil-securitytxt-04 -Foudil & Shafranovich Expires December 6, 2019 [Page 21] +Foudil & Shafranovich Expires December 18, 2019 [Page 21] Internet-Draft A Method for Web Security Policies June 2019 @@ -1229,4 +1229,4 @@ Authors' Addresses -Foudil & Shafranovich Expires December 6, 2019 [Page 22] +Foudil & Shafranovich Expires December 18, 2019 [Page 22]