AWS Security ChangesHomeSearch

AWS wellarchitected: Expand ADVSEC02 data protection guidance across lifecycle

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

File: wellarchitected/latest/video-streaming-advertising-lens/advsec02.md · Type: encryption

Summary

Rewrites the ADVSEC02 question from transit-only to protecting advertising data across transit, storage, collaboration, and computation; adds four best-practice links (TLS encryption, secure linear/ad signaling, least-privilege data collaboration, confidential computing), a 'Capability intent' section, and a 'Common issues to watch for' list covering key/certificate reuse, raw-record sharing, and unapproved policy changes. Also fixes a cross-reference from ADVSEC01-BP04 to ADVSEC01-BP05 on identity governance.

Security assessment

The change is security-pillar guidance, not a fix for a specific vulnerability: it adds best practices for TLS in transit, least-privilege cross-party collaboration, confidential computing, and scoped keys/certificates, plus warnings that reusing broad keys or sharing raw records turns one compromise into shared exposure. No CVE, incident, or concrete flaw is referenced.

Evidence

+[ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS](./advsec02-bp01.html)  

Diff

diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advsec02.md b/wellarchitected/latest/video-streaming-advertising-lens/advsec02.md
index cdb1f7f..ce0ccff 100644
--- a//wellarchitected/latest/video-streaming-advertising-lens/advsec02.md
+++ b//wellarchitected/latest/video-streaming-advertising-lens/advsec02.md
@@ -6,0 +7,2 @@
+Capability intentCommon issues to watch for
+
@@ -9 +11,5 @@
-ADVSEC02: How do you protect data in transit?  
+Advertising data moves through auctions, media workflows, shared analysis environments, and measurement systems operated by separate organizations. Data protection keeps that information confidential and unaltered while preserving the latency, availability, and collaboration properties that advertising workloads require. 
+
+This capability covers protection in transit, at rest, during collaboration, and during record-level computation. It doesn't define identity governance or decide which regulatory obligations apply. 
+
+ADVSEC02: How do you protect advertising data throughout transit, storage, collaboration, and computation?   
@@ -10,0 +17,25 @@ ADVSEC02: How do you protect data in transit?
+[ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS](./advsec02-bp01.html)  
+[ADVSEC02-BP02 Protect linear distribution feeds and ad signaling in converged delivery](./advsec02-bp02.html)  
+[ADVSEC02-BP03 Implement secure data collaboration with least privileged access and privacy controls](./advsec02-bp03.html)  
+[ADVSEC02-BP04 Implement confidential computing for cross-party measurement without exposing raw viewer data](./advsec02-bp04.html)  
+  
+## Capability intent
+
+  * Data sensitivity, processing purpose, and trust boundaries determine protection requirements throughout the data lifecycle. 
+
+  * Protection remains effective as data crosses partner, network, media, storage, and computation boundaries. 
+
+  * Cryptographic identities, keys, certificates, and release authority have limited scope, named owners, and controlled lifecycles. 
+
+  * Cross-party analysis reveals only approved information and produces evidence that every contributor can evaluate. 
+
+  * Control owners detect, review, and resolve control changes, exceptions, and failures without bypassing partner or data-owner decisions. 
+
+
+
+
+## Common issues to watch for
+
+  * Protecting primary data stores but leaving copies in logs, exports, media paths, or temporary computation outside the same control boundary. 
+
+  * Selecting encryption or collaboration technology before defining what each party can learn, which produces controls that don't match the trust model. 
@@ -12 +43 @@ ADVSEC02: How do you protect data in transit?
-Protecting data in transit for advertising workloads is crucial as it involves the constant movement of potentially sensitive information including customer data, campaign metrics, and financial metrics across various portions of the network. 
+  * Reusing broad keys, certificates, or administrative authority across partners, which turns one compromise or rotation failure into a shared outage or exposure. 
@@ -14 +45 @@ Protecting data in transit for advertising workloads is crucial as it involves t
-###### Best practices
+  * Teams trust the collaboration environment, then share raw records or permit unrestricted analysis. This removes purpose and disclosure limits. 
@@ -16 +47 @@ Protecting data in transit for advertising workloads is crucial as it involves t
-  * [ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS](./advsec02-bp01.html)
+  * Updating protected workloads or release policies without contributor approval, which breaks attestation and weakens the basis for partner trust. 
@@ -27 +58 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-ADVSEC01-BP04 Implement authorization by setting access policies, and implement least privilege access to protect programmatic workloads
+ADVSEC01-BP05 Implement cross-platform identity governance for converged linear and digital operations