Data from Configuration Repository: SNMP (MIB Dump)
- ID
- T1602.001
- Tactics
- TA0009 Collection
- Sub-technique of
- T1602 Data from Configuration Repository
- Platforms
- Network Devices
- Data sources
- Network Traffic Content, Network Connection Creation, File Modification
- Source
- attack.mitre.org
- MITRE last modified
- 25 Oct 2025
Adversaries may target the Management Information Base (MIB) to collect and/or mine valuable information in a network managed using Simple Network Management Protocol (SNMP).
The MIB is a configuration repository that stores variable information accessible via SNMP in the form of object identifiers (OID). Each OID identifies a variable that can be read or set and permits active management tasks, such as configuration changes, through remote modification of these variables. SNMP can give administrators great insight in their systems, such as, system information, description of hardware, physical location, and software packages[5]. The MIB may also contain device operational information, including running configuration, routing table, and interface details.
Adversaries may use SNMP queries to collect MIB content directly from SNMP-managed devices in order to collect network information that allows the adversary to build network maps and facilitate future targeted exploitation.[2][3]
Detection
- DET0453 Detection Strategy for SNMP (MIB Dump) on Network Devices
Data components: Network Traffic Content, Network Connection Creation, File Modification
Mitigations (6)
- M1030 Network Segmentation
Segregate SNMP traffic on a separate management network.[1]
- M1031 Network Intrusion Prevention
Configure intrusion prevention devices to detect SNMP queries and commands from unauthorized sources.[2]
- M1037 Filter Network Traffic
Apply extended ACLs to block unauthorized protocols outside the trusted network.[1]
- M1041 Encrypt Sensitive Information
Configure SNMPv3 to use the highest level of security (authPriv) available.[1]
- M1051 Update Software
Keep system images and software updated and migrate to SNMPv3.[3]
- M1054 Software Configuration
Allowlist MIB objects and implement SNMP views.[4]
Groups (1)
References
- US-CERT TA17-156A SNMP Abuse 2017
- US-CERT-TA18-106A
- Cisco Blog Legacy Device Attacks
- Cisco Securing SNMP
- SANS Information Security Reading Room Securing SNMP Securing SNMP
