- 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)
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.
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: