AWS wellarchitected: Rewrite ADVSEC04 from data protection to content integrity and ad fraud
Summary
Replaces the ADVSEC04 best-practice page topic from DMP raw-data protection (S3 bucket policies, SSE-KMS) with a new focus on content integrity, brand safety, supply-chain fraud, and delivery manipulation, including new capability-intent statements, common issues, and four renumbered best practices (ADVSEC04-BP01..BP04).
Security assessment
The diff is an editorial restructuring of a Well-Architected security lens page: it drops the S3/SSE-KMS data-protection prose and swaps in guidance on validating ad creatives, brand safety guardrails, supply-chain transparency, and detecting creative substitution/fabricated sessions. It is security guidance (defensive best practices) but does not reference a specific vulnerability, CVE, incident, or permission/encryption fix, so it is documentation-level rather than a remediation.
Evidence
+ADVSEC04: How do you preserve content integrity and guard against unsafe placement, supply-chain fraud, and delivery manipulation?
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advsec04.md b/wellarchitected/latest/video-streaming-advertising-lens/advsec04.md index b3b62fd..b9778b3 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advsec04.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advsec04.md @@ -7 +7 @@ -Key AWS servicesResources +Capability intentCommon issues to watch for @@ -9 +9 @@ Key AWS servicesResources -# Data protection +# Content integrity, brand safety, and ad fraud prevention @@ -11,4 +11 @@ Key AWS servicesResources -ADVSEC04: How do you store and protect raw data in your DMP system? ---- - -A DMP solution often collects multiple forms of data from customers, advertising solutions, DSPs, and SSPs to transform raw data and provide insights to different portions of a cloud-based advertising workload. Protecting DMPs usually requires robust security measures for the different parts of the pipeline that ingest and transform data. Consider using Amazon S3 as a centralized data store. Amazon S3 is an object storage service that can securely store data for a range of use cases. For data protection, strict S3 bucket policies should be implemented that enforce encryption of data at rest and define strict access controls. +Advertising decisions depend on claims about the creative, content environment, seller, supply path, and viewer session. This capability establishes evidence for those claims and keeps an approved decision valid from campaign activation through delivery. @@ -16 +13 @@ A DMP solution often collects multiple forms of data from customers, advertising -An enhanced layer of protection would be to enforce the use of service-side encryption (SSE) with an AWS KMS-managed key (SSE-KMS) which can assist in protecting the data but also meet potential compliance requirements. SSE-KMS allows you to maintain the ownership of the keys with the ability to revoke access depending on the job requirements to the data. By implementing SSE-KMS you have a defense in depth strategy as the consumer of the data needs access to the data on S3 and permission to use the KMS key to decrypt it. A combination of these features verify data is protected at rest. +The scope includes malvertising, brand suitability, supply-chain misrepresentation, creative substitution, and fabricated delivery sessions. It doesn't cover volumetric protection at the infrastructure boundary or the privacy terms governing audience data. @@ -18 +15,6 @@ An enhanced layer of protection would be to enforce the use of service-side encr -###### Best practices +ADVSEC04: How do you preserve content integrity and guard against unsafe placement, supply-chain fraud, and delivery manipulation? +--- +[ADVSEC04-BP01 Validate and sanitize ad creative content before campaign activation](./advsec04-bp01.html) +[ADVSEC04-BP02 Create guardrails and controls to maintain brand safety and content moderation within your workload](./advsec04-bp02.html) +[ADVSEC04-BP03 Implement supply chain transparency controls to block ad fraud](./advsec04-bp03.html) +[ADVSEC04-BP04 Secure ad creative delivery and content integrity across converged channels](./advsec04-bp04.html) @@ -20 +22 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * [ADVSEC04-BP01 Implement secure data collaboration with least privileged access and privacy controls](./advsec04-bp01.html) +## Capability intent @@ -22 +24 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * Key AWS services + * Evidence from an accountable authority supports creative, content, seller, supply-path, and session claims. @@ -24 +26 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * Resources + * Release, placement, and delivery decisions remain valid when dependencies, relationships, content, or threat indicators change. @@ -25,0 +28 @@ An enhanced layer of protection would be to enforce the use of service-side encr + * Blocking, quarantine, review, revocation, and fraud responses reflect defined risk states rather than informal operator judgment. @@ -26,0 +30 @@ An enhanced layer of protection would be to enforce the use of service-side encr + * Workload controls enforce advertiser and publisher policies consistently across auction, stitching, and delivery boundaries. @@ -27,0 +32 @@ An enhanced layer of protection would be to enforce the use of service-side encr + * Investigation records connect the affected asset or session to the evidence, decision, owner, and exposure window. @@ -29 +33,0 @@ An enhanced layer of protection would be to enforce the use of service-side encr -## Key AWS services @@ -31 +34,0 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * [AWS S3](https://aws.amazon.com/pm/serv-s3/) @@ -33 +35,0 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * [AWS KMS](https://aws.amazon.com/kms/) @@ -34,0 +37 @@ An enhanced layer of protection would be to enforce the use of service-side encr +## Common issues to watch for @@ -35,0 +39 @@ An enhanced layer of protection would be to enforce the use of service-side encr + * Approving only the submitted creative file although remote scripts, wrappers, media, or destinations can change its behavior after release. @@ -36,0 +41 @@ An enhanced layer of protection would be to enforce the use of service-side encr + * Classifying content only at campaign setup, which misses content drift and advertiser-specific suitability decisions during delivery. @@ -38 +43 @@ An enhanced layer of protection would be to enforce the use of service-side encr -## Resources + * Treating public seller declarations as the commercial authority, which can preserve stale or unauthorized supply relationships. @@ -40 +45 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * [Using server-side encryption with AWS KMS keys (SSE-KMS)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html) + * Validating only the first or last supply-path participant, which leaves intermediary misrepresentation undetected. @@ -42 +47 @@ An enhanced layer of protection would be to enforce the use of service-side encr - * [Bucket policies for Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-policies.html) + * Trusting an approved asset URL or authenticated session without verifying delivered bytes and behavior, which permits substitution and fabricated activity. @@ -53 +58 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -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 @@ -55 +60 @@ ADVSEC03-BP01 Use distributed denial of service (DDoS) protection service to mai -ADVSEC04-BP01 Implement secure data collaboration with least privileged access and privacy controls +ADVSEC04-BP01 Validate and sanitize ad creative content before campaign activation