AN0647: Analytic 0647
Defenders may observe adversary attempts to collect or export full device configurations by detecting unusual SNMP queries, Smart Install (SMI) activity, or CLI/API commands that request running or startup configuration dumps. Correlated behaviors include high-volume read requests for sensitive OIDs, repeated use of 'show running-config' or equivalent commands from untrusted IPs, or unexpected TFTP/SCP/FTP transfers containing configuration files. These behaviors often appear in sequence: anomalous authentication or privilege escalation, followed by bulk configuration retrieval and outbound transfer.
Analyst context for executives and security teams
This analytic matters because full network device configurations can expose routing design, access controls, credentials or secrets, management paths, and resilience dependencies. For executives and security leaders, the business issue is not just configuration theft; it is loss of trust in the infrastructure that carries production, cloud, branch, and operational traffic. The behavior centers on unusual attempts to retrieve running or startup configurations from network devices through SNMP, Smart Install activity, CLI/API commands, or follow-on file transfers.
Executive priority
Prioritize this as a network infrastructure protection and incident readiness question: can the organization prove who is allowed to read device configurations, from where, and how that activity is logged? Security leaders should ask whether configuration retrieval is limited to approved management systems, whether device command/accounting logs are retained for investigations, and whether outbound transfers of configuration files would be visible. This also supports audit and compliance evidence around privileged access, change control, and protection of sensitive infrastructure information.
Technical view
For SOC, detection engineering, and IR teams, validate visibility on Network Devices for attempts to collect or export full configurations. The supplied ATT&CK description points to unusual SNMP queries, Smart Install activity, CLI/API commands requesting running or startup configuration dumps, and unexpected TFTP/SCP/FTP transfers containing configuration files. Useful detection logic should correlate management-plane authentication or privilege changes with bulk configuration retrieval and outbound transfer. Because no formal ATT&CK detection text or relationships were supplied, local baselines and authorized management workflows are essential.
Likely telemetry
- Network device AAA/authentication logs for management access and privilege changes
- CLI command accounting logs, including repeated 'show running-config' or equivalent commands
- Network device API access logs where configuration retrieval is supported
- SNMP query logs or network telemetry showing high-volume reads for sensitive OIDs
- Smart Install activity logs or network observations where applicable
Detection direction
- Baseline legitimate configuration backup, monitoring, and network management activity before alerting on volume alone.
- Flag configuration dump commands or API calls from untrusted, unusual, or non-management IP addresses.
- Look for high-volume SNMP read activity against sensitive OIDs, especially when not sourced from approved monitoring systems.
- Correlate anomalous authentication or privilege escalation followed by configuration retrieval and TFTP/SCP/FTP transfer activity.
- Treat scheduled backup tools, configuration management platforms, and administrator troubleshooting as expected false-positive sources that require allowlisting and change-ticket context.
Mitigation priorities
- Restrict network device management access to approved administrative networks and systems.
- Enforce least-privilege administrative access and retain command/accounting evidence for configuration retrieval actions.
- Limit or disable unnecessary management services and legacy transfer paths where they are not required.
- Control and monitor SNMP access, including which sources may query sensitive device information.
- Use approved, authenticated configuration backup processes so legitimate exports are distinguishable from unusual retrievals.
Analyst notes and limits
The strongest defensive value comes from correlating several weak signals: management login, privilege change, configuration dump command or SNMP/SMI retrieval, and file transfer. In many environments, legitimate backup and monitoring tools will resemble parts of this behavior, so detection quality depends on an accurate inventory of approved management sources and expected schedules.
The ATT&CK object provides a description but no separate official detection field, no tactics, and no relationship context. This take is therefore limited to the supplied Network Devices platform and the behaviors explicitly named in the object. Local device types, logging capabilities, retention, and authorized administration patterns are required to turn this into production detection logic.
Analytic 0647
Defenders may observe adversary attempts to collect or export full device configurations by detecting unusual SNMP queries, Smart Install (SMI) activity, or CLI/API commands that request running or startup configuration dumps. Correlated behaviors include high-volume read requests for sensitive OIDs, repeated use of 'show running-config' or equivalent commands from untrusted IPs, or unexpected TFTP/SCP/FTP transfers containing configuration files. These behaviors often appear in sequence: anomalous authentication or privilege escalation, followed by bulk configuration retrieval and outbound transfer.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | c651e66894a8… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack AN0647Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.