T1599 Network Boundary Bridging

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.(Citation: Kaspersky ThreatNeedle Feb 2021) In the cases where a border device separates two separate organizations, the adversary can also facilitate lateral movement into new victim environments.

View in MITRE ATT&CK®

CRI Profile Mappings

Capability ID Capability Description Mapping Type ATT&CK ID ATT&CK Name Notes
PR.IR-01.06 Production environment segregation Mitigates T1599 Network Boundary Bridging
Comments
This diagnostic statement provides protections for production environments. Measures such as network segmentation and access control reduce the attack surface, restrict movement by adversaries, and protect critical assets and data from compromise.
References
    PR.AA-05.02 Privileged system access Mitigates T1599 Network Boundary Bridging
    Comments
    This diagnostic statement protects against Network Boundary Bridging through the use of privileged account management and the use of multi-factor authentication.
    References
      DE.CM-06.02 Third-party access monitoring Mitigates T1599 Network Boundary Bridging
      Comments
      This diagnostic statement protects against Network Boundary Bridging through the use of privileged account management. Employing auditing, privilege access management, and just in time access protects against adversaries trying to obtain illicit access to critical systems.
      References
        DE.CM-01.03 Unauthorized network connections and data transfers Mitigates T1599 Network Boundary Bridging
        Comments
        This diagnostic statement provides protection from Network Boundary Bridging by using tools to detect and block the use of unauthorized devices and connections to prevent abuse by adversaries.
        References
          PR.PS-01.07 Cryptographic keys and certificates Mitigates T1599 Network Boundary Bridging
          Comments
          This diagnostic statement protects against Network Boundary Bridging through the use of revocation of keys and key management. Employing key protection strategies and key management for key material used in identity management and authentication processes (including multi-factor authentication or MFA for network devices using TACACS+/RADIUS), limitations to specific accounts along with access control mechanisms provides protection against adversaries attempting to perform Network Boundary Bridging.
          References
            PR.AA-03.01 Authentication requirements Mitigates T1599 Network Boundary Bridging
            Comments
            This diagnostic statement describes how the organization implement appropriate authentication requirements, including selecting mechanisms based on risk, utilizing multi-factor authentication where necessary, and safeguarding the storage of authenticators like pins and passwords to protect sensitive access credentials.
            References
              PR.IR-04.01 Utilization monitoring Mitigates T1599 Network Boundary Bridging
              Comments
              This diagnostic statement describes how the organization establishes and manages baseline measures of network activity. Supported by network monitoring tools and other controls to detect events and identify incidents. Mitigating mechanisms may include: Data Loss Prevention (DLP); Filtering Network Traffic; Limit Network Traffic; Network Intrusion Prevention Systems (NIPS); and Network Segmentation for these type of network-based techniques.
              References
                PR.IR-01.03 Network communications integrity and availability Mitigates T1599 Network Boundary Bridging
                Comments
                This diagnostic statement protects against Network Boundary Bridging through the use of secure network configurations, architecture, implementations of zero trust architecture, and segmentation.
                References
                  PR.AA-01.01 Identity and credential management Mitigates T1599 Network Boundary Bridging
                  Comments
                  This diagnostic statement protects against Network Boundary Bridging through the use of hardened access control policies, secure defaults, password complexity requirements, multifactor authentication requirements, and removal of terminated accounts.
                  References
                    PR.PS-01.08 End-user device protection Mitigates T1599 Network Boundary Bridging
                    Comments
                    This diagnostic statement protects against Network Boundary Bridging through the use of limiting access to resources to only authorized devices, management of personal computing devices, network intrusion prevention, and the use of antimalware.
                    References

                      NIST 800-53 Mappings

                      Capability ID Capability Description Mapping Type ATT&CK ID ATT&CK Name Notes
                      CA-07 Continuous Monitoring mitigates T1599 Network Boundary Bridging
                      CM-06 Configuration Settings mitigates T1599 Network Boundary Bridging
                      CM-05 Access Restrictions for Change mitigates T1599 Network Boundary Bridging
                      IA-05 Authenticator Management mitigates T1599 Network Boundary Bridging
                      SC-28 Protection of Information at Rest mitigates T1599 Network Boundary Bridging
                      SI-10 Information Input Validation mitigates T1599 Network Boundary Bridging
                      SI-15 Information Output Filtering mitigates T1599 Network Boundary Bridging
                      SI-07 Software, Firmware, and Information Integrity mitigates T1599 Network Boundary Bridging
                      CM-02 Baseline Configuration mitigates T1599 Network Boundary Bridging
                      IA-02 Identification and Authentication (Organizational Users) mitigates T1599 Network Boundary Bridging
                      CM-07 Least Functionality mitigates T1599 Network Boundary Bridging
                      SI-04 System Monitoring mitigates T1599 Network Boundary Bridging
                      AC-02 Account Management mitigates T1599 Network Boundary Bridging
                      AC-03 Access Enforcement mitigates T1599 Network Boundary Bridging
                      AC-04 Information Flow Enforcement mitigates T1599 Network Boundary Bridging
                      AC-05 Separation of Duties mitigates T1599 Network Boundary Bridging
                      AC-06 Least Privilege mitigates T1599 Network Boundary Bridging
                      SC-07 Boundary Protection mitigates T1599 Network Boundary Bridging

                      VERIS Mappings

                      Capability ID Capability Description Mapping Type ATT&CK ID ATT&CK Name Notes
                      action.hacking.variety.Unknown Unknown related-to T1599 Network Boundary Bridging

                      AWS Mappings

                      Capability ID Capability Description Mapping Type ATT&CK ID ATT&CK Name Notes
                      amazon_inspector Amazon Inspector technique_scores T1599 Network Boundary Bridging
                      Comments
                      The Amazon Inspector Best Practices assessment package can assess security control "Configure permissions for system directories" that prevents privilege escalation by local users and ensures only the root account can modify/execute system configuration information and binaries. Amazon Inspector does not directly protect against system modifications rather it just checks to see if security controls are in place which can inform decisions around hardening the system. Furthermore, Amazon Inspector only supports a subset of the sub-techniques for this technique. Due to these things and the fact the security control is only supported for Linux platforms, the score is Minimal.
                      References

                      ATT&CK Subtechniques

                      Technique ID Technique Name Number of Mappings
                      T1599.001 Network Address Translation Traversal 28