Current View
File name:

-

File size:

-

Title:

-

Author:

-

Subject:

-

Keywords:

-

Creation Date:

-

Modification Date:

-

Creator:

-

PDF Producer:

-

PDF Version:

-

Page Count:

-

Page Size:

-

Fast Web View:

-

Preparing document for printing…
0%
Using Arbor Cloud to Protect Multi-Cloud and Hybrid Environments Against DDoS Attacks Security teams running hybrid or multi-cloud environments can learn why cloud-hosted assets remain exposed to distributed denial-of-service (DDoS) attacks and how Arbor Cloud protects them. The use case explains the limits of cloud provider and content delivery network (CDN) protections and describes on-demand and always-on Arbor Cloud deployment modes. Why are cloud-hosted assets still at risk from DDoS attacks? Hosting an asset in the cloud does not make it less susceptible to DDoS attacks, and downtime can be costly and damage reputation. Modern attacks are dynamic, multi-vector, and span layers 3 to 7, so blocking high-volume layer 3 attacks is not sufficient. Cloud providers and commercial CDNs often offer DDoS protection, but these services tend to address volumetric layer 3 attacks, can be less effective in multi-cloud environments, and may lack a dedicated security operations center (SOC) team. How does Arbor Cloud protect hybrid and multi-cloud environments? Arbor Cloud provides one consistent service that detects, intercepts, and mitigates DDoS attack traffic and returns only clean traffic to its destination, whether traffic arrives directly from the internet or through a CDN. The service is built on Arbor Sightline and the Arbor Threat Mitigation System (TMS), and its advantages include: • The ASERT Intelligence Feed (AIF) for global intelligence on DDoS attack activity and sources • Globally distributed scrubbing centers that mitigate attacks close to the source • A 24-hour Arbor Cloud SOC staffed with DDoS experts who manage mitigation events • Customized mitigation templates with SOC support What are the on-demand and always-on modes? In on-demand mode, DNS or Border Gateway Protocol (BGP) routing redirects affected traffic to Arbor Cloud during an attack. In always-on mode, traffic for critical assets routes through Arbor Cloud via DNS or BGP at all times, and the service detects an attack within seconds and redirects traffic for the attacked hosts to TMS platforms in its scrubbing centers. Frequently Asked Questions Can an enterprise use its own IP address space with public cloud providers? Yes. Bringing its own IP address space to providers such as AWS and Azure lets an enterprise use standard BGP routing to redirect traffic to Arbor Cloud globally. Does moving to the cloud remove the need for DDoS protection? No. The use case states the cloud does not inherently protect against modern DDoS attacks. Asset Type: Use Case

About this content