Security Hardening Adobe Acrobat DC for macOS
I would start with one thing and that’s work on your time to patch in your environment. Measure how many endpoints are out of date and average time to get machines patched once Adobe releases an update (plan on 40 updates a year if you use the core CC suite - 15 if you just deploy acrobat).

You can control it.
It’s something one person can tackle.
It is your best defense to get ready to take next steps on how the quickly patched software is used.

If you don’t have federated ID services, get that next. Then look at Adobe Console to use SSO / federation and then decide if you just manage apps and lock everyone out of Adobe Updates and have a side channel for patching. JAMF and Munki and Fleetsmith (cough, Apple) are the three solutions I would evaluate if you know nothing about MDM. If you know everything about MDM - still evaluate them and then expand to include your current MDM or others that might fit your niche.
Security is a war of attrition and you will never have enough time to train, hire, manage but you can get better at evaluating your biggest gaps, work to close them and then repeat the observe, measure, plan, act, measure, react cycle.