Security

Where is the best place to see what informaton CP knows about a device in order to then use some of this information to build policies?

 

IIs it limited to just info found withintin the endpoint repostiroy, or can you also use info found within the Request Details>Input>Computed attrreibutes form for the device in Access Tracker?  

 

Ive seen similar devices, using the same enforcement profiles and onbaorded in the same way, showing from very limited device attributes, to more comprehensive info with the Identity>Endpoints section of the Config.  So for example, two ipads, I would expect to show very similar attrivutes, but one may have 2 or 3 fields, the otehr abotu 20.  Is there any reason for this?

 

Also, is it possible to remotely wipe a device? Ive seen  some conflicting informaiton, and just wondered if it was possible without MDM integration, so just to devices that had ben directly onboard with CP.

 

Thanks

 

Either Endpoints or in access tracker as you mentioned. ClearPass does not have the ability to wipe devices as it does not manage them.

Thanks..

 

What is meant by this I found in an online doc...

 

Triggering Actions Performed on Endpoints

To trigger actions that are performed on endpoints, select an endpoint by clicking the check box and click the Trigger Server Action button from the Endpoints page.

For example, locking a device, triggering a remote, enterprise wipe, and so on.

The following figure displays the Trigger Server Action page:

 

Action Description

Specifies the description of the action. For example, the description can be "Delete all information stored" if the configured action is Remote Wipe.

 

I had also added some further info to original post (about differences in device info) before I saw your reply.. any ideas on this one?

 

Thanks

Those are triggers to an EMM solution. If you’re not using one, they’re not used.

Thanks.. so those devices that have been onboared using our MDM (Mobile Iron) and known to CP, CP could instruct a remote wipe, but not those just onboarded directly?

Yes, correct, but you generally want to initiate EMM commands in the EMM platform itself.