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.
|M1041||Encrypt Sensitive Information||
Configure SNMPv3 to use the highest level of security (authPriv) available.
|M1037||Filter Network Traffic||
Apply extended ACLs to block unauthorized protocols outside the trusted network.
|M1031||Network Intrusion Prevention||
Configure intrusion prevention devices to detect SNMP queries and commands from unauthorized sources.
Segregate SNMP traffic on a separate management network.
Allowlist MIB objects and implement SNMP views.
Keep system images and software updated and migrate to SNMPv3.
|ID||Data Source||Data Component||Detects|
|DS0029||Network Traffic||Network Connection Creation||
Monitor for newly constructed network connections that are sent or received by untrusted hosts or uncommon data flows. Consider analyzing packet contents to detect application layer protocols, leveraging SSL/TLS inspection for encrypted traffic, that do not follow the expected protocol standards and traffic flows (e.g. unauthorized, gratuitous, or anomalous traffic patterns attempting to access configuration content)
|Network Traffic Content||
Monitor and analyze traffic patterns and packet inspection associated to protocol(s) that do not follow the expected protocol standards and traffic flows (e.g. unauthorized, gratuitous, or anomalous traffic patterns attempting to access configuration content)