AWS security-ir medium security documentation change
Summary
Fixed CLI examples by replacing invalid 'email' enum value with valid notification types ('Case Created', 'Case Closed') and corrected JSON syntax in communicationPreferences arrays.
Security assessment
The correction of invalid enum values prevents potential misconfiguration of incident notifications. Incorrect configuration could lead to missed security alerts, delaying incident response. The specific replacement of security notification types constitutes concrete evidence of addressing a security weakness.
Diff
diff --git a/security-ir/latest/userguide/enable-sir-using-cli.md b/security-ir/latest/userguide/enable-sir-using-cli.md index ca267eea8..0f664628d 100644 --- a//security-ir/latest/userguide/enable-sir-using-cli.md +++ b//security-ir/latest/userguide/enable-sir-using-cli.md @@ -44,2 +44,2 @@ Onboard with a delegated administrator using the API/CLI (recommended) - "communicationPreferences": ["email"] - } + "communicationPreferences": ["Case Created", "Case Closed"] + }, @@ -50 +50 @@ Onboard with a delegated administrator using the API/CLI (recommended) - "communicationPreferences": ["email"] + "communicationPreferences": ["Case Created", "Case Closed"] @@ -83,2 +83,2 @@ Onboard with a management account using the API/CLI - "communicationPreferences": ["email"] - } + "communicationPreferences": ["Case Created", "Case Closed"] + }, @@ -89 +89 @@ Onboard with a management account using the API/CLI - "communicationPreferences": ["email"] + "communicationPreferences": ["Case Created", "Case Closed"]