Collect Cloud Identity Devices logs

This guide will explain how to export Cloud Identity Devices logs into Google Security Operations using Cloud Storage. The parser extracts fields from JSON logs, transforms specific fields like deviceType and dates, and maps them to the UDM, creating an asset_entity representing the device and enriching it with hardware and metadata information.

Before You Begin

Ensure that you have the following prerequisites:

• Google Cloud Identity is enabled in your Google Cloud project.
• Google SecOps instance.
• Privileged access to Google Cloud Identity and Cloud Logging.

Create a Cloud Storage bucket

1. Sign in to the Google Cloud console .

2. Go to the Cloud Storage Bucketspage.

   Go to Buckets

3. Click Create.

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

   1. In the Get startedsection, do the following:

      1. Enter a unique name that meets the bucket name requirements; for example, gcp-cloudidentity-devices-logs.

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

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

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

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

      1. Select a Location type.

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

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

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

   4. In the Choose how to control access to objectssection, clear Enforce public access prevention, and select an Access controlmodel for your bucket's objects.

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

      1. Select any of the options under Data protectionthat 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.

Configure Cloud Identity Devices 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, cloud-identity-devices-logs-sink .
   • Sink Destination: select Cloud Storage Storageand enter the URI for your bucket; for example, gs://gcp-cloudidentity-devices-logs .

   • Log Filter:

       logName 
      = 
      "projects/<your-project-id>/logs/cloudaudit.googleapis.com%2Factivity" 
     resource.type = 
      "cloud_identity_device" 
      
     

   • Set Export Options: include all log entries.

5. Click Create.

Configure permissions for Cloud Storage

1. Go to IAM & Admin > IAM.
2. Locate the Cloud Loggingservice account.
3. Grant the roles/storage.adminon the bucket.

Set up feeds

There are two different entry points to set up feeds in the Google SecOps platform:

• SIEM Settings > Feeds > Add New
• Content Hub > Content Packs > Get Started

How to set up the Google Cloud Identity Devices feed

1. Click the Google Cloud Compute platformpack.
2. Locate the Google Cloud Identity Deviceslog type and click Add new feed.
3. Specify values for the following fields:
   • Source Type: Third party API
   • OAuth JWT endpoint: endpoint to retrieve the OAuth JSON web token (JWT).
   • JWT claims issuer: usually the client ID.
   • JWT claims subject: usually an email address.
   • JWT claims audience: JWT claims audience.
   • RSA private key: enter in PEM format.

Advanced options

• Feed Name: A prepopulated value that identifies the feed.
• Asset Namespace: Namespace associated with the feed.
• Ingestion Labels: Labels applied to all events from this feed.

1. Click Create feed.

For more information about configuring multiple feeds for different log types within this product family, see Configure feeds by product .

UDM Mapping Table

Log Field	UDM Mapping	Logic
createTime	entity.metadata.creation_timestamp	The value of createTime is parsed as a timestamp and mapped.
deviceId	entity.entity.asset.asset_id	Directly mapped.
deviceType	entity.entity.asset.platform_software.platform	Mapped to MAC if the original value is MAC_OS or IOS . Mapped to WINDOWS , MAC , or LINUX if the original value matches. Otherwise, set to UNKNOWN_PLATFORM .
encryptionState	entity.entity.asset.attribute.labels.key	Value is set to encryptionState . Used as part of a label.
encryptionState	entity.entity.asset.attribute.labels.value	Directly mapped. Used as part of a label.
lastSyncTime	entity.entity.asset.system_last_update_time	The value of lastSyncTime is parsed as a timestamp and mapped.
managementState	entity.entity.asset.attribute.labels.key	Value is set to managementState . Used as part of a label.
managementState	entity.entity.asset.attribute.labels.value	Directly mapped. Used as part of a label.
model	entity.entity.asset.hardware.model	Directly mapped.
name	entity.entity.asset.product_object_id	The portion after devices/ is extracted and mapped.
name	entity.entity.resource.name	Directly mapped.
osVersion	entity.entity.asset.platform_software.platform_version	Directly mapped.
securityPatchTime	entity.entity.asset.attribute.labels.key	Value is set to securityPatchTime . Used as part of a label.
securityPatchTime	entity.entity.asset.attribute.labels.value	Directly mapped. Used as part of a label.
serialNumber	entity.entity.asset.hardware.serial_number	Directly mapped. Copied from the top-level create_time field in the raw log. Value is set to ASSET . Value is set to GCP Cloud Identity Devices . Value is set to Google Cloud Platform . Copied from the top-level create_time field in the raw log.

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