Configure Security Settings for NSX Edge Nodes by Using the User Interface
You perform the procedure in NSX to configure traffic logging for Gateway Firewall rules, publish any firewall policy/rule changes, deny traffic by default, flood protection profile, ingress filters, restrict traffic and disable Internet Control Message Protocol (ICMP) unreachable notifications, mask replies, redirects on the external interfaces. Configure the settings for all NSX edge instances in your VMware Cloud Foundation environment.
- In a Web browser, log in to the NSX Manager cluster as an administrator by using the user interface.
- VMW-NSX-01429,VMW-NSX-01514Configure the NSX Gateway Firewall on the tier-0 and tier-1 gateways to generate traffic log entries.If the tier-0 gateway is deployed in an active/active high availability mode and no stateless rules exist, this configuration is not applicable.
- On the main navigation bar, clickSecurity.
- In the left pane, navigate to/
- Click theGateway specific rulestab.
- From theGatewaydrop-down menu, select the respective gateway.
- For each tier-0 gateway and for each rule with logging disabled, click the gear icon, activate theLoggingtoggle, and clickApply.
- On theGateway Firewallpage, clickPublish.
- Repeat the procedure for each tier-1 gateway and for each rule with deactivated logging.
- VMW-NSX-01431,VMW-NSX-01432Configure the NSX Gateway Firewall on the tier-0 and tier-1 gateways to deny network traffic by default and allow network traffic by exception.
- On the main navigation bar, clickSecurity.
- In the left pane, navigate to.
- Click theGateway specific rulestab.
- From theGatewaydrop-down menu, select the respective gateway.
- Expand the default policy, and from theActionsdrop-down menu, selectRejectorDrop.
- On theGateway Firewallpage, clickPublish.
- Repeat the procedure for each tier-1 gateway.
- VMW-NSX-01437Configure the multicast NSX tier-0 gateway to deactivate Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing.
- Navigate toand expand the target Tier-0 gateway.
- ExpandInterfaces and GRE Tunnels, click on the number ofExternal and Service interfacespresent to open the interfaces dialog, and then select "Edit" on the target interface.
- Expand "Multicast", change PIM to "Deactivated", and then click "Save".
- VMW-NSX-01438Remove inactive interfaces on an NSX Tier-0 gateway.
- Navigate toand expand the target Tier-0 gateway.
- ExpandInterfaces and GRE Tunnels, click on the number of "External and Service interfaces" present to open the interfaces dialog, and then select "Edit" on the target interface.
- Select "Delete" on the unneeded interface, and then click "Delete" again to confirm.
- VMW-NSX-01442Disconnect inactive linked segments for NSX Tier-1 gateways.
- Navigate toand edit the target segment.
- Under Connected Gateway, change to "None" and click "Save.The stale linked segment can also be deleted if there are no active workloads attached to it.
- Naviate toand edit the target Tier-1 Gateway.
- Expand Service Interfaces and click on the number to view the Service Interfaces.
- On the stale service interface, selectDeleteand clickDeleteagain to confirm.
- VMW-NSX-01453,VMW-NSX-01515Configure flood protection profiles on the NSX Gateway Firewall for the tier-0 and tier-1 gateways to protect against Denial of Service (DDoS) attacks.If the tier-0 gateway is deployed in an active/active high availability mode and no stateless rules exist, this configuration is not applicable.
- On the main navigation bar, clickSecurity.
- In the left pane, navigate to.
- Click theunderGeneral Security Settingstab.
- Fom theAdd profiledrop-down menu, selectAdd Edge Gateway profile.
- Enter a name and specify appropriate values for the following:TCP half open connection limit,UDP active flow limit,ICMP active flow limit, andOther active connection limit.
- Configure theApplied tofield to contain the tier-0 gateways, and then clickSave.
- Repeat this step for the tier-1 gateway and setApplied toto contain the tier-1 gateways.
- VMW-NSX-01460To protect against route table flooding and prefix de-aggregation attacks, configure the NSX tier-0 gateway to use maximum prefixes.
- On the main navigation bar, clickNetworking.
- In the left pane, navigate to.
- Expand the NSX tier-0 gateway.
- Expand theBGPsection and clickBGP neighbors.
- In theSet BGP neighborsdialog box, click the vertical ellipsis and clickEditfor the first neighbor.
- Click the number in theRoute filtercolumn.
- To configure the maximum routes value, specific to your environment, in theSet route filterdialog box, click the vertical ellipsis menu and clickEdit.
- Repeat the step to configure all neighbors.
- VMW-NSX-01494,VMW-NSX-01495,VMW-NSX-01496Configure the NSX tier-0 gateway to have Internet Control Message Protocol (ICMP) unreachable notifications, mask replies, and disable redirects on all external interfaces.If the tier-0 gateway is deployed in an active/active high availability mode and no stateless rules exist, this configuration is not applicable.NSX does not come with a pre-configured service for ICMP mask replies. You may need to create this service.
- On the main navigation bar, clickSecurity.
- In the left pane, navigate to.
- Click theAll shared rulestab.
- ClickAdd rule(Add a policy first if needed) and, in theServicescolumn, click theEditbutton.
- On theSet servicesdialog box, on theServicestab, select theICMP destination unreachableservice, and clickApply.
- Click theSettingsicon for the newly added rule and, on theSettingsdialog box, activate theLoggingtoggle.
- In theApplied tocolumn, click theEditicon.
- In theApplied todialog box, select the target NSX tier-0 gateway and clickApply.
- On theGateway Firewallpage, clickPublish.
- Repeat the procedure for theICMP mask repliesandICMP redirectservices.
A rule can also be created under Gateway Specific Rules to meet this requirement. - VMW-NSX-01532NSX Tier-1 Gateway Firewall must be configured to inspect traffic at the application layer.
- On the main navigation bar, clickSecurity.
- In the left pane, navigate toand selectGateway Specific Rules.
- From the Gateway drop down chooseTier-1 Gateway
- For each rule that should have a Context Profile enabled, click the penci icon in theProfilescolumn. and selectContext profileunderSelect profiledialog box.
- Select an existing Context Profile or create a custom one then clickApply.
- After all the changes are made, clickPublish.
Not all App IDs will be suitable for use in all cases and should be evaluated in each environment before use.A list of App IDs for application layer rules is available here: https://docs.vmware.com/en/NSX-Application-IDs/index.html - VMW-NSX-01469Unicast Reverse Path Forwarding (uRPF) must be enabled on the NSX Tier-0 Gateway
- On the main navigation bar, clickNetworking.
- In the left pane, navigate to.
- Expand the NSX tier-0 gateway.
- Expand theInterfaces and GRE Tunnelssection and click the number ofExternal and Service Interfaces.
- In theSet Interfacesdialog box, click the vertical ellipsis and clickEditfor the first interface.
- From the drop-down set theURPF ModetoStrictand then clickSave.
- Repeat the step to configure all interfaces.
- VMW-NSX-01459VMW-NSX-01470The NSX Tier-0 Gateway router must be configured to use encryption for BGP routing protocol authentication and use a unique password for each autonomous system (AS) that it peers with.
- On the main navigation bar, clickNetworking.
- In the left pane, navigate to.
- Expand the NSX tier-0 gateway.
- Expand theBGPsection and click the number next toBGP neighbors.
- In theSet BGP neighborsdialog box, click the vertical ellipsis and clickEditfor the first neighbor.
- UnderTimers and Password, enter a unique password of up to 20 characters that is different from other autonomous systems and then clickSave.
- Repeat the step to configure all neighbors.
- VMW-NSX-01536The NSX Tier-0 Gateway router must be configured to use encryption for OSPF routing protocol authentication.
- On the main navigation bar, clickNetworking.
- In the left pane, navigate to.
- Expand the NSX tier-0 gateway.
- Expand theOSPFsection and click number next toArea Definition.
- In theSet Area Definitiondialog box, click the vertical ellipsis and clickEditfor the first Area definition.
- Change theAuthenticationdrop-down to MD5 and enter a Key ID and password and then clickSave.
- Repeat the step to configure all Area definitions.
The MD5 password can have a maximum of 16 characters.