Linux-related Extensions to NFS version 4.2 Security Labels
draft-cel-nfsv4-linux-seclabel-xtensions-00

Document Type Active Internet-Draft (individual)
Last updated 2018-04-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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 File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                           April 9, 2018
Expires: October 11, 2018

      Linux-related Extensions to NFS version 4.2 Security Labels
              draft-cel-nfsv4-linux-seclabel-xtensions-00

Abstract

   NFS version 4.2 introduces an optional feature known as NFSv4
   Security Labels.  This document extends NFSv4 Security Labels to
   support Linux file capabilities and the Linux Integrity Measurement
   Architecture.

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 October 11, 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 October 11, 2018                [Page 1]
Internet-Draft          Linux Seclabel Extensions             April 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Linux Integrity Measurement Architecture  . . . . . . . .   2
     1.2.  Linux File Capabilities . . . . . . . . . . . . . . . . .   3
     1.3.  NFSv4 Security Labels . . . . . . . . . . . . . . . . . .   4
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Handling File Capabilities on NFS Mounts  . . . . . . . . . .   4
   4.  Handling IMA Metadata on NFS Mounts . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
     5.1.  Protection of File Capability Metadata  . . . . . . . . .   6
     5.2.  Protection of IMA Metadata  . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   In the current document, we define a way to manage both IMA metadata
   and Linux file capabilities on NFS files using existing NFSv4
   Security Label protocol elements.  Before specifying new protocol,
   let's contextualize and define the terminology used in the body of
   this document.

1.1.  Linux Integrity Measurement Architecture

   The Linux Integrity Measurement Architecture (hereafter, IMA)
   provides assurance that the content of a file is unaltered and
   authentic to what was originally written to that file.  In addition,
   an Extended Verification Module (hereafter, EVM) can assure that a
   file's attribute information remains unaltered.

   The goal is to detect when a remote attacker, a local attacker, or
   unintentional software behavior has modified the content or
   attributes of a file.  This is done by cryptographically signing HMAC
   hashes of a file's content and attribute metadata, and then storing
   the signed hashes separately.  These hashes are typically updated
   whenever the file is legitimately modified.

   Integrity verification is not performed by applications or by file
   systems.  Applications are not exposed to the operation of integrity
   verification.  File systems are responsible only for persistent
   storage of file content and signed hashes.  When a file is first
   read, content and hashes are passed to IMA modules for measurement

Lever                   Expires October 11, 2018                [Page 2]
Internet-Draft          Linux Seclabel Extensions             April 2018

   and appraisal.  Application access is denied if the hashes cannot be
Show full document text