VACM
VACM is used to control access to managed objects in a MIB or MIBs. This is where the Access Control Subsystem comes into play.
The Basics
The msgFlags, msgSecurityModel, and scopedPDU fields are used by VACM for message access. Each parameter is used to determine access to managed objects. An error is returned to the sender if access is not allowed for the request type. VACM makes use of four tables for different aspects of access control. We will discuss these tables next.
Context Table
The vacmContextTable is a collection of managed objects that have access constraints which are associated with a context name. The vacmContextTable stores all available contexts. The table is indexed by a contextName, and each row in this table contains:
-
vacmContextName A textual name for the context
Security to Group Table
The vacmSecurityToGroupTable is used to store group information. A group is made up of zero or more securityModel and securityName combinations. This combination defines what managed objects can be accessed. The table itself is indexed by a securityModel and securityName. The table contains rows made up of the following columns:
-
vacmSecurityModel The security model in use—e.g., USM.
-
vacmSecurityName In the case of the USM,
securityNameanduserNameare identical.-
vacmGroupName A textual name for the group to which this table entry belongs.
Access Table
The vacmAccessTable is used to store the access rights defined for groups. This table is indexed by a groupName, contextPrefix ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access