View-based Access Control Model
E766584
The View-based Access Control Model (VACM) is a security framework for SNMP that controls which portions of management data each user or group is allowed to access based on configurable views.
All labels observed (1)
| Label | Occurrences |
|---|---|
| View-based Access Control Model canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8891180 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: View-based Access Control Model Context triple: [RFC 2575, defines, View-based Access Control Model]
-
A.
User-based Security Model
The User-based Security Model is a framework for providing authentication, privacy, and access control in SNMPv3 by defining security based on individual user identities and associated cryptographic keys.
-
B.
Access Control Model
An Access Control Model is a framework that specifies how permissions are granted, restricted, and enforced to regulate which users or systems can access particular resources or operations.
-
C.
Cross-Enterprise User Assertion
Cross-Enterprise User Assertion is a healthcare IT standard that enables secure, interoperable sharing of user identity and authentication information across different organizations and systems.
-
D.
RSA Identity Governance and Lifecycle
RSA Identity Governance and Lifecycle is an enterprise solution for managing user access, enforcing security policies, and ensuring compliance across identities and applications.
-
E.
Binary Authorization
Binary Authorization is a Google Cloud security service that enforces deploy-time image verification and policy controls to ensure only trusted container images are run in your environments.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: View-based Access Control Model Target entity description: The View-based Access Control Model (VACM) is a security framework for SNMP that controls which portions of management data each user or group is allowed to access based on configurable views.
-
A.
User-based Security Model
The User-based Security Model is a framework for providing authentication, privacy, and access control in SNMPv3 by defining security based on individual user identities and associated cryptographic keys.
-
B.
Access Control Model
An Access Control Model is a framework that specifies how permissions are granted, restricted, and enforced to regulate which users or systems can access particular resources or operations.
-
C.
Cross-Enterprise User Assertion
Cross-Enterprise User Assertion is a healthcare IT standard that enables secure, interoperable sharing of user identity and authentication information across different organizations and systems.
-
D.
RSA Identity Governance and Lifecycle
RSA Identity Governance and Lifecycle is an enterprise solution for managing user access, enforcing security policies, and ensuring compliance across identities and applications.
-
E.
Binary Authorization
Binary Authorization is a Google Cloud security service that enforces deploy-time image verification and policy controls to ensure only trusted container images are run in your environments.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
SNMP security model ⓘ access control model ⓘ |
| abbreviation | VACM ⓘ |
| appliesTo |
SNMP agents
ⓘ
SNMP managers ⓘ |
| area | network management security ⓘ |
| authorizes | SNMP operations based on group and view ⓘ |
| basedOn | views of the MIB tree ⓘ |
| compatibleWith |
SNMPv3 USM
NERFINISHED
ⓘ
User-based Security Model NERFINISHED ⓘ |
| controls |
notification access to MIB objects
ⓘ
read access to MIB objects ⓘ write access to MIB objects ⓘ |
| controlsAccessTo |
MIB objects
ⓘ
SNMP management information ⓘ |
| definedInRFC | RFC 2575 NERFINISHED ⓘ |
| designedFor | fine-grained access control ⓘ |
| fullName | View-based Access Control Model NERFINISHED ⓘ |
| granularity | OID subtree level ⓘ |
| hasComponent |
vacmAccessTable
ⓘ
vacmContextTable ⓘ vacmSecurityToGroupTable ⓘ vacmViewTreeFamilyTable ⓘ |
| maps | securityName to groupName ⓘ |
| organization | IETF NERFINISHED ⓘ |
| partOf | SNMP framework ⓘ |
| replaces | SNMPv2 Party-based Security Model NERFINISHED ⓘ |
| scope | agent-side access control ⓘ |
| supportsOperation |
SNMP GET
NERFINISHED
ⓘ
SNMP GETBULK NERFINISHED ⓘ SNMP GETNEXT NERFINISHED ⓘ SNMP INFORM NERFINISHED ⓘ SNMP SET ⓘ SNMP TRAP NERFINISHED ⓘ |
| usedBy |
SNMPv1
NERFINISHED
ⓘ
SNMPv2c NERFINISHED ⓘ SNMPv3 NERFINISHED ⓘ |
| usesConcept |
MIB view
NERFINISHED
ⓘ
context ⓘ groupName ⓘ notifyView ⓘ readView ⓘ securityLevel ⓘ securityModel ⓘ securityName ⓘ view mask ⓘ view subtree ⓘ writeView ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: View-based Access Control Model Description of subject: The View-based Access Control Model (VACM) is a security framework for SNMP that controls which portions of management data each user or group is allowed to access based on configurable views.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.