IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« ImageLoad via Windows Update Auto Update Client Incoming DCOM Lateral Movement via MSHTA »
Elastic Docs ›Elastic Security Solution [8.4] ›Detections and alerts ›Prebuilt rule reference

Inbound Connection to an Unsecure Elasticsearch Node

edit

Inbound Connection to an Unsecure Elasticsearch Node

edit

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.

Rule type: query

Rule indices:

  • auditbeat-*
  • filebeat-*
  • packetbeat-*
  • logs-endpoint.events.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Network
  • Threat Detection
  • Initial Access
  • Host

Version: 7 (version history)

Added (Elastic Stack release): 7.10.0

Last modified (Elastic Stack release): 8.4.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

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.

Investigation guide

edit











Rule query
edit








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











Threat mapping
edit




Framework: MITRE ATT&CKTM














Rule version history
edit










Version 7 (8.4.0 release)








    

  • 
Formatting only

    • 









Version 5 (7.14.0 release)








    

  • 

    Updated query, changed from:
    

    

    

    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
    

    

    • 









Version 4 (7.13.0 release)








    

  • 
Formatting only

    • 









Version 3 (7.12.0 release)








    

  • 
Formatting only

    • 









Version 2 (7.11.2 release)








    

  • 
Formatting only

    • 




















« ImageLoad via Windows Update Auto Update Client


Incoming DCOM Lateral Movement via MSHTA »