Maintain current contact details

AWS remediation

+### Console +1. Sign in as the account root user. +2. Open AWS Account settings. +3. Update primary contact details (name, email, phone, address). +4. Save and periodically re-validate details. + +### AWS CLI +~~~bash +aws account put-contact-information \

• --contact-information file://contact-information.json +~~~

+Example file: +~~~json +{

• "FullName": "Security Team",
• "AddressLine1": "Street 1",
• "City": "City",
• "StateOrRegion": "State",
• "DistrictOrCounty": "County",
• "PostalCode": "00000",
• "CountryCode": "US",
• "PhoneNumber": "+1-000-000-0000",
• "CompanyName": "Example",
• "WebsiteUrl": "https://example.com" +} +~~~

+### References +- https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-update-contact.html +- https://docs.aws.amazon.com/cli/latest/reference/account/put-contact-information.html

Service-wide remediation

Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.

Platform

Use the provider or platform baseline, preventive policy, and IaC modules to enforce this setting consistently when many resources are affected.

Operational rollout

1. Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
2. Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
3. Re-scan and track approved exceptions with an owner and expiry date.