Security Needs for the NFSv4 Protocols
draft-dnoveck-nfsv4-security-needs-00

Document Type Active Internet-Draft (individual)
Author David Noveck 
Last updated 2020-06-18
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
NFSv4                                                          D. Noveck
Internet-Draft                                                    NetApp
Intended status: Informational                             June 18, 2020
Expires: December 20, 2020

                 Security Needs for the NFSv4 Protocols
                 draft-dnoveck-nfsv4-security-needs-00

Abstract

   This document discusses the existing inadequacies in the handling of
   security issues within the NFSv4 protocols and the steps that might
   be taken to correct the situation, including the preparation of new
   standards-track documents updating existing ones.  Because the
   security approach has been and should remain the same for all minor
   versions, it is expected that security for all the NFSv4 protocols
   will be addressed together in a single NFSv4-wide standards-track
   document.

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 20, 2020.

Copyright Notice

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

Noveck                  Expires December 20, 2020               [Page 1]
Internet-Draft            NFSv4 Security Needs                 June 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Requirements Language Usage in this Document  . . . . . . . .   4
   4.  Situation to be Addressed . . . . . . . . . . . . . . . . . .   5
     4.1.  NFSv4 Use Environments to be Addressed  . . . . . . . . .   5
     4.2.  Emergence and Correction of Security Issues . . . . . . .   7
   5.  Major Problems to Address . . . . . . . . . . . . . . . . . .   9
     5.1.  Problems with Security Presentation/Organization  . . . .  10
       5.1.1.  Problems with Presentation of Security Architecture .  10
       5.1.2.  Problems with Security Evaluation . . . . . . . . . .  12
     5.2.  Problems with treatment of AUTH_SYS . . . . . . . . . . .  12
     5.3.  Problems with Confidentiality . . . . . . . . . . . . . .  16
   6.  Framework for Correcting Problems . . . . . . . . . . . . . .  19
     6.1.  Correcting Problems with Regard to Threat Analyses  . . .  19
     6.2.  Correcting Problems with Regard to Use of Normative Terms  20
   7.  Opportunities for Improvement Provided by Recent Work within
       the RPC Layer . . . . . . . . . . . . . . . . . . . . . . . .  21
     7.1.  Opportunities for Improvement in Encryption . . . . . . .  21
     7.2.  Opportunities for Improvement in Authentication . . . . .  22
     7.3.  Opportunities for Improvement when Using RDMA Transports   22
   8.  Issues that Need to be Addressed  . . . . . . . . . . . . . .  23
     8.1.  Threat  Analysis Goals  . . . . . . . . . . . . . . . . .  23
       8.1.1.  Background  . . . . . . . . . . . . . . . . . . . . .  23
       8.1.2.  Issues to be Addressed  . . . . . . . . . . . . . . .  25
     8.2.  NFSv4 Extension Policies  . . . . . . . . . . . . . . . .  25
       8.2.1.  Background  . . . . . . . . . . . . . . . . . . . . .  25
       8.2.2.  Addressing Extension Issues . . . . . . . . . . . . .  26
     8.3.  TLS Encryption Policies . . . . . . . . . . . . . . . . .  27
       8.3.1.  Background  . . . . . . . . . . . . . . . . . . . . .  27
       8.3.2.  Issues to Address . . . . . . . . . . . . . . . . . .  28
     8.4.  Handling of AUTH_SYS  . . . . . . . . . . . . . . . . . .  31
       8.4.1.  Historical Background . . . . . . . . . . . . . . . .  31
       8.4.2.  Background for Existing AUTH_SYS in NFSv4 . . . . . .  32
       8.4.3.  Core Issue to Resolve for AUTH_SYS  . . . . . . . . .  33
       8.4.4.  Need to Better Document and Explain Issues with
Show full document text