Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
account_maintain_different_contact_details_to_security_billing_and_operationsProvider: AWS
Service:
accountSeverity: MEDIUM
Categories:
resilienceResource type:
OtherWhat this check verifies
AWS account alternate contacts are defined for Security, Billing, and Operations withname, email, and phone. The finding evaluates that all three exist, are distinct from one another, and differ from the primary (root) contact.
Risk
Missing or shared contacts can delay response to abuse alerts, credential compromise, or billing anomalies, reducing availability (possible AWS traffic throttling) and raising confidentiality and integrity risk through extended exposure. If AWS cannot reach you, urgent mitigation may disrupt service.Recommendation
Maintain distinct, monitored Security, Billing, and Operations alternate contacts that differ from the root contact.- Use team aliases and 24x7 phones
- Review and test contact paths regularly
- Centralize at org level for consistency
Remediation
- Terraform
- Dashboard steps
References
- https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/account_alternate_contact
- https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-update-contact-alternate.html
- https://builder.aws.com/content/2qRw97fe8JFwfk2AbpJ3sYNpNvM/aws-bulk-update-alternate-contacts-across-organization
- https://github.com/aws-samples/aws-account-alternate-contact-with-terraform
- https://trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/IAM/account-security-alternate-contacts.html
- https://repost.aws/articles/ARDFbpt-bvQ8iuErnqVVcCXQ/managing-aws-organization-alternate-contacts-via-csv
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = account_maintain_different_contact_details_to_security_billing_and_operations. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks