Akamai API Security

Since multiple teams were involved in issue resolving, at least ten plus people from our side were involved in the implementation process. Everyone was contributing, even if we consider two per team. We are mostly talking about engineers, so they are all engineers. This ten plus people includes one from the NOC team, one from the operations team, and two or three from the security team.

What I already appreciate about Akamai API Security  is that initially we were struggling with how to get this configured, but after that everything went smoothly. We were also surprised to discover there were five hundred plus endpoints that we are using across the organization, which was a surprise even to our management and leadership. We did not know that many teams were simply pushing small APIs and big APIs into the server. This gave us an overall picture of how many APIs we are using across our organization, and now we are more cautious about which APIs should be used publicly and how we secure our APIs. Since it gives a very good dashboard and a unified platform, it is very helpful for us to know which API is coming from which team and how many teams are using one particular API. All of this is a really good advantage for our management as well as our leadership, and we can even go back and show it to the respective project teams. API discovery and fingerprinting is the main feature that we appreciated.

We are showing the reports from Akamai API Security  to HITRUST  compliance and HIPAA compliance certifications. We are also using PCI, so we share these reports as evidence to these auditors when they come.

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.

The procurement for Akamai API Security happened almost ten months ago, and actual work has started only a couple of months before.

Good, its fast and easily scalable, the Akamai  team is very helpful 

Regarding Akamai technical support, since I am not directly involved in it, I do not want to provide inaccurate information. I will rate it at eight.

Positive

Because Akamai API Security was a new tool, we definitely needed support from the vendor directly. We were working only using Postman and Bruno. We had to directly move from installable tools to Akamai, which is a cloud platform. We definitely wanted some tool knowledge from the vendor, and once that was provided, things went very smooth. The tool started identifying the endpoints all by itself, and we ourselves do not have any visibility.

The main challenges we had with Akamai API Security were how to set it up on the AWS  cloud environment and how to access this portal. We had to handle the major and basic configuration, and given that our organization had a lot of internal APIs which are not exposed to the outside environment, public APIs, and intermediary APIs, all these had to be interconnected. The vendor also had to understand our current environment and then recommend how to specifically access our internal APIs. All those network-related issues required us to bring in the NOC team and ask them to open certain ports specific to our APIs, and then everything went smoothly. The major heavy lift was done by the network team and the vendor side.

I can identify all of these benefits after the implementation of Akamai API Security. Identifying and following up with the team was previously very challenging. Teams are reluctant to provide information, some managers ask us to look at their Confluence  page, our time is wasted, and everyone's time is wasted. We have to follow up with the developers, they are on leave, and everything was a mess. Getting everything from one single portal without anyone's interference saved us a lot of money, time, and frustration.

I am unaware of Akamai API Security's ability to adjust security policies in real-time.

I am 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.

Regarding Akamai technical support, since I am not directly involved in it, I do not want to provide inaccurate information. I will rate it at eight.

I received a very good feedback from my team regarding Akamai API Security, so I would rate it as nine. My overall review rating for Akamai API Security is eight.

Our main use case for Akamai API Security  is securing the API security as we're using the API gateways.

A specific example of how we use Akamai API Security  with our API gateways is when somebody hits our member-facing website from outside. We're actively monitoring where they're coming from and whether it's legitimate, and then we are doing all sorts of security checks based on our policy to ensure compliance.

The best features that Akamai API Security offers are the information and aggregation we get, as well as the alerts that we receive.

These features help my team in our daily work because my team is actually working on different things apart from making sure the lights are on, and even though API security is something they would look into, they can't spend a whole lot of time on this. We definitely depend on these kinds of tools. When we get an alert, we try to look at the information so it's at a high level so we can act accordingly. Once we know the information we're looking at, our team can go deeply and investigate that. In terms of aggregation, we heavily rely on these alerts.

Akamai API Security has made a positive difference for our organization by improving our security posture and saving our team time, as we can actually prioritize tasks unless there are some false positives, but it is definitely saving a lot of time.

We definitely see that our posture is much better.

I don't really have anything to add about any needed improvements at this point.

I just started with Akamai API Security before evaluating other options.

Akamai API Security is stable.

I don't have any issues with customer support right now.

I previously used a different solution before Akamai API Security, which was Check Point.

I have seen a return on investment, and the main thing is the time saved, allowing our employees to focus on other priority work.

The experience with pricing, setup cost, and licensing is that it's a totally different team to work on, but I heard the setup is pretty straightforward.

I would definitely advise others looking into using Akamai API Security to do a POC. I found this interview really great and don't think anything needs to change for the future. I would rate this experience an 8.

Positive