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 Google Cloud Identity is enabled in your Google Cloud project.
- Ensure that you have a Google SecOps instance.
- Ensure that you have privileged access to Google Cloud Identity and Cloud Logging.
Create a Cloud Storage bucket
- Sign in to the Google Cloud console.
Go to the Cloud Storage Buckets page.
Click Create.
On the Create a bucket page, enter your bucket information. After each of the following steps, click Continue to proceed to the next step:
In the Get started section, do the following:
- Enter a unique name that meets the bucket name requirements; for example, gcp-cloudidentity-devices-logs.
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.
To add a bucket label, click the expander arrow to expand the Labels section.
Click Add label, and specify a key and a value for your label.
In the Choose where to store your data section, do the following:
- Select a Location type.
Use the location type menu to select a Location where object data within your bucket will be permanently stored.
To set up cross-bucket replication, expand the Set up cross-bucket replication section.
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.
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.
In the Choose how to protect object data section, do the following:
- Select any of the options under Data protection that you want to set for your bucket.
- To choose how your object data will be encrypted, click the expander arrow labeled Data encryption, and select a Data encryption method.
Click Create.
ConfigureCloud Identity Devices Logs Export
- Sign in to the Google Cloud console.
- Go to Logging > Log Router.
- Click Create Sink.
Provide the following configuration parameters:
- Sink Name: enter a meaningful name; for example,
cloud-identity-devices-logs-sink
. - Sink Destination: select Cloud Storage Storage and 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.
- Sink Name: enter a meaningful name; for example,
Click Create.
Configure permissions for Cloud Storage
- Go to IAM & Admin > IAM.
- Locate the Cloud Logging service account.
- Grant the roles/storage.admin on the bucket.
Configure a feed in Google SecOps to ingest Cloud Identity Devices logs
- Go to SIEM Settings > Feeds.
- Click Add new.
- In the Feed name field, enter a name for the feed; for example, GCP Cloud Identity Devices Logs.
- Select Google Cloud Storage as the Source type.
- Select GCP Cloud Identity Devices as the Log type.
- Click Get Service Account next to the Chronicle Service Account field.
- Click Next.
Specify values for the following input parameters:
- Storage Bucket URI: Cloud Storage bucket URL; for example,
gs://gcp-cloudidentity-devices-logs
. - URI Is A: select Directory which includes subdirectories.
Source deletion options: select the deletion option according to your preference.
Asset namespace: the asset namespace.
Ingestion labels: the label applied to the events from this feed.
- Storage Bucket URI: Cloud Storage bucket URL; for example,
Click Next.
Review your new feed configuration in the Finalize screen, and then click Submit.
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. |
Changes
2022-03-27
- Mapped
resource.name
to the long unique resource namename
.
2022-04-13
- Newly created parser.
Need more help? Get answers from Community members and Google SecOps professionals.