# 1.1 Maintain Current Contact Details (Manual) - Source: https://support.icompaas.com/support/solutions/articles/62000233102-1-1-maintain-current-contact-details-manual- - Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS CIS V.4 Level 1 Benchmarks](https://support.icompaas.com/support/solutions/62000112671) › [CIS Control 1](https://support.icompaas.com/support/solutions/folders/62000169194) - Last updated: 2026-05-29 - Publisher: iCompaas, Inc. (https://www.icompaas.com) ### **Profile Applicability:** **Level 1** ## **Description:** Ensure that the contact email and telephone details for AWS accounts are up-to-date and mapped to more than one individual in the organization. AWS will use these contact details to notify the account owner if the AWS Abuse team detects a breach of the Acceptable Use Policy or a security compromise. Contact details should not belong to a single individual, as they may become unavailable. Instead, contact details should be configured as follows: - Email Address: Use a mail alias that forwards notifications to multiple individuals. - Phone Contact: Use a PABX hunt group or call-forwarding system for redundancy. ## Rationale: If an AWS account is exhibiting prohibited or suspicious behavior, AWS will attempt to contact the account owner via the listed email and phone number. If AWS cannot establish contact and urgent mitigation is required, AWS may: - Throttle traffic between the account and AWS API endpoints. - Restrict Internet access to mitigate potential threats. This could result in service disruptions. Ensuring that multiple responsible individuals can be contacted promptly prevents downtime and security escalations. ## Impact: - Failure to maintain current contact details can result in AWS taking proactive security measures, including throttling or blocking network traffic. - Delays in security incident response due to unmonitored or outdated contact details. - Non-compliance with security policies, leading to increased business risks. ## Default Value: By default, AWS requires contact details during account creation. However, these details may become outdated over time unless periodically reviewed and updated. ## Pre-Requisites: 1. AWS Account Access: - IAM user with Billing permissions (aws-portal:\*Billing). 2. List of Contact Details: - Ensure an updated email alias is available. - Ensure a functional phone contact (PABX or forwarding enabled). 3. Organization Approval: - Verify who should receive AWS notifications. ## Remediation: Test Plan: Using AWS Console 1. Sign in to the AWS Management Console.                 ![](https://support.icompaas.com/assets/kb/2690793a96e7c9fa.png) 2. Open the Billing and Cost Management console: [AWS Billing Console](https://console.aws.amazon.com/billing/home#/)                     ![](https://support.icompaas.com/assets/kb/f95121621f962f80.png) 3. In the navigation bar, select your account name, then click Account.                   ![](https://support.icompaas.com/assets/kb/ce9e3d4feabf622d.png) 4. On the Account Settings page, review the current details: - Email address (ensure it is an alias).                       ![](https://support.icompaas.com/assets/kb/b4a1d7fc123a10ff.png) - Phone number (ensure it is not linked to a single individual).                          ![](https://support.icompaas.com/assets/kb/e0883433a2d6d481.png) ## Implementation Steps: ## Using AWS Console 1. Sign in to the AWS Management Console. 2. Open the Billing and Cost Management console: [AWS Billing Console](https://console.aws.amazon.com/billing/home#/).                    ![](https://support.icompaas.com/assets/kb/5c17b95473f78586.png) 3. Select your account name, then choose Account.                      ![](https://support.icompaas.com/assets/kb/533601c8d83d712a.png) 4. On the Account Settings page, locate Account Settings.                  ![](https://support.icompaas.com/assets/kb/5fb888d6ef1f78e9.png) 5. Click Edit next to the required field.             ![](https://support.icompaas.com/assets/kb/bde55ca3b2e72e05.png) 6. Update the following fields: - Email address (use an alias, e.g., aws-security@yourcompany.com). - Phone number (use a PABX hunt group if possible). 7. Click Save Changes.              ![](https://support.icompaas.com/assets/kb/3aee53e6c2ef8611.png) 8. Click Done. ## Backout Plan: - If the updated information is incorrect: 1. Return to Account Settings in the Billing and Cost Management console.         ![](https://support.icompaas.com/assets/kb/51315cf370287844.png) 2. Re-enter the previous contact details.               ![](https://support.icompaas.com/assets/kb/2335db4f8bbcb41a.png) 3. Save changes and validate email and phone responses.               ![](https://support.icompaas.com/assets/kb/415743d37dc38583.png) ## References: - [AWS Account Billing and Contact Management Documentation](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-account-payment.html#contact-info) ## CIS Controls Mapping:

CIS Control Version

Control ID

Control Description

CIS v8

17.2

Establish and maintain contact information for reporting security incidents. Verify contacts annually to ensure accuracy.

CIS v7

19.3

Designate management personnel and backups to support incident handling.

## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.