Overview
Licensing is based on a subscription model and is paid annually upfront. Pricing of the protected assets per agent will decrease with the increase in agent quantity. Licensing is based on the # of protected assets (VMs, Bare Metal Servers, VDI, Desktop, containers Nodes, etc.) Licensing for management - Required for on-prem/non-SaaS installations only.
Licensing for SaaS management - FOC (recommended offering)
There is a different license for Serves vs. desktop/laptop/vdi, as well as K8 nodes and Legacy OS.
There are services that are based on the number of agents/assets as well.
Contact Seller for Assets Types options:
- Disaster Recovery Management - 12,500$
- Workload Visibility & Enforcement (Qty 200) - 78,000$
- Workload Visibility (Qty 200) - 39,000$
- Legacy Workload Visibility & Enforcement (Qty 100) - 78,000$
- Endpoint/VDI Visibility & Enforcement (Qty 1000) - 39,000$
- Container Kubernetes Host (Qty 50) - 75,000$
Highlights
- -Granular, AI-powered segmentation Implement policies in a few clicks using AI recommendations, templates for remediating ransomware and other common use cases, and precise workload attributes like processes, users, and domain names -Real-time and historical visibility Map application dependencies and flows down to the user and process levels on a real-time or historical basis
- -Broad platform support Cover modern and legacy operating systems across bare-metal servers, virtual machines, containers, IoT, and cloud instances -Flexible asset labeling Add rich context with a customizable labeling hierarchy for visibility and enforcement, and integration with orchestration tools and configuration management databases for automated labeling -Multiple protection methods Integrate CSI, defense, and threat-hunting capabilities to reduce incident response time
- Contact Seller for Offer
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/hour |
|---|---|
m5.2xlarge Recommended | $10.00 |
t3.large | $1.00 |
Vendor refund policy
no refund
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Resources
Vendor resources
Support
Vendor support
Support is provided during working hours Sun to Thu between 08:00-17:30. We recommend you open a call in our support portal at: https://serviceportal.www.bynet.co.il/login , or call 1-700-50-8001
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products

