We use the solution for micro segmentation.

The most valuable features of the solution are the maps and ring fencing that help monitor events.

It's not easy to learn to use this program. It would be very helpful for beginners if the solution had more windows to help with the terms inside instead of going to the documentation.

I have been using Akamai Guardicore Segmentation for six months.

I rate Akamai Guardicore Segmentation a nine out of ten for stability.

Around four people are working with the solution daily in our organization.

I rate Akamai Guardicore Segmentation a nine out of ten for scalability.

The solution's initial setup is not hard. However, you have to learn it because it's not plug-and-play.

I, an integrator, and the Akamai staff implemented the solution.

Overall, I rate Akamai Guardicore Segmentation a nine out of ten.

We use the product in the production environment of server infrastructure.

The tool's most valuable feature is its visibility.

Kubernetes is not installed in the way we need it.

I have been using the product since October.

We faced some minor issues, but overall, the product is stable. I rate it an eight to nine out of ten.

I rate the tool's scalability an eight out of ten. My company has four to six users.

Akamai Guardicore Segmentation's deployment is smooth. The deployment team promised us that the implementation would be completed in three weeks, but the product was available within two weeks.

Akamai Guardicore Segmentation is expensive.

I rate Akamai Guardicore Segmentation an eight out of ten. Adopting the product often involves a greenfield approach, requiring adjustments and careful planning.

It's micro-segmentation.

The label-based segmentation is the most valuable feature.

There are always areas for improvement. It doesn't support a PAAC solution (Platforma as a service) in the cloud. So that could be improved.

In future releases, I would like to see more integration with other products.

I have been offering this solution for more than three years.

It's very stable.

It's very scalable. It's primarily the larger customers with thousands of servers.

The customer service and support are very good.

Akamai is much better than other solutions, such as ColorTokens and Illumio. It is more user-friendly and has more features. In fact, Illumio is actually implementing a lot of the features that Guardicore has had for years.

The initial setup is very easy. It's a safe solution, so you can actually install it in five minutes. So it's very easy to install.

So installation is fast. But then you have to roll it out to all these servers that the customer has, and that would take a couple of days or a week or a month perhaps and require, let's say, four people to do it.

We don't maintain it because it's safe. So it's very easy.

The price is the same as other products in the market. There's no price argument to choose one or the other product, it will cost the customer approximately the same.

You pay for a year, two years, or three years, how many years you want, but you don't actually buy the product; you lease it for a year. And then you can buy it for another year and so on.

The support is included in the license.

I would say that you should use it for micro-segmentation instead of trying to use firewalls. Because some customers try to use other solutions like firewalls, and it's not the best solution.

Overall, I would rate the solution a nine out of ten. It is an amazing solution.

Our clients look for server-to-server segmentation that includes both inbound and outbound ringfencing.

The tool is easy to use and simple to deploy to achieve segmentation objectives. It offers a graphical view of real-time workflows and traffic patterns into server-to-server communications. Also, the amount of process, service level visibility the agents deployed on the servers provide via network logs is very informative.

Guardicore Centra should incorporate automation so that we aren't required to write custom scripts by leveraging APIs quite often. The tool also has limitations on overall policy rules that can be configured on the platform (60k rules) which seems a lot but with big chatty applications and a huge application count to segment, this limit can turn out to be small if the goal is to segment a lot of application servers. Operationally there are too many clicks and analyses needed to do quick and safe changes (for e.g. label replacement) in the production environment. I think that the incorporation of automation templates for some standard use cases can help clients make changes with confidence and without the possibility of human error.

I have been working with the solution for close to an year.

I would rate the tool's stability a seven out of ten due to the capacity limit. Once we reach 70-80 percent of the maximum rules, the system becomes slow in terms of response. The backend processes being a SaaS solution need to be more robust.

I would rate the product's scalability a five out of ten due to the current limits on the number of agents, labels, and rules. Around 5000 servers use Guardicore Centra in my organization.

The product's support takes more time to respond back.

Guardicore Centra's setup was straightforward and I would rate it a seven out of ten. The tool's setup is straightforward as long as you identify the servers and establish the right processes. The tool came with an installation guide and setup took about four to five hours to complete. The deployment depends on the solution size and if the POC is small, the setup is easier and quicker. If you plan for enterprise-wide deployment, then you need to do capacity sizing and planning.

I was not directly involved in licensing etc. costs but only in solution architecture and operationalization.

I would rate the solution a six out of ten. We mostly have enterprise customers for Guardicore Centra. I would advise users to try this out on a handful of servers for the first time (like < 20 servers to begin with). During and after segmentation, monitor the solution for some period to notice how operationally effective it is and the data sources relied upon for building labels, and policies, and ultimately how easy it is to incorporate any changes needed thereafter.