Getting Potential Device Vulnerability Overview

Description

Get the number of unmonitored and non-compliant devices in WSO2 EMM.

Resource Path /dashboard/potential-vulnerabilities

URL

/mdm-admin/dashboard/potential-vulnerabilities

HTTP Method GET

Request/Response Format application/json

cURL command

curl -v -L -G -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/dashboard/potential-vulnerabilities

For more information on how to generate the <EMM_API_TOKEN>, see Generating the EMM API Token.
By default, <EMM_HOST> is localhost. However, if you are using a public IP, the respective IP address or domain needs to be specified.
By default, <EMM_HTTPS_PORT> has been set to 9443. However, if the port offset has been incremented by n, the default port value needs to be incremented by n.

Example:

curl -v -L -G -H "Content-Type: application/json" -H "Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c" -k -v https://localhost:9443/mdm-admin/dashboard/potential-vulnerabilities

Sample output

> GET /mdm-admin/dashboard/potential-vulnerabilities HTTP/1.1
> User-Agent: curl/7.38.0
> Host: localhost:9443
> Accept: */*
> Content-Type: application/json
> Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c
< HTTP/1.1 200 OK
< Cache-Control: private
< Expires: Thu, 01 Jan 1970 05:30:00 IST
< Date: Sat, 30 Apr 2016 01:55:36 GMT
< Content-Type: application/json
< Content-Length: 164
< Server: WSO2 Carbon Server
[{"context":"potential-vulnerability","data":[{"group":"non-compliant","label":"Non-Compliant","count":5},{"group":"unmonitored","label":"Unmonitored","count":0}]}]

Sample JSON Output Definition

[  
   {  
      "context":"potential-vulnerability",
      "data":[  
         {  
            "group":"non-compliant",
            "label":"Non-Compliant",
            "count":5
         },
         {  
            "group":"unmonitored",
            "label":"Unmonitored",
            "count":0
         }
      ]
   }
]

Parameter	Definition
`context`	Defines the attribute, to which the data is being populated. In this use case the attribute is `potential-vulnerability`.
`data`	Defines the data received.
`group`	The devices are grouped as follows: `non-compliant`: The number of devices that have not complied to the policies enforced on the device by WSO2 EMM. `unmonitored`: The number of devices that have no policy assigned on them.
`label`	Defines the name of the grouped devices.
`count`	The number of devices in each category.