Incident Manager at a computer software company with 1,001-5,000 employees
Real User
Top 5
Feb 2, 2026
The tool is blocking and only the person who has access to the tool can actually see how many DDoS attacks were blocked. Since I do not log in to the portal myself, I am unaware of this capability. I heard the word Akamai's anomaly detection from my team that they use this, but I don't know about it on the technical aspect. I am unaware of Akamai API Security's ability to adjust security policies in real-time. I am also unaware of which feature of Akamai API Security has helped us monitor API usage trends. Someone who is actually hands-on using Akamai API Security might know this.
Senior Engineering Manager Cybersecurity at a computer software company with 1,001-5,000 employees
Real User
Top 5
Dec 13, 2024
The challenge I found was with contextualization and how analytics are generated. Reports were sent in a raw format without proper analytics. There was no mechanism to identify which APIs will always have PII information, such as those with PCI data. Tuning to skip known APIs wasn't available.
Platform Engineer at a retailer with 10,001+ employees
Real User
Oct 27, 2023
It would be beneficial to use machine learning and API throttling together to identify how the APIs are called and whether it's coming from the right person or the wrong person. Akamai is developing that type of feature called URL protection, which is a mixture of API throttling and machine learning. Before blocking everything, this feature would check and first block requests coming from a hosting provider with a bad reputation.
Akamai API Security offers robust protection against DDoS attacks and is highly valued for its efficient API throttling capabilities, allowing multiple users to manage traffic effectively. This ensures both optimal performance and enhanced security by controlling API access and utilization.\n\nAkamai API Security excels in safeguarding APIs with its industry-leading throttling features, allowing multiple users to prevent overload and abuse. By managing traffic efficiently, users can maintain...
The tool is blocking and only the person who has access to the tool can actually see how many DDoS attacks were blocked. Since I do not log in to the portal myself, I am unaware of this capability. I heard the word Akamai's anomaly detection from my team that they use this, but I don't know about it on the technical aspect. I am unaware of Akamai API Security's ability to adjust security policies in real-time. I am also unaware of which feature of Akamai API Security has helped us monitor API usage trends. Someone who is actually hands-on using Akamai API Security might know this.
More features would be beneficial.
The challenge I found was with contextualization and how analytics are generated. Reports were sent in a raw format without proper analytics. There was no mechanism to identify which APIs will always have PII information, such as those with PCI data. Tuning to skip known APIs wasn't available.
It would be beneficial to use machine learning and API throttling together to identify how the APIs are called and whether it's coming from the right person or the wrong person. Akamai is developing that type of feature called URL protection, which is a mixture of API throttling and machine learning. Before blocking everything, this feature would check and first block requests coming from a hosting provider with a bad reputation.