Arbor DDoS Reviews

We use it to protect our infrastructure from DDoS attacks. It is used to protect web applications to provide a secure infrastructure for our client.

The artificial intelligence feature is most appreciated. This solution can lower the throughput and clear the traffic, which is something really important for us. It also provides good protection.

It is user-friendly, and its integration has also been really fast. We have many critical applications, and it was easy to integrate Arbor DDoS with our website, mobile application, and web banking.

They should improve the reporting section and make it a little bit more detailed. I would like to have much better and more detailed reports.

I have been using this solution for three months. It was implemented in February.

Its stability is really good.

Because it is on-premise, it has limited capability. That's why in six months, we would like to move to the cloud. Moving to the cloud will also enable us to prevent biometric attacks. It will make it easier for us to protect all the throughput traffic.

Our client is a medium-sized company in Bolivia with around 3,000 employees.

Their technical support is really good. They have a nice workflow.

We had Check Point and Radware solutions. Gartner Quadrant ratings were one of the key factors for going for this solution.

Its initial setup was easy. It was a one-month project, and its implementation was very fast.

Five engineers were involved in its implementation.

I would advise others to do a proof of concept. That's a good way to choose a solution. We did a proof of concept, and it gave us a good idea, so I would advise others to do that.

I would rate Arbor DDoS a nine out of ten. I am really happy with this solution.

The solution looks into volumetric attacks and gets them resolved.

The technical support engineers can create more labs within the environment. Real-case scenarios that have taken too long to resolve or were escalated can be directly converted into articles. It is highly possible that someone else may also face similar problems. Such articles will help people easily find a solution to their specific issues.

I have been using Arbor DDoS for seven years.

Arbor DDoS is a stable solution.

Arbor DDoS is a scalable solution. It can be used by small, medium and enterprise businesses.

The solution's integration is simple if you know the steps. If you don't know the steps, it becomes complex. It can become difficult depending on the layer, negotiation, and communication. If everything is laid out in software terms it is not difficult. You just need to follow the process. I would recommend the solution to other users.

Overall, I rate the solution a nine out of ten.

We have captured a profile for every production group which has a server-type configuration. We also enable signaling. If there is a huge amount of traffic, it will indicate that to us. Accordingly, we will inform them to take action or whatever. We will determine whether it is legitimate or not based on the requirements.

There is a given bandwidth for any organization, an expected amount of traffic at a given point of time. If it sees more than the traffic which we are expecting at a given point of time, it could be an anomaly. We will then check internally whether a download or upload is happening, etc. Normally, if it sees a huge amount of traffic at the same time, then automated cloud signaling will be enabled and, automatically, the traffic will be dropped.

There are multiple malicious IPs which are present everywhere. So, wherever the traffic comes from, it comes directly to the internet firewall, which utilizes the firewall's bandwidth, latency, etc. We block such traffic directly at the Arbor level only. 

Also, with network-level signatures, we can block things like malicious packets at the Arbor level only.

It's very user-friendly. Everything is done through a GUI. It doesn't take much time to learn how to use it. Once you see it a few times you understand it.

It provides packet capture and we can block or whitelist whichever IPs we need to. Whatever traffic we want to block - and we get IPs from internal teams and from national teams - we block at the Arbor level only, because if it gets to the firewall then firewall bandwidth will be taken.

With Arbor, every six or 12 months, we can do DDoS testing.

Also, there are HTTP connections. We can tell it there are multiple production categories which are present in a server-type configuration and we can use that. 

In very rare situations we use it to capture traffic. If there is any malicious traffic we can capture the packet where we can see the HTTP request.

On the main page there are alerts that we are unable to clear, even though the issue has been resolved.

The stability is very good. We have never faced an issue with it.

The scalability depends on the box but we have never had any issues with that.

We use technical support when there is some issue with the box or traffic and we are unable to resolve it. Our interaction with them is good. They check the issues. It usually takes them one or two days to respond. They're knowledgeable and helpful.

The last issue we contacted them on was during implementation. We connected to one of two management ports but it was not working. They told us to change the management port and when we did everything was fine.

I did the initial setup. It's not complex. We have a default admin and password where we need to set a management IP. Once management IP is set, if we connect it through a comm port, we need to set our system IP tools in the same subnet so that we can connect to Arbor. After that, we can set up usernames, passwords, and an IP access list. We can even change the group password.

If you have some knowledge, the implementation will only take between a half-hour and an hour. The only scenario where it takes time is when we put it into inline mode; when we mount the devices into the network.

One person is enough for deployment, if they have knowledge of how to implement it. There is no need for two or three. The number of people required to maintain it depends on the automation. One person is often enough. 

