Compliance data, meaning compliance or on-compliance with any policies that you have defined within WORKFLOW/AUDIT, can be retrieved from the /compliance endpoint.
The output is a list where each entry represents a policy, along with its description and two other lists, one with the device IDs of compliant devices, and the other with device IDs for non-compliant devices.
Example:
{
"data": [
{
"policy": "Standard Operator Station",
"description": "Operator station with Siemens hardware, Windows 11 & basic infrastructure environment (OS, whitelisting, backup, patches)",
"compliantDevices": [],
"nonCompliantDevices": [
"FRKIBKMZ301",
"FRKQLZDG302",
"FRKZMDHT303",
"FRKBMWOH304",
"FRKMGKHI305",
"FRKWGUZT306"
]
},
{
"policy": "Outdated OS",
"description": "Must not run outdated Windows versions",
"compliantDevices": [
"FRKRNWPJ292",
"FRKZUGFN310",
"FRKVMDTP311",
"FRKFZWLA332",
"FRKIBKMZ301",
"FRKQLZDG302",
"FRKJRDYZ312",
"FRKWPXUJ313",
],
"nonCompliantDevices": [
"CLTFUQIV1334",
"CLTMLXVG1335",
"CLTDSWUV1336",
"CLTFOJYW1464",
]
}
],
"info": {
"user": "John Doe",
"origin": "OTbase Inventory 8.00"
}
}
Unlike other endpoints, output for /compliance is not paged as you wouldn't expect huge output volumes. -- Note that compliance data is also included in the /devices data model if you use include=compliance or include=all.
Comments
0 comments
Please sign in to leave a comment.