Customer reviews
Micro-segmentation has strengthened Kubernetes visibility and protected dynamic pod communications
What is our primary use case?
By doing instrumentation in Kubernetes, which I have done already, even in OpenShift for on-premise environments and also on Azure , we are able to see all the pods that go up and down and all the communication that they establish inside the pod and outside the Kubernetes environment.
What is most valuable?
In general, I would say that the best features that Akamai Guardicore Segmentation offers include visibility and the ability to have Layer 7 visibility, which means that we are not only looking for source IPs and ports and target source target IPs and ports, but we are also looking for services. We are able to see even the service that we can create rules for, allowing from server A one specific service to communicate with server B, but if some other service tries to do that communication, it will be blocked, making that a great feature of Guardicore segmentation. There is also the deception model they have, which is the Honeypot model. Once we have one rule that is blocked for some specific ports, we can intercept an insider threat that tries to do RDP to one server that should not happen. With the deception model, that communication is blocked, and the insider is sent to a Honeypot server where they think they have established that communication and may try to add some script there. Guardicore adds logs and creates an incident, so we can see what that communication has done and how someone tried to compromise the environment.
After implementing Akamai Guardicore Segmentation, I can say that for most customers with whom we implement Guardicore, we see once we do micro-segmentation for an application that the connection—possible connections that can be established on that application—usually drops by 80%. If we map out the proper communications that one application should have and create rules to apply the proper blocking, we see one application that could have a hundred thousand different types of communications, and after micro-segmentation, it can have only twenty thousand, thereby significantly increasing the security posture.
In day-to-day operations, we usually don't have any impact, which is the idea of Guardicore. Once we have the rules in place, we only allow the communication that is supposed to happen. This is why we increase the security posture, but we don't impact applications usability and anything else. For day-to-day operation and risk management, as I have mentioned, we typically reduce the communications that we can have with a specific application, so if a customer's environment is compromised, usually we can guarantee that with Guardicore segmentation, if we have the proper rules in place, other applications will not be compromised, and the communication will stay only inside that specific application.
What needs improvement?
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
My advice for others looking into using Akamai Guardicore Segmentation is to think about labeling. You should have labels for your entire environment regarding applications, which means having a good CMDB . You don't need to have a full CMDB , but you should at least build one with information about servers and which applications those servers are members of and what roles they play in the applications, so with that, you will be able to extract the best from the solution. I would rate this product an 8 out of 10.
Micro-segmentation has strengthened enterprise security planning and supports complex networks
What is our primary use case?
I usually recommend Akamai Guardicore Segmentation for larger companies, as we started to work with Guardicore before the acquisition and then moved to distribute Akamai . Akamai Guardicore Segmentation is not a simple solution for the Italian market because we are suffering from nanism; the majority of our companies have under 1,000 employees. Akamai Guardicore Segmentation is enterprise software, but they are pretty good in that area.
It is more suitable for bigger companies. The reasons are not solely about pricing; it is also about the knowledge of the security manager in companies across Italy. For example, a small company with 500 employees might have a limited budget for cybersecurity and typically does not consider micro-segmentation as a primary solution. They may manage cybersecurity issues effectively with their existing LAN setup until they grow larger and face more complexity, which is why micro-segmentation becomes necessary. However, in Italy, it is not as well-known as in other markets due to the customer base.
What is most valuable?
I usually recommend Akamai Guardicore Segmentation for larger companies, as we started to work with Guardicore before the acquisition and then moved to distribute Akamai . Akamai Guardicore Segmentation is not a simple solution for the Italian market because we are suffering from nanism; the majority of our companies have under 1,000 employees. Akamai Guardicore Segmentation is enterprise software, but they are pretty good in that area.
Regarding their interface, I cannot answer on technical issues or aspects because I am the sales manager, and here we show the characteristics of the software, but we do not make any demonstration of the product because we are a distributor.
What needs improvement?
To become more competitive, I believe they have to work on technology knowledge and address the brand awareness issues for my market. In more consolidated markets such as the US or UK, where companies have several factories and thousands of employees, they could focus more on marketing the brand and the technologies.
For how long have I used the solution?
I have been dealing with Akamai for three years overall.
How are customer service and support?
No one has asked for more, so I find the technical support in my region is pretty good.
How was the initial setup?
At the moment, I have no issues with documentation, integration with third-party solutions, or the initial setup; everything is pretty good, although you can always do more.
What's my experience with pricing, setup cost, and licensing?
Concerning their pricing, it is not cheap, but it is reasonable with respect to the kind of market you have to face.
Which other solutions did I evaluate?
I think it is hard to say if it is the best option on the market at the moment because I do not know a lot of alternatives in that area. They appear to be the kind of solution that stands out; even though Guardicore is not as famous as CyberArk, they are pretty known for what they do.
Micro-segmentation has improved network visibility and actively reduces lateral attack movement
What is our primary use case?
My main use case for Akamai Guardicore Segmentation is for big micro-segmentation at my company. A specific example of how I use micro-segmentation with Akamai Guardicore Segmentation in my company is the segmentation of big broadcast domains, where with this I could segregate the front end, the back end, backup networks, and out-of-band networks for administration. I have many cases with jumper services also, so many cases that we could mention working with Akamai Guardicore Segmentation.
What is most valuable?
More than twenty ring-fences implemented with Akamai Guardicore Segmentation have produced significant results with a three-hundred-sixty-degree vision of all the network traffic including the biggest system that we hold today.
The best feature Akamai Guardicore Segmentation offers is great threat intelligence. Threat intelligence stands out to me as a best feature of Akamai Guardicore Segmentation because you are ready, for example, for ransomware attacks and lateral movements. I am very happy with the solution.
In addition to threat intelligence, I have other ring-fences also. The way that Akamai Guardicore Segmentation holds the segmentation in the simplest way, giving the best visibility, is really the best thing for me.
Akamai Guardicore Segmentation has positively impacted my organization by improving security because it increased the perimeters and the breaks in small perimeters and also giving me visibility over three hundred sixty degrees over the network.
Since implementing Akamai Guardicore Segmentation, I have seen specific outcomes such as reducing incidents because only the tight traffic is really allowed, so you reduce the possibilities of issues and also increase the security.
What needs improvement?
Akamai Guardicore Segmentation can be improved through the follow-up with the customer experience of the Guardicore team, and they gave me a lot of insights to improve the configuration. I say that we have everyday fine-tunings to increase the power of the tool. I am very happy with this.
For how long have I used the solution?
I have been using Akamai Guardicore Segmentation for three years and a half.
What do I think about the stability of the solution?
Akamai Guardicore Segmentation is very stable.
What do I think about the scalability of the solution?
Akamai Guardicore Segmentation is very scalable because I could deploy anywhere without any hardware needs, for example.
How are customer service and support?
The customer support for Akamai Guardicore Segmentation is amazing. They are very close and help me all the time.
Which solution did I use previously and why did I switch?
Akamai Guardicore Segmentation is my first solution.
What was our ROI?
I have seen a return on investment as it requires fewer employees needed.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Akamai Guardicore Segmentation is great. It has a fair cost for our business.
Which other solutions did I evaluate?
I did not evaluate other options.
What other advice do I have?
My advice for others looking into using Akamai Guardicore Segmentation is that it gives visibility, security, and really does the right segmentation of your broadcast domains, improving not only security but visibility that you really need for your business. Akamai Guardicore Segmentation is the tool that makes me sleeping well every day, and I would rate it a ten on a scale of one to ten.
Zero-trust micro-segmentation has strengthened security and improves east-west traffic visibility
What is our primary use case?
Our main use case for Akamai Guardicore Segmentation is to implement micro-segmentation and Zero Trust security across hybrid environments, including both on-premises and cloud workloads. We primarily use it to gain visibility into east-west traffic to control the communication between application and servers, which helps in reducing the risk of lateral movement in case of security breach. Additionally, we use it for application dependency mapping to understand how workloads interact, creating granular segmentation policies based on application, environment, and role, improving compliance posture, especially for banking and financial customers. Overall, it helps us to move from traditional perimeter-based security to more workload-level security approach.
How has it helped my organization?
Akamai Guardicore Segmentation has had a very significant positive impact on our organization, especially in terms of security posture, operational efficiency, and compliance. From a security perspective, it has helped us to greatly reduce lateral movement risk by enforcing strict micro-segmentation policies. Even if a system is compromised, the attack surface is limited, which strengthens our overall zero-trust approach.
In terms of efficiency, the visibility and visualization feature have reduced the time required for troubleshooting and policy validation. Our team can quickly identify communication issues and resolve them faster compared to traditional methods.
From a compliance standpoint, especially for banking customers, it has helped us to meet regulatory requirements more effectively by ensuring the proper segmentation between critical workloads and sensitive data environments. Overall, it has improved our control, visibility, and response time, making our security operations more proactive rather than reactive.
What is most valuable?
One of the best features of Akamai Guardicore Segmentation is its real-time visibility and visualization capabilities. It provides a detailed map of all east-west traffic, which is very helpful for both security and troubleshooting. Another key feature is application dependency mapping, which visually shows the communication flows between servers. This helps in understanding the complex environments and designing accurate segmentation policies.
The granular micro-segmentation capability is also very powerful. We can create a policy based on labels such as application, environment, or role, allowing only required communication and blocking everything else, which significantly reduces the lateral movement risk.
Additionally, the agent-based deployment is lightweight and works well across hybrid environments, including on-premises and cloud, making it flexible and easy to scale. Overall, the combination of visibility, visualization, and fine-grained control makes it a very effective micro-segmentation solution.
What needs improvement?
While Akamai Guardicore Segmentation is a very powerful solution, there are a few areas where it could be improved. One of the main challenges is the initial deployment and policy design complexity. In large environments, understanding all application dependencies and creating the right policies can take time and requires close coordination with application teams.
The user interface and policy management can also be improved. As the number of policies grows, managing and organizing them becomes slightly complex. A more simplified or intuitive policy structure would help operational teams.
Another area is integration with other security tools such as SIEM or SOAR platforms. While integration is possible, making it more seamless and easier to configure would add value. Additionally, the reporting and dashboard could be enhanced to provide more customizable and business-level insights, especially for management and reporting.
One small improvement I would suggest for Akamai Guardicore Segmentation is having more automation capabilities for policy creation and recommendation. For example, AI-driven suggestions based on observed traffic patterns would help reduce manual effort during the initial policy design. It would also help to have more predefined templates for common use cases, especially for industries such as banking, to speed up deployment. Another area is enhanced reporting customization where we can easily generate business-level dashboards for management and compliance teams without any additional effort.
For how long have I used the solution?
I have been working with Akamai Guardicore Segmentation for around one to two years as part of my role managing security.
How are customer service and support?
The customer service rating I would give is a four out of ten.
What other advice do I have?
In one of our banking customer environments, we used Akamai Guardicore Segmentation to segment the critical application tiers such as web, application, and database servers. Initially, we enabled visibility mode to understand the east-west traffic and identify all communication flows between workloads. During this phase, we discovered several unnecessary open communications, especially between application and database layers. Based on this, we created granular segmentation policies to allow only required ports and protocols and blocked all other unnecessary traffic. For example, only specific application servers were allowed to communicate with the database servers on required ports while all other lateral movement paths were restricted.
One additional point I would highlight is that with Akamai Guardicore Segmentation, we do not just use it for static segmentation, but also for continuous monitoring and policy optimization. Even after the initial deployment, we regularly review the traffic patterns and update the policies based on application changes. This is very important in dynamic environments such as banking, where new service integrations are frequently introduced. Another key aspect is that we use it as a part of a broader zero-trust strategy, integrating it with other security solutions such as WAF and secure web gateways to create a layered defense approach. Also, from an operational perspective, it has helped us to reduce the dependency on traditional network-based segmentation, making security more application-aware and flexible, especially in hybrid and cloud environments.
The visualization feature in Akamai Guardicore Segmentation has been extremely helpful for our daily operations, especially in troubleshooting and policy design. From a troubleshooting perspective, it gives us a clear, real-time view of communication flows between workloads. Instead of checking logs manually, we can quickly identify where traffic is being allowed or blocked. This significantly reduces the time required to identify issues. For policy design, the visualization helps us to understand the application dependencies before enforcing any rules. This ensures we do not accidentally block legitimate traffic, which is very critical in banking environments. It also helps in identifying unnecessary or suspicious communication paths, validating policies after implementation, and collaborating with application teams, since the visual maps are easy to understand even for non-security teams. Overall, it makes both troubleshooting faster and policy creation more accurate, reducing the operational effort and minimizing the business impact.
Based on our experience with Akamai Guardicore Segmentation, we have seen a noticeable improvement in both troubleshooting and policy validation timelines. Earlier, troubleshooting east-west communication issues used to take around two to four hours since we had to rely on manual log analysis and multiple tools. With Guardicore visualization, we can now identify the issue within twenty to thirty-five minutes, which is roughly around sixty-five percent to eighty-five percent reduction in troubleshooting time. For policy validation, it previously took several hours to a full day, especially when coordinating with application teams. Now with the clear dependency mapping and real-time visibility, we are able to validate policies within thirty-five to sixty-five minutes, improving efficiency by around fifty-five percent to seventy-five percent. Additionally, incident response time improved by fifty-five percent, policy deployment errors reduced significantly due to better visibility, and faster onboarding of newer applications since dependencies are clearly mapped. Overall, these improvements have helped our team become more efficient, proactive, and accurate in operations.
My main advice for anyone considering Akamai Guardicore Segmentation is to start with the visibility mode before enforcing any policies. Understanding application dependencies and traffic flow is very important to avoid unintended disruptions. Also, involve application and infrastructure teams early in the process since accurate segmentation depends on knowing how applications communicate. I recommend taking a phased approach by starting with monitoring and mapping, identifying the required versus unnecessary traffic, and gradually enforcing the policies. Additionally, keep policies simple and structured initially and refine them over time as you gain more visibility. Overall, if implemented properly, it is a very effective solution for achieving zero-trust and reducing lateral movement risks.
Akamai Guardicore Segmentation is a very effective solution for organizations looking to strengthen their zero-trust security model, especially in complex hybrid environments. What stands out the most is its ability to provide deep visibility and control over east-west traffic, which is something traditional security solutions often lack. While there are areas for improvement such as policy management simplicity and automation, the core capabilities are very strong and deliver real value in terms of security, operational efficiency, and compliance. From my experience, when implemented with the right approach, it can significantly enhance an organization’s overall security posture and reduce lateral movement risk. I would rate this product an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsegmentation has protected critical environments and now blocks lateral ransomware movement
What is our primary use case?
I use Akamai Guardicore Segmentation to block lateral movement of malicious software like ransomware. This is very important to protect my business and my corporation.
I create labels for any assets to create rule sets in Guardicore Center with the configuration.
The logs and network logs provide visibility that is very important for my business and my corporate entity. We use microsegmentation by environment. I do segmentation for production, homologation, and development. It is very important.
Today, I have segmentation for Kubernetes in Guardicore, but I have problems with Guardicore with segmentation for Kubernetes because it is connected to SaaS. This is very important because we have projects starting in Kubernetes in my enterprise.
Akamai Guardicore Segmentation is deployed in my organization on a hybrid cloud because 99% is on a private cloud computer.
What is most valuable?
The best features of Akamai Guardicore Segmentation are maps and network logs. I think the analysis of logs and hits in Akamai Guardicore Segmentation is fantastic.
The impact of Akamai Guardicore Segmentation is very important because it reduced risk for my corporation and organization. It is very important.
Akamai Guardicore Segmentation reduced risk because it blocked malicious ransomware and uninspected traffic. I appreciate this. It is very good.
Akamai Guardicore Segmentation reduces risk, and the configuration is very easy, among other things.
What needs improvement?
I think the pricing is very high. It is a big cost. The price of Akamai Guardicore Segmentation is very expensive, but it is important to the enterprise. I think it is more or less.
For how long have I used the solution?
I have been using Akamai Guardicore Segmentation for approximately five years.
What do I think about the stability of the solution?
Akamai Guardicore Segmentation is very stable.
What do I think about the scalability of the solution?
It is very scalable.
How are customer service and support?
I like the Akamai support very much. The response is very fast. The attention is very good.
Which solution did I use previously and why did I switch?
I did not evaluate other options. I am happy with Akamai Guardicore Segmentation.
What about the implementation team?
We have a relationship with this vendor. We are a partner and an experienced user.
What was our ROI?
The investment is necessary for enterprises to reduce risk, protect the enterprise, and have visibility of the network.
Which other solutions did I evaluate?
What other advice do I have?
I gave this product a review rating of 10.