Cisco Systems MaaS360 manual Conclusion, Disclaimer

Page 41

Figure 29

AnyConnect Provisioning Profile

Conclusion

The integration of the network policy enforced by Cisco ISE and the device policy offered by the Fiberlink MaaS360 MDM engine offers a new paradigm for BYOD deployments where security and productivity are not competing objectives.

Disclaimer

The Fiberlink MaaS360 configurations shown in this document should not be considered validated design guidance with respect to how the Fiberlink MaaS360 should be configured and deployed. They are provided as a working example that details how the case studies explored in the CVD can be carried forward to the MDM in an effort to provide a fully integrated and complementary policy across both platforms. This in turn will result in a comprehensive solution where the network and mobile devices are in pursuit of a common business objective. Fiberlink MaaS360 is the only source for recommendations and best practices as it applies to their products and offerings.

Integrating Fiberlink MaaS360 with Cisco Identity Services Engine

41

 

 

Image 41
Contents Revised August 6 Page Page Overview Fiberlink MaaS360 Capabilities and FeaturesCapability Features Fiberlink MaaS360-Key Capabilities Deployment Models Import MDM Certificate to ISE Getting Fiberlink MaaS360 Ready for ISEExporting the MDM Site Certificate with Internet Explorer Grant ISE Access to the Fiberlink MaaS360 API Manage Administrator Account Add Account Add MDM Server to ISE Configure the MDM API on ISE Message Explanation Verify Connectivity to MDMReview MDM Dictionaries DMZ Enterprise IntegrationFiberlink MaaS360 Cloud Extender Download Cloud Extender Installation Wizard AD Group Memberships Active Directory/LDAP IntegrationOwnership User Group Restrictions MDM Profiles Create Policies Shows the flow of this process MDM APNS/GCN Mobile Client Application-Fiberlink MaaS360 AgentDevice Ownership MDM On-boarding User ExperienceMDM Enrollment MDM Enrollment-Terms of Acceptance Pass Code Complexity Enterprise Application StoreInstallation of Maas360 Application Data at-Rest Corporate DataForced CoA from ISE Corporate WipeISE Compliance versus MDM Compliance Verify Device ComplianceEnd User Portal Action Type Options Device Scanning Intervals Device Compliance/RestrictionsManually Updating the MDM Server PINLockStatusRegisterStatus Manage Lost/Stolen DevicesJailbroken or Rooted devices Application Distribution Cisco Applications Jabber, etc Disclaimer Conclusion