Overview
Overview
+Registering a dedicated security contact ensures AWS security notifications reach the right team quickly.
Remediation guidance
AWS remediation
+### Console +1. Sign in as root user or delegated account administrator. +2. Open AWS Account settings and locate Alternate contacts. +3. Set Security contact email/phone for your security team mailbox. +4. Confirm contact is monitored and part of incident response workflows. + +### AWS CLI +~~~bash +aws account put-alternate-contact \
- --alternate-contact-type SECURITY \
- --email-address [email protected] \
- --name "Security Team" \
- --phone-number "+1-000-000-0000" \
- --title "Security" +~~~
+### References +- https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-update-contact-alternate.html +- https://docs.aws.amazon.com/cli/latest/reference/account/put-alternate-contact.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
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
No stored query bodies are attached to this entry.
