📝 Google Organization Essential Contacts is not configured 🟢

• Contextual name: 📝 Organization Essential Contacts is not configured 🟢
• ID: /ce/ca/google/iam/essential-contacts-for-organization
• Located in: 📁 Google IAM

Flags

• 🟢 Policy with categories
• 🟢 Policy with type
• 🟢 Production policy

Our Metadata

• Policy Type: COMPLIANCE_POLICY
• Policy Category:
  • SECURITY

Similar Policies

• Cloud Conformity
  • Configure Essential Contacts for Organizations

Logic

• 🧠 prod.logic.yaml 🟢
  • 📗 Google Resource Manager Organization
  • 🔌 Google Resource Manager Organization - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

It is recommended that Essential Contacts is configured to designate email addresses for Google Cloud services to notify of important technical or security information.

Rationale

Many Google Cloud services, such as Cloud Billing, send out notifications to share important information with Google Cloud users. By default, these notifications are sent to members with certain Identity and Access Management (IAM) roles. With Essential Contacts, you can customize who receives notifications by providing your own list of contacts.

Impact

There is no charge for Essential Contacts except for the 'Technical Incidents' category that is only available to premium support customers.

Audit

From Google Cloud Console

1. Go to Essential Contacts by visiting https://console.cloud.google.com/iam-admin/essential-contacts
2. Make sure the organization appears in the resource selector at the top of the page. The resource selector tells you what project, folder, or organization you are currently managing contacts for.

... see more

Remediation

Open File

Remediation

From Google Cloud Console

1. Go to Essential Contacts by visiting https://console.cloud.google.com/iam-admin/essential-contacts
2. Make sure the organization appears in the resource selector at the top of the page. The resource selector tells you what project, folder, or organization you are currently managing contacts for.
3. Click +Add contact
4. In the Email and Confirm Email fields, enter the email address of the contact.
5. From the Notification categories drop-down menu, select the notification categories that you want the contact to receive communications for.
6. Click Save

From Google Cloud CLI

1. To add an organization Essential Contacts run a command:

   gcloud essential-contacts create --email="<EMAIL>" \

   --notification-categories="<NOTIFICATION_CATEGORIES>" \

   --organization=<ORGANIZATION_ID>

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS GCP v1.3.0 → 💼 1.16 Ensure Essential Contacts is Configured for Organization - Level 1 (Automated)			1
💼 CIS GCP v2.0.0 → 💼 1.16 Ensure Essential Contacts is Configured for Organization - Level 1 (Automated)			1
💼 CIS GCP v3.0.0 → 💼 1.16 Ensure Essential Contacts is Configured for Organization - Level 1 (Automated)			1
💼 Cloudaware Framework → 💼 General Access Controls			11
💼 FedRAMP High Security Controls → 💼 IR-6 Incident Reporting (L)(M)(H)	2	10	13
💼 FedRAMP Low Security Controls → 💼 IR-6 Incident Reporting (L)(M)(H)			1
💼 FedRAMP Moderate Security Controls → 💼 IR-6 Incident Reporting (L)(M)(H)	2		13
💼 ISO/IEC 27001:2022 → 💼 5.5 Contact with authorities		2	3
💼 ISO/IEC 27001:2022 → 💼 5.6 Contact with special interest		2	3
💼 ISO/IEC 27001:2022 → 💼 5.20 Addressing information security within supplier agreements		2	3
💼 ISO/IEC 27001:2022 → 💼 5.24 Information security incident management planning and preparation		2	3
💼 NIST CSF v1.1 → 💼 RS.CO-1: Personnel know their roles and order of operations when a response is needed			1
💼 NIST CSF v2.0 → 💼 PR.AT-01: Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind			8
💼 NIST CSF v2.0 → 💼 RC.CO-03: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders			1
💼 NIST CSF v2.0 → 💼 RS.AN-06: Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved			18
💼 NIST CSF v2.0 → 💼 RS.AN-07: Incident data and metadata are collected, and their integrity and provenance are preserved			18
💼 NIST CSF v2.0 → 💼 RS.AN-08: An incident's magnitude is estimated and validated			1
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents			30
💼 NIST CSF v2.0 → 💼 RS.CO-03: Information is shared with designated internal and external stakeholders			18
💼 NIST CSF v2.0 → 💼 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared			1
💼 NIST CSF v2.0 → 💼 RS.MA-02: Incident reports are triaged and validated			24
💼 NIST CSF v2.0 → 💼 RS.MA-03: Incidents are categorized and prioritized			1
💼 NIST CSF v2.0 → 💼 RS.MA-04: Incidents are escalated or elevated as needed			1
💼 NIST SP 800-53 Revision 5 → 💼 IR-6 Incident Reporting	3		1
💼 SOC 2 → 💼 CC2.3-1 Communicates to External Parties			1