--- title: "Cloud Table" slug: "cloud-table-1" updated: 2026-10-22T15:23:47Z published: 2026-10-22T15:23:47Z canonical: "docs.databee.buzz/cloud-table-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt > Use this file to discover all available pages before exploring further. # Cloud Table ## Purpose The Cloud Table Core Data Product is an inventory of your cloud data-table resources, such as NoSQL tables. Each asset appears once, no matter how many feeds report it, and the table keeps both its current state and its history. Use it to see which tables exist, when they first appeared and when they were closed, and to join back to OCSF activity and findings that involve those resources. ## Entity Correlation The Entity Correlator identifies a cloud asset by its unique ID (`uid`), for example an Amazon Resource Name. When several feeds report the same `uid`, they are merged into a single asset with a single `id`. If feeds disagree about a value, feed priority and recency decide which one is kept. ## Understanding the Table When a value on an asset changes, a new row is created, and `active` is set to false on the older rows, so each asset has exactly one row with `active = TRUE`. The table is refreshed hourly. An asset appears in this table when the feed that reports it classifies it as a table (type ID 3). The `end_time` field is populated when an asset is closed: either the source reports it as decommissioned, or no feed has reported it for the cloud-resource retention period (365 days by default, configurable). A closed asset has `active = FALSE`. If a closed asset is reported again, it is tracked as a new asset with a new `id`. ## Joining to CDPs and OCSF `cloud_table.id` identifies the asset across all of its history rows. OCSF event tables that reference cloud resources carry the asset in their `resources` array, and each element's `id` matches the CDP `id`. Join on that element to find the activity and findings that involve a table. ## [Schema](/docs/cloud-table) ## Example Queries Find all active cloud tables ```sql SELECT * FROM cloud_table WHERE active=TRUE ``` Find the latest record for a given id ```sql SELECT * FROM cloud_table WHERE active=TRUE AND id={id} ``` Find the largest active cloud tables ```sql SELECT id, name, uid, size FROM cloud_table WHERE active=TRUE ORDER BY size DESC NULLS LAST ``` How to join back to OCSF ```sql SELECT t.name, a.* FROM OCSF.{activity} a,     LATERAL FLATTEN(input => a.resources) r,     CDP.cloud_table t WHERE t.id = r.value:id::INT  AND t.active=TRUE ``` ## CDP Data Dictionary | **Caption** | **Name** | **Requirement** | **Type** | **Description** | | --- | --- | --- | --- | --- | | Active | active | optional | boolean_t | ResourceDetails.end_time: The timestamp of when the resource was decommissioned or removed from tracking. Using the start_time and end_time together bound the time when a particular resource state is valid. If there is no end_time it tells the analyst that this is the current state of the resource a | | Created Time | created_time | optional | timestamp_t | ResourceDetails.created_time: The time when the resource was created. | | Description | desc | optional | string_t | ResourceDetails.desc: The description of the resource. | | End Time | end_time | optional | timestamp_t | ResourceDetails.end_time: The timestamp of when the resource was decommissioned or removed from tracking. Using the start_time and end_time together bound the time when a particular resource state is valid. If there is no end_time it tells the analyst that this is the current state of the resource a | | First Seen Time | first_seen_time | optional | timestamp_t | ResourceDetails.backtrace: This object is a key value set that relates each field in the entity to the raw event that gave DataBee that particular value in the correlation. | | Groups Name | groups | optional | string_t Array | ResourceDetails.groups: The groups to which the resource belongs. Group.name: The group name. | | History ID | hid | optional | integer_t | ResourceDetails.hid: The unique DataBee ID to identify a particular history entry or row in an entity table (i.e., user, device or product table). This field is the primary key and should not be mapped manually as the DataBee product populates this field itself. | | ID | id | required | integer_t | ResourceDetails.id: The unique identifier used by DataBee for a specific cloud asset. This is the primary key for the Resource Details table and is referenced as 'resource_id' in activity and event tables to link to this cloud asset. Enables joins and correlations with events and activities. Synonym | | Modified Time | modified_time | optional | timestamp_t | ResourceDetails.modified_time: The time when the resource was last modified. | | Name | name | recommended | string_t | ResourceDetails.name: The name of the resource. | | Record Created At | record_created_at | required | timestamp_t | CDPs generated timestamp when record was created. | | Record Updated At | record_updated_at | required | timestamp_t | CDPs generated timestamp when record was last updated. | | Size | size | optional | string_t | ResourceDetails.size: The size of the resource in bytes. | | Unique ID | uid | recommended | string_t | ResourceDetails.uid: The unique identifier of the resource. |