A Method for Web Security Policies

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Edwin Foudil 
Last updated 2017-09-19 (latest revision 2017-09-10)
Stream (None)
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
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
Intended status: Informational                        September 10, 2017
Expires: February 20, 2018

                   A Method for Web Security Policies


   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 February 20, 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                  Expires February 20, 2018               [Page 1]
Internet-Draft               INTERNET-DRAFT                  August 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

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 in this process by making it easier for companies to designate
   the preferred steps for researchers to take when trying to reach out.

1.2.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119

2.  The Specification

   Security.txt is a text file located in the website's top-level
   directory.  This text file contains 4 directives with different
   values.  The "directive" is the first part of a field all the way up
   to the colon ("In-scope:").  Directives are case-insensitive.  The
   "value" comes after the directive ("example.com").  A "field" always
   consists of a directive and a value ("In-scope: example.com").  A
   security.txt file can have an unlimited number of fields.  It is
   important to note that you need a separate line for every field.  One
   MUST NOT chain multiple values for a single directive.  Everything
   MUST be in a separate field.

   A security.txt file only applies to the application it is located in.


   Comments can be added using the # symbol:

   # This is a comment.

   You MAY use one or more comments as descriptive text immediately
   before the field.  Parsers can then associate the comments with the
   respective field.

2.2.  Separate Fields

   A separate line is required for every new value and field.  You MUST
   NOT chain everything in to a single field.  Every line must end with
   a line feed character (%x0A).

Foudil                  Expires February 20, 2018               [Page 2]
Internet-Draft               INTERNET-DRAFT                  August 2017

2.3.  Contact:

   Add an address that researchers MAY use for reporting security
   issues.  The value can be an email address, a phone number and/or a
   security page with more information.  The "Contact:" directive MUST
   always be present in a security.txt file.

   Contact: security@example.com
   Contact: +1-201-555-0123
   Contact: https://example.com/security

2.4.  Encryption:

   This directive allows you to add your key for encrypted
   communication.  You MUST NOT directly add your PGP key.  The value
   MUST be a link to a page which contains your key.  Keys SHOULD be
   loaded over HTTPS.

   Encryption: https://example.com/pgp-key.txt
Show full document text