Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Certified Safe Software Service (TMCSSS) v1.069.00 of EAC to be released

    • Updated:
    • 10 Apr 2015
    • Product/Version:
    • Endpoint Application Control 1.0
    • Platform:
    • Windows 2008 Enterprise
    • Windows 2008 Server R2
    • Windows 2012 Enterprise
Summary

Certified Safe Software Service (TMCSSS) v1.069.00 of Endpoint Application Control (EAC) will be released on April 30, 2015 and has the following new features:

  • Support for Windows Store Applications (Metro Applications or Runtime Applications)

    Previously, the Certified Safe Software pattern only included 32-bit and 64-bit AMD/Intel-based applications. This release will be adding a new type of application to our Certified Safe Software pattern called the Windows Store Applications.
     
  • Application Name Normalization

    Removal of the suffix "x64" in display names of 231 64-bit applications. For example, the "Java x64" will be merged into the existing application name “Java". This means selecting only "Java" will cover both 64-bit and 32-bit versions of that application.

After the pattern update, TMCSSS-based 64-bit applications will not be visible in the application name.

When this happens, the policy and rules previously containing TMCSSS-based 64-bit applications may not function as expected. 32-bit applications are not affected by this change.

Customers affected are those who are using Endpoint Application Control 1.0  and above, with rules that include 64-bit applications based on TMCSSS pattern.

Details
Public

Before the pattern release date on April 30, edit your rules by selecting both 64-bit and 32-bit TMCSSS-based applications. For example, select both “Java” and “Java x64” applications so that the policies using the rules will still be able to detect 64-bit version of Java application whenever it is running on the system.

There is no need to recreate the policies and rules. All you have to do is update the affected policy by editing the rules and selecting the new name that contains both 32-bit and 64-bit applications.
Premium
Internal
Rating:
Category:
Install; Update
Solution Id:
1109367
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.