---
oid: "1.3.6.1.2.1.44.1.2.3.1"
short-description: "mipSecViolationEntry OBJECT-TYPE"
last-modified: "2019-10-09"
parent-oid: "1.3.6.1.2.1.44.1.2.3"
---

## OID: `1.3.6.1.2.1.44.1.2.3.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) mipMIB(44) mipMIBObjects(1) mipSecurity(2) mipSecViolationTable(3) mipSecViolationEntry(1)}
```

### Description

```asn1
mipSecViolationEntry OBJECT-TYPE
SYNTAX MipSecViolationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about one particular security violation."
INDEX { mipSecViolatorAddress }
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 2006](https://www.rfc-editor.org/rfc/rfc2006.html).

### Child OIDs

- `1.3.6.1.2.1.44.1.2.3.1.1`: `mipSecViolatorAddress(1)`
- `1.3.6.1.2.1.44.1.2.3.1.2`: `mipSecViolationCounter(2)`
- `1.3.6.1.2.1.44.1.2.3.1.3`: `mipSecRecentViolationSPI(3)`
- `1.3.6.1.2.1.44.1.2.3.1.4`: `mipSecRecentViolationTime(4)`
- `1.3.6.1.2.1.44.1.2.3.1.5`: `mipSecRecentViolationIDLow(5)`
- `1.3.6.1.2.1.44.1.2.3.1.6`: `mipSecRecentViolationIDHigh(6)`
- `1.3.6.1.2.1.44.1.2.3.1.7`: `mipSecRecentViolationReason(7)`

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.