• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Adobe Creative Cloud Administration, Major Design Flaw, Vulnerabilities (Enterprise)

New Here ,
Jul 05, 2024 Jul 05, 2024

Copy link to clipboard

Copied

Adobe Creative Cloud does not, by default, automatically remove older versions of software when updating. This has potential to cause a lot of vulnerabilities as the old version is left behind on the system when it is auto updated by Adobe CC. Currently after deployment of Adobe CC the end-user can install their own software however, the end-user must manually check the box to remove old versions when auto-updating.

 

When packaging/creating profiles for Adobe CC, in the Adobe Admin Console, there is no way to enforce removal of older versions of Adobe Software during auto-updates. From an enterprise management perspective this exposes the clients to needless vulnerabilities.

 

Please allow IT administrators for Adobe to enforce automatic removal of old versions of Adobe software products when updating. When software is patched for vulnerabilities it makes no sense to leave behind the old vulnerable version.

 

Views

116

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Jul 08, 2024 Jul 08, 2024

@Matt38409715e24q We use Jamf to deploy the packages and then remove the older versions of the software via policies at a later date. It's a much more efficient method and we  control when we remove the older software, allowing users to transfer the previous settings before we remove the older version. However - we also don't allow our users to manually update anything. We test everything and schedule deployments to keep everyone on the same managed version.

Votes

Translate

Translate
Community Expert ,
Jul 08, 2024 Jul 08, 2024

Copy link to clipboard

Copied

@Matt38409715e24q 

I've moved your post to Enterprise & Teams

Jane

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 08, 2024 Jul 08, 2024

Copy link to clipboard

Copied

LATEST

@Matt38409715e24q We use Jamf to deploy the packages and then remove the older versions of the software via policies at a later date. It's a much more efficient method and we  control when we remove the older software, allowing users to transfer the previous settings before we remove the older version. However - we also don't allow our users to manually update anything. We test everything and schedule deployments to keep everyone on the same managed version.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines