AWS wellarchitected: Rewrites ADVSEC05 from fraud detection to privacy and regulatory adherence
Summary
Replaces the ADVSEC05 fraud-detection guidance (AWS WAF, Amazon GuardDuty, Amazon Fraud Detector references and ADVSEC05-BP01 content sanitization) with a privacy-and-regulatory-adherence capability: new question on governing regulatory obligations and privacy-preserving advertising, three new best-practice links (data protection obligations, linear/digital compliance, privacy-preserving advertising), capability-intent bullets on consent/purpose/retention metadata traceability, and new common-issues guidance on legacy tracking paths, metadata loss, and source-rule mixing.
Security assessment
The rewritten section documents privacy/regulatory governance controls — translating obligations into control objectives, preserving consent/purpose/retention metadata through derived data, restricting cross-channel processing to authorized purposes, and isolating legacy tracking paths. This is security-and-privacy best-practice documentation with no reference to a specific vulnerability, CVE, or incident, so it is not incident-driven, but it does add security documentation.
Evidence
+ * Purpose, consent, jurisdiction, retention, and rights-management metadata remain traceable through source and derived data.
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advsec05.md b/wellarchitected/latest/video-streaming-advertising-lens/advsec05.md index 179dea5..d3d66ab 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advsec05.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advsec05.md @@ -7 +7 @@ -Key AWS servicesResources +Capability intentCommon issues to watch for @@ -9 +9 @@ Key AWS servicesResources -# Fraud detection +# Privacy and regulatory adherence @@ -11,6 +11 @@ Key AWS servicesResources -ADVSEC05: How do you detect and block fraud in your advertisement solution? ---- - -Traffic fraud in digital advertising could impact the advertising solution by affecting ad spend through fake clicks, bot traffic, and manipulation schemes. Workloads benefit from resilient and secure systems that implement defense in depth strategies for fraud prevention. Effective protection assists advertisers optimize budgets by focusing on genuine traffic and properly represented inventory, while publishers can maintain reputation and revenue by addressing fraudulent activities on their solution. - -Consider using AWS WAF to evaluate traffic to your advertising solution and filter out suspicious or un-wanted bot traffic through customizable rules. Amazon GuardDuty can also be utilized to help protect your AWS accounts, workloads, and data from threats. +Advertising data can be subject to different requirements based on jurisdiction, collection context, consent, processing purpose, and business agreement. Privacy and regulatory adherence helps you transition requirements into approved decisions that remain attached to data as it moves and changes. @@ -18 +13 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt -###### Best practices +This capability also governs the transition away from tracking methods that expose people across contexts. It defines obligations, evidence, permitted use, migration boundaries, and retirement decisions rather than duplicating data-protection or identity mechanisms. @@ -20,3 +15,5 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * [ADVSEC05-BP01 Validate and sanitize content before running a campaign](./advsec05-bp01.html) - - * Key AWS services +ADVSEC05: How do you govern regulatory obligations and privacy-preserving advertising across data types, jurisdictions, and channels? +--- +[ADVSEC05-BP01 Verify that your advertising workload meets applicable data protection obligations](./advsec05-bp01.html) +[ADVSEC05-BP02 Design for compliance across both linear and digital data flows](./advsec05-bp02.html) +[ADVSEC05-BP03 Enable privacy-preserving advertising capabilities while protecting user data](./advsec05-bp03.html) @@ -24 +21 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * Resources +## Capability intent @@ -25,0 +23 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt + * Regulatory and contractual obligations are translated into approved control objectives with accountable business, privacy, and engineering owners. @@ -26,0 +25 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt + * Purpose, consent, jurisdiction, retention, and rights-management metadata remain traceable through source and derived data. @@ -27,0 +27 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt + * Cross-channel processing proceeds only when every contributing source authorizes the intended purpose. @@ -29 +29 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt -## Key AWS services + * Privacy-preserving capabilities meet accepted utility and exposure criteria without reconnecting results to prohibited legacy identifiers. @@ -31 +31 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * AWS WAF + * Evidence, exceptions, migrations, and decommissioning decisions remain reviewable throughout their lifecycles. @@ -33 +32,0 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * Amazon GuardDuty @@ -35 +33,0 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * Amazon Fraud Detector @@ -37,0 +36 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt +## Common issues to watch for @@ -38,0 +38 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt + * Treating a technical setting as compliance proof without linking it to an approved obligation, affected data, and evidence period. @@ -40 +40 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt -## Resources + * Losing purpose, consent, retention, or deletion metadata in derived datasets, which breaks later use and rights decisions. @@ -42 +42 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * [Amazon GuardDuty](https://aws.amazon.com/guardduty/) + * Combining linear, digital, household, or user-level data under the least restrictive source rule, which permits uses that one source did not authorize. @@ -44 +44 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * [AWS WAF rules](https://docs.aws.amazon.com/waf/latest/developerguide/waf-rules.html) + * Running legacy and replacement tracking paths without isolation, which lets aggregate or identity-limited results flow back into user-level profiles. @@ -46 +46 @@ Consider using AWS WAF to evaluate traffic to your advertising solution and filt - * [Amazon Fraud Detector FAQs](https://aws.amazon.com/fraud-detector/faqs/#topic-0) + * Starting privacy alternatives without effectiveness criteria or a retirement plan, which preserves duplicate data stores and exposed interfaces indefinitely. @@ -57 +57 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -ADVSEC04-BP01 Implement secure data collaboration with least privileged access and privacy controls +ADVSEC04-BP04 Secure ad creative delivery and content integrity across converged channels @@ -59 +59 @@ ADVSEC04-BP01 Implement secure data collaboration with least privileged access a -ADVSEC05-BP01 Validate and sanitize content before running a campaign +ADVSEC05-BP01 Verify that your advertising workload meets applicable data protection obligations