OpenSearch domain allows TLS 1.0

Severity
Low
Service
OpenSearch
Check ID
ES_TLS_POLICY_WEAK

What this check finds

The domain endpoint TLS security policy is Policy-Min-TLS-1-0-2019-07, which accepts the deprecated TLS 1.0 and 1.1.

Passing looks like: OpenSearch domains require TLS 1.2 or later.

How to fix it

Set the TLS security policy to Policy-Min-TLS-1-2-2019-07 or later.

AWS CLI

  1. aws opensearch update-domain-config --domain-name DOMAIN --domain-endpoint-options TLSSecurityPolicy=Policy-Min-TLS-1-2-2019-07

Names in capitals are placeholders for your own resource. Review a command before you run it.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to OpenSearch domain allows TLS 1.0
FrameworkControls
PCI-DSS v4.0.1
  • 4.2 PAN is protected with strong cryptography during transmission over open, public networks
NIST SP 800-53 Rev5 (Moderate)
  • SC-8 Transmission Confidentiality and Integrity
  • SC-23 Session Authenticity
NIST Cybersecurity Framework 2.0
  • PR.DS-02 Data-in-transit is protected
ISO/IEC 27001:2022 Annex A
  • A.8.24 Use of cryptography

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More OpenSearch checks

All OpenSearch checks

Find out what is actually exposed in your AWS environment.

Connect one AWS account and run your first security assessment.

No credit card · Agentless · Read-only