Google Cloud
Bring in the Cloud Audit Logs of your Google Cloud project.
It reads the project's Cloud Audit Logs: admin activity and, if you grant the permission, data access. Admin activity logs are always enabled and free of charge.
Before you start
Administer permission on Security (SIEM).
In the project, the Cloud Logging API enabled.
The Google Cloud connection in Settings → Monitoring → Cloud services (the FinOps one works). See Connect AWS, Google Cloud, Azure, Cloudflare or Coolify.
The service account of that connection must have the Logs Viewer role (
roles/logging.viewer). For data access logs,roles/logging.privateLogViewer.
Steps
Go to Settings → SIEM integrations → Google Cloud. The page shows what is read, the connection or token, and the minimum permission.
Click Add.
Type the Name, choose the Google Cloud connection and, if the project is not the service account's project, its Project ID.
Click Add.
On the integration's card, click Test.
Manage the integration
Each integration has its card with the status (Waiting for the first read, Reading, With errors with the reason, or Paused), the connection, what it reads, the last read, the last event and the events brought in.
Test: authenticates and reads the last hour without storing anything. If a permission is missing, the error says which one.
Read now: reads without waiting for the next pass.
Pause or Enable.
Edit (pencil) and Delete (trash). When you delete it, ARGUNIS stops reading; the events already brought in stay in the SIEM with their retention.
What happens next
ARGUNIS reads every 5 minutes; the first time it brings in the last 24 hours. Events arrive in Security → Explore events and in the SIEM rules as one more source, which is included when the integration is created. ARGUNIS only reads: it changes nothing in your account.