Skip to main content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Access Review

GCP access review connector

Access Review now supports Google Cloud Platform as a connector, listing project IAM principals and service accounts with best-effort MFA and last-activity signals from a dedicated setup page in the console.

GCP access review connector logo

Access Review adds Google Cloud Platform as a connector. You give it a service account through workload identity federation, and it pulls back project IAM principals and service accounts.

For each identity it does its best to surface last activity and MFA status. Users get Admin Activity logs and Directory 2-Step Verification enrollment, service accounts get Policy Analyzer with a Cloud Audit Logs fallback. When a signal isn’t available, it just says so instead of guessing.

Setting it up now has its own page in the console: a dedicated connect flow with a Terraform module reference, matching the pattern we shipped for AWS. Find it from the provider catalog or right next to the AWS connector in setup.