More Info:

This rule checks if Amazon EMR clusters have Kerberos enabled. It is marked as NON_COMPLIANT if a security configuration is not attached to the cluster or if the security configuration does not satisfy the specified rule parameters.

Risk Level

Medium

Address

Security

Compliance Standards

CBP,RBI_MD_ITF

Triage and Remediation

Remediation

To remediate the misconfiguration of not having Kerberos enabled for Amazon EMR clusters in AWS Redshift using the AWS console, follow these steps:

  1. Login to AWS Console: Go to the AWS Management Console and login with your credentials.

  2. Navigate to Amazon Redshift Console: Click on the “Services” dropdown menu at the top left corner, then select “Redshift” under the Analytics section.

  3. Select your Redshift Cluster: From the list of clusters, select the Redshift cluster for which you want to enable Kerberos.

  4. Modify Cluster: Click on the cluster identifier to open the cluster details. In the cluster details page, click on the “Modify” button.

  5. Enable Kerberos Authentication: Scroll down to the “Security and Access Control” section in the Modify Cluster page.

  6. Enable Kerberos: Under the “Authentication” section, select “Kerberos” as the authentication type. You will need to provide the Kerberos server details such as KDC server hostname, realm, and other relevant information.

  7. Save Changes: After providing the necessary Kerberos authentication details, scroll down to the bottom of the page and click on the “Modify Cluster” button to save the changes.

  8. Verify Kerberos Configuration: Once the modification is completed, verify that Kerberos authentication is successfully enabled for the Redshift cluster.

By following these steps, you can remediate the misconfiguration of not having Kerberos enabled for Amazon EMR clusters in AWS Redshift using the AWS console.