Integrity Measurement for Network File System version 4
draft-ietf-nfsv4-integrity-measurement-00

Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2018-05-29
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                            May 29, 2018
Expires: November 30, 2018

        Integrity Measurement for Network File System version 4
               draft-ietf-nfsv4-integrity-measurement-00

Abstract

   This document specifies an OPTIONAL extension to NFS version 4.2 that
   enables Linux Integrity Measurement Architecture metadata (IMA) to be
   conveyed between NFSv4.2 servers and clients.

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 November 30, 2018.

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.

Lever                   Expires November 30, 2018               [Page 1]
Internet-Draft                IMA over NFS                      May 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Extension Considerations . . . . . . . . . . . . . .   3
     3.1.  XDR Extraction  . . . . . . . . . . . . . . . . . . . . .   3
   4.  Managing IMA Metadata on NFS Files  . . . . . . . . . . . . .   4
     4.1.  XDR Definition  . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Protecting File Content . . . . . . . . . . . . . . . . .   6
     4.3.  Protecting File Attributes  . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The Linux Integrity Measurement Architecture (IMA) provides assurance
   that the content of files is unaltered and authentic to what was
   originally written to those files.  In addition, an Extended
   Verification Module (EVM) assures that file attribute information
   remains similarly unaltered.

   The primary goal is to detect when a remote attacker, a local
   attacker, or unintentional software behavior has modified the content
   or attributes of a file either in transit or at rest.  This is done
   by separately storing HMAC hashes [RFC2104] of a file's byte stream
   content and attribute metadata.  These hashes are updated whenever
   the file is legitimately modified.  The hashes themselves can be
   protected by cryptographic signature.

   Subsequent integrity verification is not performed by applications or
   by file systems.  File systems are responsible only for persistent
   storage of file content and hashes.  When a file is read, content,
   attributes, and hashes are passed to IMA and EVM modules for
   measurement and appraisal.  Application access is denied if the
   hashes or their signatures cannot be verified.

   Some files may be immutable, in which case their integrity metadata
   is signed by an RSA public key signature [RFC8017].  Such files can
   be accessed in read-only mode or deleted by an appropriately
   privileged agent, but cannot otherwise be modified.

   Key material used to sign and verify file content and attribute
   metadata must be protected.  A Trusted Platform Module [TPM-SUM] can

Lever                   Expires November 30, 2018               [Page 2]
Internet-Draft                IMA over NFS                      May 2018

Show full document text