TOS Usage Data

General

The following table lists the general TOS information included in the TOS Usage report.

Report Information	Description
Report metadata	Date Time Report serial number
Site name	The name of the site on which TOS is deployed
License file ID	The license file ID
License type	Evaluation/Production
Site type	The type of site on which TOS is deployed
Site ID	Unique ID generated by TOS per deployment
TOS Status
High availability status	enabled/disabled
Disaster recovery status	enabled/disabled

Devices

The following table lists the information collected for each device monitored by TOS.

Information Collected	Description
ID	The device ID
Device Parent ID	The ID of the management device. If the device is a managed device it will include both the Device ID and the Device Parent ID
Vendor	Device vendor name. Used to identify which devices require a license.
Model	The device model name. Used to identify which devices require a license.
Model number	The device model number. Used to identify which devices belong to small and medium sized enterprises
Device name	The name of the device entered into TOS
Domain	The domain where the device is deployed. Used to better understand the division of devices across domains.
Is the device a cluster	Indicator whether TOS consider the device as part of a cluster.
Is the device a virtual context	Indicator whether TOS considers the device as part of a virtual context. Used to help customers better understand the total device count made up of both physical and virtual devices.
Virtual context name	The name of the virtual context to which the device belongs
Is the device disabled	Indicator whether the device is disabled. Used to determine whether the device requires a license.
Check Point only. Management ID of the primary member of a CMA or MDS	The management IF of a primary member of a Check Point CMA or MDS. Used to determine whether a device is a secondary device and therefore does not require a license.
Number of rule on the device in current revision	Helps determine whether the device belongs to a small or medium sized enterprise. Also used for identifying monitored devices with no policies associated with it.
Device license status	For pre-flip customers, Tufin needs to know whether a device is unlicensed. Devices that are disabled don't require a license and therefore need to be excluded from the device count.

Cloud

The following table lists the information collected for the following cloud entities.

Information Collected	Description
VPC/VNET ID Billable VM Count Unbillable VM count	The billable/unbillable VM count is used to determine the number of licenses required.
Cisco ACI ID Daily count of Cisco ACI leafs	The number of Cisco ACI leafs for every monitored Cisco ACI system. Used to determine how many licenses are required.
NSX ID Daily count of NSX CPUs	Number of NSX-T CPUs and cores. Used to determine how many licenses are required.

Information Collected

Description

VPC/VNET

ID
Billable VM Count
Unbillable VM count

The billable/unbillable VM count is used to determine the number of licenses required.

Cisco ACI

ID
Daily count of Cisco ACI leafs

The number of Cisco ACI leafs for every monitored Cisco ACI system. Used to determine how many licenses are required.

NSX

ID
Daily count of NSX CPUs

Number of NSX-T CPUs and cores. Used to determine how many licenses are required.

SecureApp Applications

The following table lists the information collected for SecureApp Applications.

Information Collected	Description
ID	The application ID
Name	The application name
Status	Used to help determine how many applications are actually being monitored.