AWS wellarchitected: Streaming Media Lens SMSEC07: remove maturity levels table
Summary
Removes the 'Maturity levels' table (levels 1-5 covering incident response procedures for content leaks and piracy) and updates the page header to drop the 'Maturity levels' column label from 'Capability intentMaturity levelsCommon issues to watch for' to 'Capability intentCommon issues to watch for'.
Security assessment
The change deletes an existing maturity-model table and rewords a header; it removes guidance rather than documenting a new control and shows no evidence of addressing a specific vulnerability, incident, or CVE.
Evidence
-Capability intentMaturity levelsCommon issues to watch for
Diff
diff --git a/wellarchitected/latest/streaming-media-lens/smsec07.md b/wellarchitected/latest/streaming-media-lens/smsec07.md index ae8327f..f11e39a 100644 --- a//wellarchitected/latest/streaming-media-lens/smsec07.md +++ b//wellarchitected/latest/streaming-media-lens/smsec07.md @@ -7 +7 @@ -Capability intentMaturity levelsCommon issues to watch for +Capability intentCommon issues to watch for @@ -28,10 +27,0 @@ SMSEC07: Have your incident responders reviewed processes on how to respond to i -## Maturity levels - -Level | Name | What it looks like ----|---|--- -1 | Initial | No documented incident response procedures exist. Response is improvised when incidents occur. -2 | Emerging | Basic procedures are documented but untested. Escalation paths exist for standard security events but not streaming-specific scenarios. -3 | Defined | Incident response plans cover both standard security events and streaming-specific incidents (content leaks, piracy). Communication protocols include content licensors. -4 | Proactive | Regular drills and tabletop exercises validate procedures. Escalation from piracy detection to legal action is well-exercised and measured. -5 | Optimized | Post-incident reviews feed back into procedure improvements. Response times are tracked, and lessons learned are incorporated across the organization. -