Skip to content

Commit fa34190

Browse files
Update understanding-asset-details.md
1 parent fd68e50 commit fa34190

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/external-attack-surface-management/understanding-asset-details.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ This section displays any name servers that are running on the asset to provide
177177

178178
This section lists any open ports detected on the asset. Microsoft regularly scans around 230 distinct ports. This data is useful to identify any unsecured services that shouldn't be accessible from the open internet. These services include databases, IoT devices, and network services like routers and switches. It's also helpful in identifying shadow IT infrastructure or insecure remote access services.
179179

180-
In this section, Defender EASM provides the open port number, a description of the port, the last state it was observed in, and the **First seen** and **Last seen** dates. The **Recent** column indicates whether the port was observed as open during the most recent scan.
180+
In this section, Defender EASM provides the open port number, a description of the port, the last state it was observed in, and the **First seen** and **Last seen** dates. The **Recent** column indicates whether the port was observed as open during the most recent scan. Defender EASM considers a port “open” when our system can successfully complete a syn-ack handshake that results in attributed banners. When we can establish a TCP connection but are unable to complete our service fingerprinting, we mark the port as “filtered”. A "closed" port is still accessible but there is no service listening on the port and thus denies connections.
181181

182182
![Screenshot that shows the asset details page Open ports section of the Services tab.](media/Inventory_9.png)
183183

0 commit comments

Comments
 (0)