We have seven people who directly access Arbor DDoS, mostly project engineers.

I was working in the ISP environment and the Arbor DDoS solution is integrated in there.

We have certain gaming server data centers having some big or small LAN protectors. All protectors have been added to Arbor for mitigation and protection and the IPs with frequent attacks are separately added for more focus monitoring. Usually when gaming users go online they experience this type of high volume attack. We pick those IPs and separately define an Arbor for mitigation and the whether those are positive.

Specifically in the ISP infrastructure where I was working, Arbor DDoS is integrated to detect the threats and mitigation. Basically, the peak flow TMS solution and peak flow SP solution has been procured by my company. We are providing services to customers and protecting our own infrastructure as well.

When you work in an ISP or enterprise environment, the main priority is to protect your services or your customers services, like bandwidth. There must be no high volume breach towards any customer, such as a DDoS attack or application level attack. The purpose of procuring a peak flow TMS solution is to mitigate the high volume attacks towards our customers and to protect our internal infrastructure as well. This is our priority in this aspect.

I think the diversity of protection is extremely limited. It must be expanded in future upgrades and versions. Plus, hardware stability is a big issue with Arbor. We have frequent outages with the hardware.

Arbor is good for expansions or forecasts, and helps us as well. Their pre-sales team is very dedicated and focused and they just nominate the POC, who then provides the capability, descriptions and presentations to us.

They are helpful. Their response time is good. 

No, we were just manually blackholing at level three, an upper level. We were not using any specific DDoS solutions like Arbor.

Initial setup is a bit complex because it is a Linux based working environment for configuration. A bit of expertise is required to configure the setup. It requires an expert level assistance from Arbor to complete the configuration or to apply any new system.

Deployment took around 3-4 months because we had two sites nationwide on which peak flow was deployed.

Yes. They were just handling the physical connectivity, the mounting, placement and insertion of the cords. By law, integration is pushed by the Arbor expert.

Licensing is good and they are very helpful to us. Without licensing you cannot get the complete features of the product, as well as the complete level of support, so licensing is obviously a good option.

Actually there is a different planning team which takes care of the projects, so I don't know if they were considering any other vendor or not, but right now Arbor is the first choice and we are working with it.

Arbor has a global ranking in reliability and credibility. They are very unique and can respond to a very wide scope of threats from their global deployment. So, Arbor is very helpful to have inside of the most recent attacks and their backgrounds.

Arbor has a global ranking and global recognition. Whenever you do a search on Google, you can find Arbor on the top three or top five DDoS protection vendors. Obviously, Arbor is very reliable.

We are an internet service provider. We are using Arbor in our networks and it mitigates all attacks on our network. We are using BGP for traffic diversion.

When we implement Arbor in an organization it is protected against DDoS attacks. We also protect our services, our customers and their networks with it. We need Arbor or a similar solution in our organization.

It's very flexible and we can easily deploy it to our network. It's very user-friendly. We can do everything via the web interface and troubleshoot easily from the CLI. It's not complicated. I like the features.

Sometimes the PPM module gives you an error. They improved it, they deployed a patch, and fixed it. Generally, if it gives you an error, you need to power it off and back on again.

It's more stable than its competitors. We haven't had any stability issues with it.

It's scalable.

Technical support is pretty good. Sometimes first-level engineers take too much time, but when they escalate to the engineers they solve our problems. So the first level of support, I am not sure about them, but the other levels are good.

They respond to our tickets.

We used Cisco Guard but Cisco no longer sells that solution. It was a very complex solution and our customer satisfaction was very low. We searched for a new solution and we liked Arbor.

It is easy to deploy. You can easily configure the interface, connect your network, and easily do the BGP configuration from the menu.

If you're deploying the TMS product, it takes about one hour for the physical deployment and configuration requirements. The Collector is easily done in TMS. Their inline solution, APS devices, is also easily done. It takes about a half an hour for an APS device.

We don't have a specific deployment strategy. For deployment, the minimum staff required is one security guy and one network guy.

We generally get support from Arbor engineers while we deploy.

We have gained from this product, and our customers are also satisfied with this solution. It helps with our profit. It's a good investment.

Arbor's products are very expensive. Their competitors are cheap when compared with Arbor. Now we are using Arbor, but in the future, if the price remains expensive, we might PoC the competitors. If we have the budget, we want to use Arbor, but in the future, if we have budget problems we may try other products.

I would recommend Arbor's solution. I like it.

In terms of increasing the usage of Arbor, when we expand our networks, we open new sites or data centers, we always use Arbor. In the future, if expand out, we will use it again.

