Firebase
Connect Firebase to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Firebase to collect infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Firebase's guide | firebase.google.com |
Connect with an API token
-
In Firebase:
- In the Google Cloud console, go to the Create service account page and select the Google Cloud project that backs your Firebase project.
- Enter a service account name, then click Create and continue.
- Choose the IAM role Firebase Viewer (roles/firebase.viewer, "Read-only access to all Firebase services"), click Continue, then click Done.
- Go to the Service accounts page, click the email address of the new service account and open the Keys tab.
- Click Add key › Create new key, select JSON as the Key type and click Create. The JSON key file downloads.
Where to find the other values:
- Base URL (optional): Leave blank; Firebase APIs are served by Google.
- Account / Org / Workspace (optional): Your Firebase project ID (the Google Cloud project you selected above).
Firebase shows the secret only once, so copy it before you leave the page.
Firebase's public documentation does not cover every step.
Source: docs.cloud.google.com, docs.cloud.google.com, firebase.google.com, firebase.google.com, checked 2026-10-07.
The permissions Safeguard needs:
firebase.readonly. -
On Compliance › Connectors, open Firebase, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Firebase and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.1 | 1 |
| ISO/IEC 27001 | Automated tests | A.5.15 | 1 |
| HIPAA Security Rule | Automated tests | 164.312(a)(1) | 1 |
| PCI DSS | Automated tests | 7.2.1 | 1 |
| NIST CSF 2.0 | Automated tests | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Infrastructure connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks