Cross-source coverage
T1602 / ATT&CK
Data from Configuration Repository
1 rule across 1 source.
From MITRE ATT&CK 19.2
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. Data from configuration repositories may be exposed by various protocols and software and can store a wide variety of data, much of which may align with adversary Discovery objectives.
- Tactics
- Collection
- Platforms
- Network Devices
- Telemetry
-
NSM:Flownetworkdevice:syslog
How MITRE says to detect it DET0592
Detection Strategy for Data from Configuration Repository on Network Devices
Network Devices Analytic 1630
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. Suspicious sequences include repeated queries from untrusted IPs, abnormal query types requesting sensitive configuration data, or repository access occurring outside of normal administrative maintenance windows. Abnormal authentication attempts, sudden enumeration of device inventory, or bulk data transfer of configuration files may also be observed.
NSM:FlowUnexpected or unauthorized inbound connections to SNMP, NETCONF, or RESTCONF servicesnetworkdevice:syslogAuthentication failures or unusual community string usage in SNMP queries
Sub-techniques with coverage
Counted in the 1 above — a rule tagged a sub-technique covers this technique too.
elastic/detection-rules
1 rule| Detection | Severity | Format |
|---|---|---|
| FortiGate Configuration File Downloaded | Medium | Elastic TOML |