A strange infosec guideline implemented in our org where any exe application developed using Visual Studio on our laptop cannot be debugged on Visual studio itself. There is a blanket ban of executing any exe on our laptop recently preventing us from debugging any application developed using Visual studio. Now windows team is saying that they can give exception if our exe contains "Publisher Name" as "Microsoft" or "OrgName". We get option in Visual studio 2022 to set Publisher Name under Project file Properties for .Net framework 4.x but the same option is not available for .Netcore apps. Even though .Net framework 4.x has the option to set "Publisher Name" but the same is not getting reflected when we double click on the built exe.
Now the suggestion I needed here are:
any suggestion that put me in the right direction would be great help...Thanks in advance.
Edit: Adding screenshot for reference.
Edit 2: Adding screen shot from Windows Defender alert
A strange infosec guideline implemented in our org where any exe application developed using Visual Studio on our laptop cannot be debugged on Visual studio itself. There is a blanket ban of executing any exe on our laptop recently preventing us from debugging any application developed using Visual studio. Now windows team is saying that they can give exception if our exe contains "Publisher Name" as "Microsoft" or "OrgName". We get option in Visual studio 2022 to set Publisher Name under Project file Properties for .Net framework 4.x but the same option is not available for .Netcore apps. Even though .Net framework 4.x has the option to set "Publisher Name" but the same is not getting reflected when we double click on the built exe.
Now the suggestion I needed here are:
any suggestion that put me in the right direction would be great help...Thanks in advance.
Edit: Adding screenshot for reference.
Edit 2: Adding screen shot from Windows Defender alert
This is handled by the certificate the application is signed with. Getting your code signed through a credible certificate authority is almost the only way to distribute your software and have people trust your code.
Here's some good documentation how code signing works, how it verifies authenticity and more:
https://pkic.org/uploads/2013/10/CASC-Code-Signing.pdf
You could self sign, however, it will only apply to the local machine that has it installed.
DigiCert is what our company uses for our application certificates:
https://www.digicert.com/signing/code-signing-certificates