Our primary use case is protection of our website. About 70 percent of our holiday bookings, about 7,000 in total, go through our website. ShieldX protects that environment. When we moved from a physical environment in Rackspace — and this was a project that we started two and a half years ago — we identified the main risk to the business, which was infection of the website. We were moving our site to AWS, from a hosted, private environment to a private AWS environment. We were concerned about the potential damage to the business if we got hacked. ShieldX was a necessity to enable us to move the business forward into AWS. We have two installations of ShieldX. We have one installation running in AWS, it's protecting our web environment. And we have another installation on-prem which is protecting corporate servers.
Senior Systems Engineer at Larry H. Miller Group of Companies
Real User
2019-03-25T06:49:00Z
Mar 25, 2019
The primary use case is microsegmentation. We are segmenting our servers, so only people who need access to a server can see and access it, then vice versa. We are using the latest version and deployed around September/October last year.
CIO at a comms service provider with 1,001-5,000 employees
Real User
2018-11-06T13:09:00Z
Nov 6, 2018
ShieldX has been designed from the very beginning to work well in cloud environments. It understands autoscaling, automation, and auto-configuration. These are the things which are important in today's operating environment. We have already added it to the enterprise environment. We are in the process now of putting it into production. We are somewhere around 15 to 20 percent done. Our goal is to get up as high as 100 percent within the next six to nine months.
The ShieldX Elastic Security Platform dynamically scales to deliver comprehensive and consistent controls to protect data centers, cloud infrastructure, applications and data no matter where they are or where they go to make the cloud more secure than on-premise deployments. Our frictionless approach leverages agentless technology as well as the ShieldX Adaptive Intention Engine which autonomously translates and enforces intention into a set of comprehensive controls - microsegmentation,...
Our primary use case is protection of our website. About 70 percent of our holiday bookings, about 7,000 in total, go through our website. ShieldX protects that environment. When we moved from a physical environment in Rackspace — and this was a project that we started two and a half years ago — we identified the main risk to the business, which was infection of the website. We were moving our site to AWS, from a hosted, private environment to a private AWS environment. We were concerned about the potential damage to the business if we got hacked. ShieldX was a necessity to enable us to move the business forward into AWS. We have two installations of ShieldX. We have one installation running in AWS, it's protecting our web environment. And we have another installation on-prem which is protecting corporate servers.
The primary use case is microsegmentation. We are segmenting our servers, so only people who need access to a server can see and access it, then vice versa. We are using the latest version and deployed around September/October last year.
Our primary use case is to provide microsegmentation and microsecurity controls in a multi-cloud and multi-data-center environment.
ShieldX has been designed from the very beginning to work well in cloud environments. It understands autoscaling, automation, and auto-configuration. These are the things which are important in today's operating environment. We have already added it to the enterprise environment. We are in the process now of putting it into production. We are somewhere around 15 to 20 percent done. Our goal is to get up as high as 100 percent within the next six to nine months.