TSM-MIB
AI MIB Summary
The TSM-MIB module facilitates the monitoring and management of SSH Security Model parameters, specifically tracking session states, authentication attempts, and cryptographic negotiation metrics across network devices supporting the SSHv2 protocol. It enables administrators to audit access control events and detect anomalies within secure shell connections by exposing standardized SNMP objects for session counts, failed login counters, and protocol version statistics.
The Secure Shell Security Model MIB
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices.
Main OID:
tsmMIB.1.3.6.1.4.1.3727.20.20.3.1.xxxx
14
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
14 total| Object Name |
|---|
tsmMIBThe Secure Shell Security Model MIB
Copyright (C) The Internet Society (2006). This
version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.4.1.3727.20.20.3.1.xxxx |
tsmNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.0 |
tsmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1 |
tsmStats OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.1 |
tsmUser OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2 |
tsmUserSpinLockAn advisory lock used to allow several cooperating
Command Generator Applications to coordinate their
use of facilities to alter the tsmUserTable.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.1 |
tsmUserTableThe table of users configured in the SNMP engine's
Local Configuration Datastore (LCD).
To create a new user (i.e., to instantiate a new
conceptual row in this table), it is recommended to
follow this procedure:
1) GET(tsmUserSpinLock.0) and save in sValue.
2) SET(tsmUserSpinLock.0=sValue,
tsmUserStatus=createAndWait)
Finally, activate the new user:
3) SET(tsmUserStatus=active)
The new user should now be available and ready to be
used for SNMPv3 communication.
The use of tsmUserSpinlock is to avoid conflicts with
another SNMP command generator application which may
also be acting on the tsmUserTable. SEQUENCE OF tsmUserEntry .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.2 |
tsmUserEntryA user configured in the SNMP engine's Local
Configuration Datastore (LCD) for the Session
Security Model. tsmUserEntry .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.2.1 |
tsmUserSecurityNameA human readable string representing the user in
Security Model independent format.
[todo: Wehn used with transport models that perform
authentication, the tsmUserSecurityName is the
securityName passed in tmStateReference.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.2.1.1 |
tsmUserStorageTypeThe storage type for this conceptual row.
It is an implementation issue to decide if a SET for
a readOnly or permanent row is accepted at all. In some
contexts this may make sense, in others it may not. If
a SET for a readOnly or permanent row is not accepted
at all, then a 'wrongValue' error must be returned.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.2.1.4 |
tsmUserStatusThe status of this conceptual row.
Until instances of all corresponding columns are
appropriately configured, the value of the
corresponding instance of the tsmUserStatus column
is 'notReady'.
The RowStatus TC [RFC2579] requires that this
DESCRIPTION clause states under which circumstances
other objects in this row can be modified:
The value of this object has no effect on whether
other objects in this conceptual row can be modified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.xxxx.1.2.2.1.5 |
tsmConformance OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.2 |
tsmGroups OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.2.1 |
tsmCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.xxxx.2.2 |