I rate it a nine out of ten because I have been using it for about eight years and it's very user-friendly, troubleshooting is good, and the reporting side is also good. It's easy to deploy and our customer feedback has been good. It's just that the pricing is very expensive, so I give it a nine.

The solution is used for protection and to review any potential attack.

The solution is flexible, easy to implement and has an efficient technical support team.

The implementation should be made easier. 

I have been using the solution for more than five years.

It is a stable solution. It could be more stable depending on the upgrade of the software. I rate the stability an eight out of ten.

It is a scalable solution.For the cloud version the scalability is ten out of ten but for the on-premises, it depends on the sizing of the file. The solution is best for medium sized enterprises. All our clients are medium -sized enterprises.

The technical support is good.

The initial setup is easy. It takes two days to be deployed. One or two engineers are required for the deployment depending on the use cases.

I see a Return on Investment.

The pricing of the solution is cheap.

I rate the overall solution an eight out of ten.

We receive work orders and implement them for the client. This we do in respects of MMSP solutions. 

We do not help to integrate Arbor in other companies.

An issue which needs to be addressed concerns information I received of attacks on the radar and Arbor, allegedly, not taking any action. I wish to compare this with Fortinet DDoS, with which I am more familiar. This solution places more of an emphasis on the behavior of the traffic and provides a response in respects of the volume. But, it also learns the traffic behavior of the customer as concerns its response to other attacks.

I would like to see a feature concerning the response or one which addresses the need for behavior learning of the customer's traffic. I am sure Arbor is working on it. 

We've been using Arbor DDoS for three years.

The stability is okay and we have not encountered problems with the solution. 

As I mentioned, we only provide support in the role of technical operators, so the question about plans for increased usage should be directed towards the operator. He is in a position to say whether he has plans to sell more equipment to his customers. While the desire to desire to sell is not at issue, the willingness of people in this country to pay for the security is. 

We received from the customer, who is an operator, all of the technical knowledge needed to support NETSCOUT.

The initial setup was okay and did not take long. 

The licensing of a complete Arbor solution, including fire-walling and unified site management, can get expensive. This is a cost-benefit scenario in which the risk of losing everything must be weighed against the increased expense of the solution. This decision lies with the end customer and it depends on his protection policy. Apparently, taking protective measures is not prevalent in our culture, as people have a tendency to think that they will not be the target of an attack, even though this may be the ultimate result. 

I believe we have 10 or 15 users who are working with the solution. 

I rate Arbor DDoS as a ten out of ten. 

We use Arbor DDoS in the Asia Pacific region for a couple of government clients and Financial sector. The primary use case is for different types of problems that we do not see with other solutions, such as IPS, IDS, and FireEye. It has that type of detection and it blocks things.

It detect and protect DDOS effectively.

We can reduce the bandwidth to minimize the attack level. If we see more than 2.5 GBs we drop it directly. Many times an attack is with hundreds of GBs on our devices. We're able to filter that out.

Also, it is able to find new, different IPs. Arbor keeps them for one or two days, but it will release them after some time. That enables us to blacklist them permanently so that we don't get that IP's traffic.

It also denies fragmented packets.

If we want to see live traffic, we can see do so. But once an attack that lasts for five minutes is done, the data is no longer there.  It would be an improvement if we could see recent traffic in the dashboard. We can check and download live traffic, but a past attack, with all the details, such as why it happened and how to mitigate and prevent such future attacks, would be helpful to see.

It's a stable solution. We haven't had any issues up until now, except for one or two times. On those occasions, we found attacks were getting through but then we realized we needed to update the signature database. Since then, it has been working fine. It is blocking as it should.

There haven't been any bugs.

We haven't had any issues with the scalability.

Technical support is good. They respond swiftly.

We found what we wanted in Arbor DDoS. It met our expectations, as IT users of different types of complex environments. It fit our needs. After we did the PoC, we found that this product is good. It was scalable and stable.

The initial setup is complex.

Deployment took about four months. After getting vendor support for installation, we then configured IP ranges for different clients. Then we set up the bandwidth and enabled logins.

There has not been much to deploy and maintain since then.

Arbor directly helped with the deployment.

DDoS is a major problem. If it infiltrates one device, it can move laterally, compromising much more. Up until now, we haven't lost any confidential data. The DDoS protection solution is a valuable tool to our organization.

We did look at competitors but I don't remember which ones now.

We have two teams that work with it. There is the maintenance team and we are the team that takes action.

I would rate Arbor DDoS at eight out of ten. It's stable, it's scalable, and it can handle complex environments.