T1599 Network Boundary Bridging

Enterprise

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.

01

Plattformen

Plattformen, für die dies gilt.

Network Devices
02

Taktiken

ATT&CK-Taktiken, denen diese Technik dient.

03

Untertechniken (1)

Spezifischere Einträge unterhalb dieses.

04

Gegenmaßnahmen

ATT&CK-Gegenmaßnahmen, die dies verringern.

05

Erkannt durch (2)

Datenkomponenten, die dies erkennen.

06

NIST CSF 2.0 — Relevanzbereiche (Protect / Detect)

NIST-CSF-2.0-Bereiche mit dem größten Bezug (belegbasiert).

Abgeleitet aus MITRE CTID (Apache-2.0) und dem NIST-800-53-↔-CSF-Crosswalk (gemeinfrei). Eine indikative Relevanz entlang der Protect-/Detect-Achse — keine Compliance-Bewertung und keine Abdeckungsaussage.

08

Angriffsmuster (1)

CAPEC-Angriffsmuster, die dies ausnutzen.

09

Gruppen (2)

Zugehörige Bedrohungsgruppen.

10

Kampagnen (1)

Kampagnen, die dies verwenden.

11

Quelle

Wo diese Definition veröffentlicht ist.