AWS Security ChangesHomeSearch

AWS wellarchitected: Expand ingress control guidance for SSP bid endpoints

Service: wellarchitected · 2026-11-11 · Documentation medium

File: wellarchitected/latest/video-streaming-advertising-lens/advsec01-bp02.md · Type: network

Summary

Rewrites the ADVSEC01-BP02 best practice to add detailed ingress-protection guidance for programmatic advertising bid endpoints, including a defense-in-depth model (IP allowlisting, OpenRTB field validation, sellers.json cross-referencing), implementation steps for AWS WAF IP sets, the OpenRTB Attribute Module, staged enforcement, sellers.json validation, AWS PrivateLink, WAF Bot Control, and rate-based rules, plus updated related best practices, documents, and services links.

Security assessment

The change is purely documentation: it expands a Well-Architected security best practice with concrete hardening guidance (WAF IP sets, Bot Control, rate-based rules, PrivateLink, sellers.json validation) to block unauthorized/fraudulent bid requests. It documents security features and best practices but does not reference or remediate any specific vulnerability, CVE, or incident, so it is security documentation rather than a security-issue fix.

Evidence

+  1. **Configure AWS WAF IP sets for authorized SSP partners:** Create IP sets containing the known egress IP ranges for each approved SSP. Associate WAF web ACLs with your bid endpoint ALB or CloudFront distribution. Update IP sets dynamically as SSP infrastructure changes using AWS WAF APIs. 

Diff

diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advsec01-bp02.md b/wellarchitected/latest/video-streaming-advertising-lens/advsec01-bp02.md
index 0dbc65d..0e7fb5f 100644
--- a//wellarchitected/latest/video-streaming-advertising-lens/advsec01-bp02.md
+++ b//wellarchitected/latest/video-streaming-advertising-lens/advsec01-bp02.md
@@ -7 +7 @@
-Implementation GuidanceResources
+Implementation guidanceResources
@@ -11 +11,62 @@ Implementation GuidanceResources
-Provide a mechanism to control and manage third-party access to each part of your cloud network environment. 
+In programmatic advertising, DSPs receive bid requests from dozens to hundreds of SSP partners. Without ingress controls that validate each SSP connection, unauthorized parties can submit fraudulent bid requests, access bidding signals, or send invalid traffic. That traffic consumes compute resources without generating revenue. 
+
+**Desired outcome:**
+
+  * You have validated every inbound SSP connection against an approved partner list before bid requests reach your bidding logic. 
+
+  * You have ingress controls that operate within the allocated bid-request latency budget. 
+
+  * You have automated updates for SSP allow lists as partnerships change, without infrastructure redeployment. 
+
+
+
+
+**Common anti-patterns:**
+
+  * Accepting bid requests from any source without verifying the SSP's identity against sellers.json or an approved partner registry. 
+
+  * Relying exclusively on application-layer validation for SSP authorization, which consumes compute on invalid requests before rejection. 
+
+  * Maintaining static IP allowlists that become stale as SSP infrastructure changes and either over-permit or break partner connections. 
+
+
+
+
+**Benefits of establishing this best practice:**
+
+  * Blocks unauthorized bid requests at the network edge before they consume bidding compute resources. 
+
+  * Reduces exposure to bid request injection attacks that attempt to harvest bidding algorithms or audience signals. 
+
+  * Enables supply-path optimization by restricting inbound traffic to verified, high-quality SSP partners. 
+
+
+
+
+**Level of risk exposed if this best practice is not established:** High 
+
+## Implementation guidance
+
+Ingress protection for bid endpoints uses a defense-in-depth model with three filtering layers, and each layer catches threats the others miss. Network-edge filtering (IP allowlisting) is the fastest and cheapest to run, and also the most brittle. SSPs rotate infrastructure, use CDN-fronted endpoints, and scale across cloud regions, so static IP sets go stale within weeks without automated maintenance. Protocol-layer inspection (OpenRTB field validation) catches semantically invalid bid requests that pass IP checks, but it adds processing latency. Application-layer validation (sellers.json cross-referencing) is the most authoritative check and also the slowest, because it requires external lookups against cached declaration files. 
+
+The layers compensate for each other's failure modes. When an SSP changes IP ranges without notice, protocol-layer validation still catches unauthorized requests. When a threat actor crafts valid-looking OpenRTB payloads from an authorized IP, sellers.json validation detects the identity mismatch. No single layer provides complete protection. 
+
+Each filter reads certain OpenRTB fields and assumes they arrive in a certain form. The same field can arrive as a single value on one supply path and as an array on another. It can also arrive empty, absent, or truncated. Each variation needs a representative test, because a filter that treats an unreadable field as acceptable will admit the request. Testing against your own corpus still leaves the forms you have not seen, so stage enforcement. Annotate traffic first, then enforce on a fraction of it. This exposes field behavior across live supply paths, and an unexpected form costs observation rather than lost bids. 
+
+Tight allowlists improve security but create friction when you onboard new SSPs (days of lead time) or when existing partners scale during high-traffic events. Supply-path optimization through IAB Tech Lab transparency initiatives (sellers.json, ads.txt, and the SupplyChain object) improves both security and bid economics. Reducing authorized supply paths shrinks the attack surface and removes low-quality intermediaries. 
+
+### Implementation steps
+
+  1. **Configure AWS WAF IP sets for authorized SSP partners:** Create IP sets containing the known egress IP ranges for each approved SSP. Associate WAF web ACLs with your bid endpoint ALB or CloudFront distribution. Update IP sets dynamically as SSP infrastructure changes using AWS WAF APIs. 
+
+  2. **Configure the module and define each filter criterion:** Configure the [OpenRTB Attribute Module](https://docs.aws.amazon.com/rtb-fabric/latest/userguide/modules.html) (openRtbAttributeModule) on an active link. For each criterion, record the field path, the data type you expect, how a match is evaluated when the field is scalar and when it is an array, and the outcome you expect. Combine criteria with AND logic inside a filter, and combine filters with OR logic. Select the documented INCLUDE or EXCLUDE filter type and the noBid or headerTag action for the intended policy. 
+
+  3. **Validate criteria and promote enforcement in stages:** Build a test set covering a passing request, an unlisted value, a malformed field, a missing field, and an array field where one element is unlisted. Start with the annotating action and a holdback that limits enforcement to a small share of eligible traffic. Record the holdback stages, the promotion threshold each stage must meet, the module version and OpenRTB revision you tested, the accountable owner, the approval date, and the next review date. Promote to the next stage only when the current one meets its threshold. 
+
+  4. **Implement sellers.json validation for SSP verification:** Build a validation layer (Lambda or inline in bid processing) that cross-references the SSP's claimed identity against their published sellers.json. Cache sellers.json lookups to avoid per-request latency. Alert on SSPs whose bid requests don't match their published seller declarations. 
+
+  5. **Establish private connectivity for high-volume SSP partners:** Configure AWS PrivateLink for SSP partners operating on AWS to remove public internet transit for bid traffic. For non-AWS SSPs, use VPC security groups to restrict inbound traffic to documented SSP IP ranges. 
+
+  6. **Enable AWS WAF Bot Control:** Deploy the [AWS WAF Bot Control managed rule group](https://docs.aws.amazon.com/waf/latest/developerguide/aws-managed-rule-groups-bot.html) on bid endpoints to detect automated invalid traffic. Test labels and actions against expected SSP traffic before blocking requests. 
+
+  7. **Configure rate-based rules:** Add [AWS WAF rate-based rules](https://docs.aws.amazon.com/waf/latest/developerguide/waf-rule-statement-type-rate-based.html) for each SSP traffic boundary. Alert on unexpected increases, and throttle request floods that exceed the approved traffic profile. 
@@ -13 +73,0 @@ Provide a mechanism to control and manage third-party access to each part of you
-## Implementation Guidance
@@ -15 +74,0 @@ Provide a mechanism to control and manage third-party access to each part of you
-Consider using [AWS WAF](https://aws.amazon.com/waf/) to allow access for authorized IPs for traffic that arrives at your [Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html), [Amazon API Gateway](https://aws.amazon.com/api-gateway/), and Amazon CloudFront distributions. AWS WAF helps protect your web applications against common web exploits that may compromise security. Using AWS WAF rules, you can define a set of inspection criteria and review when incoming requests meets the set criteria. It is recommended to use AWS WAF rules to inspect incoming traffic based on several factors like source IP or originating geographic location. 
@@ -17 +75,0 @@ Consider using [AWS WAF](https://aws.amazon.com/waf/) to allow access for author
-Additionally, consider using AWS PrivateLink to restrict access to your AWS services. AWS PrivateLink allows for the private connection between your AWS VPCs and AWS services without exposing your network traffic to the public internet. If you cannot use AWS PrivateLink, consider using IAM to control access to your AWS services. 
@@ -21 +79,12 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Configure security groups for your Classic Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-vpc-security-groups.html)
+**Related best practices:**
+
+  * [ADVSEC01-BP01 Implement user authentication and access control to protect bidding process and content](./advsec01-bp01.html)
+
+  * [ADVSEC01-BP03 Restrict DSP outbound traffic to authorized SSPs only](./advsec01-bp03.html)
+
+  * [ADVSEC04-BP03 Implement supply chain transparency controls to block ad fraud](./advsec04-bp03.html)
+
+
+
+
+**Related documents:**
@@ -23 +92 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [How do I use AWS WAF to create IP set rules to restrict IPv4 and IPv6 access?](https://repost.aws/knowledge-center/waf-allow-my-ip-block-other-ip)
+  * [AWS WAF IP set rules for IPv4 and IPv6](https://repost.aws/knowledge-center/waf-allow-my-ip-block-other-ip)
@@ -25 +94 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Update the security groups for your Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-security-groups.html)
+  * [AWS PrivateLink documentation](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html)
@@ -27 +96 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Controlling access to Amazon Kinesis Data Streams resources using IAM](https://docs.aws.amazon.com/streams/latest/dev/controlling-access.html)
+  * [Network Load Balancer security groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-security-groups.html)
@@ -29 +98 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Introducing Amazon API Gateway Private Endpoints](https://aws.amazon.com/blogs/compute/introducing-amazon-api-gateway-private-endpoints/)
+  * [IAB Tech Lab sellers.json specification](https://iabtechlab.com/sellers-json/)
@@ -31 +99,0 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Use interface VPC endpoints for Amazon Kinesis Data Streams](https://docs.aws.amazon.com/streams/latest/dev/vpc.html)
@@ -33 +100,0 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Private Amazon AppFlow flows](https://docs.aws.amazon.com/appflow/latest/userguide/private-flows.html)
@@ -35 +101,0 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Create a server in a virtual private cloud](https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html)
@@ -37 +103 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Configuring VPC endpoints as AWS Database Migration Service source and target endpoints](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_VPC_Endpoints.html)
+**Related services:**
@@ -39 +105 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Creating an interface VPC endpoint for AWS Data Exchange](https://docs.aws.amazon.com/data-exchange/latest/userguide/vpc-interface-endpoints.html)
+  * [AWS WAF](https://aws.amazon.com/waf/)
@@ -41 +107 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [AWS PrivateLink for Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html)
+  * [AWS RTB Fabric](https://aws.amazon.com/rtb-fabric/)
@@ -43 +109 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Considerations for AWS Glue VPC endpoints](https://docs.aws.amazon.com/glue/latest/dg/vpc-interface-endpoints.html)
+  * [AWS PrivateLink](https://aws.amazon.com/privatelink/)
@@ -45 +111 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Amazon MSK multi-VPC private connectivity in a single Region](https://docs.aws.amazon.com/msk/latest/developerguide/aws-access-mult-vpc.html)
+  * [Amazon CloudFront](https://aws.amazon.com/cloudfront/)
@@ -47 +113 @@ Additionally, consider using AWS PrivateLink to restrict access to your AWS serv
-  * [Changing an Amazon MSK cluster's security group](https://docs.aws.amazon.com/msk/latest/developerguide/change-security-group.html)
+  * [Amazon API Gateway](https://aws.amazon.com/api-gateway/)