AWS wellarchitected: ADVSEC03: Reframe availability guidance as volumetric attack protection
Summary
Rewrites the ADVSEC03 security question from generic 'protect availability of your programmatic advertisement platform' to 'protect advertising infrastructure from volumetric attacks and malicious request behavior'. Adds a 'Capability intent' section (endpoint availability during attacks, partner-identity/behavior-aware traffic decisions, scoped and expiring planned-event exceptions, request-layer threat detection at every ingress path, retained event context) and a 'Common issues to watch for' section (single global rate limits, non-expiring limit increases, unprotected alternate/internal ingress paths, treating successful parsing as authorization, misassigning post-delivery creative changes to edge controls). Renames best practice ADVSEC03-BP01 to 'Protect advertising endpoints against volumetric and application-layer attacks' and updates the related-links list.
Security assessment
The change is editorial/structural security guidance rather than a fix for a specific vulnerability: it documents DDoS/application-layer attack protection, rate-limit scoping, ingress-path coverage, and request-layer injection awareness for advertising endpoints. No CVE, incident, or concrete flaw is referenced, so it is security documentation (hardening guidance) at medium severity.
Evidence
+ADVSEC03: How do you protect advertising infrastructure from volumetric attacks and malicious request behavior?
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advsec03.md b/wellarchitected/latest/video-streaming-advertising-lens/advsec03.md index 8b8d503..9f90984 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advsec03.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advsec03.md @@ -6,0 +7,2 @@ +Capability intentCommon issues to watch for + @@ -9 +11,5 @@ -ADVSEC03: How do you protect availability of your programmatic advertisement platform? +Advertising endpoints receive variable traffic from partners, viewers, devices, and operator interfaces. Infrastructure protection distinguishes expected demand from volumetric abuse and malicious requests without interrupting legitimate auctions or playback sessions. + +This capability covers network, edge, and request-layer controls. Creative substitution after delivery and changes inside an approved asset belong to content-integrity controls. + +ADVSEC03: How do you protect advertising infrastructure from volumetric attacks and malicious request behavior? @@ -10,0 +17,22 @@ ADVSEC03: How do you protect availability of your programmatic advertisement pla +[ADVSEC03-BP01 Protect advertising endpoints against volumetric and application-layer attacks](./advsec03-bp01.html) + +## Capability intent + + * Critical endpoints remain available during attacks, partner anomalies, and planned traffic peaks. + + * Traffic decisions account for partner identity, request behavior, business exposure, and confidence in the available baseline. + + * Teams define the scope and duration of planned-event exceptions, obtain approval, and remove the exceptions after the event. + + * Teams detect request-layer threats at every approved ingress path without assigning post-delivery content changes to infrastructure controls. + + * Protection events retain enough technical and business context for timely response and later tuning. + + + + +## Common issues to watch for + + * Applying one global rate limit to every partner and endpoint, which blocks legitimate demand and hides partner-specific anomalies. + + * Increasing limits for an event without an owner or expiration, which turns a temporary exception into permanent exposure. @@ -12 +40 @@ ADVSEC03: How do you protect availability of your programmatic advertisement pla -Robust security measures protect advertisement workloads and can maintain desired uptime. + * Protecting the public entry point but leaving alternate or internal ingress paths outside equivalent request controls. @@ -14 +42 @@ Robust security measures protect advertisement workloads and can maintain desire -###### Best practices + * Treating successful request parsing as proof of authorization, which misses validly formed abuse and request-layer injection attempts. @@ -16 +44 @@ Robust security measures protect advertisement workloads and can maintain desire - * [ADVSEC03-BP01 Use distributed denial of service (DDoS) protection service to maintain platform availability](./advsec03-bp01.html) + * Assigning browser-side or post-delivery creative changes to edge controls, which leaves the actual content-integrity response path unclear. @@ -27 +55 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS +ADVSEC02-BP04 Implement confidential computing for cross-party measurement without exposing raw viewer data @@ -29 +57 @@ ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS -ADVSEC03-BP01 Use distributed denial of service (DDoS) protection service to maintain platform availability +ADVSEC03-BP01 Protect advertising endpoints against volumetric and application-layer attacks