We are a bank with Internet banking and corporate banking portals, which exposes multiple applications externally. These exposed applications come under the Azure DDoS Protection plan, integrated with our Firewall. Any resources related to publicly exposed applications, such as private endpoints and channel applications, also fall under the Azure DDoS Protection plan.
We usually enable DDoS Protection for any client. It's an additional layer of protection. We enable DDoS protection in addition to the default protection we get. But, it depends on the architectural requirements. Some applications may not require DDoS protection based on their application standards or requirements. But I strongly suggest enabling DDoS protection for any client applications that are exposed to the internet, not just the intranet.
I use Azure DDoS Protection to safeguard my applications and prevent distributed denial-of-service attacks. Additionally, I ensure that all firewalls provide comprehensive protection against application-layer threats. To ensure the security of my web applications and proper implementation of all DDoS protection measures, I implemented Azure DDoS Protection. As a result, my RDP access and data are now securely protected.
Head of Cloud Engineering at a financial services firm with 10,001+ employees
Real User
Feb 12, 2023
We use DDoS Protection to protect public IPs exposed through Azure. Everything in our product with a public IP is protected. It still provides protection once our product is onboarded on the subscription. The solution gives us alerts when something is triggered or if it detects anything strange. DDoS Protection is integrated with Azure Defender, so it's already monitored by our security team.
Analyst - Security Officer at a non-tech company with 201-500 employees
Real User
Aug 24, 2021
We are building our infrastructure to be secure. We have a solution that is exposed to all users and without a VPN. That is why we had to do some work to protect it against any DDoS attacks.
Azure DDoS Protection, combined with application design best practices, provides defense against DDoS attacks.
To learn more about our solution, ask questions, and share feedback, join our Microsoft Security, Compliance and Identity Community.
We are a bank with Internet banking and corporate banking portals, which exposes multiple applications externally. These exposed applications come under the Azure DDoS Protection plan, integrated with our Firewall. Any resources related to publicly exposed applications, such as private endpoints and channel applications, also fall under the Azure DDoS Protection plan.
We use this solution as a partner for all customer problems and various customer applications. We are utilizing it for business applications.
We usually enable DDoS Protection for any client. It's an additional layer of protection. We enable DDoS protection in addition to the default protection we get. But, it depends on the architectural requirements. Some applications may not require DDoS protection based on their application standards or requirements. But I strongly suggest enabling DDoS protection for any client applications that are exposed to the internet, not just the intranet.
I use Azure DDoS Protection to safeguard my applications and prevent distributed denial-of-service attacks. Additionally, I ensure that all firewalls provide comprehensive protection against application-layer threats. To ensure the security of my web applications and proper implementation of all DDoS protection measures, I implemented Azure DDoS Protection. As a result, my RDP access and data are now securely protected.
We use DDoS Protection to protect public IPs exposed through Azure. Everything in our product with a public IP is protected. It still provides protection once our product is onboarded on the subscription. The solution gives us alerts when something is triggered or if it detects anything strange. DDoS Protection is integrated with Azure Defender, so it's already monitored by our security team.
I am using Azure DDoS Protection to protect my public endpoints in Azure.
We are building our infrastructure to be secure. We have a solution that is exposed to all users and without a VPN. That is why we had to do some work to protect it against any DDoS attacks.