Framework overlap

Does AWS Well-Architected Security Pillar cover Texas Data Privacy Act?

You hold AWS Well-Architected Security Pillar and have been told to do Texas Data Privacy Act. Here is how much overlaps, control by control.

50% of Texas Data Privacy Act you already have

AWS Well-Architected Security Pillar already covers about 50% of Texas Data Privacy Act, leaving 3 of 6 controls as genuinely new work.

Already covered 2 Likely covered 1 New work 3

What is genuinely new work

Nothing in AWS Well-Architected Security Pillar reaches these. This is the list to scope.

TEXASTDPSA-4
Privacy Notice Content Requirements
TEXASTDPSA-5
DPIA, Universal Opt-Out, Processor Management
TEXASTDPSA-6
Consumer Appeal and Enforcement
Show the 3 you already have
TEXASTDPSA-2
Consumer Rights
TEXASTDPSA-3
Sensitive Data, Children, Sale Notice
TEXASTDPSA-1
Scope, Applicability, Exemptions

How this is calculated

Already covered means a mapping runs from a control in AWS Well-Architected Security Pillar to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition