To ensure compliance and security of your Elastic MapReduce (EMR) clusters, it is important to implement data encryption. This will help prevent unauthorized access to sensitive data stored on your EMR clusters and their associated data storage systems, including data at-rest and data in-transit, which can be intercepted as it travels through the network. Compliance requirements may include protecting sensitive data that could potentially identify a specific individual, such as Personally Identifiable Information (PII), which is commonly found in industries such as Financial Services, Healthcare, and Telecommunications.When dealing with production data, it is highly recommended to use encryption to protect it from unauthorized access and meet compliance requirements for data-at-rest and in-transit encryption within your organization. ‍


To ensure that EMR clusters are encrypted in-transit and at-rest, you can take the following remediation steps:

  1. Enable encryption in-transit - Configure SSL/TLS for encrypting network traffic between EMR components, including the master node, core nodes, and task nodes.
  2. Enable encryption at-rest - Use server-side encryption to encrypt data stored in EMR cluster's HDFS or other data storage systems, such as Amazon S3 or EBS volumes.
  3. Use encryption-compatible storage systems - Use storage systems that are compatible with encryption, such as Amazon S3 with server-side encryption or EBS volumes with encryption.
  4. Use appropriate encryption algorithms and key management - Use appropriate encryption algorithms and key management to ensure the security and confidentiality of data in-transit and at-rest.
  5. Verify compliance with relevant regulations - Verify compliance with relevant regulations such as HIPAA, PCI-DSS, and GDPR that require encryption of data-at-rest and in-transit.

By following these remediation steps, you can ensure that your EMR clusters are properly encrypted in-transit and at-rest and meet the necessary security and compliance requirements.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.