Hi, I am looking for a guide on possibilities to create and assign a certificate to an executable that could be later used for TIE reputation whitelisting purposes. The idea is to have the least possible cost and effort solution that would allow for assigning a positive reputation to software in TIE across different file versions.
The problem I am currently facing is in house Software created without certificates cannot be effectively whitelisted as it changes to frequently for the file whitelisting to have a lasting impact. Whiteout whitelisting the Software has unknown TIE reputation which leads to scans with all ATP modules and in result, performance problems.
Thank you in advance for any clarification on this subject!
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.