HyTrust Adds Policy Management to Appliance

Comments
Print

HyTrust Inc. has announced the general availability of HyTrust Appliance 1.5 on Aug. 24th.

Adding to the core capabilities of HyTrust Appliance 1.0 – centralized access control, template-based security configuration and audit-quality log aggregation for the hypervisor – HyTrust Appliance 1.5 delivers the first enterprise-class, object-based policy management capability, built specifically for security and compliance policy enforcement of virtual infrastructure, the company said. In the new version, HyTrust also has added new features such as expanded VMware platform support.

“Building on the success of HyTrust’s initial product launch earlier this year, the company is again delivering a solution that will help accelerate the wave of virtualization deployment that is sweeping across enterprise datacenters,” said Eric Chiu, president and CEO of HyTrust. “The policy definition and automated enforcement capabilities available in HyTrust Appliance 1.5 enable unprecedented, proactive control over the critical elements of virtualized infrastructure.”

HyTrust has pioneered a label-based approach for policy management (similar to Web 2.0 “tagging”) that allows organizations to create policy-based categories for virtual infrastructure objects, allowing for better organization and more automated controls. Thus, HyTrust Appliance 1.5 now enforces granular authorization of all virtual infrastructure management operations, according to user role, object, label, protocol and IP address. This makes it easy for administrators to define virtual infrastructure policies and enforce them systematically – a task that previously forced organizations to use fixed boundaries to silo their environments, as well as to depend upon manual change control processes to keep track of changes in their environment. With HyTrust, enterprises can embrace a single internal-cloud environment in which policies are not only automatically enforced, but also updated dynamically with the infrastructure.

Comments
comments powered by Disqus