Vcloud vs Vsphere:vmware Detailed security new changes

In the August 29 news of the Beijing time, VMware unveiled the Vcloud suite at the VMworld conference this week and painstakingly explained the significant difference in functionality and naming between the Vcloud security model and the existing Vsphere Cloud computing virtualization operating system.

VMware's underlying security technology has been known as VShield, which is essentially a technical approach in the vsphere, involving a set of APIs in the Edge and app Datacenter products that support agentless use of third-party security products. The VShield model also includes VMware's inherent security features, such as firewall capabilities.

Jonathan Gohstand, director of Network and security product marketing, said Vcloud is expected to ship next month, vsphere as part of three basic vcloud software types. Also, Vcloud will include Vdirector management. But VMware does not want to use the name VShield, but rather to call it "Vcloud Network and security" or VCNS.

In addition, the VShield endpoint (API for supporting agentless use of Third-party software products for Gohstand) will be implanted directly into the management program and will no longer charge a separate API fee, says.

He points out that Vcloud's vcns for standard use or high-availability features will be discussed, including failover. Vcns also includes software-based networks, such as the Vxlan launched by Cisco and VMware last year. But Vcns does not include any components from the Nicera that VMware just acquired last week.

The VShield API in Vsphere is defining agentless use of security technology because agent-based software in a virtual environment can cause performance problems. VMware's VShield agentless architecture reduces load during virus scanning, primarily by assigning a separate place for third-party security software as a security module to scan data.

Some vendors (including McAfee) are trying to convince VMware to extend the agentless use of their APIs, because sometimes agent-based software is more efficient, especially when malware is quarantined and deleted.

Gohstand acknowledges these problems, but says VMware will continue to use agentless in the API because they do see the need to uninstall the security feature, adding that VMware recognizes that a hybrid approach may be needed, That is, in Third-party software can support both agentless and agent functions.

The Vcns API will be expanded in the future, and Gohstand also says VMware is taking a more open approach to working with Third-party security vendors to ensure that their products run in VMware's Safe mode. VMware has so far operated mainly in small ecosystems, and they have chosen to collaborate with the security industry partners (such as trend technology) to solve technical problems. But now VMware will adopt a more open approach to security providers to enable their products to support Vcns in Vcloud.

Gohstand says security vendors will be able to create software more easily to support the Vcns API. VMware will closely monitor suppliers ' willingness to join the Vmready software Developers Network and security programs, take mandatory training and submit products for automated inspections.