The attributes shown in Table 4 should help clarify the difference between compliance policies.

Table 4

Compliance Attributes

ISE Compliance Attributes

Fiberlink MaaS360 Compliance Attributes

Before using the DeviceCompliantStatus attribute provided by the MDM, especially if the ISE administrator is not the MDM administrator, great care is needed to ensure network access is not restricted due to a non-related MDM compliancy condition. The administrator must realize that MDM compliance is not specific to security concerns and that the MDM is responding to compliance conditions outside of the network domain. This point is clarified in Table 5 by looking at the available MDM responses to a non-compliant condition.

Table 5

MDM Responses

 

 

Action Type

Options

Profile Removal

OS Version Enforcement

Encryption Enforcement

Integrating Fiberlink MaaS360 with Cisco Identity Services Engine

35

 

 

Page 35
Image 35
Cisco Systems MaaS360 manual Action Type Options