Unrestricted inbound Elasticsearch access
Incident Management が一般に使用できるようになりました。 Incident Management が広範に使用できるようになりました。
<  Back to rules search

Unrestricted inbound Elasticsearch access

ec2

Classification:

compliance

Set up the ec2 integration.

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Overview

Description

Reduce the probability of a breach by checking EC2 security groups for inbound rules that allow unfettered access to TCP port 9200, used by the Elasticsearch, and restrict access to IP addresses that require this port.

Rationale

Malicious activity, such as denial-of-service (DoS) attacks and hacking, can occur when permitting unfettered Elasticsearch access.

Remediation

  1. First, remove the security group rule(s) that allow public, unrestricted access to the Elasticsearch database. The rule in question will open port 9200 for ingress from anywhere.

  2. Now that the database is contained, authorize only the specific entities that need access to the database like EC2 instances, or lambdas. You can do this by adding inbound security group rules for a specific elastic IP address, a specific range of IP addresses, or by allowing access for entities in another AWS security group.