tfMITRE ATT&CK sub-technique

SNMP (MIB Dump) T1602.001

sub-technique of T1602 Data from Configuration Repository

Tactic: Collection
Platform: Network Devices
Version: 1.1
Created: 19 October 2020
Last modified: 24 October 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).

ReconResource DevInitial AccessExecutionPersistencePriv EscStealthDef ImpairmentCred AccessDiscoveryLateral MoveCollectionC2ExfiltrationImpact

Threat groupsNone recorded

Threat groupsNone recorded · 29% of ATT&CK techniques have none either.

CampaignsNone recorded

CampaignsNone recorded · 54% of ATT&CK techniques have none either.

Tools & malwareNone recorded

Tools & malwareNone recorded · 29% of ATT&CK techniques have none either.

Detection rulesNone recorded

Detection rulesNone recorded · 33% of ATT&CK techniques have none either.

Offense vs defense T1602.001

Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.

SNMP (MIB Dump) detection strategy DET0453

MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.

Detection Strategy for SNMP (MIB Dump) on Network Devices

Enterprise

1 platform

AN1249 · Network Devices

Defenders may observe suspicious SNMP MIB enumeration through abnormal queries for large sets of OIDs, repeated SNMP GETBULK/GETNEXT requests, or queries originating from non-administrative IP addresses. Anomalous use of community strings, authentication failures, or enumeration activity outside maintenance windows may also indicate attempts to dump MIB contents. Correlation across syslog, NetFlow, and SNMP audit data can reveal chains of behavior such as repeated authentication failures followed by successful large-scale OID retrieval.

Log sources

The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.

Data component	Name	Channel
File ModificationDC0061	networkdevice:audit	SNMP configuration changes, such as enabling read/write access or modifying community strings
Network Connection CreationDC0082	NSM:Flow	High-volume or repeated SNMP GETBULK/GETNEXT queries from untrusted or external IPs
Network Traffic ContentDC0085	networkdevice:syslog	Authentication failures, unexpected community string usage, or unauthorized SNMPv1/v2 requests

Tunable fields

MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.

Field	What you tune
AuthorizedAdminIPs	Expected IP ranges allowed to query SNMP. Deviation indicates possible misuse.
NormalSNMPQueryRate	Baseline frequency and volume of SNMP queries; anomalies above threshold may indicate dumping.
CommunityStringPatterns	Expected community strings (e.g., hashed or custom values). Unrecognized strings may signal abuse.
TimeWindow	Time periods during which SNMP queries are authorized. Queries outside these hours may be malicious.

SNMP (MIB Dump) detections T1602.001

No detection rules are mapped to this technique yet.

None recorded— 33% of ATT&CK techniques have none either

Drag headers to reorder | Drag edges to resize

Loading detections...

Select	Title	Description	Category	Status	Event	Product	MITRE ATT&CK	CVEs	Severity	Author	Created	Updated	ID	Refs