Managing Secure Client

[Bucket]

Will it be possible to deploy and manage the Cisco + Secure connect secure client via Secure-X / XDR?

Is there anything special in the secure client installation file generated from the secure connect / Umbrella dashboard or can it be deployed by uploading the profile to Secure-X / XDR and then generating the installation file there? Is there any disadvantage?

[alemabrahao]

Maybe it will help you.

https://documentation.meraki.com/CiscoPlusSecureConnect/Cisco___Secure_Connect_Onboarding/Cisco__Sec...

[Bucket]

I don't think that is related. The document describes SSO for the Meraki and Umbrella dashboard.

[alemabrahao]

I think that it's not the right community. Are you looking for something about Meraki?

[Bucket]

I am asking about management and deployment of secure client, which is part of secure connect.This is the documentation from the Meraki page, but it leaves out some details.

https://documentation.meraki.com/CiscoPlusSecureConnect/Cisco__Secure_Connect_Now_Remote_Access

What I am curious about is whether secure client used for secure connect can (or shouldn't) be managed / deployed via Secure-X / XDR. Is there anything special about the installation file generated by Meraki and Umbrella or is it just the normal installer with a profile that can be used with any type deployment. When I read the documentation is sounds like I am able to deploy the secure client XML whatever way I want.

I find it hard to only talk about Meraki when talking about secure connect, when it seems to be a combination of Meraki, Umbrella and secure client.

[Gary_Geihsler1 · Accepted solution]

The management of Secure Client in the context of Cisco+ Secure Connect can be done any of the ways you might manage the client. SecureX deployment works, MDM will work, manual distribution will work. 

One aspect that is unique is that every time a user does their authorization to Cisco+ Secure Connect the xml profile is updated and placed in the proper file structure. This allows the admin to make changes to the client configuration without having to do any sort of push to the end users.