Potential Non-Standard Port HTTP/HTTPS connection

Last updated 9 days ago on 2025-01-22

Created 2 years ago on 2023-07-10

About

Identifies potentially malicious processes communicating via a port paring typically not associated with HTTP/HTTPS. For example, HTTP over port 8443 or port 440 as opposed to the traditional port 80 , 443. Adversaries may make changes to the standard port a protocol uses to bypass filtering or muddle analysis/parsing of network data.

Tags

Domain: EndpointOS: LinuxOS: macOSUse Case: Threat DetectionTactic: Command and ControlRule Type: BBRData Source: Elastic DefendData Source: Elastic EndgameLanguage: eql

Severity

low

Risk Score

MITRE ATT&CK™

Command and Control (TA0011)(opens in a new tab or window)

↳ Application Layer Protocol (T1071)(opens in a new tab or window)

↳ Non-Standard Port (T1571)(opens in a new tab or window)

↳ Encrypted Channel (T1573)(opens in a new tab or window)

License

Elastic License v2(opens in a new tab or window)

Definition

Rule Type: Event Correlation Rule
Integration Pack: Prebuilt Security Detection Rules
Index Patterns: logs-endpoint.events.*endgame-*
Related Integrations: endpoint(opens in a new tab or window)
Query

network where process.name : ("http", "https") and destination.port not in (80, 443) and event.action in (
  "connection_attempted", "ipv4_connection_attempt_event", "connection_accepted", "ipv4_connection_accept_event"
) and destination.ip != "127.0.0.1"

Install detection rules in Elastic Security

Detect Potential Non-Standard Port HTTP/HTTPS connection in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).