--- title: "Device" slug: "device-2" updated: 2026-10-22T15:25:32Z published: 2026-10-22T15:25:32Z canonical: "docs.databee.buzz/device-2" --- > ## 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. # Device ## Purpose The Device CDP contains information on all devices and assets within an organization. The Device CDP is ideal for answering questions about the current and historical status of the organization's asset inventory and can be joined to OCSF event tables for further historical trend analysis. ## Entity Correlation The Device CDP leverages the Entity Correlator to effectively track and manage the distinct assets that DataBee has identified within the organization. The Entity Correlator utilizes several key fields to identify and differentiate users, listed below in their rank order of importance: - Serial Number: this unique identifier is the primary field used to distinguish each asset within the system - IMEI: the IMEI of the device serves as the secondary piece of information to identify a device - MAC: the MAC address provides an additional layer of identification - Hostname: hostname, or the unique name of the device, is used in conjunction with the above attributes to identify a device - IP: the IP address is the last used piece of information as it can easily change ## Understanding the Table The Device CDP is a Type 2 Slowly Changing table. In a Type 2 table any modifications to an entity will result in the creation of new rows for that device ID, capturing the updated fields. The `active` column for the older row is set to `False`, ensuring that historical data remains unaltered and providing a clear distinction between current and previous states. Consequently, users can trace the evolution of the data over time, making it easier to perform audits and historical analyses. `End_time` is populated only if a device has been merged into another device by the Entity Correlator. In such cases, a new row is created to reflect the merged asset, and the `end_time` field is populated for all previous rows associated with the device. This ensures that there is a clear distinction between the historical data and the current state of the Entity Correlator. By tracking the `end_time`, users can easily identify when a particular device entity was last active before being merged. On the other hand, if a device’s attributes are merely updated without merging, the `end_time` will not be populated for the older row. Instead, the active field will be set to `False`. This indicates that the older information is no longer current but still retains its historical significance. The Device CDP includes the `is_encrypted` boolean field, indicating whether the device has encryption enabled as reported by its management source. ## Joining to CDPs and OCSF The `device.id` column is the primary identifier used for all joins within the Core Data Products. This column ensures consistency and reliability when linking different data sets within the CDPs. If the security hygiene entitlement feature is enabled, the `device.id` can also be utilized to join data back to the Open Cybersecurity Schema Framework (OCSF) tables, providing a seamless connection between the two data architectures. In scenarios where the security hygiene entitlement is not enabled, alternative identifiers must be used. These alternatives include `device.hardware_info_serial_number`, `device.mac`, or `device.hostname`. ## [Schema](/user-manual/docs/device-1) ## Example Queries Find all active devices ```plaintext SELECT * FROM device where active=TRUE ``` Find the latest record for a given id ```plaintext SELECT * FROM device where active=TRUE and id={id} ``` Find all active entities and their latest row ```plaintext SELECT * FROM device where active=TRUE ``` How to join back to OCSF ```plaintext SELECT * FROM CDP.device left join OCSF.{activity} on CDP.device.id = OCSF.{activity}.device_id ``` How to join back to OCSF without security hygiene ```plaintext SELECT * FROM CDP.device left join OCSF.{activity} on CDP.device.mac = OCSF.{activity}.device.mac ``` ## CDP Data Dictionary | **Caption** | **Name** | **Requirement** | **Type** | **Description** | | --- | --- | --- | --- | --- | | Active | active | optional | boolean_t | Device.modified_time: The time when the device was last known to have been modified. | | Created Time | created_time | optional | timestamp_t | Device.created_time: The time when the device was known to have been created. | | Applicable Compliance Standards | compliance_scope | recommended | string_t Array | Device.compliance_scope: Indicates regulatory scope for the device. For example, PCI DSS level or other compliance tiers. Useful for compliance reporting and filtering devices by regulatory requirements. | | Name | device_name | optional | string_t | Device.name: The alternate device name, ordinarily as assigned by an administrator. | | Domain | domain | optional | string_t | Device.domain: The network domain where the device resides. For example: `work.example.com`. | | End Time | end_time | optional | timestamp_t | Device.end_time: The end time of when a particular state of the user was valid. Using the `start_time` and `end_time` together bound the time when a particular user state was valid. If there is no `end_time` it tells the analyst that this is the current state of the user as DataBee understands it. There will ever only be a single user for which the `end_time` is `null`. | | Environment | environment | optional | string_t | Device.environment: The operational environment in which the device exists. For example: Production, Development, QA. | | First Seen Time | first_seen_time | optional | timestamp_t | Device.first_seen_time: The initial discovery time of the device. | | Group Names | group_names | optional | string_t Array | Device.groups: The group names to which the device belongs. For example: `['Windows Laptops', 'Engineering']` Group.name: The group name. | | History ID | hid | required | integer_t | Device.hid: The unique DataBee ID to identify a particular history entry in an object table. This field is the PK and should not be mapped manually as the DataBee product populates this field itself. | | Hostname | hostname | recommended | string_t | Device.hostname: The device hostname. | | Hardware Info BIOS Manufacturer | hw_info_bios_manufacturer | optional | string_t | Device.hw_info: The endpoint hardware information. | | Hardware Info Serial Number | hw_info_serial_number | optional | string_t | Device.hw_info: The endpoint hardware information. DeviceHwInfo.serial_number: The device manufacturer serial number. | | Hypervisor | hypervisor | optional | string_t | Device.hypervisor: The name of the hypervisor running on the device. For example, `Xen`, `VMware`, `Hyper-V`, `VirtualBox`, etc. | | Device ID | id | required | integer_t | Device.id: The unique identifier used by DataBee for a specific device. This will be logged as `device_id` in activity tables to link to a particular device in this table. This field should not be mapped manually as the DataBee product populates this field itself. | | Image Name | image_name | optional | string_t | Device.image: The image used as a template to run the virtual machine. Image.name: The image name. For example: `elixir`. | | IMEI | imei | optional | string_t | Device.imei: The International Mobile Station Equipment Identifier that is associated with the device. For example: `123456789012345` | | IMEI List | imei_list | optional | string_t Array | Device.imei_list: A list of IMEI identifiers associated with a device. Useful for tracking and managing mobile devices. Values are unique for each mobile device. | | Instance UID | instance_uid | recommended | string_t | Device.instance_uid: The unique identifier of a VM instance. For example: `56 4d ef 2d 3f d4 14 e2-2e 04 c5 34 3a ec ee 65` for a VMWare UUIDE. | | IP Address | ip | recommended | string_t | Device.ip: The device IP address, in either IPv4 or IPv6 format. | | Compliant Device | is_compliant | optional | boolean_t | Device.is_compliant: The event occurred on a compliant device. | | Encrypted | is_encrypted | optional | boolean_t | Device.is_encrypted: Indicates whether device is encrypted. | | Managed Device | is_managed | optional | boolean_t | Device.is_managed: The event occurred on a managed device. | | Personal Device | is_personal | optional | boolean_t | Device.is_personal: The event occurred on a personal device. | | Trusted Device | is_trusted | optional | boolean_t | Device.is_trusted: The event occurred on a trusted device. | | Virtual Device | is_virtual | optional | boolean_t | Device.is_virtual: Indicates whether the device is virtual. | | Last Seen Time | last_seen_time | optional | timestamp_t | Device.last_seen_time: The most recent discovery time of the device. | | Geo Location City | location_city | optional | string_t | Device.location: The geographical location of the device. Location.city: The name of the city. For example: san diego. | | Geo Location Country | location_country | optional | string_t | Device.location: The geographical location of the device. Location.country: The ISO 3166-1 Alpha-2 country code. For the complete list of country codes see `ISO 3166-1 alpha-2 codes <https://www.iso.org/obp/ui/#iso:pub:PUB500001:en>`_. | | MAC Address | mac | optional | string_t | Device.mac: The Media Access Control (MAC) address of the endpoint. | | Modified Time | modified_time | optional | timestamp_t | Device.modified_time: The time when the device was last known to have been modified. | | Network Interfaces Hostnames | network_interfaces_hostnames | optional | string_t Array | Device.network_interfaces: The network interfaces that are associated with the device, one for each unique MAC address/IP address/hostname/name combination. | | Network Interfaces IP Addresses | network_interfaces_ips | optional | string_t Array | Device.network_interfaces: The network interfaces that are associated with the device, one for each unique MAC address/IP address/hostname/name combination. | | Network Interfaces MAC Addresses | network_interfaces_macs | optional | string_t Array | Device.network_interfaces: The network interfaces that are associated with the device, one for each unique MAC address/IP address/hostname/name combination. | | Organization Name | org_name | optional | string_t | Device.org: Organization and org unit related to the device. Organization.name: The name of the organization. For example, Widget, Inc. | | Organization Org Unit Name | org_ou_name | optional | string_t | Device.org: Organization and org unit related to the device. Organization.ou_name: The name of the organizational unit, within an organization. For example, Finance, IT, R&D. | | OS Name | os_name | optional | string_t | Device.os: The endpoint operating system. Os.name: The operating system name. | | OS Type | os_type | optional | string_t | Device.os: The endpoint operating system. Os.type: The type of the operating system. | | OS Version | os_version | optional | string_t | Device.os: The endpoint operating system. Os.version: The version of the OS running on the device that originated the event. For example: 'Windows 10', 'OS X 10.7', or 'iOS 9'. | | OS Vendor Name | os_vendor_name | optional | string_t | Device.os: The endpoint operating system. Os.vendor_name: Organization that develops, sells, or supports an operating system. | | Owner Email Address | owner_email_addr | optional | string_t | Device.owner: The primary owner of a device. User.email_addr: The user's primary email address. For example: `noone@nowhere.ru`. | | Owner Employee UID | owner_employee_uid | optional | string_t | Device.owner: The primary owner of a device. User.ldap_person: The additional LDAP attributes that describe a person. LdapPerson.employee_uid: The unique identifier for an employee, often used for linking and integration with HR systems. For example: E12345. | | Owner Full Name | owner_full_name | optional | string_t | Device.owner: The primary owner of a device. User.full_name: The full name of the user, as reported by the product. | | Owner Name | owner_name | recommended | string_t | Device.owner: The primary owner of a device. User.name: The username. For example, `janedoe1`. | | Owner ID | owner_user_id | optional | integer_t | Device.owner: The primary owner of a device. User.id: The unique identifier used by DataBee for a specific user. This will be logged as `user_id` in activity tables to link to a particular user in this table. This field should not be mapped manually as the DataBee product populates this field itself. | | 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. | | Region | region | recommended | string_t | Device.region: The region where the virtual machine is located. For example, an AWS Region. | | Risk Level | risk_level | optional | string_t | Device.risk_level: A label indicating the risk level associated with an entity or event. For example: high, medium, low. Useful for risk management and prioritization. | | Selected Owner Selected On Time | selected_on | optional | timestamp_t | Device.selected_owner: The owner selected by a DataBee user to assign to a device. Keys in object are user_id an integer, user_email a string and selected_on a datetime. SelectedOwner.selected_on: The time when the owner selection was made. | | Selected Owner DataBee User Email | selected_owner_user_email | optional | string_t | Device.selected_owner: The owner selected by a DataBee user to assign to a device. Keys in object are user_id an integer, user_email a string and selected_on a datetime. SelectedOwner.user_email: The email address of the DataBee user that made the selection. | | Selected Owner DataBee User ID | selected_owner_user_id | optional | integer_t | Device.selected_owner: The owner selected by a DataBee user to assign to a device. Keys in object are user_id an integer, user_email a string and selected_on a datetime. SelectedOwner.user_id: This is the id that DataBee uses to link this to a specific user. | | Data Sources | sources | recommended | string_t Array | Device.backtrace: This object is a key value set that relates each field in the user to the earliest raw event that gave DataBee that particular value in the correlation. For example, `{'email_addr': 'email_activity.key=123456'}` | | Start Time | start_time | optional | timestamp_t | Device.start_time: The start time when a particular state of the user became valid. | | Type | type | optional | string_t | Device.type: The device type. For example: `unknown`, `server`, `desktop`, `laptop`, `tablet`, `mobile`, `virtual`, `browser`, or `other`. | | Type ID | type_id | required | integer_t | Device.type_id: The device type ID. | | Unique ID | uid | recommended | string_t | Device.uid: A universally unique identifier of the device. For example, the Windows TargetSID or AWS EC2 ARN. Used for integration with external systems or as an alternate join key. | | VPC UID | vpc_uid | optional | string_t | Device.vpc_uid: The unique identifier of the Virtual Private Cloud (VPC). For example: Often the VPC ARN similar to: `arn:aws:ec2:us-east-1:123456789012:vpc/vpc-1234567890abcdef0`. |