For VMware customers that already use the security known as vShield in current VMware's products, it's expected that NSX Service Composer will be able to accept and apply that rules base.
There may be some drawbacks to NSX Service Composer, at least in the beginning. Feroz and Vaidya indicated that NSX Service Composer at this point cannot do certain things, such as schedule anti-malware scans, though that's possible in the future. Although the NSX API is open, VMware customers may find some of their security vendors are not in the NSX program. And centralizing security provisioning by tying multiple security vendors consoles and functions into NSX Service Composer raises new questions about how to keep track of monitoring console uptime or other troubleshooting issues. But VMware intends to have a kind of "alarm system" to provide details about these sorts of problems and ways to remedy them.
In addition, NSX service Composer as yet has no way to share critical security information with the type of product known as security information and event management (SIEM) which centralize and correlate security events. "There is a plan, but we don't have it yet," acknowledged Vaidya.
Sign up for Computerworld eNewsletters.