截屏视频帮助
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Checking 64 Bit Applications in Endpoint Protection Whitelist

创建时间: 17 3 月 2013 | 3 条评论

Hi,

I intend to use Symantec Endpoint Protection running in Lockdown mode to enforce Appliaction Whitelisting on Windows 7 64 bit running various 64 bit applications. To do this I need to create a File Fingerprint List for those 64 bit applications but my understanding is that the checksum utility provided with SEP only handles 32 bit applications. Can anyone suggest a workaround for incorporating 64 bits apps into the fingerprint list?

Thanks.

操作系统:

评论 条评论跳转至最新评论

.Brian 的图片

Are you on SEP 12.1? All features are supported on 64 bit, including System Lockdown. Where did you see that checksum.exe won't handle 64 bit apps?

I have this running in a test environment, 64 bit machines included.

System Lockdown will not work on 64 bit machines running SEP 11.x. It is not supported so there is no workaround.

Symantec Endpoint Protection 11.0 compatibility with 64-bit platform

Article:TECH102143  |  Created: 2007-01-23  |  Updated: 2010-12-03  |  Article URL http://www.symantec.com/docs/TECH102143

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

bruce.legge 的图片

Hi,

I have the information second-hand from an organisation running SEP 12.1. They can run SEP in Lockdown mode but the checksums they generate to create the file fingerprint list can only be generated for 32 bit applications, not 64 bit.

Can anyone confirm that the checksum utility in SEP 12.1 can handle 64 bit apps?

Thanks.

.Brian 的图片

It works just fine for me.

The KB article for it does not mention it won't work

Creating a file fingerprint list with checksum.exe

Article:HOWTO81199  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL http://www.symantec.com/docs/HOWTO81199

Since System Lockdown is fully supported in 12.1 and no mention is made in the KB article of it not working for 64 bit, I don't see why it won't work. But as I said, it already works for me.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.