|
| 1 | +--- |
| 2 | +title: Azure Operator Nexus Network Fabric Services |
| 3 | +description: Overview of Network Fabric Services for Azure Operator Nexus. |
| 4 | +author: lnyswonger |
| 5 | +ms.author: lnyswonger |
| 6 | +ms.reviewer: jdasari |
| 7 | +ms.date: 12/21/2023 |
| 8 | +ms.service: azure-operator-nexus |
| 9 | +ms.topic: conceptual |
| 10 | +--- |
| 11 | + |
| 12 | +# Network Fabric Services overview |
| 13 | +The Network Fabric Controller (NFC) serves as the host for Nexus Network Fabric (NNF) services, illustrated in the diagram below. These services enable secure internet access for on-premises applications and services. Communication between on-premises applications and NNF services is facilitated through a specialized Express Route service (VPN). This setup allows on-premises services to connect to the NNF services via Express Route at one end, and access internet-based services at the other end. |
| 14 | + |
| 15 | +:::image type="content" source="media/network-fabric-controller-architecture.png" alt-text="A flowchart for creating a Network Fabric Controller in Azure, detailing the progression from user request to the associated Azure resources."::: |
| 16 | + |
| 17 | + |
| 18 | +## Enhanced Security with Nexus Network Fabric Proxy Management |
| 19 | +The Nexus Network Fabric employs a robust, cloud-native proxy designed to protect the Nexus infrastructure and its associated workloads. This proxy is primarily focused on preventing data exfiltration attacks and maintaining a controlled allowlist of URLs for NNF instance connections. In combination with the under-cloud proxy, the NNF proxy delivers comprehensive security for workload networks. There are two distinct aspects of this system: the Infrastructure Management Proxy, which handles all infrastructure traffic, and the Workload Management Proxy, dedicated to facilitating communication between workloads and public or Azure endpoints. |
| 20 | + |
| 21 | +## Optimized Time Synchronization with Managed Network Time Protocol (NTP) |
| 22 | +The Network Time Protocol (NTP) is an essential network protocol that aligns the time settings of computer systems over packet-switched networks. In the Azure Operator Nexus instance, NTP is instrumental in ensuring the consistent time settings across all compute nodes and network devices. This level of synchronization is critical for the Network Functions (NFs) operating within the infrastructure. It significantly contributes to the effectiveness of telemetry and security measures, maintaining the integrity and coordination of the system. |
| 23 | + |
| 24 | +## Nexus Network Fabric Resources |
| 25 | +The following are key resources for Nexus Network Fabric. |
| 26 | + |
| 27 | +### InternetGateways |
| 28 | +*InternetGateways* is a critical resource in network architecture, acting as the connecting bridge between a virtual network and the Internet. It enables virtual machines and other entities within a virtual network to communicate seamlessly with external services. These services range from websites and APIs to various cloud services, making InternetGateways a versatile and essential component. |
| 29 | + |
| 30 | +#### Properties |
| 31 | + |
| 32 | +| Property | Description | |
| 33 | +|------------------|------------------------------------------------------------------------------------------------------| |
| 34 | +| Name | Serves as the unique identifier for the Internet Gateway. | |
| 35 | +| Location | Specifies the Azure region where the Internet Gateway is deployed, ensuring regional compliance and optimization. | |
| 36 | +| Subnets | Defines the subnets linked with the Internet Gateway, determining the network segments it services. | |
| 37 | +| Public IP Address| Assigns a public IP address to the gateway, enabling external network interactions. | |
| 38 | +| Routes | Outlines the routing rules and configurations for managing traffic through the gateway. | |
| 39 | + |
| 40 | + |
| 41 | +#### Use cases |
| 42 | + |
| 43 | +* **Internet Access:** Facilitates Internet connectivity for virtual network resources, crucial for updates, downloads, and accessing external services. |
| 44 | +* **Hybrid Connectivity:** Ideal for hybrid scenarios, allowing secure connections between on-premises networks and Azure resources. |
| 45 | +* **Load Balancing:** Enhances network performance and availability by evenly distributing traffic across multiple gateways. |
| 46 | +* **Security Enforcement:** Enables the implementation of robust security policies, such as outbound traffic restrictions and encryption mandates. |
| 47 | + |
| 48 | +### InternetGatewayRules |
| 49 | +*InternetGatewayRules* represents a set of rules associated with an Internet Gateway in the Managed Network Fabric. These rules establish guidelines for either permitting or restricting traffic as it moves through the Internet Gateway, providing a framework for network traffic management. |
| 50 | + |
| 51 | +#### Properties |
| 52 | + |
| 53 | +| Property | Description | |
| 54 | +|------------------------------|--------------------------------------------------------------------------------------| |
| 55 | +| Name | Acts as the unique identifier for each rule. | |
| 56 | +| Priority | Sets the evaluation order of the rules, with higher priority rules taking precedence.| |
| 57 | +| Action | Determines the action (e.g., allow, deny) for traffic that matches the rule criteria.| |
| 58 | +| Source IP Address Range | Identifies the originating IP address range applicable to the rule. | |
| 59 | +| Destination IP Address Range | Defines the targeted IP address range for the rule. | |
| 60 | +| Protocol | Specifies the network protocol (e.g., TCP, UDP) relevant to the rule. | |
| 61 | +| Port Range | Details the port range for the rule, if applicable. | |
| 62 | + |
| 63 | + |
| 64 | +#### Use cases |
| 65 | + |
| 66 | +* **Traffic Filtering:** InternetGatewayRules enable organizations to control both incoming and outgoing network traffic based on specific criteria. For example, they can block certain IP ranges or allow only particular protocols. |
| 67 | + |
| 68 | +* **Enforcing Security Policies:** These rules are instrumental in implementing security measures, such as restricting traffic to enhance network security. An organization might block known malicious IP ranges or limit traffic to specific ports for certain services. |
| 69 | + |
| 70 | +* **Compliance Assurance:** The rules can also be utilized to comply with regulatory standards by limiting types of traffic, thereby aiding in data privacy and access control. |
| 71 | + |
| 72 | +* **Traffic Load Balancing:** InternetGatewayRules can distribute network traffic across multiple gateways to optimize resource utilization. This includes prioritizing or throttling traffic based on business needs. |
| 73 | + |
| 74 | +## FAQs |
| 75 | + |
| 76 | +**Is Support Available for HTTP Endpoints?** |
| 77 | + |
| 78 | +Azure's default configuration supports only HTTPS endpoints to ensure secure communication. HTTP endpoints are not supported as part of this security measure. By prioritizing HTTPS, Azure maintains high standards of data integrity and privacy. |
| 79 | + |
| 80 | +**How Can I Safeguard Against Data Exfiltration?** |
| 81 | + |
| 82 | +To strengthen security against data exfiltration, Azure supports the allowance of specific Fully Qualified Domain Names (FQDNs) on the proxy. This additional security measure ensures that your network can only be accessed by approved traffic, greatly minimizing the potential for unauthorized data movement. |
0 commit comments