RE: Updating the MIB security guidelines

["C. M. Heard" <heard@pobox.com>]

On Sat, 28 Dec 2002, Wijnen, Bert (Bert) wrote:
[ ... ]
> > -- for all MIBs you must evaluate
> > 
> >    Some of the readable objects in this MIB module (including objects
> >    with a MAX-ACCESS clause of accessible-for-notify) may be considered
> 
> or maybe even better:
> 
>      Some of the readable objects in this MIB module (that is all objects
>      with a MAX-ACCESS other than not-accessible) may be considered

I recommend changing "that is all objects with to "i.e., objects with ..."
since the "all" might be read as "all ... may be considered" which is not 
what we mean.  The result would be:

       Some of the readable objects in this MIB module (i.e., objects
       with a MAX-ACCESS other than not-accessible) may be considered

> >    sensitive or vulnerable in some network environments.  It is thus
> >    important to control even GET and/or NOTIFY access to these objects
> >    and possibly to even encrypt the values of these objects when
> >    sending them over the network via SNMP.  These are the tables and
> >    objects and their sensitivity/vulnerability:
> > 
> >     <list the tables and objects and state why they are sensitive>

//cmh