Merge pull request #108768 from memildin/asc-melvyn-20200129

Removed invalid ANH table

Author: PMEds28

articles/security-center/index.yml

@@ -36,8 +36,8 @@ landingContent:
         links:
           - text: Protect your containers
             url: container-security.md
-          - text: Add dynamic compliance packages
-            url: update-regulatory-compliance-packages.md
+          - text: Integrated vulnerability assessment for VMs
+            url: built-in-vulnerability-assessment.md
           - text: Review the schemas for security alerts 
             url: alerts-schemas.md
           - text: Automate responses to alerts and recommendations

articles/security-center/security-center-adaptive-network-hardening.md

@@ -27,7 +27,7 @@ Adaptive Network Hardening provides recommendations to further harden the NSG ru
 For example, let's say the existing NSG rule is to allow traffic from 140.20.30.10/24 on port 22. The Adaptive Network Hardening's recommendation, based on the analysis, would be to narrow the range and allow traffic from 140.23.30.10/29 – which is a narrower IP range, and deny all other traffic to that port.
 
 >[!TIP]
-> Adaptive Network Hardening recommendations are only supported on specific ports. For the full list, see [Which ports are supported?](#which-ports-are-supported) below. 
+> Adaptive Network Hardening recommendations are only supported on the following specific ports (for both UDP and TCP): 13, 17, 19, 22, 23, 53, 69, 81, 111, 119, 123, 135, 137, 138, 139, 161, 162, 389, 445, 512, 514, 593, 636, 873, 1433, 1434, 1900, 1900, 2049, 2301, 2323, 2381, 3268, 3306, 3389, 4333, 5353, 5432, 5555, 5800, 5900, 5900, 5985, 5986, 6379, 6379, 7000, 7001, 7199, 8081, 8089, 8545, 9042, 9160, 9300, 11211, 16379, 26379, 27017, 37215
 
 
 ![Network hardening view](./media/security-center-adaptive-network-hardening/traffic-hardening.png)
@@ -135,74 +135,4 @@ When necessary, you can delete a recommended rule for the current session. For e
 
 1. In the **Rules** tab, click on the three dots (...) at the end of the rule's row, and click **Delete**.  
 
-    ![hardening rules](./media/security-center-adaptive-network-hardening/delete-hard-rule.png)
-
- 
-
-## Which ports are supported?
-
-Adaptive Network Hardening recommendations are only supported on specific ports. This table gives you the full list:
-
-|Port|Protocol|Associated Service|
-|:---:|:----:|:----|
-|13|UDP|Daytime service|
-|17|UDP|QOTD protocol|
-|19|UDP|CHARGEN protocol|
-|22|TCP|SSH|
-|23|TCP|Telnet|
-|53|UDP|DNS|
-|69|UDP|TFTP|
-|81|TCP|Potentially malicious (TOR exit node)|
-|111|TCP/UDP|RPC|
-|119|TCP|NNTP|
-|123|UDP|NTP|
-|135|TCP/UDP|Endpoint Mapper; RPC; DCE|
-|137|TCP/UDP|NetBIOS Name Service|
-|138|TCP/UDP|NetBIOS Datagram Service|
-|139|TCP|NetBIOS Session Service|
-|161|TCP/UDP|SNMP|
-|162|TCP/UDP|SNMP|
-|389|TCP|LDAP|
-|445|TCP|SMB|
-|512|TCP|Rexec|
-|514|TCP|Remote shell|
-|593|TCP/UDP|HTTP RPC|
-|636|TCP|LDAP|
-|873|TCP|Rsync|
-|1433|TCP|MS SQL|
-|1434|UDP|MS SQL|
-|1900|UDP|SSDP|
-|1900|UDP|SSDP|
-|2049|TCP/UDP|NFS|
-|2301|TCP|Compaq management service|
-|2323|TCP|3d-nfsd|
-|2381|TCP|Compaq management service|
-|3268|TCP|LDAP|
-|3306|TCP|MySQL|
-|3389|TCP|RDP|
-|4333|TCP|mSQL|
-|5353|UDP|mDNS|
-|5432|TCP|PostgreSQL|
-|5555|TCP|Personal Agent; HP OmniBack|
-|5800|TCP|VNC|
-|5900|TCP|Remote framebuffer; VNC|
-|5900|TCP|VNC|
-|5985|TCP|Windows PowerShell|
-|5986|TCP|Windows PowerShell|
-|6379|TCP|Redis|
-|6379|TCP|Redis|
-|7000|TCP|Cassandra|
-|7001|TCP|Cassandra|
-|7199|TCP|Cassandra|
-|8081|TCP|CosmosDB; Sun Proxy Admin|
-|8089|TCP|Splunk|
-|8545|TCP|Potentially malicious (Cryptominer)|
-|9042|TCP|Cassandra|
-|9160|TCP|Cassandra|
-|9300|TCP|Elasticsearch|
-|11211|UDP|Memcached|
-|16379|TCP|Redis|
-|26379|TCP|Redis|
-|27017|TCP|MongoDB|
-|37215|TCP|Potentially malicious|
-||||
+    ![hardening rules](./media/security-center-adaptive-network-hardening/delete-hard-rule.png)