Cross-source coverage
T1599 / ATT&CK
Network Boundary Bridging
5 rules across 3 sources.
From MITRE ATT&CK 19.2
Adversaries may bridge network boundaries by compromising perimeter network devices or internal devices responsible for network segmentation. Breaching these devices may enable an adversary to bypass restrictions on traffic routing that otherwise separate trusted and untrusted networks.
Devices such as routers and firewalls can be used to create boundaries between trusted and untrusted networks. They achieve this by restricting traffic types to enforce organizational policy in an attempt to reduce the risk inherent in such connections. Restriction of traffic can be achieved by prohibiting IP addresses, layer 4 protocol ports, or through deep packet inspection to identify applications. To participate with the rest of the network, these devices can be directly addressable or transparent, but their mode of operation has no bearing on how the adversary can bypass them when compromised.
When an adversary takes control of such a boundary device, they can bypass its policy enforcement to pass normally prohibited traffic across the trust boundary between the two separated networks without hinderance. By achieving sufficient rights on the device, an adversary can reconfigure the device to allow the traffic they want, allowing them to then further achieve goals such as command and control via Multi-hop Proxy or exfiltration of data via Traffic Duplication. Adversaries may also target internal devices responsible for network segmentation and abuse these in conjunction with Internal Proxy to achieve the same goals. In the cases where a border device separates two separate organizations, the adversary can also facilitate lateral movement into new victim environments.
- Tactics
- Defense Impairment
- Platforms
- Network Devices
- Telemetry
-
NSM:Flownetworkdevice:syslog
How MITRE says to detect it DET0006
Detection Strategy for Network Boundary Bridging
Network Devices Analytic 0015
From a defender’s perspective, suspicious bridging is observed when network devices begin allowing traffic that contradicts existing segmentation or access policies. Observable behaviors include sudden modifications to ACLs or firewall rules, unusual cross-boundary traffic flows (e.g., east-west communications across separated VLANs), or simultaneous ingress/egress anomalies. Multi-event correlation is key: configuration changes on a router/firewall followed by unexpected traffic patterns, especially from unusual sources, is a strong indicator of compromise.
NSM:FlowUnexpected flows between segmented networks or prohibited portsnetworkdevice:syslogACL/Firewall rule modification or new route injection
Sub-techniques with coverage
Counted in the 5 above — a rule tagged a sub-technique covers this technique too.
panther-labs/panther-analysis
3 rules| Detection | Severity | Format |
|---|---|---|
| External Principal Accessing AWS Resources Via VPC Endpoint | Medium | Panther Python |
| Sensitive API Calls Via VPC Endpoint | Medium | Panther Python |
| VPC Endpoint Access Denied | Medium | Panther Python |
SigmaHQ/sigma
1 rule| Detection | Severity | Format |
|---|---|---|
| WinDivert Driver Load | High | Sigma |
splunk/security_content
1 rule| Detection | Severity | Format |
|---|---|---|
| AWS Bedrock Claude Cross Region Possible Inference Abuse | Undefined | SPL |