Network Working Group J. Gould
Internet-Draft VeriSign, Inc.
Intended status: Standards Track September 12, 2018
Expires: March 16, 2019

Login Security Policy Extensions Mapping for the Extensible Provisioning Protocol (EPP)
draft-gould-regext-login-security-policy-00

Abstract

This document describes an Extensible Provisioning Protocol (EPP) extension of the Registry Mapping to define the server policy of the Login Security EPP extension. The server policy of the Login Security EPP extension includes the MAYs, SHOULDs, and options implemented by the server.

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 March 16, 2019.

Copyright Notice

Copyright (c) 2018 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.

Table of Contents

1. Introduction

This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This document describes an extension of the Registry Mapping to define the server policy of the Login Security EPP extension for a registry system.

1.1. Conventions Used in This Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation.

In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol.

The XML namespace prefix "loginSecPolicy" is used for the namespace "urn:ietf:params:xml:ns:epp:loginSecPolicy-0.1", but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

The XML namespace prefix "loginSec" is used for the namespace "urn:ietf:params:xml:ns:loginSec-0.1", as defined in [I-D.gould-regext-login-security], but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

2. Object Attributes

An EPP login security policy has attributes and associated values that may be viewed and modified by the sponsoring client or the server. This section describes each attribute type in detail. The formal syntax for the attribute values described here can be found in the "Formal Syntax" section of this document and in the appropriate normative references.

2.1. Dates and Times

Date and time attribute values MUST be represented in Universal Coordinated Time (UTC) using the Gregorian calendar. The extended date-time form using upper case "T" and "Z" characters defined in XML Schema Part 2 MUST be used to represent date-time values, as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters.

2.2. Event Types

The <loginSecPolicy:event> element has a REQUIRED "type" attribute and an OPTIONAL "name" attribute that defines the security event type. The "name" attribute is used to define a sub-type or the type name when the "type" attribute is "custom". The enumerated list of "type" values include:

"password":
Identifies a password expiry event policy.
"certificate":
Identifies a client certificate expiry event policy.
"cipher":
Identifies an insecure or deprecated TLS cipher suite event policy.
"tlsProtocol":
Identifies an insecure or deprecated TLS protocol event policy.
"newPw":
Identifies the new password complexity requirements event policy.
"stat":
Identifies the login security statistical warning event policy. The "name" attribute defines the statistic.
"custom":
Identifies a custom event type that MUST set the "name" attribute with the custom event type name.

2.3. System Object

The System object, represented by the <registry:system> element in the Registry Mapping, is the object that is extended by this extension with the <loginSecPolicy:system> element. The <loginSecPolicy:system> element contains the following child elements:

Example of a <loginSecPolicy:system> element that defines the password policy and the policy of each of the supported login security events:

<loginSecPolicy:system>
  <loginSecPolicy:pw>
  <loginSecPolicy:expression>
    (?=.*\d)
    (?=.*[a-zA-Z])
    (?=.*[\x21-\x2F\x3A-\x40\x5B-\x60\x7B-\x7E])
    (?!^\s+)
    (?!.*\s+$)
    (?!.*\s{2,})
    ^[\x20-\x7e]{16,128}$
  </loginSecPolicy:expression>
  <loginSecPolicy:description>
    16 to 128 printable characters (alphanumeric, space, and 
    special characters) with at least one number, letter, and 
    special character, with no leading or trailing whitespace, 
    and with no consecutive spaces.
  </loginSecPolicy:description>
  </loginSecPolicy:pw>
  <loginSecPolicy:userAgentSupport>true
  </loginSecPolicy:userAgentSupport>
  <loginSecPolicy:event type="password">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:level>error</loginSecPolicy:level>
    <loginSecPolicy:exDate>true</loginSecPolicy:exDate>
    <loginSecPolicy:exPeriod>P90D</loginSecPolicy:exPeriod>
    <loginSecPolicy:warningPeriod>P15D</loginSecPolicy:warningPeriod>
    <loginSecPolicy:exError>login</loginSecPolicy:exError>
  </loginSecPolicy:event>
  <loginSecPolicy:event 
    type="certificate">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:level>error</loginSecPolicy:level>
    <loginSecPolicy:exDate>true</loginSecPolicy:exDate>
    <loginSecPolicy:warningPeriod>P15D</loginSecPolicy:warningPeriod>
    <loginSecPolicy:exError>connect</loginSecPolicy:exError>
  </loginSecPolicy:event>
  <loginSecPolicy:event 
    type="cipher">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:exDate>false</loginSecPolicy:exDate>
  </loginSecPolicy:event>
  <loginSecPolicy:event 
    type="tlsProtocol">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:exDate>false</loginSecPolicy:exDate>
  </loginSecPolicy:event>
  <loginSecPolicy:event 
    type="stat" name="failedLogins">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:exDate>false</loginSecPolicy:exDate>
    <loginSecPolicy:threshold>100</loginSecPolicy:threshold>
    <loginSecPolicy:period>P1D</loginSecPolicy:period>
  </loginSecPolicy:event>
  <loginSecPolicy:event 
    type="custom" name="myCustomEvent">
    <loginSecPolicy:level>warning</loginSecPolicy:level>
    <loginSecPolicy:exDate>false</loginSecPolicy:exDate>
  </loginSecPolicy:event>    
