Forum Discussion

yumdarling's avatar
yumdarling
Icon for Community Manager rankCommunity Manager
3 months ago

Cato Connect Event: AMA with Professional Services

Ever wish you could get direct time with the experts?

On June 3rd, 2025 at 11:00 AM EDT, you’ll get just that — a live AMA with two of our Principal Consultants from the Cato Professional Services team.

We’ll cover topics like:

  • Designing and implementing a CMA deployment
  • Best practices we’ve seen across real-world environments
  • Your questions — seriously, bring them

Here’s how to get the most out of it:

  1. Click here to register and get the calendar invite and join us live
  2. Post your questions below in the comments — we’ll answer pre-submitted ones first, before tackling live chat during the session
    + See a question you like? Give it a “like” to help it rise to the top

Note: We won’t be able to look at specific CMA instances — demos will be done using internal environments.

That’s it — register, post your questions, and we’ll see you there!

Presenters:

Mihai Radoveanu
Principal Consultant
Professional Services, ItalyDavid Tudor
Principal Consultant
Professional Services, USA

                                                                 



 

 

 

If you run into any issues, @mention me or email us at community@catonetworks.com 

cato connect event

1 Reply

  • PrakashRIndia's avatar
    PrakashRIndia
    Satellite
    2 months ago

    The Cato Connect was wonderful. One of the issue we raised was around device posture policy basis domain and it was clarified that this falls under advanced configuration and can be done by support/CSM team. I raised ticket for the same and the response was that they can apply but from backend and at account level. I want to exclude some of my senior management from this policy but it is not feasible now since done at account level. Also I cant do testing by applying this device posture basis domain for some 2-3 users to see if it works properly and also no option from frontend to disable if there is any issue and totally depend on service ticket and backend team. This makes this good policy not to be deployed as it has potential risk since neither testing can be done nor exclusion can be done unlike any other device posture policy since policy deployed from backend and deployed at account level.