ipsecSaMonitorCompliance — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
The compliance statement for SNMPv2 entities which implement the IPsec Monitoring MIB.
{1 3 6 1 2 1 500 1 8 1}
The compliance statement for SNMPv2 entities which implement the IPsec Monitoring MIB.
Status in source: current.
Names: ipsecSaMonitorCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"ipsecSaMonitorCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for SNMPv2 entities which implement the IPsec Monitoring MIB.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"ipsecSaEspGroup",
",",
"ipsecSaAhGroup",
",",
"ipsecSaErrorsGroup",
",",
"ipsecSaFailureTrapEnableGroup",
",",
"ipsecSaFailureTrapGroup",
"}",
"OBJECT",
"espAuthFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"ahAuthFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"espReplayFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"ahReplayFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"espPolicyFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"ahPolicyFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"invalidSpiTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"OBJECT",
"otherPolicyFailureTrapEnable",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"If an implementation cannot properly secure this variable against unauthorized write access, it SHOULD implement it as read-only, to prevent the security risk of enabling the traps. Of course, there must be other means of controlling the generation of the associated trap.\"",
"GROUP",
"ipsecSaIpcompGroup",
"DESCRIPTION",
"\"This group is mandatory only for those systems that implement the IPComp protocol as a part of the IPsec suite.\"",
"::=",
"{",
"saConformance",
"1",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for SNMPv2 entities which implement the IPsec Monitoring MIB."
],
null,
[
"ComplianceModules",
[
[
null,
[
"ipsecSaEspGroup",
"ipsecSaAhGroup",
"ipsecSaErrorsGroup",
"ipsecSaFailureTrapEnableGroup",
"ipsecSaFailureTrapGroup"
]
]
]
]
]
}Vendor MIB copy from the Observium Community archive.
Module: IPSEC-SA-MON-MIB
ipsecSaMonitorCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the IPsec Monitoring MIB."
MODULE -- this module
MANDATORY-GROUPS {
ipsecSaEspGroup, ipsecSaAhGroup, ipsecSaErrorsGroup,
ipsecSaFailureTrapEnableGroup, ipsecSaFailureTrapGroup
}
-- Allow all the trap controls to be read-only
OBJECT espAuthFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT ahAuthFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT espReplayFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT ahReplayFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT espPolicyFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT ahPolicyFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT invalidSpiTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
OBJECT otherPolicyFailureTrapEnable
MIN-ACCESS read-only
DESCRIPTION
"If an implementation cannot properly secure this
variable against unauthorized write access, it
SHOULD implement it as read-only, to prevent the
security risk of enabling the traps. Of course,
there must be other means of controlling the
generation of the associated trap."
GROUP ipsecSaIpcompGroup
DESCRIPTION
"This group is mandatory only for those systems that
implement the IPComp protocol as a part of the IPsec
suite."
::= { saConformance 1 }{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'Counter64', 'mib-2'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'NOTIFICATION-GROUP', 'MODULE-COMPLIANCE'], 'IPSEC-ISAKMP-IKE-DOI-TC': ['IpsecDoiIdentType', 'IpsecDoiEncapsulationMode', 'IpsecDoiEspTransform', 'IpsecDoiAhTransform', 'IpsecDoiAuthAlgorithm', 'IpsecDoiIpcompTransform', 'IpsecDoiSecProtocolId']}Related source files and packages:
Downloaded: 2026-10-24T02:14:27.114148+00:00.