T1602
Data from Configuration Repository
Network Devicesnothing on this site yetT1602 on attack.mitre.org
Adversaries may collect data related to managed devices from configuration repositories. Configuration repositories are used by management systems in order to configure, manage, and control data on remote systems. Configuration repositories may also facilitate remote access and administration of devices. Adversaries may target these repositories in order to collect large quantities of sensitive system administration data.
If this is happening now
Checklists and playbooks to open while the alert is still live.
Playbook for this stage
Suspected data theft by an insider
A resignation with unusual file access, a DLP alert, or an unexplained large transfer.
how MITRE says to see it
Detection Strategy for Data from Configuration Repository on Network Devices
- Defenders may observe adversary attempts to extract configuration data from management repositories by monitoring for anomalous SNMP queries, API calls, or protocol requests (e.g., NETCONF, RESTCONF) that enumerate system configuration.
what reduces it
- M1031 Network Intrusion Prevention. Configure intrusion prevention devices to detect SNMP queries and commands from unauthorized sources.
- M1037 Filter Network Traffic. Apply extended ACLs to block unauthorized protocols outside the trusted network.
- M1030 Network Segmentation. Segregate SNMP traffic on a separate management network.
- M1054 Software Configuration. Allowlist MIB objects and implement SNMP views.
- M1051 Update Software. Keep system images and software updated and migrate to SNMPv3.
- M1041 Encrypt Sensitive Information. Configure SNMPv3 to use the highest level of security (authPriv) available.