M0814: Static Network Configuration
Configure hosts and devices to use static network configurations when possible, protocols that require dynamic discovery/addressing (e.g., ARP, DHCP, DNS) can be used to manipulate network message forwarding and enable various AiTM attacks. This mitigation may not always be usable due to limited device features or challenges introduced with different network configurations.
Security context for executives and security teams
M0814: Static Network Configuration describes Configure hosts and devices to use static network configurations when possible, protocols that require dynamic discovery/addressing (e.g., ARP, DHCP, DNS) can be used to manipulate network message forwarding and enable various AiTM attacks. This mitigation may not always be usable due to limited device features or challenges introduced with different network configurations.
Executive priority
M0814: Static Network Configuration is an official MITRE ATT&CK mitigation. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.
Technical view
Security teams should validate M0814: Static Network Configuration by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (the platforms named in the official object), and available local telemetry before making detection or mitigation decisions.
Likely telemetry
- Official ATT&CK relationships and object metadata
Detection direction
- Validate whether M0814: Static Network Configuration appears in your detection coverage and tabletop scenarios.
- Use the object to align executive risk language with SOC, incident response, and detection engineering work.
- Do not treat ATT&CK relationship context as attribution without corroborating evidence.
Mitigation priorities
- Map the object to existing controls and identify missing telemetry or response ownership.
- Prioritize mitigations that reduce exposure on the listed platforms and tactics.
- Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits
Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.
This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Static Network Configuration
Configure hosts and devices to use static network configurations when possible, protocols that require dynamic discovery/addressing (e.g., ARP, DHCP, DNS) can be used to manipulate network message forwarding and enable various AiTM attacks. This mitigation may not always be usable due to limited device features or challenges introduced with different network configurations.
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.
Techniques used
This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| ICS | T0846.001 | Port ScanSub-technique | ICS environments typically have more statically defined devices, therefore minimize the use of both IT discovery protocols (e.g., DHCP, LLDP) and discovery functions in automation protocols.CitationD. Parsons and D. Wylie September 2019CitationColin Gray Examples of automation protocols with discovery capabilities include OPC UA Device DiscoveryCitationJosh Rinaldi April 2016, BACnetCitationAditya K Sood July 2019, and Ethernet/IP.CitationLangner November 2018 |
| ICS | T0846.003 | Multicast DiscoverySub-technique | ICS environments typically have more statically defined devices, therefore minimize the use of both IT discovery protocols (e.g., DHCP, LLDP) and discovery functions in automation protocols.CitationD. Parsons and D. Wylie September 2019CitationColin Gray Examples of automation protocols with discovery capabilities include OPC UA Device Discovery CitationJosh Rinaldi April 2016, BACnetCitationAditya K Sood July 2019, and Ethernet/IP.CitationLangner November 2018 |
| ICS | T0878 | Alarm Suppression | Unauthorized connections can be prevented by statically defining the hosts and ports used for automation protocol connections. |
| ICS | T0888 | Remote System Information Discovery | ICS environments typically have more statically defined devices, therefore minimize the use of both IT discovery protocols (e.g., DHCP, LLDP) and discovery functions in automation protocols. CitationD. Parsons and D. Wylie September 2019 CitationColin Gray Examples of automation protocols with discovery capabilities include OPC UA Device Discovery CitationJosh Rinaldi April 2016, BACnet CitationAditya K Sood July 2019, and Ethernet/IP. CitationLangner November 2018 |
| ICS | T0830 | Adversary-in-the-Middle | Statically defined ARP entries can prevent manipulation and sniffing of switched network traffic, as some AiTM techniques depend on sending spoofed ARP messages to manipulate network host's dynamic ARP tables. |
| ICS | T1691.002 | Reporting MessageSub-technique | Unauthorized connections can be prevented by statically defining the hosts and ports used for automation protocol connections. |
| ICS | T0846 | Remote System Discovery | ICS environments typically have more statically defined devices, therefore minimize the use of both IT discovery protocols (e.g., DHCP, LLDP) and discovery functions in automation protocols.CitationD. Parsons and D. Wylie September 2019CitationColin Gray Examples of automation protocols with discovery capabilities include OPC UA Device DiscoveryCitationJosh Rinaldi April 2016, BACnetCitationAditya K Sood July 2019, and Ethernet/IP.CitationLangner November 2018 |
| ICS | T0846.002 | Broadcast DiscoverySub-technique | ICS environments typically have more statically defined devices, therefore minimize the use of both IT discovery protocols (e.g., DHCP, LLDP) and discovery functions in automation protocols.CitationD. Parsons and D. Wylie September 2019CitationColin Gray Examples of automation protocols with discovery capabilities include OPC UA Device DiscoveryCitationJosh Rinaldi April 2016, BACnetCitationAditya K Sood July 2019, and Ethernet/IP.CitationLangner November 2018 |
| ICS | T1691 | Block Operational Technology Message | Unauthorized connections can be prevented by statically defining the hosts and ports used for automation protocol connections. |
| ICS | T0842 | Network Sniffing | Statically defined ARP entries can prevent manipulation and sniffing of switched network traffic, as some AiTM techniques depend on sending spoofed ARP messages to manipulate network host's dynamic ARP tables. |
| ICS | T1691.001 | Command MessageSub-technique | Unauthorized connections can be prevented by statically defining the hosts and ports used for automation protocol connections. |
All related ATT&CK context
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(2)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.2 | 1.2 | Current bundle | 7ba9b5c5f267… | ||
| 19.1 | 1.2 | Older bundle | 7ba9b5c5f267… |
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-attackM0814Open 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.