Elastic Security Detection Rules

Inbound Connection to an Unsecure Elasticsearch Node

Last updated 7 months ago on 2025-01-15
Created 5 years ago on 2020-08-11

About

Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS), and/or lack authentication, and are accepting inbound network connections over the default Elasticsearch port.
Tags
Use Case: Threat DetectionTactic: Initial AccessDomain: EndpointLanguage: lucene
Severity
medium
Risk Score
47
MITRE ATT&CK™

Initial Access (TA0001)(opens in a new tab or window)

↳ Exploit Public-Facing Application (T1190)(opens in a new tab or window)

False Positive Examples
If you have front-facing proxies that provide authentication and TLS, this rule would need to be tuned to eliminate the source IP address of your reverse-proxy.
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
packetbeat-*logs-network_traffic.*
Related Integrations

network_traffic(opens in a new tab or window)

Query
(event.dataset: network_traffic.http OR (event.category: network_traffic AND network.protocol: http)) AND
    status:OK AND destination.port:9200 AND network.direction:inbound AND NOT http.response.headers.content-type:"image/x-icon" AND NOT
    _exists_:http.request.headers.authorization

Install detection rules in Elastic Security

Detect Inbound Connection to an Unsecure Elasticsearch Node 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).