Collect Cloud Identity and Access Management (IAM) Analysis logs

Supported in:

Google SecOps SIEM

Note: This feature is covered by Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the Google Security Operations Technical Support Service guidelines and the Google Security Operations Service Specific Terms.

This document explains how to export and ingest Cloud IAM Analysis logs into Google Security Operations using Cloud Storage. The parser extracts user and resource information from Google Cloud IAM JSON data. It then maps the extracted fields to the UDM, creating user entities with associated roles and resource relationships, ultimately enriching security context within the Google SecOps platform.

Before you begin

• Ensure that you have a Google SecOps instance.
• Ensure that Google Cloud IAM is set up and active in your Google Cloud environment.
• Ensure that you have privileged access to Google Cloud and appropriate permissions to access IAM logs.

Create a Cloud Storage bucket

1. Sign in to the Google Cloud console.

2. Go to the Cloud Storage Buckets page.

   Go to Buckets

3. Click Create.

4. On the Create a bucket page, enter your bucket information. After each of the following steps, click Continue to proceed to the next step:

   1. In the Get started section, do the following:

      1. Enter a unique name that meets the bucket name requirements; for example, google-cloud-iam-logs.

      2. To enable hierarchical namespace, click the expander arrow to expand the Optimize for file oriented and data-intensive workloads section, and then select Enable Hierarchical namespace on this bucket.

         Note: You cannot enable hierarchical namespace on an existing bucket.

      3. To add a bucket label, click the expander arrow to expand the Labels section.

      4. Click Add label, and specify a key and a value for your label.

   2. In the Choose where to store your data section, do the following:

      1. Select a Location type.

      2. Use the location type menu to select a Location where object data within your bucket will be permanently stored.

         Note: If you select the dual-region location type, you can also choose to enable turbo replication by using the relevant checkbox.

      3. To set up cross-bucket replication, expand the Set up cross-bucket replication section.

   3. In the Choose a storage class for your data section, either select a default storage class for the bucket, or select Autoclass for automatic storage class management of your bucket's data.

   4. In the Choose how to control access to objects section, select not to enforce public access prevention, and select an access control model for your bucket's objects.

      Note: If public access prevention is already enforced by your project's organization policy, the Prevent public access checkbox is locked.

   5. In the Choose how to protect object data section, do the following:

      1. Select any of the options under Data protection that you want to set for your bucket.
      2. To choose how your object data will be encrypted, click the expander arrow labeled Data encryption, and select a Data encryption method.

5. Click Create.

Note: Be sure to provide your Google SecOps service account with permissions to Read or Read & Write to the newly created bucket.

Configure Google Cloud IAM Analysis logs export

1. Sign in to the Google Cloud console.
2. Go to Logging > Log Router.
3. Click Create Sink.

4. Provide the following configuration parameters:

   • Sink Name: enter a meaningful name; for example, IAM-Analysis-Sink.
   • Sink Destination: select Cloud Storage Storage and enter the URI for your bucket; for example, gs://gcp-iam-analysis-logs.

   • Log Filter:

     logName="*iam*"
     resource.type="gce_instance"
     

     Configure permissions for Cloud Storage

5. Go to IAM & Admin > IAM.

6. Locate the Cloud Logging service account.

7. Grant the roles/storage.admin on the bucket.

Configure a feed in Google SecOps to ingest Google Cloud IAM Analysis logs

1. Go to SIEM Settings > Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed; for example, Google Cloud IAM Analysis Logs.
4. Select Google Cloud Storage as the Source type.
5. Select GCP IAM Analysis as the Log type.
6. Click Get Service Account next to the Chronicle Service Account field.
7. Click Next.

8. Specify values for the following input parameters:

   • Storage Bucket URI: Cloud Storage bucket URL; for example, gs://gcp-iam-analysis-logs.
   • URI Is A: select Directory which includes subdirectories.

   • Source deletion options: select the deletion option according to your preference.

     Note: If you select the Delete transferred files or Delete transferred files and empty directories option, make sure that you granted appropriate permissions to the service account.

   • Asset namespace: the asset namespace.

   • Ingestion labels: the label applied to the events from this feed.

9. Click Next.

10. Review your new feed configuration in the Finalize screen, and then click Submit.

UDM Mapping Table

Log Field	UDM Mapping	Logic
accessControlLists.accesses.permission	relations.entity.resource.attribute.permissions.name	Directly from the accessControlLists.accesses.permission field in the raw log.
attachedResourceFullName	relations.entity.resource.name	Directly from the attachedResourceFullName field in the raw log, but with any trailing resource names removed.
	relations.entity.resource.attribute.cloud.environment	Set to GOOGLE_CLOUD_PLATFORM.
	relations.entity.resource.product_object_id	For STORAGE_BUCKET, directly from the attachedResourceFullName field in the raw log, but with any trailing resource names removed. For BigQuery datasets, it's the projectName (extracted from attachedResourceFullName) followed by a colon and the datasetName (extracted from attachedResourceFullName) field.
	relations.entity.resource.resource_type	Determined by the pattern of the attachedResourceFullName field in the raw log.
	relations.entity_type	Set to RESOURCE, except for SERVICE_ACCOUNT, where it's set to USER.
	relations.relationship	Set to MEMBER.
	metadata.collected_timestamp	Directly from the timestamp field in the raw log.
	metadata.entity_type	Set to USER.
	metadata.product_name	Set to GCP IAM ANALYSIS.
	metadata.vendor_name	Set to Google Cloud Platform.
iamBinding.role	entity.user.attribute.roles.name	Directly from the iamBinding.role field in the raw log.
identityList.identities.name	entity.user.attribute.roles.type	Set to SERVICE_ACCOUNT if the identityList.identities.name field contains the string serviceAccount.
	entity.user.email_addresses	If the identityList.identities.name field contains an @ symbol, it's treated as an email address.
	entity.user.userid	If the identityList.identities.name field doesn't contain an @ symbol, it's treated as a userid.
identityList.identities.product_object_id	entity.user.product_object_id	Directly from the identityList.identities.product_object_id field in the raw log.
timestamp	timestamp	Directly from the timestamp field in the raw log.

Changes

2023-02-27

Bug fix:

• Removed mapping of field iamBinding.members to entity.user.group_identifiers.

2022-12-28

Enhancement:

• Mapped the field iamBinding.role to entity.user.attribute.role.name.
• Mapped the field iamBinding.members to entity.user.group_identifiers.

2022-07-27

Enhancement:

• Removed the mapping for identity.product_object_id which was mapped to event.idm.entity.entity.user.userid.

Need more help? Get answers from Community members and Google SecOps professionals.