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

Create a technical support case if you need further support.

Deep Security Agent Incompatibility Issue with AWS Windows and Linux Instances using smBIOS 2.7

    • Updated:
    • 11 Jul 2018
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 9.6
    • Deep Security As A Service
    • Platform:
    • Amazon AMI 32-bit
    • Amazon AMI 64-bit
    • Linux All
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Foundation R2
    • Windows 2012 Standard R2
Trend Micro has released new versions of the Trend Micro Deep Security Agent (DSA) to address incompatibilities introduced by smBIOS 2.7 of AWS Elastic Compute Cloud (EC2) Windows and Linux Amazon Machine Images (AMIs).  
The following criteria are required for your deployment to be affected:
  • You have one (1) or more AWS Cloud Connectors configured
  • You have activated (or re-activated) computers starting in October 2017
  • You are using an affected agent (see details below) 
Updated Oct. 31, 2017 @ 6:00 PM (GMT)
Recently, AWS introduced a change to smBIOS version 2.7 for EC2. Shortly after the change was introduced, Trend Micro began to receive customer inquiries and incident reports that showed new EC2 instances using the latest smBIOS were not being properly protected by Trend Micro Deep Security agents. 

Computers that failed to be correctly identified will activate outside of an AWS cloud connector, will not be assigned EC2 metadata, and may not be assigned the expected security policy.  In these cases assigning security policy or relay groups based on EC2 metadata - using Event Based Tasks (EBT's) for example - will be incorrect.
Trend Micro has identified the root cause and has released new versions of the DSA starting on October 20, 2017, that resolve this incompatibility.

Existing EC2 instances with smBIOS 2.4 that have Deep Security agents already installed are unaffected. 

Updated Deep Security Agents

Trend Micro has released the following updated Deep Security Agents to address the issue:

ProductUpdated versionNotesPlatformAvailability
Deep Security AgentVersion 10.1 CP (Feature Release) ReadmeAllNow
Version 10.0 Update 5 CP ReadmeAllNow
Version 9.6 SP1 P1 Update 12 CP ReadmeAllNow
Solution Id:
Did this article help you?

Thank you for your feedback!

*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.