XEDIA-SECURITY-MIB
The XEDIA-SECURITY-MIB provides SNMP management objects for enforcing and monitoring access control policies on Xedia hardware, specifically implementing a hierarchical security model that validates object-wide, instantiated, and parent-level permissions before executing security functions.
Imported Objects
Objects
22 total| Object Name |
|---|
xediaSecurityMIBThis module defines objects for management of the 'Security'
mechanism in Xedia devices.
Security Model:
In all cases, a top level, 'object-wide' security check is performed,
followed by the 'instantiated object' (particular instance or row) check,
if specified, followed by the security function (when appropriate),
followed by the required 'parent' security checks, in the same order. MODULE-IDENTITY .1.3.6.1.4.1.838.3.8 |
xsecurityObjects OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.1 |
xsecurityGeneral OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.1.1 |
xsecurityAdminThe administrative status of the 'Security mechanism' in the router.
The value 'enabled(1)' indicates that the appropriate security
checks will be performed on all configured objects. The value
'disabled(2)' indicates that no security checks will be performed
on any objects.rw Enumeration .1.3.6.1.4.1.838.3.8.1.1.1 |
xsecurityParentDepthThe number of 'parent' nodes inwhich the security checks are
performed for any given object. The security checks start at
the endpoint (the actual object requested) and traverse upwards,
checking the immediate parent node, then that parent's parent,
etc., until the maximun number of parents is reached, or there
are no more parents.rw INTEGER .1.3.6.1.4.1.838.3.8.1.1.2 |
xsecurityFunctionIDThe textual string ID used to determine a specific set of
special customer security functions, when appropriate. Only
OS builds containing customized security functions will take
advantage of this object.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.8.1.1.3 |
xsecurityObjectTables OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.1.2 |
xsecurityObjConfTableA list of security object configuration entries. The number
of entries is representative of the number of objects defined
in the supported mib. SEQUENCE OF XsecurityObjConfEntry .1.3.6.1.4.1.838.3.8.1.2.1 |
xsecurityObjConfEntryAn entry containing additional management information
applicable to a particular Rip2 interface. XsecurityObjConfEntry .1.3.6.1.4.1.838.3.8.1.2.1.1 |
xsecurityObjIDThe Object Identifier of a known object, or a particular instance
of the object. Objects can be end nodes, which contain readable
data, or they can be inner nodes which are only used to identify
the end points. The object ID can be secified by using the complete
OID of an object, with the exact OID digits making up the instance
portion of the object when needed. In all cases, an 'end of ID'
marker of decimal '999' will be used to separate the base objectID
from the instance portion of the whole OID.
When '.0' instance information is specified, the 'object-wide' security
levels of the object are modified. But, when specific instance
information is specified, the security levels of a particular instance
are modifed. Then,only requests with exactly matching instance
information are validated against the specified levels.
The '.0' also indicates where the 'base' oid ends and the instance
information (if any) begins. This way, it is possible to identify
high level nodes with specific instances matching lower level nodes.
ie: ifEntry.1
The '999' is necessary since ifEntry.1 looks exactly the same
as ifIndex.
1.3.6.1.2.1.2.2.1 ifEntry
1.3.6.1.2.1.2.2.1.1 ifIndex OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.1.2.1.1.1 |
xsecurityObjNameThe mib name of the specificed object.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.8.1.2.1.1.2 |
xsecurityObjInstanceThe instance portion of the specified object. The
OID digits are represented in a readable string format.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.8.1.2.1.1.3 |
xsecurityObjReadAdminThe 'Read' administrative status of the 'Security mechanism' for
an individual object. The value 'enabled(1)' indicates that the
appropriate security checks will be performed on all access to
the spcified object. The value 'disabled(2)' indicates that
no security checks will be performed for the specified object,
although, all expected 'parent' security checks will still be
performed.rw Enumeration .1.3.6.1.4.1.838.3.8.1.2.1.1.4 |
xsecurityObjWriteAdminThe 'Write' administrative status of the 'Security mechanism' for
an individual object. The value 'enabled(1)' indicates that the
appropriate security checks will be performed on all access to
the spcified object. The value 'disabled(2)' indicates that
no security checks will be performed for the specified object,
although, all expected 'parent' security checks will still be
performed.rw Enumeration .1.3.6.1.4.1.838.3.8.1.2.1.1.5 |
xsecurityObjReadFunctAdminThe 'Read' administrative status of the 'Security Function mechanism'
for an individual object. The value 'enabled(1)' indicates that the
appropriate security functions will be called on all access to
the spcified object. The value 'disabled(2)' indicates that
no security functions will be called for the specified object.rw Enumeration .1.3.6.1.4.1.838.3.8.1.2.1.1.6 |
xsecurityObjWriteFunctAdminThe 'Write' administrative status of the 'Security Function mechanism'
for an individual object. The value 'enabled(1)' indicates that the
appropriate security functions will be called on all access to
the spcified object. The value 'disabled(2)' indicates that
no security functions will be called for the specified object.rw Enumeration .1.3.6.1.4.1.838.3.8.1.2.1.1.7 |
xsecurityObjReadLevelsThe bit mask associated with a particular object for 'reading'
and 'viewing'. The levels of security indicate which community
entries have read access to the variable. The level matches
the index, or entry number of the community table.rw BIT STRING { s10(0), s9(1), s8(2), s7(3), s6(4), s5(5), s4(6), s3(7), s2(8), s1(9) } .1.3.6.1.4.1.838.3.8.1.2.1.1.8 |
xsecurityObjWriteLevelsThe bit mask associated with a particular object for 'writinging'
and 'setting'. The levels of security indicate which community
entries have read access to the variable. The level matches
the index, or entry number of the community table.rw BIT STRING { s10(0), s9(1), s8(2), s7(3), s6(4), s5(5), s4(6), s3(7), s2(8), s1(9) } .1.3.6.1.4.1.838.3.8.1.2.1.1.9 |
xsecurityObjRowStatusThis object is used to add and remove entries from the
table. It is important to note that the '.0' entry, which
represents the 'object level' can not be added or deleted,
they simply always exists. However the 'instanciated' table
rows can be added or deleted as necessary.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.8.1.2.1.1.10 |
xsecurityConformance OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.2 |
xsecurityCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.2.1 |
xsecurityGroups OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.8.2.2 |
More MIBs from Xedia
Browse all XediaMIBs →The XEDIA-SYSTEM-MIB provides SNMP objects to monitor and manage system-level parameters, including hardware status, resource utilization, and operational state, specifically for Xedia embedded networking devices.
The XEDIA-NETWORK-ADDRESS-TRANSLATOR-MIB provides management objects for monitoring and configuring Xedia's proprietary Network Address Translator (NAT) devices, enabling the tracking of translation sessions, address pool utilization, and packet flow statistics between RFC1918 private networks and the public Internet.
The XEDIA-POLICY-MIB enables SNMP-based configuration and monitoring of routing policy definitions, including match conditions, action sets, and policy application states, specifically within Xedia networking hardware. This module provides granular visibility into the operational status and parameter values of traffic steering rules to facilitate automated policy enforcement and troubleshooting.
The XEDIA-IPSEC-MIB enables monitoring and configuration of Xedia IPsec VPN tunnel states, security associations, and cryptographic parameters on Xedia networking hardware. It provides specific objects for tracking tunnel establishment status, packet counters, and IPsec policy enforcement metrics to ensure secure data transmission integrity.
The XEDIA-IP-MIB extends standard IETF IP-MIB functionality to monitor and manage IP-layer parameters, interfaces, and routing statistics specifically within Xedia hardware platforms. This module provides vendor-specific object identifiers for tracking IP traffic counters, interface states, and protocol configurations on Xedia network devices.
The XEDIA-NETWORK-TIME-PROTOCOL-MIB enables monitoring of Xedia's RFC 1305-compliant Network Time Protocol (NTP) implementation to manage UTC synchronization states, server association parameters, and time offset metrics across network hosts.