I did a POC for Trend Micro Deep Security 9.0 and ran into the following shortcomings when using with vCloud Director 5.1:
- Deep Security cannot protect Windows VMs, if the VMs have the same SID. It will come up as "duplicate SID" and will not be protected. Unless you have a way to enforce the tenant to click on "Generate a new SID" checkbox in the customization box in vCloud Director when deploying a new VM/vApp, it will be difficult to ensure that the new VMs deployed by the tenant will be automatically protected. I spoke to TrendMicro about this, and this issue existed in Deep Security 8.0 as well, and they submitted it as a "feature request"
- In order to make the vShield Endpoint based anti-virus solution work, all of the VMs will have to have VMTool installed, with a custom option to make sure that vShield Endpoint driver/agent is installed. I spoke to VMware vCloud Product Manager about this, and requested that "Install VM Tool" option in vCloud Director would automatically install this agent/driver. That should take care of the Windows VMs. Also, with so many different flavors of Linux OS out there, it will be very difficult to ensure that VMTool is installed automatically on all of the Linux VMs that the tenants deploy. This issue will hold true for any vShield Endpoint based anti-virus solutions.
These products seem to be geared more toward VMware View environment, where you have the complete control of the template. I have not come across a solution that will work seamlessly in vCloud Director environment yet.