<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="VMW_NSX-T_T1_Gateway_RTR_STIG" xml:lang="en" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2022-03-09">accepted</status><title>VMware NSX-T Tier 1 Gateway RTR Security Technical Implementation Guide</title><description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</description><notice id="terms-of-use" xml:lang="en"></notice><front-matter xml:lang="en"></front-matter><rear-matter xml:lang="en"></rear-matter><reference href="https://cyber.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 1 Benchmark Date: 30 Mar 2022</plain-text><plain-text id="generator">3.3.0.27375</plain-text><plain-text id="conventionsVersion">1.10.0</plain-text><version>1</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-1_Public"><title>I - Mission Critical Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-1_Sensitive"><title>I - Mission Critical Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-2_Classified"><title>II - Mission Support Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-2_Public"><title>II - Mission Support Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-2_Sensitive"><title>II - Mission Support Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-3_Classified"><title>III - Administrative Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-3_Public"><title>III - Administrative Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Profile id="MAC-3_Sensitive"><title>III - Administrative Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-251770" selected="true" /><select idref="V-251771" selected="true" /><select idref="V-251772" selected="true" /><select idref="V-251773" selected="true" /></Profile><Group id="V-251770"><title>SRG-NET-000019-RTR-000007</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251770r810210_rule" weight="10.0" severity="high"><version>T1RT-3X-000016</version><title>The NSX-T Tier-1 Gateway must be configured to have all inactive interfaces removed.</title><description>&lt;VulnDiscussion&gt;An inactive interface is rarely monitored or controlled and may expose a network to an undetected attack on that interface.

If an interface is no longer used, the configuration must be deleted.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target VMware NSX-T Tier 1 Gateway RTR</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>VMware NSX-T Tier 1 Gateway RTR</dc:subject><dc:identifier>5454</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001414</ident><fixtext fixref="F-55161r810209_fix">To remove a stale linked segment from a Tier-1 Gateway, do the following:

From the NSX-T Manager web interface, go to Networking &gt;&gt; Segments and edit the target segment.

Under Connected Gateway, change to "None" and click "Save".

Note: The stale linked segment can also be deleted if there are no active workloads attached to it.

To remove a stale service interface from a Tier-1 Gateway, do the following:

From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways &gt;&gt; Edit the target Tier-1 Gateway.

Expand Service Interfaces &gt;&gt; click on the number to view the Service Interfaces.

On the stale service interface, select "Delete" and click "Delete" again to confirm.</fixtext><fix id="F-55161r810209_fix" /><check system="C-55207r810208_chk"><check-content-ref href="VMware_NSX-T_Tier_1_Gateway_RTR_STIG.xml" name="M" /><check-content>From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways.

For every Tier-1 Gateway, expand the Tier-1 Gateway. Click on the number in the Linked Segments to review the currently linked segments.

For every Tier-1 Gateway, expand the Tier-1 Gateway. Expand Service Interfaces, then click on the number to review the Service Interfaces.

Review each interface or linked segment present to determine if they are not in use or inactive.

If there are any linked segments or service interfaces present on a Tier-1 Gateway that are not in use or inactive, this is a finding.</check-content></check></Rule></Group><Group id="V-251771"><title>SRG-NET-000131-RTR-000035</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251771r810213_rule" weight="10.0" severity="low"><version>T1RT-3X-000027</version><title>The NSX-T Tier-1 Gateway must be configured to have the DHCP service disabled if not in use.</title><description>&lt;VulnDiscussion&gt;A compromised router introduces risk to the entire network infrastructure, as well as data resources that are accessible via the network. The perimeter defense has no oversight or control of attacks by malicious users within the network. Preventing network breaches from within is dependent on implementing a comprehensive defense-in-depth strategy, including securing each device connected to the network. This is accomplished by following and implementing all security guidance applicable for each node type. A fundamental step in securing each router is to enable only the capabilities required for operation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target VMware NSX-T Tier 1 Gateway RTR</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>VMware NSX-T Tier 1 Gateway RTR</dc:subject><dc:identifier>5454</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000381</ident><fixtext fixref="F-55162r810212_fix">From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways and edit the target Tier-1 Gateway.

Click "Set DHCP Configuration", select "No Dynamic IP Address Allocation", click "Save", and then close "Editing".</fixtext><fix id="F-55162r810212_fix" /><check system="C-55208r810211_chk"><check-content-ref href="VMware_NSX-T_Tier_1_Gateway_RTR_STIG.xml" name="M" /><check-content>From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways.

For every Tier-1 Gateway expand the Tier-1 Gateway to view the DHCP configuration.

If a DHCP profile is configured and not in use, this is a finding.</check-content></check></Rule></Group><Group id="V-251772"><title>SRG-NET-000193-RTR-000112</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251772r810216_rule" weight="10.0" severity="medium"><version>T1RT-3X-000034</version><title>The NSX-T Tier-1 Gateway must be configured to enforce a Quality-of-Service (QoS) policy to limit the effects of packet flooding denial-of-service (DoS) attacks.</title><description>&lt;VulnDiscussion&gt;DoS is a condition when a resource is not available for legitimate users. Packet flooding distributed denial-of-service (DDoS) attacks are referred to as volumetric attacks and have the objective of overloading a network or circuit to deny or seriously degrade performance, which denies access to the services that normally traverse the network or circuit. Volumetric attacks have become relatively easy to launch using readily available tools such as Low Orbit Ion Cannon or botnets. 

Measures to mitigate the effects of a successful volumetric attack must be taken to ensure that sufficient capacity is available for mission-critical traffic. Managing capacity may include, for example, establishing selected network usage priorities or quotas and enforcing them using rate limiting, Quality of Service (QoS), or other resource reservation control methods. These measures may also mitigate the effects of sudden decreases in network capacity that are the result of accidental or intentional physical damage to telecommunications facilities (such as cable cuts or weather-related outages).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target VMware NSX-T Tier 1 Gateway RTR</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>VMware NSX-T Tier 1 Gateway RTR</dc:subject><dc:identifier>5454</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001095</ident><fixtext fixref="F-55163r810215_fix">To create a segment QoS profile, do the following:

From the NSX-T Manager web interface, go to Networking &gt;&gt; Segments &gt;&gt; Segment Profiles.

Click "Add Segment Profile" and select "QoS".

Configure a profile name and QoS settings as needed and click "Save".

To apply a QoS profile to a segment do the following:

From the NSX-T Manager web interface, go to Networking &gt;&gt; Segments and edit the target segment.

Expand Segment Profiles and under QoS select the profile previously created and "Save".</fixtext><fix id="F-55163r810215_fix" /><check system="C-55209r810214_chk"><check-content-ref href="VMware_NSX-T_Tier_1_Gateway_RTR_STIG.xml" name="M" /><check-content>From the NSX-T Manager web interface, go to Networking &gt;&gt; Segments.

For every Segment connected to a Tier-1 Gateway, Expand Segment &gt;&gt; Expand Segment Profiles &gt;&gt; Record QOS Segment Profile.

Go to Segment Profiles &gt;&gt; Expand QOS Segment Profile recorded in previous steps.

If there are traffic priorities specified by the Combatant Commands/Services/Agencies needed to ensure sufficient capacity for mission-critical traffic and none are configured, this is a finding.</check-content></check></Rule></Group><Group id="V-251773"><title>SRG-NET-000131-RTR-000035</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251773r810219_rule" weight="10.0" severity="low"><version>T1RT-3X-000084</version><title>The NSX-T Tier-1 Gateway must be configured to have multicast disabled if not in use.</title><description>&lt;VulnDiscussion&gt;A compromised router introduces risk to the entire network infrastructure, as well as data resources that are accessible via the network. The perimeter defense has no oversight or control of attacks by malicious users within the network. Preventing network breaches from within is dependent on implementing a comprehensive defense-in-depth strategy, including securing each device connected to the network. This is accomplished by following and implementing all security guidance applicable for each node type. A fundamental step in securing each router is to enable only the capabilities required for operation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target VMware NSX-T Tier 1 Gateway RTR</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>VMware NSX-T Tier 1 Gateway RTR</dc:subject><dc:identifier>5454</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000381</ident><fixtext fixref="F-55164r810218_fix">To disable Multicast do the following:

From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways and edit the target Tier-1 Gateway.

Expand Multicast and change from "Enabled" to "Disabled" and then click "Save".</fixtext><fix id="F-55164r810218_fix" /><check system="C-55210r810217_chk"><check-content-ref href="VMware_NSX-T_Tier_1_Gateway_RTR_STIG.xml" name="M" /><check-content>From the NSX-T Manager web interface, go to Networking &gt;&gt; Tier-1 Gateways.

For every Tier-1 Gateway, expand the Tier-1 Gateway then expand Multicast to view the Multicast configuration.

If Multicast is enabled and not in use, this is a finding.</check-content></check></Rule></Group></Benchmark>