Hello, you are using an old browser that's unsafe and no longer supported. Please consider updating your browser to a newer version, or downloading a modern browser.

Global Accelerated Learning • Est. 1999
Glossary Term OID

Training Camp • Cybersecurity Glossary

What is OID?

An Object Identifier - a globally unique, hierarchical sequence of numbers (like 1.3.6.1.2.1) that names objects in SNMP MIBs, X.509 certificates, and LDAP directories.

Glossary > Network Security > OID

OID — An Object Identifier - a globally unique

Understanding OID

An OID (Object Identifier) is a globally unique, hierarchical sequence of numbers used to unambiguously name an object or concept. Standardized jointly by ISO/IEC and ITU-T, OIDs are written as dot-separated integers (for example 1.3.6.1.2.1) where each number represents a node in a global naming tree, and the path from the root makes every identifier unique.

The OID tree is administered hierarchically: top-level arcs include 0 (ITU-T), 1 (ISO), and 2 (joint ISO/ITU-T). Each authority assigns sub-arcs beneath the nodes it controls, so organizations register their own branch and define identifiers under it without collision. This delegation lets vendors and standards bodies mint identifiers independently while keeping the whole space coordinated. OIDs are most associated with SNMP, where a Management Information Base (MIB) maps each manageable variable - such as interface traffic counters - to a specific OID under 1.3.6.1.2.1, but they are also used in X.509 certificates and LDAP directories.

OIDs matter to security because they precisely identify the elements that monitoring, cryptographic, and directory systems act on. In SNMP, an OID pinpoints exactly which device variable is being read or written, so access controls and views are defined per-OID to restrict what a manager can touch. In X.509, OIDs identify signature algorithms, extensions, and certificate policies - so an attacker or a flawed parser misinterpreting an OID could lead to a certificate being trusted incorrectly. Unambiguous naming is foundational to evaluating these objects correctly.

For example, a network management station polls OID 1.3.6.1.2.1.2.2.1.10 (ifInOctets) on a switch to read inbound byte counts on an interface, using SNMP. Because the OID uniquely identifies that exact counter across vendors, the monitoring tool retrieves consistent data, and the switch's SNMP view can be configured to expose only that branch of the MIB while denying access to more sensitive OIDs.

Learn More About OID:

Ready to Get Certified?

Turn knowledge into credentials with our instructor-led cybersecurity boot camps.

View All Courses →