More Info:
Any expired domain names registered with AWS Route 53 should be identified and restored. The restoration fee will be charged to your AWS account and you will get a confirmation email once the registration process is completed.Risk Level
HighAddress
Reliability, SecurityCompliance Standards
- APRA CPS 234 (Australia)
- BSI C5 (Germany)
- Brazil LGPD
- CCPA / CPRA (California)
- CIS Critical Security Controls v8
- CMMC 2.0
- CSA Cloud Controls Matrix v4
- Cloudanix Best Practice
- DPDPA
- Digital Operational Resilience Act (EU)
- ISO/IEC 27017
- ISO/IEC 27018
- ISO/IEC 27701
- KSA PDPL
- MAS Technology Risk Management (Singapore)
- MITRE ATT&CK (Cloud)
- NIST SP 800-171
- NYDFS 23 NYCRR 500
- SWIFT Customer Security Controls Framework
- Sarbanes-Oxley IT General Controls
- UK NCSC Cyber Assessment Framework
Triage and Remediation
- Remediation
Remediation
Using Console
Using Console
To remediate the misconfiguration of Route 53 not identifying any expired domains in AWS, you can follow the below steps:
- Log in to the AWS Management Console and navigate to the Route 53 service.
- Click on the “Registered domains” option in the left-hand menu.
- In the list of registered domains, identify the domain that is expired and select it.
- Click on the “Renew domain registration” button in the top-right corner of the page.
- Follow the on-screen instructions to complete the domain renewal process.
- Once the domain is renewed, Route 53 will automatically start identifying it again.
Using CLI
Using CLI
To remediate the misconfiguration in AWS Route 53 using AWS CLI, follow these steps:Replace Replace This command should not return any records for the expired domain.By following these steps, you can remediate the misconfiguration in AWS Route 53 and ensure that any expired domains are identified and deleted.
- Open the AWS CLI on your local system or EC2 instance.
- Run the following command to list all the hosted zones in your AWS account:
- Identify the hosted zone that contains the expired domain.
- Run the following command to get the details of the expired domain:
<hosted-zone-id> with the ID of the hosted zone that contains the expired domain and <expired-domain-name> with the name of the expired domain.- If the output of the above command returns any records for the expired domain, run the following command to delete those records:
<hosted-zone-id> with the ID of the hosted zone that contains the expired domain, <expired-domain-name> with the name of the expired domain, <record-type> with the type of record that needs to be deleted (e.g. A, CNAME, MX, etc.), <ttl> with the TTL value of the record, and <record-value> with the value of the record.- Verify that the expired domain records have been deleted by running the following command:
Using Python
Using Python
To remediate the misconfiguration in AWS Route 53 using Python, follow the below steps:Step 1: Install and configure the AWS CLI on your local machine.Step 2: Create a Python script that uses the boto3 library to interact with AWS Route 53.Step 3: Use the Note: This script assumes that the
list_hosted_zones() method to get a list of all the hosted zones in your AWS account.Step 4: Loop through the hosted zones and use the list_resource_record_sets() method to get a list of all the resource record sets in each hosted zone.Step 5: Check the Expiration field of each resource record set to see if it is expired.Step 6: If a resource record set is expired, use the change_resource_record_sets() method to delete the record set.Step 7: Save and run the Python script.Here is a sample Python script that you can use as a starting point:Expiration field is already set in the resource record sets. If it is not set, you may need to modify the script to check for other indicators of expiration.Using Terraform
Using Terraform
Terraform cannot renew or restore Route 53 registered domains; the AWS provider does not expose a If the status in
renew-domain or equivalent operation, so this remediation must be done via CLI or console.To match the verified CLI fix, use the AWS CLI:StatusList is redemptionPeriod, follow the AWS console/docs to restore via the more complex update-domain-contact flow. Renewing or restoring will incur costs billed to your AWS account.
