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%
Defending Financial Services Institutions from Modern HTTPS Layer 7 DDoS Attacks Security and network teams at financial institutions can learn why encrypted HTTPS Layer 7 DDoS attacks bypass traditional defenses and how NETSCOUT Arbor Edge Defense (AED), Adaptive DDoS Protection (ADP), and the ATLAS Intelligence Feed (AIF) provide edge-based protection. The case study covers the threat, lessons learned, the solution architecture, and the results. Why are HTTPS Layer 7 attacks a problem for financial institutions? Attackers hide malicious requests inside encrypted sessions that mimic legitimate user behavior, and they force security devices, API gateways, web application firewalls (WAFs), and backend services to spend resources on TLS processing. Existing on-premises DDoS solutions proved inadequate against these attacks on API gateways and banking services, and institutions concluded they needed inline Layer 7 protection with native TLS decryption. What lessons does the case study draw? It names four lessons: • Encrypted traffic is not inherently safe • Volume is no longer the defining signal, since low-and-slow application attacks can be as damaging as floods • Defense must start at the network edge • Signatures alone are insufficient, so adaptive, behavior-based defenses are needed How do the three components work together? AED uses a stateless architecture at the network edge, with dynamic fingerprinting and selective TLS decryption, and blocks up to 10 million indicators of compromise (IoCs). ADP adds a machine learning layer that finds previously unknown patterns and low-and-slow attacks below fixed thresholds. AIF supplies global threat intelligence on malicious IPs, IoT botnets, and command-and-control infrastructure. NETSCOUT also describes its approach as glass box, exposing the signals and logic behind each mitigation. Frequently Asked Questions Is decryption always required to stop encrypted attacks? No. Non-decrypting methods work against HTTPS request floods, TLS handshake abuse, and connection exhaustion, but stealthier attacks may need selective decryption. What results did institutions report? They report stronger API gateway protection, continuous availability under attack, less strain on internal security infrastructure, and better resilience against encrypted and novel attacks. Asset Type: Case Study

About this content