DETECTION OVERVIEW
Risk Factors
Protocols are assigned to standard ports by the Internet Assigned Numbers Authority (IANA) to help identify different types of traffic. For example, HTTP protocol traffic is often assigned to standard ports 80 or 443. Remote service protocols are also assigned to standard ports, such as RDP:3389 and SSH:22. Traffic on standard ports is often allowed to pass through firewalls. Attackers who want to evade detection can configure external servers, or proxies, to listen for protocol traffic on unusual, non-standard ports. For example, RDP traffic can be exchanged on port 80, helping the malicious traffic blend in with HTTP traffic.
The system might change the risk score for this detection.
Category

N/A
Investigate unusual or unexpected activity associated with remote service protocols
Network analysis and visibility solutions remain underrepresented in enterprises. Find out why in this preview of a new Wave report.
ExtraHop® Named a Leader in First-Ever Gartner® Magic Quadrant™ for Network Detection and Response
Visit this resource for more information.
This analysis exposes the critical link between an organization's lack of internal visibility and the escalating cost of compromise, demanding an urgent re-evaluation of how core business assets are protected.
Learn why you need to be wary of the claims certain network detection and response providers make about their coverage against the MITRE ATT&CK framework.
Learn how NDR from RevealX helps security teams detect and investigate more adversary TTPs in the MITRE ATT&CK framework than rule-based tools.
