View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
RFC 2575

Document Type RFC - Draft Standard (April 1999; No errata)
Obsoleted by RFC 3415
Obsoletes RFC 2275
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2575 (Draft Standard)
Consensus Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          B. Wijnen
Request for Comments: 2575                     IBM T. J. Watson Research
Obsoletes: 2275                                               R. Presuhn
Category: Standards Track                             BMC Software, Inc.
                                                           K. McCloghrie
                                                     Cisco Systems, Inc.
                                                              April 1999

             View-based Access Control Model (VACM) for the
               Simple Network Management Protocol (SNMP)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

Abstract

   This document describes the View-based Access Control Model for use
   in the SNMP architecture [RFC2571].  It defines the Elements of
   Procedure for controlling access to management information.  This
   document also includes a MIB for remotely managing the configuration
   parameters for the View-based Access Control Model.

Table of Contents

   1.  Introduction                                             2
   1.2.  Access Control                                         3
   1.3.  Local Configuration Datastore                          3
   2.  Elements of the Model                                    3
   2.1.  Groups                                                 3
   2.2.  securityLevel                                          4
   2.3.  Contexts                                               4
   2.4.  MIB Views and View Families                            4
   2.4.1.  View Subtree                                         5
   2.4.2.  ViewTreeFamily                                       5
   2.5.  Access Policy                                          6
   3.  Elements of Procedure                                    6
   3.1.  Overview  of isAccessAllowed Process                   8
   3.2.  Processing the isAccessAllowed Service Request         9

Wijnen, et al.              Standards Track                     [Page 1]
RFC 2575                     VACM for SNMP                    April 1999

   4.  Definitions                                             10
   5.  Intellectual Property                                   27
   6.  Acknowledgements                                        28
   7.  Security Considerations                                 29
   7.1.  Recommended Practices                                 29
   7.2.  Defining Groups                                       30
   7.3.  Conformance                                           30
   7.4.  Access to the SNMP-VIEW-BASED-ACM-MIB                 30
   8.  References                                              31
   9.  Editors' Addresses                                      32
   A.1.  Installation Parameters                               33
   B.  Change Log                                              37
   C.  Full Copyright Statement                                38

1.  Introduction

   The Architecture for describing Internet Management Frameworks
   [RFC2571] describes that an SNMP engine is composed of:

     1) a Dispatcher
     2) a Message Processing Subsystem,
     3) a Security Subsystem, and
     4) an Access Control Subsystem.

   Applications make use of the services of these subsystems.

   It is important to understand the SNMP architecture and its
   terminology to understand where the View-based Access Control Model
   described in this document fits into the architecture and interacts
   with other subsystems within the architecture.  The reader is
   expected to have read and understood the description and terminology
   of the SNMP architecture, as defined in [RFC2571].

   The Access Control Subsystem of an SNMP engine has the responsibility
   for checking whether a specific type of access (read, write, notify)
   to a particular object (instance) is allowed.

   It is the purpose of this document to define a specific model of the
   Access Control Subsystem, designated the View-based Access Control
   Model. Note that this is not necessarily the only Access Control
   Model.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].
Show full document text