</loginSecPolicy:system>

3. EPP Command Mapping

A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing login security policy via EPP.

3.1. EPP Query Commands

EPP provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information.

3.1.1. EPP <check> Command

This extension does not define any extension of the EPP <check> command or response described in the Registry Mapping.

3.1.2. EPP <info> Command

This extension does not add any elements to the EPP <info> command described in the Registry Mapping. However, additional elements are defined for the <info> response to a query for the registry system attributes.

When an <info> command has been processed successfully, the EPP <resData> element MUST contain a child elements as described in the Registry Mapping. In addition, the EPP <extension> element SHOULD contain a child <lp:infData> element that identifies the extension namespace if the system object has data associated with this extension and based on server policy. The <loginSecPolicy:infData> element contains the following child elements:

<lp:system>:
Element that contains the full set of login security policy attributes for the system as defined in Section 2.3.

Example <info> response to query for the registry system attributes including the login security policy attributes:

S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S:  <response>
S:    <result code="1000">
S:      <msg>Command completed successfully</msg>
S:    </result>
S:    <resData>
S:      <registry:infData
S:        xmlns:registry="urn:ietf:params:xml:ns:registry-0.1">
S:      ...
S:      </registry:infData>
S:    </resData>
S:    <extension>
S:      <loginSecPolicy:infData 
S:        xmlns:loginSecPolicy=
S:          "urn:ietf:params:xml:ns:epp:loginSecPolicy-0.1">
S:      ...
S:      </loginSecPolicy:infData>
S:    </extension>
S:    <trID>
S:      <clTRID>ABC-12345</clTRID>
S:      <svTRID>54322-XYZ</svTRID>
S:    </trID>
S:  </response>
S:</epp>

3.1.3. EPP <transfer> Query Command

Transfer semantics do not directly apply to system objects, so there is no extension defined for the EPP <transfer> query command.

3.2. EPP Transform Commands

EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.

3.2.1. EPP <create> Command

This extension does not add any elements to the EPP <create> command or <create> response described in the Registry Mapping.

3.2.2. EPP <delete> Command

This extension does not add any elements to the EPP <delete> command or <delete> response described in the Registry Mapping.

3.2.3. EPP <renew> Command

Renew semantics do not directly apply to system objects, so there is no extension defined for the EPP <renew> command.

3.2.4. EPP <transfer> Command

Transfer semantics do not directly apply to system objects, so there is no extension defined for the EPP <transfer> command.

3.2.5. EPP <update> Command

This extension does not add any elements to the EPP <update> command or <update> response described in the Registry Mapping.

4. Formal Syntax

One schema presented here is the EPP Login Security Policy Schema.

The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.

4.1. Launch Policy Schema

BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" 
  xmlns:loginSecPolicy=
    "urn:ietf:params:xml:ns:epp:loginSecPolicy-0.1" 
  targetNamespace="urn:ietf:params:xml:ns:epp:loginSecPolicy-0.1" 
  elementFormDefault="qualified">
  <annotation>
    <documentation>Extensible Provisioning Protocol v1.0
       Login Security Policy Extension Schema.</documentation>
  </annotation>
  <!--
    Child response elements.
  -->
  <element name="infData" 
    type="loginSecPolicy:systemContainerType" />
  <!--
    Container for system login security policy
  -->
  <complexType name="systemContainerType">
    <sequence>
      <element name="system" 
        type="loginSecPolicy:systemType" />
    </sequence>
  </complexType>
  <!-- 
    System login security policies
  -->
  <complexType name="systemType">
    <sequence>
      <element name="pw" 
        type="loginSecPolicy:pwType" />
      <element name="userAgentSupport" 
        type="boolean" minOccurs="0" default="false" />
      <element name="event" 
        type="loginSecPolicy:eventType" 
        minOccurs="0" maxOccurs="unbounded" />
    </sequence>
  </complexType>
  <complexType name="pwType">
    <sequence>
      <element name="expression" 
        type="string" />
      <element name="description" minOccurs="0">
        <complexType>
          <simpleContent>
            <extension base="normalizedString">
              <attribute name="lang" 
                type="language" default="en" />
            </extension>
          </simpleContent>
        </complexType>
      </element>
    </sequence>
  </complexType>
  <complexType name="eventType">
    <sequence>
      <element name="level" 
        type="loginSecPolicy:levelEnum" 
        minOccurs="1" maxOccurs="2" />
      <element name="exDate" 
        type="boolean" minOccurs="0" default="false" />
      <element name="exPeriod" 
        type="duration" minOccurs="0" />
      <element name="warningPeriod" 
        type="duration" minOccurs="0" />
      <element name="exError" 
        type="loginSecPolicy:exErrorType" minOccurs="0" />
      <element name="threshold" 
        type="integer" minOccurs="0" />
      <element name="period" 
        type="duration" minOccurs="0" />
    </sequence>
    <attribute name="type" 
      type="loginSecPolicy:typeEnum" use="required" />
    <attribute name="name" 
      type="token" />
  </complexType>
  <!--
    Enumerated list of event types, with extensibility via "custom".
    -->
  <simpleType name="typeEnum">
    <restriction base="token">
      <enumeration value="password" />
      <enumeration value="certificate" />
      <enumeration value="cipher" />
      <enumeration value="tlsProtocol" />
      <enumeration value="newPw" />
      <enumeration value="stat" />
      <enumeration value="custom" />
    </restriction>
  </simpleType>
  <!--
    Enumerated list of levels.
    -->
  <simpleType name="levelEnum">
    <restriction base="token">
      <enumeration value="warning" />
      <enumeration value="error" />
    </restriction>
  </simpleType>
  <!--
    Enumerated list of event expiration error types
    -->
  <simpleType name="exErrorType">
    <restriction base="token">
      <enumeration value="connect" />
      <enumeration value="login" />
      <enumeration value="none" />
    </restriction>
  </simpleType>
  <!--
End of schema.
-->
</schema>
END

5. IANA Considerations

5.1. XML Namespace

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688].

Registration request for the login security policy namespace:

Registration request for the login security policy XML schema:

5.2. EPP Extension Registry

The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in [RFC7451]. The details of the registration are as follows:

Name of Extension: "Login Security Policy Extensions Mapping for the Extensible Provisioning Protocol (EPP)"

Document status: Standards Track

Reference: (insert reference to RFC version of this document)

Registrant Name and Email Address: IESG, <iesg@ietf.org>

TLDs: Any

IPR Disclosure: None

Status: Active

Notes: None

6. Implementation Status

TBD

7. Security Considerations

The mapping extensions described in this document provide additional security services beyond those described by EPP and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.

This mapping does define the login security policy of the server, where there are security considerations with defining the policy, which include:

  1. The server SHOULD follow login password complexity best practices, such as the NIST Special Publication 800-63B.
  2. The server MAY have a login password expiry that requires the client to regularly change the login password.
  3. The server SHOULD inform the client of the expiry of the login password.
  4. The server MUST store the login password at rest securely, such as hashing or encrypting the login password.
  5. The server SHOULD deprecate and eliminate insecure ciphers and protocols.
  6. The server SHOULD inform the client of the use of insecure ciphers and protocols.
  7. The server SHOULD inform the client of an expiring client certificate.

8. Acknowledgements

TBD

9. References

9.1. Normative References

[I-D.gould-carney-regext-registry] Gould, J., Jia, L., Carney, R. and J. Kolker, "Registry Mapping for the Extensible Provisioning Protocol (EPP)", Internet-Draft draft-gould-carney-regext-registry-03, August 2018.
[I-D.gould-regext-login-security] Gould, J. and M. Pozun, "Login Security Extension for the Extensible Provisioning Protocol (EPP)", Internet-Draft draft-gould-regext-login-security-02, August 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009.

9.2. Informative References

[pcre] Hazel, P., "Perl-compatible Regular Expressions (PCRE)", October 2016.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017.

Appendix A. Change History

Author's Address

James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US EMail: jgould@verisign.com URI: http://www.verisigninc.com