- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Use a secure protocol and cipher to protect communication between the client and your Classic Elastic Load Balancers (ELBs). TLS 1.0 and 1.1 are vulnerable to attacks due to multiple insecurities, for this reason we recommend the use of ELBSecurityPolicy-TLS-1-2-2017-01
which authorizes TLS 1.2.
Insecure communication channels increase the risk of attacks, such as man-in-the-middle, downgrade attacks, and sensitive data breaches. It is recommended to configure listeners to use HTTPS, or SSL, and ELBSecurityPolicy-TLS-1-2-2017-01
, or a custom policy with an equivalent or more secure configuration. TLS on port 443 will generate a pass
condition for this rule only if a secure policy is attached to the listener.
This configuration check tests for a listener configured using HTTPS, SSL, or TLS on port 443, as well as for the absence of ciphers and protocols for secure listener configurations that are not recommended by AWS.
It is recommended to modify listeners configured to use TLS on port 443, to HTTPS on port 443, and select a secure policy.
ELBSecurityPolicy-TLS-1-2-2017-01
or a Custom Security Policy that is as or more secure.ELBSecurityPolicy-TLS-1-2-2017-01
or a Custom Security Policy that is as or more secure.