@Etresoft, @DTS Engineer, thank you for your answers 🙏 At current moment I am gathering information about what we can technically make and achieve) Based on your answers I understand next (please correct me if I am wrong in any point): If we need to change a team (legally) and DeveloperId certificate - that's exactly whole new app (no options there). As @DTS Engineer said - if we legally should change everything and stop using previous brand name anywhere (including bundle ids) it's also here - whole new app release is required Whole new app release requires user approvals for System Extension/Proxy Configuration for nonMDM installation - we will not transfer user consent from old app - platform technical limitation. Without new app release and using existing DeveloperId certificate in fact we have got an option to make a superficial branding without changing app/bundle ids Without new app release and using existing DeveloperId certificate I guess I solved almost all issues and got positive results those could be applied by our company. But I suppose that proxy configuration will continue using bundle ID = com.myApp1.osx.proxy. Is it possible to make visible part (for Activity Monitor app at least) with another name for proxy, like MyNewAppProxy? Because by default it's using bundleId as a title in processes list as far as I remember.

Hello everyone. We have got the same issue on BigSur. I would like to join this thread and receive any reply from Apple Support :)

Thank you so much for full answer. Yes, we are distributing our application using Developer ID certificate with notarization. PKG passed notarization process successfully. We have solved the problem - 3rd party vendor confirmed that it was a false positive decision from their side. Right now the problem has beed solved. Thanks for your help 🙏

About the links - I got it 🙏. Thank you Regarding technical question - my question is incorrect, or this vulnerability doesn't related to Apps or it's a secret by Apple)? Right now it doesn't totally clear, if you can elaborate more I'll really appreciate it

Thanks a lot for your explanation and all answers. I got it - so only one way to avoid Blocked System Extension popup it distribute application only via MDM - company admin should install app using MDM system and whitelist required system extension. Now it's clear. 🤝