CYBBACK|for Google Cloud IAM
Quick User Guide

Your first GCP IAM snapshot
in under 10 minutes.

From sign-up to a fully encrypted, restorable snapshot of your project IAM - bindings, service accounts, custom roles, org policies. This guide walks you through every step.

AudienceGCP & security admins
Reading time~ 8 minutes
Setup time~ 10 minutes
VersionEN - 2026
What you'll learn

6 steps to a production-ready backup

1
Get started

Sign up - trial or paid licence

CYBBACK offers two ways to get started. Both unlock the full Google Cloud IAM feature set.

Option A - Free trial

  1. Open cybback.com/essai-gratuit.
  2. Fill in your work email, company and a password. Click Start free trial.
  3. Confirm via the verification email.
  4. On the trial selection screen, pick Google Cloud IAM. Your trial workspace is provisioned instantly.
Painless onboarding

Trial accounts get the full Google Cloud IAM feature set - encryption, BYOB, scheduling, granular restore. Switch to a paid plan at any moment without losing data.

Option B - Paid licence (Stripe checkout)

  1. Go to cybback.com/tarifs and pick the Google Cloud IAM plan that matches the number of GCP projects to protect.
  2. Click Subscribe. Stripe Checkout supports cards, SEPA and invoicing on annual plans.
  3. Your licence is active immediately - visible under Account → Subscription.
2
Connect Google Cloud IAM

Service account & organization roles

CYBBACK reads and restores Google Cloud IAM through one service account. Granted on the organization, its roles cover the organization, every folder and every project below it: one connection protects the whole hierarchy.

1. Create the service account

  1. Open console.cloud.google.com and pick a project to host the account (for example your administration project).
  2. In that project, enable the Identity and Access Management (IAM) API, the Cloud Resource Manager API and the Organization Policy API.
  3. Go to IAM & Admin → Service Accounts → + Create service account. Name it backup-iam.
  4. Open the new service account → Keys → Add key → JSON. Save the file safely.

2. Grant the roles on the organization

In the picker at the top of the console, choose the organization (not a project), then IAM & Admin → IAM → Grant access, paste the service account address and add:

On the organization (backup AND restore): • roles/iam.securityAdmin Security Admin • roles/iam.organizationRoleAdmin Organization Role Administrator • roles/iam.serviceAccountAdmin Service Account Admin • roles/orgpolicy.policyAdmin Organization Policy Administrator • roles/browser Browser Without an organization (single project), on the project: • roles/iam.securityAdmin • roles/iam.serviceAccountAdmin • roles/iam.roleAdmin
Organization roles are only listed on the organization

Organization Policy Administrator and Organization Role Administrator do not appear in a project's role list: select the organization first. Do not grant Organization Administrator, which is far broader than needed.

3. Paste credentials into CYBBACK

  1. Open app.cybback.com/dashboard/giam-backup → Settings.
  2. Upload the JSON key and enter the Project ID of the service account.
  3. Turn on Include organization policies and enter the organization ID (IAM & Admin → Settings, with the organization selected).
  4. Click Validate, then Save. The next backup covers the organization, its folders and all its projects.
app.cybback.com/dashboard/giam-backup
Dashboard
Settings
Google Cloud IAM configurationEncrypted at rest
 
3
Encryption at rest

Enable AES-256-GCM encryption

Backup files are stored on CYBBACK's secure EU infrastructure by default. Add a second layer with client-side encryption: each file is encrypted before it leaves the worker.

  1. On the Settings tab of the Google Cloud IAM page, scroll to Security options.
  2. Toggle AES-256 Encryption ON.
  3. Click Save. Applies to new backups; previous backups remain readable.
Settings → Security options
AES-256 EncryptionRecommended

Encrypts your backup data with AES-256-GCM before being sent to storage.

EnabledYour next backups will be end-to-end encrypted
4
Bring Your Own Bucket

Use your own S3-compatible storage

Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.

Provision the bucket

  1. In your S3 provider, create a private bucket (no public access, versioning recommended).
  2. Create an access key / secret key with permissions limited to that bucket.
  3. Note your endpoint URL and region.

Configure CYBBACK

  1. Open Dashboard → Storage.
  2. Select My own S3 storage.
  3. Fill the form, click Test connection, then Save.
Dashboard → Storage
S3 ConfigurationEncrypted at rest
 
Test before saving

Always click Test connection first. CYBBACK writes & deletes a probe file to validate credentials, region and permissions.

5
First backup

Run your first backup

You're now fully configured. Time to run your first IAM snapshot - manually for instant peace of mind, then schedule recurring runs.

Manual backup

  1. Go back to the Dashboard tab.
  2. Click Start a backup. The job appears with status pending, then running.
  3. Progress is streamed live: organization hierarchy, IAM policies of every resource, then service accounts, roles and policies project by project.

Schedule automatic backups

  1. From Dashboard → Schedules, click New schedule.
  2. Service: Google Cloud IAM. Frequency: Daily / Weekly / Custom (cron).
  3. Pick a window and click Save.
Snapshot-first

IAM state is small - a full backup of a typical project completes in 10–30 seconds. Daily snapshots add negligible storage cost while giving you a perfect audit trail.

Track your backups

6
Restore

Restore - access by access, like the console

The restore page shows the Google Cloud console as it was at the backup date: the organization, folders and projects on the left; IAM, service accounts, roles and organization policies on the right. Every single access (one principal on one role) can be ticked.

The 3-step restore flow

  1. Selection. Pick a resource in the hierarchy, then tick access in View by principals or View by roles, service accounts, custom roles or policies. Compare with Google Cloud marks what has disappeared since the backup, and Select what is gone ticks it all at once.
  2. Options.
    • Dry-run (on by default) - reads the real state and tells exactly what would be done, without writing anything.
    • Put back the access of restored service accounts and who can use them.
    • Overwrite - resets a changed custom role, a changed policy and an account's enabled or disabled state.
  3. Execution. Live progress and a line per change: access added, account recovered, role recovered, policy reset.
Dashboard → Google Cloud IAM → Restore
IAM
Service accounts
Roles
Organization policies
Project billing-prod · View by principals2 access gone since the backup
ops-team@example.comGroup · roles/compute.admin · missing today
deploy@billing-prod.iam.gserviceaccount.comService account · deleted since the backup
 

Good to know

Limits

Service account keys are not restorable (Google never returns the private key): create new keys. An account deleted more than 30 days ago is recreated with a new unique ID. Access to a principal already deleted at the backup date cannot be put back.

You're all set.

Need help? Our team replies within one business day on every plan.

Contact support →