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.
Fill in your work email, company and a password. Click Start free trial.
Confirm via the verification email.
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)
Go to cybback.com/tarifs and pick the Google Cloud IAM plan that matches the number of GCP projects to protect.
Click Subscribe. Stripe Checkout supports cards, SEPA and invoicing on annual plans.
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
Open console.cloud.google.com and pick a project to host the account (for example your administration project).
In that project, enable the Identity and Access Management (IAM) API, the Cloud Resource Manager API and the Organization Policy API.
Go to IAM & Admin → Service Accounts → + Create service account. Name it backup-iam.
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.
Upload the JSON key and enter the Project ID of the service account.
Turn on Include organization policies and enter the organization ID (IAM & Admin → Settings, with the organization selected).
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.
On the Settings tab of the Google Cloud IAM page, scroll to Security options.
Toggle AES-256 Encryption ON.
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
In your S3 provider, create a private bucket (no public access, versioning recommended).
Create an access key / secret key with permissions limited to that bucket.
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
Real-time: the Events page streams every operation across all services via SSE.
Notifications: success / failure / drift alerts via email, Slack and webhooks.
Drift detection: alerts on suspicious permission changes, role permission expansions, or sudden binding count changes between runs.
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
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.
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.
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
deploy@billing-prod.iam.gserviceaccount.comService account · deleted since the backup
Good to know
Nothing is ever removed: the restore adds to the policies in place; access added since the backup stays.
Same identity when possible: a service account deleted less than 30 days ago is undeleted with its unique ID; a deleted custom role is undeleted first.
Always start with a dry-run, then click Proceed with real restore.
Export: a ZIP of the JSON files is available from the Export button for an offline copy.
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.