Skip to main content

🛡️ AWS ElastiCache Replication Group is not encrypted in-transit🟢

  • Contextual name: 🛡️ Replication Group is not encrypted in-transit🟢
  • ID: /ce/ca/aws/elasticache/replication-group-in-transit-encryption
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Logic​

Similar Policies​

Description​

Open File

Description​

This policy identifies AWS ElastiCache Replication Groups that are not configured to enforce encryption of data in-transit. Encryption in-transit ensures that all communication to and from the Redis cluster is protected using Transport Layer Security (TLS).

Rationale​

Enabling in-transit encryption protects data while it moves over the network. Without it, sensitive information exchanged between your applications and the Redis cluster could be intercepted by unauthorized parties.

Enforcing TLS mitigates the risk of eavesdropping and man-in-the-middle (MITM) attacks, ensuring both the confidentiality and integrity of your data, especially in environments where network traffic traverses untrusted networks.

Audit​

This policy flags an AWS ElastiCache Replication Group as INCOMPLIANT if the Transit Encryption Enabled checkbox is set to false.

The Replication Group is marked as INAPPLICABLE if its Status is not available.

Remediation​

Open File

Remediation​

Enable In-Transit Encryption on an Existing Replication Group​

Enabling in-transit encryption for an existing ElastiCache replication group is a two-step process. You must first set the transit encryption mode to preferred, which allows both encrypted and unencrypted connections. After all clients are migrated to use encrypted connections, you can then set the mode to required, which enforces encrypted connections only.

From Command Line​

  1. Set transit encryption mode to preferred

    This step enables in-transit encryption and allows clients to connect using both encrypted and unencrypted connections:

    aws elasticache modify-replication-group \
      --replication-group-id {{replication-group-id}} \
      --transit-encryption-enabled \
      --transit-encryption-mode preferred \
      --apply-immediately

    Wait for the replication group to finish updating before proceeding to the next step.

  2. Migrate all clients to use encrypted connections.

  3. Set transit encryption mode to required

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.5] ElastiCache replication groups should be encrypted in transit1no data
💼 AWS Well-Architected → 💼 SEC08-BP02 Enforce encryption at rest14no data
💼 Cloudaware Framework → 💼 Data Encryption54no data
💼 FedRAMP High Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)23785no data
💼 FedRAMP High Security Controls → 💼 AC-17(2) Protection of Confidentiality and Integrity Using Encryption (M)(H)18no data
💼 FedRAMP High Security Controls → 💼 IA-5(1) Password-based Authentication (L)(M)(H)19no data
💼 FedRAMP High Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)31no data
💼 FedRAMP High Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)1819no data
💼 FedRAMP High Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)818no data
💼 FedRAMP High Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)1632no data
💼 FedRAMP High Security Controls → 💼 SC-23 Session Authenticity (M)(H)715no data
💼 FedRAMP Low Security Controls → 💼 IA-5(1) Password-based Authentication (L)(M)(H)9no data
💼 FedRAMP Low Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)119no data
💼 FedRAMP Low Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)18no data
💼 FedRAMP Low Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)32no data
💼 FedRAMP Moderate Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)169no data
💼 FedRAMP Moderate Security Controls → 💼 AC-17(2) Protection of Confidentiality and Integrity Using Encryption (M)(H)18no data
💼 FedRAMP Moderate Security Controls → 💼 IA-5(1) Password-based Authentication (L)(M)(H)9no data
💼 FedRAMP Moderate Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)31no data
💼 FedRAMP Moderate Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)119no data
💼 FedRAMP Moderate Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)18no data
💼 FedRAMP Moderate Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)32no data
💼 FedRAMP Moderate Security Controls → 💼 SC-23 Session Authenticity (M)(H)15no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events145no data
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained72no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected159no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected135no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected151no data
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage98no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-4 Information Flow Enforcement326995no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-17(2) Remote Access _ Protection of Confidentiality and Integrity Using Encryption1218no data
💼 NIST SP 800-53 Revision 5 → 💼 IA-5(1) Authenticator Management _ Password-based Authentication9no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(4) Boundary Protection _ External Telecommunications Services31no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-8 Transmission Confidentiality and Integrity5818no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-8(1) Transmission Confidentiality and Integrity _ Cryptographic Protection817no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-8(2) Transmission Confidentiality and Integrity _ Pre- and Post-transmission Handling9no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-12(3) Cryptographic Key Establishment and Management _ Asymmetric Keys7no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-13 Cryptographic Protection421no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-23 Session Authenticity59no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-23(3) Session Authenticity _ Unique System-generated Session Identifiers8no data
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(6) Software, Firmware, and Information Integrity _ Cryptographic Protection19no data
💼 PCI DSS v3.2.1 → 💼 4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during transmission over open, public networks.1824no data
💼 PCI DSS v4.0.1 → 💼 4.2.1 Strong cryptography and security protocols are implemented to safeguard PAN during transmission over open, public networks.224no data
💼 PCI DSS v4.0 → 💼 4.2.1 Strong cryptography and security protocols are implemented to safeguard PAN during transmission over open, public networks.2924no data