Data points collected by activated policies
Absolute policies control the collection of hardware, software, usage, and system information from your devices. The Hardware policy is always activated by default, but you need to activate other policies if you want to monitor additional device information in the Secure Endpoint Console. To learn about the specific data points that are collected when a particular policy is activated, refer to the appropriate section in this topic.
How frequently is data collected from a device?
| Symbol / Value | Meaning |
|---|---|
| ✔ | The Secure Endpoint Agent collects the data point on the indicated platform and shows it in the Secure Endpoint Console. |
| n/a | The data point does not apply to the indicated platform. |
| GAC | The data point is synced directly from the Google Admin console and shows in the Secure Endpoint Console. Applies to Chromebooks only. |
| † | The Secure Endpoint Agent collects the data point on the indicated platform but the data point is not shown in the Secure Endpoint Console. |
| ✘ | The Secure Endpoint Agent does not detect the data point on the indicated platform because the platform does not make the data available, or because there is no requirement to collect this data. |
For any enrolled device, the Secure Endpoint Agent and its Hardware Data Processing (HDP) component collect the following data points:
| Data point | Device platform | |||
|---|---|---|---|---|
| Windows | Mac | Chromebook | Linux | |
| Agent specific data points | ||||
| Identifier The unique Electronic Serial Number (ESN) assigned to the Secure Endpoint Agent that is installed on a device. | ✔ | ✔ | ✔ | ✔ |
| Last connected The date and time when a device's component manager last connected to the Absolute Monitoring Center. For online devices, the component manager connects every 15 minutes. Also see component manager (CTES). | ✔ | ✔ | ✔ | |
| Last core agent connection The date and time when the device's core agent last connected to the Absolute Monitoring Center. For online devices, the core agent connects once every 24.5 hours. Also see core agent (rpcnet). | ✔ | ✔ | ✔ | |
| Hardware last updated | ✔ | ✔ | ✔ | |
| Agent status The operating condition of a device's Secure Endpoint Agent. Possible values are Active (indicates that the device's agent has connected to the Absolute Monitoring Center), Inactive (indicates one of the following: the device was moved to another account; the device was unenrolled, but it is now set to be reactivated; or the device had Persistence enabled at the factory, but it has not yet called in to the Absolute Monitoring Center), and Disabled (indicates that the agent is either flagged for removal or removed from the unenrolled device). Inactive and Disabled devices do not consume a license. | ✔ | ✔ | ✔ | |
| Core agent version A field and report column showing the version number of the core agent (rpcnet) installed on a Windows or Mac device. For Chromebooks, it shows the version number of the Absolute for Chromebooks extension. You can find the latest version number in the topic "Secure Endpoint Agent release notes" for the current release. | ✔ | ✔ (shows Chromebook extension version) |
✔ | |
| Agent version The version number of the Secure Endpoint Agent installed on the device. | ✔ | n/a | ✔ | |
| Component manager The component manager (also known as CTES) is installed on top of the core agent and manages the agent components responsible for initiating device actions and collecting device data. Most agent components are controlled by policies, such as the Hardware and Installed Applications policies. The component manager typically connects to the Absolute Monitoring Center every 15 minutes, at a minumum, to send device data and receive instructions. | ✔ | ✘ | ✔ | |
| Component manager > Status Report column that shows the status of the component manager (CTES) installed on a Windows or Mac device. Possible values are: Healthy (CTES is communicating successfully with the Absolute Monitoring Center), Packet inspection detected (CTES is not communicating with the Absolute Monitoring Center. To learn how to resolve this issue, hover over the icon and click "Learn more" in the tooltip), and No Data (CTES is not communicating with the Absolute Monitoring Center, or the status is not available because version 1.0.0.2116 or higher is not installed on the device, or the device is not a Windows or Mac device). | ✔ | ✘ | ✔ | |
| Persistence agent A field and report column showing the version number of the Absolute Persistence agent (rpcnetp), which is embedded in the firmware of a Windows device by the device manufacturer. If a device's Secure Endpoint Agent is tampered with or removed, the Persistence agent connects to the Absolute Monitoring Center, which triggers the core agent (rpcnet) to be downloaded and reinstalled on the device. (rpcnetp) | n/a | n/a | ✔ | |
| Firmware Persistence status The status of the Absolute Persistence module, which is embedded in the firmware of a Windows device by the device manufacturer. The module is responsible for monitoring the health of the Secure Endpoint Agent and restoring it if it's missing, damaged, or tampered with. Possible statuses are: Active, Deactivated, Not Supported, Pending, Pending Removal, and Unknown. | n/a | n/a | ✔ | |
| Firmware Persistence version The version number of the Absolute Persistence module, which is embedded in the firmware of a Windows device by the device manufacturer. The module is responsible for monitoring the health of the Secure Endpoint Agent and restoring it if it's missing, damaged, or tampered with. Possible versions are 1.0 and 2.x.x.x. | n/a | n/a | ✔ | |
| Activation date A field and report column that shows the date and time that the device completed its first check-in to the Absolute Monitoring Center and the device's Secure Endpoint Agent was activated. | ✔ | ✔ | ✔ | |
| Un-enrollment date A report column showing the date and time when an Unenroll Device request was submitted for a device. The device's Secure Endpoint Agent is set to Disabled. | ✔ | ✔ | ✔ | |
| ThinkShield TraceLock | n/a | n/a | n/a | |
| Playbooks | n/a | n/a | n/a | |
| Recovery Environment A customized WinPE image installed at the firmware-level of a device when the Playbooks policy is activated. The Absolute Recovery Environment is responsible for performing the instructions contained in each playbook. > Version | n/a | n/a | n/a | |
| Recovery Environment > Installed | n/a | n/a | n/a | |
| Device data points | ||||
| Device name The name assigned to the device in the operating system. For Chromebooks, device name is not applicable and therefore shows as "Chrome" in the Secure Endpoint Console. | ✔ | ✔ | ✘ | ✔ |
| Username A field and report column showing the username of the user who was logged in to the device when an agent connection occurred. If no user was logged in during the most recent agent connection, the last detected username shows. Note that if the device is shared by multiple users, the Username field shows the previous logged in user and the Current username field shows the most recent logged in user. | ✔ | ✔ | ✔ | |
| Domain The name of the device's Windows domain, if applicable. | ✔ | n/a | ✔ | |
| Encryption Status The detected status of a Windows or Mac device with respect to the installation of a full-disk encryption product. Possible values are: Encrypted, Used Space Encrypted, Not Encrypted, Suspended, Encryption In Progress, Decryption in Progress, Not Detected and No Data. | ✔ | n/a | ✘ | |
| Full system name (called System name on Mac) | ✔ | n/a | ✘ | |
| Operating System | ||||
| Name The name and version of the operating system detected on a device. The operating system is software that manages the software and hardware installed on a computer and allows programs and services to run. It is responsible for the basic operations of a computer system. | ✔ | ✔ | ✔ | ✔ |
|
For some Mac devices, the Edition field holds this information. |
✔ | ✔ | GAC | ✔ |
| Edition | n/a | ✔ | n/a | n/a |
| Build | ✔ | ✔ | n/a | n/a |
| CSDVersion / OS Service Pack | ✔ | n/a | n/a | n/a |
| Architecture | ✔ | n/a | ✔ | ✔ |
| Installation date | ✔ | ✔ | n/a | ✔ |
| Last boot time | ✔ | ✔ | n/a | ✔ |
| Update build revision | ✔ | n/a | n/a | n/a |
| Current build | ✔ | n/a | n/a | n/a |
| Release ID | ✔ | n/a | n/a | n/a |
| Edition ID | ✔ | n/a | n/a | n/a |
| Manufacturer | ✔ | n/a | n/a | ✔ |
| Product key | ✔ | ✘ | n/a | ✘ |
| Serial number | ✔ | n/a | n/a | ✔ |
| Windows directory | ✔ | n/a | n/a | n/a |
| Other OS description | ✔ | n/a | n/a | n/a |
| System Information | ||||
| Hard Drive Free Space The amount of storage currently available on a hard disk, expressed in gigabytes. | ✔ | ✔ | n/a | ✔ |
| Total physical memory The amount of dynamically accessible memory on a device, expressed in gigabytes. | ✔ | ✔ | ✔ | ✔ |
| Available physical memory | ✔ | ✔ | ✔ | ✔ |
| Total virtual memory | ✔ | ✔ | n/a | ✔ |
| Available virtual memory | ✔ | ✔ | n/a | ✔ |
| Local IP address The local IPv4 Internet Protocol address that identifies a device that is connected to a private network. | ✔ | ✔ | ✔ | ✔ |
| Local IPv6 address The local IPv6 Internet Protocol address that identifies a device that is connected to a private network. | ✔ | ✔ | ✔ | ✔ |
| Public IP address The public IPv4 Internet Protocol address that identifies a device that is connected to the Internet. | ✔ | ✔ | ✔ | ✔ |
| Public IPv6 address The public IPv6 Internet Protocol address that identifies a device that is connected to the Internet. | ✔ | ✔ | ✔ | ✔ |
| Page file space | ✔ | n/a | n/a | n/a |
| Page file | ✔ | n/a | n/a | n/a |
| Boot device | ✔ | ✔ | n/a | ✔ |
| Locale | ✔ | ✔ | ✔ | ✔ |
| Name | ✔ | ✔ | ✔ | ✔ |
| System directory | ✔ | ✔ | n/a | n/a |
| Make The manufacturer of a device. | ✔ | ✔ | GAC | ✔ |
| Model The manufacturer's designated name for the type of device. | ✔ | ✔ | GAC | ✔ |
| System type | ✔ | ✔ | n/a | ✔ |
| Serial number The identification number assigned to the device by the device manufacturer. For Windows devices, this value may correspond to the serial number of the BIOS, the motherboard, or the chassis, depending on the manufacturer. | ✔ | ✔ | GAC | ✔ |
| Time zone | ✔ | ✔ | n/a | ✔ |
| System integrity protection status | n/a | ✔ | n/a | n/a |
| BIOS | ||||
| Release date | ✔ |
n/a |
n/a | ✘ |
| Language | ✔ | n/a | ✘ | |
| Serial number | ✔ | n/a | ✔ | |
| Version | ✔ | GAC | ✔ | |
| SMBIOS version | ✔ | n/a | ✔ | |
| SMBIOS major version | ✔ | n/a | ✘ | |
| SMBIOS minor version | ✔ | n/a | ✘ | |
| Manufacturer | ✔ | n/a | ✔ | |
| Version date | ✔ | n/a | ✔ | |
| Asset tag | ✔ | n/a | ✘ | |
| Supervisor Credentials |
✔ Supported models only |
n/a | n/a | |
|
The following BIOS-related data points are not shown in Device Details, but you can add the columns to a device report. |
||||
|
TPM >
|
✔ | n/a | n/a | n/a |
|
Boot Info >
|
✔ | |||
| Battery | ||||
|
ID |
✔ | n/a | ✘ | ✔ |
| Name | ✔ | ✔ | ||
| Serial number | ✔ | ✔ | ||
| Capacity | ✔ | ✔ | ||
| Estimated charge remaining | ✔ | ✔ | ||
|
Estimated runtime This data point is not shown in Device Details, but you can add the column to a device report. |
✘ | ✘ | ||
| Expected life | ✘ | ✘ | ||
| Max recharge time | ✘ | ✘ | ||
| Memory | ||||
|
The Secure Endpoint Agent cannot collect memory information for MacBook Pro devices with an Apple M1 chip. |
||||
|
ID |
✔ | ✔ | ✔ | ✔ |
| Part number | n/a | ✔ | n/a | ✔ (✘ for ARM devices) |
| Manufacturer | ✔ | ✔ | n/a | ✔ (✘ for ARM devices and RHEL OS) |
| Serial number | ✔ | ✔ | n/a | ✔ |
| Size (bytes) | ✔ | ✔ | ✔ | ✔ |
| Slot | ✔ | ✔ | n/a | ✔ |
| Speed | ✔ | ✔ | n/a | ✔ |
| Type (or Type Detail) | ✔ | ✔ | n/a | ✘ |
| Status | n/a | ✔ | n/a | ✘ |
|
Chassis Type This data point is not shown in Device Details, but you can add the column to a device report. |
✔ | n/a | n/a | ✘ |
| CPU | ||||
|
ID For Mac devices, this field shows the same value as the Name field. |
✔ | n/a | ✔ | ✔ |
| Name | ✔ | ✔ | ✔ | ✔ |
| Architecture | ✔ | ✔ | ✔ | ✔ |
| Bus speed | ✘ | ✔ | n/a | ✔ (✘ for ARM devices) |
| Data width | ✔ | ✘ | n/a | ✔
(✘ for ARM devices) |
| Instruction set | ✘ | ✔ | n/a | ✔ |
| Logical cores | ✔ | ✔ | n/a | ✔ |
| Physical cores | ✔ | ✔ | n/a | ✔ |
| Processor speed The rate at which the computer processor computes, measured in megaHertz. | ✔ | ✘ | n/a | ✔ |
| Processor number | ✘ | ✘ | ✔ | ✔
|
| L2 cache size | ✔ | ✔ | n/a | ✔ (✘ for ARM devices) |
| L2 cache speed | ✔ | ✘ | n/a | ✘ |
| L3 cache size | ✔ | ✔ | n/a |
✔ |
| L3 cache speed | ✔ | ✘ | n/a | ✘ |
| CD ROM | ||||
| ID | ✔ | n/a | n/a | n/a |
| Name | ||||
| Drive | ||||
| Manufacturer | ||||
| Media loaded | ||||
| Media Type | ||||
| Description | ||||
| Status | ||||
| Transfer rate | ||||
| PnP device ID | ||||
| SCSI target ID | ||||
| Sound Device | ||||
| The following data points are collected for each detected sound device: | ||||
|
ID For Mac devices, this field shows the same value as the Name field. |
✔ | n/a | ✘ | ✔ |
| Name | ✔ | n/a | ||
| Manufacturer | ✔ | ✔ |
||
| Camera | ||||
|
The following data points are collected for each detected camera: |
||||
| ID | ✔ | ✔ | ✘ | ✔ (✘ for ARM devices) |
| Name | ✔ | ✔ | ||
| Description | ✔ | n/a | ||
| Model | ✘ | ✔ | ||
| Is Enabled | ✔ | ✔ | ||
| Display | ||||
| The following data points are collected for each detected display: | ||||
| ID | ✔ | n/a | n/a | ✔ |
| Name | ✔ | n/a | ✔ | ✔ |
| PnP device ID | ✔ | n/a | n/a | ✘ |
| Adapter type | ✔ | n/a | n/a | ✘ |
| Adapter description | ✔ | ✔ | n/a | ✘ |
| Manufacturer | ✔ | ✔ | n/a | ✘ |
| Adapter RAM | ✔ | n/a | n/a | ✘ |
| Driver version | ✔ | n/a | n/a | ✘ |
| Number of colors | ✔ | n/a | n/a | ✘ |
| Resolution | ✔ | n/a | ✔ | ✘ |
| Bits per pixel | ✔ | n/a | n/a | ✘ |
| Depth | n/a | ✔ | n/a | ✘ |
| Height | ✔ | ✔ | ✔ | ✔ |
| Width | ✔ | ✔ | ✔ | ✔ |
| Refresh rate | n/a | ✔ | n/a | ✘ |
| Horizontal resolution | † | n/a | n/a | † |
| Vertical resolution | † | n/a | n/a | † |
| Input | ||||
| Keyboards | ||||
|
The following data points are collected for each detected keyboard: |
||||
| ID | ✔ | n/a | ✘ | ✘ |
| Name | ✔ | |||
| Description | n/a | |||
| Layout | n/a | |||
| PnP device ID | n/a | |||
| Number of function keys | n/a | |||
| Pointing Devices | ||||
|
The following data points are collected for each detected pointing device: |
||||
|
ID For Mac devices, this field shows the same value as the Name field. |
✔ | n/a | ✘ | ✘ |
| Name | ✔ | |||
| Manufacturer | ✔ | |||
|
The following data points are not shown in Device Details, but you can add the columns to a device report. |
||||
| Number of buttons | ✔ | n/a |
✘ |
✘ |
| Power management supported | n/a | |||
| PnP device ID | n/a | |||
| Handedness | n/a | |||
| Hardware type | n/a | |||
| Cellular Modem | ||||
| The following data points are collected for each detected cellular modem: | ||||
| Adapter version | ✔ | n/a | n/a | ✘ |
| ID | ||||
| Description | ||||
| Enabled | ||||
| Current network name | ||||
| Current network numeric code | ||||
| Home network name | ||||
| Home network numeric code | ||||
| IMEI | ||||
| IMSI | ||||
| Phone number | ||||
| SIM serial | ||||
| SIM ICCID (Integrated Circuit Card Identifier) | ||||
| Type | ||||
| Network Adapters | ||||
| The following data points are collected for each detected adapter: | ||||
| ID | ✔ | n/a | ✔ | ✔ |
| Name | ✔ | ✔ | ✔ | |
| Adapter type | n/a | n/a | ✔ | |
| Installed | n/a | n/a | ✔ | |
| IPv4 address | ✔ | ✔ | ✔ | |
| IPv6 address | ✔ | n/a | ✔ | |
| IP subnet | n/a | n/a | ✔ | |
| Default gateway | n/a | n/a | ✔ | |
| DHCP enabled | n/a | n/a | ✔ | |
| DHCP server | n/a | n/a | ✔ | |
| DHCP lease expires | n/a | n/a | ✔ | |
| DHCP lease obtained | n/a | n/a | ✘ | |
| MAC address | ✔ | GAC | ✔ | |
| Manufacturer | ✔ | n/a | ✔ | |
| Product type | n/a | n/a | ✔ | |
| Speed | ✔ | n/a | ✔ | |
| Network SSID | ✔ | n/a | ✔ | |
| Video controllers | ||||
| The following data points are collected for each detected adapter: | ||||
| ID | ✔ | n/a | n/a | n/a |
| Name | ||||
| Adapter description | ||||
| Adapter RAM | ||||
| Adapter type | ||||
| Bit per pixel | ||||
| Driver version | ||||
| Number of colors | ||||
| Refresh rate | ||||
| Horizontal resolution | ||||
| Vertical resolution | ||||
| Resolution | ||||
| Storage - Disk | ||||
| The following data points are collected for each detected disk: | ||||
|
ID For Mac devices, this field shows the same value as the Name field. |
✔ | n/a |
n/a |
✔ |
| Name | ✔ | ✔ | ✔ | |
| Description | ✔ | n/a | ✔ | |
| Disk index | ✔ | n/a | ✘ | |
| Bytes per sector |
n/a |
n/a |
✔ | |
| Firmware revision | ✔ | n/a | ✘ | |
| Manufacturer | ✔ | n/a | ✔ | |
| Media type | ✔ | n/a | ✘ | |
| Model | ✔ |
n/a |
✔ | |
| Number of partitions | n/a | n/a | ✘ | |
| Sectors per track | n/a | n/a | ✘ | |
| Serial number | ✔ | n/a | ✔ | |
| Size (bytes) |
✔ | ✔ | ✔ | |
| Status | n/a | n/a | ✘ | |
| Total cylinders | n/a | n/a | ✘ | |
| Total heads | n/a | n/a | ✘ | |
| Total sectors | n/a |
n/a |
✘ | |
| Total tracks | n/a |
n/a |
✘ | |
| Total tracks per cylinder | n/a | n/a | ✘ | |
| Storage - Volumes | ||||
| The following data points are collected for each detected volume: | ||||
| ID | ✔ | ✔ | n/a | ✔ |
| Name | ✔ | ✔ | ✔ |
|
| Boot | ✔ | ✔ | ✘ | |
| Compressed | ✔ | n/a | ✘ | |
| Drive letter | ✔ | n/a | ✘ | |
| File system | ✔ | ✔ | ✔
|
|
| Serial | ✔ | ✔ | ✔
|
|
| Size (bytes) | ✔ | ✔ | ✔
|
|
| Free space (bytes) | ✔ | ✔ | ✔ |
|
| Mount point | n/a | ✔ | ✔
|
|
| Printing | ||||
| The following data points are collected for each detected printer: | ||||
|
ID For Mac devices, this field shows the same value as the Name field. |
✔ | n/a | ✘ | ✘ |
| Name | ✔ | |||
| Driver | ✔ | |||
| Server | ✘ | |||
| Share | ✘ | |||
| Port | ✘ | |||
| USB | ||||
| The following data points are collected for each detected USB device: | ||||
| Name | ✔ | ✘ | ✘ | ✘ |
| Manufacturer | ||||
| PnP device ID | ||||
| Anti-malware | ||||
| The following data points are collected for the anti-malware software detected on the device: | ||||
| Product name | ✔ | ✔ | n/a | ✘ |
| Version | ||||
| Definition | ||||
| Definition date | ||||
| Last updated | ||||
In addition to the hardware data points shown for Chromebooks in the Hardware data points section, Absolute collects additional Chromebook data points from the Google Admin console. To view these data points, open a device report and add the report columns under Chromebook.
When an Application Resilience policy is activated on a device, the Secure Endpoint Agent collects the following data points:
- Last App Resilience scan The date and time the Application Resilience (RAR) component of the Secure Endpoint Agent last ran a status check on the device.
-
Application Resilience
- Events last 30 days
- Failures last 30 days
- Repairs last 30 days
- Reinstalls last 30 days
Depending on the application, it also collects the following data points:
Resilient application Data points BitLocker® - Status (assessed compliance status of the application)
- Repair status (success or failure of the last attempted repair)
- Status checked (date and time when Status last checked)
- Last updated (date and time the status check results were made available in the console)
- Became compliant / Became non-compliant (date when the Secure Endpoint Agent last detected the application changed compliance status)
-
Status details, which may include the following information, depending on the application’s Status:
- application version
- compatibility of OS (operating system) and TPM (trusted platform module) for BitLocker
- encryption method—AES-128 or AES-256
- encryption completeness
- protection status is on or off
- drive lock status is locked or unlocked
If you selected BitLocker with Standalone MBAM, Application Resilience repairs and reinstalls MBAM and collects and reports any exceptions.
Microsoft® SCCM - Status (assessed compliance status of the application)
- Repair status (success or failure of the last attempted repair)
- Status checked (date and time when Status last checked)
- Last updated (date and time the status check results were made available in the console)
- Became compliant / Became non-compliant (date when the Secure Endpoint Agent last detected the application changed compliance status)
-
Status details, which may include the following information, depending on the application’s Status:
- application version
- status of the admin share
- date and time of the last hardware inventory scan
- date and time of the last software inventory scan
- status of key application services
- status of key registry entries
- nature of any repairs or reinstalls initiated
For all other supported applications except for BitLocker and Microsoft SCCM
- Status (assessed compliance status of the application)
- Repair status (success or failure of the last attempted repair or reinstall)
- Status checked (date and time when Status last checked)
- Last updated (date and time the status check results were made available in the console)
- Became compliant / Became non-compliant (date when the Secure Endpoint Agent last detected the application changed compliance status)
-
Status details, which may include the following information, depending on the application’s Status:
- application version
- status of key application services
- status of key registry entries
- nature of any repairs or reinstalls initiated
The Application Resilience policy is supported on Windows devices only.
The Secure Endpoint Agent collects the following data points when the Custom Data policy is activated on a Windows device:
Custom Data is only supported on Windows devices.
| Data point | |
|---|---|
| Custom data points | Provided by Absolute and added to the Custom Data policy by you. These data points are unique to you. |
|
Automatically included in the Custom Data policy, but must be enabled by you:
|
|
The Secure Endpoint Agent collects the following data points when the Device Compliance policy is activated on a Windows or Mac device:
The Device Compliance policy does not include unique data points. Instead, it collects data points from other policies as listed in the following table.
| Policy | |
|---|---|
|
|
|
|
|
|
|
|
The Secure Endpoint Agent collects the following data points when the Device Usage policy is activated on a Windows, Mac, or Chromebook device:
The Secure Endpoint Agent collects the following data points when the Endpoint Data Discovery (EDD) policy is activated on a Windows or Mac device:
The EDD policy is not supported on Chromebook devices.
| Data point | Platform | |
|---|---|---|
| Windows | Mac | |
| Scan Date | ✔ | ✔ |
| Rule | ✔ | ✔ |
| Matched token (content string that matched the Rule) | ✔ | ✔ |
| Lexicon line number that was matched | ✔ | ✔ |
| File Name | ✔ | ✔ |
| File Extension | ✔ | ✔ |
| File Type | ✔ | ✔ |
| File Path | ✔ | ✔ |
| File Owner | ✔ | ✔ |
| File Created | ✔ | ✔ |
| File Modified | ✔ | ✔ |
| File Accessed | ✔ | ✘ |
The Secure Endpoint Agent collects the following data points when the Full-Disk Encryption Status policy is activated on a Windows or Mac device:
The Full-Disk Encryption policy is not supported on Chromebook devices.
| Data point | Platform | |
|---|---|---|
| Windows | Mac | |
| Encryption > Status | ✔ | ✔ |
| Encryption > Product Name | ✔ | ✔ |
| Encryption > Version | ✔ | ✔ |
| Encryption > Algorithm | ✔ |
✔ |
| Encryption > Comments | ✔ | ✔ |
| Encryption > Key Size | ✔ |
✔ |
| Encryption > SED Capable | ✔ | ✔ |
| Encryption > Last Updated | ✔ | ✔ |
| Encryption > All Drives Encrypted | ✔ | ✔ |
| Encryption > Last BitLocker key change | ✔ | n/a |
The Secure Endpoint Agent collects the following data points when the Geolocation Tracking policy is activated on a device:
| Field | Platform | ||
|---|---|---|---|
| Windows | Mac | Chromebook | |
| Device Location > City | ✔ | ✔ | ✔ |
| Device Location > State/Province | |||
| Device Location > Country | |||
| Location (Latitude, Longitude) > Latitude | |||
| Location (Latitude, Longitude) > Longitude | |||
| Geolocation technology > Type | |||
| Geolocation technology > Accuracy (meters) | |||
| Geolocation Tracking > Last data received | |||
| Additional data points related to Wi-Fi Positioning geolocation technology: | |||
| SSID and BSSID of nearby access points | ✔ | ✔ | ✘ |
| Signal strength of nearby access points | |||
| Wi-Fi error | |||
The Secure Endpoint Agent collects the following data points when the Installed Applications policy is activated on a Windows or Mac device:
The Installed Applications policy is not supported on Chromebook devices.
| Data point | Platform | |
|---|---|---|
| Windows | Mac | |
| Application | ✔ | ✔ |
| Version | ✔ | ✔ |
| Publisher | ✔ | ✔ |
| Installed (date) | ✔ | ✔ |
| Install location | ✔ | ✔ |
| Identifier | ✔ | ✔ |
| OS Name | ✔ | ✔ |
| Username | ✔ | ✔ |
|
The following data points are available when the prerequisites for Required Applications are met. |
||
|
Compliance status (including reasons for non-compliance) |
✔ | ✔ |
| Last compliance change | ✔ | ✔ |
| Number of Compliant | ✔ | ✔ |
| Number of Non-compliant | ✔ | ✔ |
| Number of Unknown | ✔ | ✔ |
The Secure Endpoint Agent collects the following data points when the Web Usage policy is activated on a Windows
The Web Usage policy is not yet supported on Mac devices.
| Field | Platform | |
|---|---|---|
| Windows | Chromebook | |
| Website | ✔ | ✔ |
| Webpage title | ✔ | ✔ |
| Web usage > Daytime | ✔ | ✔ |
| Web Usage > Evenings and weekends | ✔ | ✔ |
| Username (of each logged in user) | ✔ | ✔ |




