A Method for Web Security Policies
draft-foudil-securitytxt-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Edwin Foudil
,
Yakov Shafranovich
|
|
Last updated |
|
2017-12-27
|
|
Stream |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group E. Foudil
Internet-Draft
Intended status: Informational Y. Shafranovich
Expires: June 30, 2018 Nightwatch Cybersecurity
December 27, 2017
A Method for Web Security Policies
draft-foudil-securitytxt-02
Abstract
When security risks in web services are discovered by independent
security researchers who understand the severity of the risk, they
often lack the channels to properly disclose them. As a result,
security issues may be left unreported. security.txt defines a
standard to help organizations define the process for security
researchers to securely disclose security vulnerabilities.
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 http://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 June 30, 2018.
Copyright Notice
Copyright (c) 2017 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
(http://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
Foudil & Shafranovich Expires June 30, 2018 [Page 1]
Internet-Draft A Method for Web Security Policies December 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Specification . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Comments . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Separate Fields . . . . . . . . . . . . . . . . . . . . . 4
2.3. Contact: . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Encryption: . . . . . . . . . . . . . . . . . . . . . . . 4
2.5. Signature: . . . . . . . . . . . . . . . . . . . . . . . 5
2.6. Policy: . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.7. Acknowledgement: . . . . . . . . . . . . . . . . . . . . 5
2.8. Example . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Location of the security.txt file . . . . . . . . . . . . . . 6
3.1. Web-based services . . . . . . . . . . . . . . . . . . . 6
3.2. File systems . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Internal hosts . . . . . . . . . . . . . . . . . . . . . 7
3.4. Extensibility . . . . . . . . . . . . . . . . . . . . . . 7
4. File Format Description . . . . . . . . . . . . . . . . . . . 7
5. Security considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6.1. Well-Known URIs registry . . . . . . . . . . . . . . . . 9
6.2. Registry for security.txt Header Fields . . . . . . . . . 9
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 12
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Appendix A. Note to Readers . . . . . . . . . . . . . . . . . . 12
Appendix B. Document History . . . . . . . . . . . . . . . . . . 12
B.1. Since draft-foudil-securitytxt-00 . . . . . . . . . . . . 12
B.2. Since draft-foudil-securitytxt-01 . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
1.1. Motivation
Many security researchers encounter situations where they are unable
to responsibly disclose security issues to companies because there is
no course of action laid out. security.txt is designed to help assist
Show full document text