Essential Contacts should be configured for the organization
This check looks at whether your Google Cloud organization has Essential Contacts set up. The safe setting is to register monitored addresses so Google can reach the right people about security, technical and other important notices.
Why it matters
Google Cloud sends notices about security issues, outages, billing and other events to people it knows about. If no one has registered contacts for the organization, those messages can go to whoever happened to create the account years ago, or to nobody who still works there.
Essential Contacts lets you choose which people or group mailboxes receive each category of notice, at the organization, folder or project level. Setting it at the organization means every project below it inherits sensible recipients, and a notice about a compromised resource reaches a team that can act on it. Google describes the categories and how inheritance works in its Resource Manager documentation.
Group mailboxes are usually safer than named individuals, because they survive staff changes.
How to check it yourself
Portal: Google Cloud console → select the organization in the project picker → IAM & Admin → Essential Contacts. Look for at least one contact and check which notification categories each one receives.
Read-only command (gcloud, listing only):
gcloud essential-contacts list --organization=ORGANIZATION_IDReplace ORGANIZATION_ID with your own organization number. An empty list means the check fails. Look as well at whether the categories you rely on, such as security and technical, are covered by an address that is actively read.
How to fix it
Portal: on the Essential Contacts page choose Add contact, enter the address of a monitored group mailbox, pick the notification categories (for example Security and Technical), and save. Repeat for any other team that should receive a category such as Billing or Legal.
Script (this adds a contact, so review it before you run it):
gcloud essential-contacts create --email="cloud-security@example.com" --notification-categories=SECURITY,TECHNICAL --organization=ORGANIZATION_IDThe address above is a placeholder. ConfigCobra only reads your organization and does not add contacts for you.
What changes when you fix it
Nothing in your running workloads changes. The effect is on who receives Google's messages: the people you named will start getting notices that previously went elsewhere or were missed.
The mailbox owners should know what to expect and who to escalate to. If you pick a busy shared inbox, consider a filter or an alias so that a security notice is not buried. Contacts set on a folder or project still apply as well, so review those if you want one consistent set of recipients.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Google Cloud Platform Foundation v5.0.0 | 1.17 | Level 1 |
More checks in Identity and Access Management
- Use corporate-managed login credentials instead of consumer accountsCIS 1.2
- Enforce multi-factor authentication for all non-service accountsCIS 1.3
- Enforce security-key two-factor authentication for all admin accountsCIS 1.4
- Use only GCP-managed keys for each service account (no user-managed keys)CIS 1.5
- Ensure service accounts hold no admin (owner/editor) privilegesCIS 1.6
Go further
- Identity and Access Management21 controls in this section
- CIS Google Cloud Platform Foundation v5.0.093 controls
- CIS Google Cloud Platform Foundation checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Google Cloud
ConfigCobra runs this check with every other control of the CIS Google Cloud Platform Foundation Benchmark, read-only.