Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track January 15, 2019 Expires: July 19, 2019 Login Security Policy Extensions Mapping for the Extensible Provisioning Protocol (EPP) draft-gould-regext-login-security-policy-02 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 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 July 19, 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 (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 Gould Expires July 19, 2019 [Page 1] Internet-Draft loginsec-policy January 2019 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 2.2. Event Types . . . . . . . . . . . . . . . . . . . . . . . 4 2.3. System Object . . . . . . . . . . . . . . . . . . . . . . 4 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 8 3.1.3. EPP Query Command . . . . . . . . . . . . 9 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 9 3.2.1. EPP Command . . . . . . . . . . . . . . . . 9 3.2.2. EPP Command . . . . . . . . . . . . . . . . 9 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 9 3.2.4. EPP Command . . . . . . . . . . . . . . . 9 3.2.5. EPP Command . . . . . . . . . . . . . . . . 9 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Launch Policy Schema . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 12 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 12 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 16 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 16 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This document describes an extension of the Registry Mapping [I-D.gould-carney-regext-registry] to define the server policy of the Login Security EPP extension [I-D.gould-regext-login-security] for a registry system. Gould Expires July 19, 2019 [Page 2] Internet-Draft loginsec-policy January 2019 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.3", 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 [1] 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. Gould Expires July 19, 2019 [Page 3] Internet-Draft loginsec-policy January 2019 2.2. Event Types The 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 element in the Registry Mapping [I-D.gould-carney-regext-registry], is the object that is extended by this extension with the element. The element contains the following child elements: : The login password format policy. The element contains the following child elements: : The login password format regular expression. The regular expression MUST conform to the Perl-compatible Regular Expression (PCRE) [pcre] syntax. Programming languages support different sets of PCRE features, so the server SHOULD define a PCRE that leverages features that are supported by a broad set of client programming languages. : The OPTIONAL human readable description of the login password format policy. The "lang" attribute MAY be present to identify the language of the description if the negotiated value is something other than the default value of "en" (English). Gould Expires July 19, 2019 [Page 4] Internet-Draft loginsec-policy January 2019 : OPTIONAL boolean value that indicates the server supports the element, with the default value of "0" (or "false"). A value of "1" (or "true") means that the server processes the element. A value of "0" (or "false") means that the server ignores the element if passed by the client. : Zero or more elements that defines the policies associated with the supported security events. The required "type" attribute and the OPTIONAL "name" attribute defines the event type, as described in Section 2.2. The element contains the following child elements: : One or two elements that indicate the possible set of event levels ("warning" or "error") the server will return to the client for the event type. : OPTIONAL boolean element that indicates whether the event type includes a element with the default value of "0" (or "false"). : OPTIONAL duration element that the event type must be reset. For example, the password will expire 30 days after being set. : OPTIONAL duration element that indicates how long prior to expiry the server will include a warning event. For example, the server will include a password expiry warning event 15 days prior to expiry. : OPTIONAL indication of what action will occur with an error, including at expiry when is "1" (or "true"). The possible values include: "connect": The client connection will fail. For example, when the client certificate expires, the TLS handshake will fail. "login": The client login will fail. For example, when the new password does not meet the server password complexity requirements or when the password expires, the login will fail. "none": There is no predefined failure action. For example, when the password expires, the server will not fail the login. Gould Expires July 19, 2019 [Page 5] Internet-Draft loginsec-policy January 2019 : OPTIONAL threshold value that triggers a warning event for a specific "stat" event. For example, a "failedLogins" "stat" warning event will occur if the number of failed logins exceeds 100. : OPTIONAL period value that is associated with a warning event for a specific "stat" event. For example, a "failedLogins" "stat" warning event will occur if the number of failed logins exceeds the value over a period of 1 day. Example of a element that defines the password policy and the policy of each of the supported login security events: (?=.*\d) (?=.*[a-zA-Z]) (?=.*[\x21-\x2F\x3A-\x40\x5B-\x60\x7B-\x7E]) (?!^\s+) (?!.*\s+$) (?!.*\s{2,}) ^[\x20-\x7e]{16,128}$ 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. true error login warning error true P90D P15D login warning Gould Expires July 19, 2019 [Page 6] Internet-Draft loginsec-policy January 2019 error true P15D connect warning false warning false warning false 100 P1D warning false 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 [RFC5730] provides three commands to retrieve object information: to determine if an object is known to the server, to retrieve detailed information associated with an object, and to retrieve object transfer status information. 3.1.1. EPP Command This extension does not define any extension of the EPP command or response described in the Registry Mapping. Gould Expires July 19, 2019 [Page 7] Internet-Draft loginsec-policy January 2019 3.1.2. EPP Command This extension does not add any elements to the EPP command described in the Registry Mapping [I-D.gould-carney-regext-registry]. However, additional elements are defined for the response to a query for the registry system attributes. When an command has been processed successfully, the EPP element MUST contain a child elements as described in the Registry Mapping [I-D.gould-carney-regext-registry]. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the system object has data associated with this extension and based on server policy. The element contains the following child elements: : Element that contains the full set of login security policy attributes for the system as defined in Section 2.3. Example response to query for the registry system attributes including the login security policy attributes: S: S: S: S: S: Command completed successfully S: S: S: S: ... S: S: S: S: S: ... S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Gould Expires July 19, 2019 [Page 8] Internet-Draft loginsec-policy January 2019 3.1.3. EPP Query Command Transfer semantics do not directly apply to system objects, so there is no extension defined for the EPP query command. 3.2. EPP Transform Commands EPP provides five commands to transform objects: to create an instance of an object, to delete an instance of an object, to extend the validity period of an object, to manage object sponsorship changes, and to change information associated with an object. 3.2.1. EPP Command This extension does not add any elements to the EPP command or response described in the Registry Mapping. 3.2.2. EPP Command This extension does not add any elements to the EPP command or response described in the Registry Mapping. 3.2.3. EPP Command Renew semantics do not directly apply to system objects, so there is no extension defined for the EPP command. 3.2.4. EPP Command Transfer semantics do not directly apply to system objects, so there is no extension defined for the EPP command. 3.2.5. EPP Command This extension does not add any elements to the EPP command or 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. Gould Expires July 19, 2019 [Page 9] Internet-Draft loginsec-policy January 2019 4.1. Launch Policy Schema BEGIN Extensible Provisioning Protocol v1.0 Login Security Policy Extension Schema. Gould Expires July 19, 2019 [Page 10] Internet-Draft loginsec-policy January 2019 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: URI: urn:ietf:params:xml:ns:epp:loginSecPolicy-0.3 Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. Registration request for the login security policy XML schema: URI: urn:ietf:params:xml:schema:epp:loginSecPolicy-0.3 Registrant Contact: IESG XML: See the "Formal Syntax" section of this document. 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: Gould Expires July 19, 2019 [Page 12] Internet-Draft loginsec-policy January 2019 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, TLDs: Any IPR Disclosure: None Status: Active Notes: None 6. Implementation Status Note to RFC Editor: Please remove this section and the reference to RFC 7942 [RFC7942] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942 [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". 6.1. Verisign EPP SDK Organization: Verisign Inc. Name: Verisign EPP SDK Gould Expires July 19, 2019 [Page 13] Internet-Draft loginsec-policy January 2019 Description: The Verisign EPP SDK includes both a full client implementation and a full server stub implementation of draft-gould- regext-login-security-policy. Level of maturity: Development Coverage: All aspects of the protocol are implemented. Licensing: GNU Lesser General Public License Contact: jgould@verisign.com URL: https://www.verisign.com/en_US/channel-resources/domain- registry-products/epp-sdks 7. Security Considerations The mapping extensions described in this document provide additional security services beyond those described by EPP [RFC5730] 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]. 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 Gould Expires July 19, 2019 [Page 14] Internet-Draft loginsec-policy January 2019 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)", draft-gould-carney-regext-registry-04 (work in progress), October 2018. [I-D.gould-regext-login-security] Gould, J. and M. Pozun, "Login Security Extension for the Extensible Provisioning Protocol (EPP)", draft-gould- regext-login-security-02 (work in progress), 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, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . 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, . Gould Expires July 19, 2019 [Page 15] Internet-Draft loginsec-policy January 2019 9.3. URIs [1] http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ [2] https://pages.nist.gov/800-63-3/sp800-63b.html Appendix A. Change History A.1. Change from 00 to 01 1. Changed the element to the element, to be more generic to identify the action taken for an error level event for any event type. The XML namespace was changed to "urn:ietf:params:xml:ns:epp:loginSecPolicy-0.3" based on the change to the XML schema. 2. Updated the Implementation Status section. A.2. Change from 01 to 02 1. Fix the inconsistent case for newPW, that required a global change in the draft text and an update to the XML schema to "urn:ietf:params:xml:ns:epp:loginSecPolicy-0.3". Author's Address James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisign.com Gould Expires July 19, 2019 [Page 16]